Imagine you're managing a website redesign. A week before launch, the client asks whether you can add a blog.
It wasn't in the agreement. It isn't in the schedule. There is, regrettably, no spare development team in the cupboard.
Before you say yes, no, or a third thing you'll regret in writing, find out what changed.
“What do you need the blog to do for launch? Is there something you need to publish that day, or do you need a place to start publishing afterward?”
Those answers could lead to very different plans. Maybe a single page solves the immediate need. Maybe another feature can wait. Maybe the blog really does require moving the launch. You still need to check what the team can deliver before offering it.
That's what I mean by presence of mind: understanding enough about the situation to ask a useful next question, and updating your approach when the answer changes things.
You don't have to know how to build the blog yourself. You do need to know that promising one changes somebody else's Tuesday.
What to notice before you answer
Start with the goal behind the request. In our imaginary redesign, “add a blog” might mean “we need somewhere to publish our launch announcement.” Or it might mean a publishing system that several people can use every week. Those are different amounts of work. Ask before estimating either one.
Then look at the constraints. What did both teams agree to? What is already scheduled? Who can tell you what a change would take? The signed agreement matters, but waving it at the client won't tell you whether there's a workable alternative.
A useful answer accounts for the people who have to carry it out. If you offer to swap out another feature, find out who was counting on that feature. Otherwise you've resolved one conversation by creating a surprise in someone else's.
Keep track of what you know and what you're assuming. You can say:
“I understand why you want somewhere to publish at launch. Let me check what a single page would take and what we'd need to move to include a full blog. I'll come back tomorrow with the options.”
That answer buys time for a reason. It also creates a commitment you need to keep. A thoughtful response followed by silence is still silence.
And yes, sometimes the answer is simply that you can't do it within the deadline. Presence of mind doesn't mean finding a clever way to accommodate every request. It means understanding enough to explain the choice and its consequences. Including the inconvenient ones.
How to practice this without waiting for a crisis
Take a recent decision to a mentor or a colleague whose judgment you trust. Pick something small enough to discuss in a few minutes. You don't need a departmental catastrophe for educational purposes.
Walk them through your thinking:
“Here's what I thought mattered, what I assumed, and what I chose. What would you have asked before deciding?”
The interesting part is where their attention goes. Maybe they ask who owns the deadline. Maybe they notice that you accepted the client's explanation without checking with the team. Or maybe they agree with your decision but would communicate it differently.
You aren't collecting the one correct answer for future blog emergencies. You're learning what another person notices, then trying that perspective on the next situation.
Come back afterward, too. What actually happened? Which assumption held up? Which one would you check sooner next time? Changing your mind in response to new information is part of the skill. Stubbornly defending last Tuesday's guess does not make it a principle.
If you're hiring, ask candidates to explain a decision with that same context: what they knew, what they asked, and what changed. I've written about showing that thinking when applying for jobs, including a warehouse example where the reasoning matters as much as the result.
This week, choose one decision and compare notes with someone. You may know more than you think. You may also discover that the question you didn't ask would have saved everybody a Friday afternoon.
Let's make work suck less,
Peter