4 ms·
> Before you say yes, pause The way I do this is respond with "Can I get back to you on that?" And perhaps append with "I need to check my schedule" or "check
by theonething 6y ago
> Before you say yes, pause
The way I do this is respond with "Can I get back to you on that?" And perhaps append with "I need to check my schedule" or "check with my spouse, etc"
And then make sure I do get back to them with an answer.
When I make a snap response to a request, I often regret it because I haven't had time to think about the request and how to relates to my schedule, plans, interests, desire to help, pros, cons etc.
By asking for more time to decide, I get the chance to think about it and that increases the chance that I'll make a decision that I'm happy with.
Of course there are situations that call for an immediate response or that you know whether you want to say yes or no immediately, but for all others, the above works for me.
- Cthulhu_ 6y agoAt work, most requests come in through e-mail, IMs or tickets/tasks, which is great because it means I can let them simmer for a bit. But then there's some colleagues who send me a DM with a "hi are you there / can I call you" because they have something that they want out of their system Right Now (with e-mail and co, you send, then the something remains in the background until replied; with a call it's a one off thing and they can move on). And my first job had some of the worst; they'd send an e-mail, then a few minutes later give me a call "did you get my e-mail?" and repeat what was in there on the call. I mean come on. At least I can laugh about it now, and I didn't mind so much when I did it because it was a very er, dynamic job anyway.