A conditional yes is a yes with its price attached: what you will do, and what has to be true for you to do it. It is the most useful sentence shape at work, and almost nobody gets taught it.
Nothing here is an argument against saying no. A clean no beats a reluctant yes, and if the answer is never, say never.
This is about the other case. The request you genuinely wanted to accept, where the yes left your keyboard naked, carrying no conditions, and three weeks later you were the person who missed.
When no is not the answer you wanted to give
A plain no ends the conversation, which is the wrong outcome when you would have helped gladly under slightly different terms.
The person asking rarely knows your queue. They asked because they had a problem, not because they wanted to load you up. When you decline flatly, they learn nothing about what would have worked, so next time they either do not ask or they ask someone worse suited.
You also lose the negotiation you never opened. Plenty of requests I have turned down would have been fine two weeks later, and nobody found that out, because "I can't take this on" contains no information about timing.
So you have a third option sitting between the bare yes and the bare no, and it is a yes that says what it costs.
The fake yes is worse than both
An unconditional yes to a request you cannot absorb is a delayed no with interest.
The other person schedules around your agreement. They stop looking for alternatives. They tell someone else it is handled. Then you deliver late, or thin, and the cost lands on them at the point where they have no options left.
That is the real harm. You let them down at the last possible moment, when it cost the most.
What a conditional yes actually contains
A conditional yes has three parts in a fixed order: the commitment, the condition, and the consequence of the condition not being met.
The commitment is what you will genuinely do. Make it smaller than the request if the request is too big. "I can review the data section" is a real commitment. "I can help with the report" is not.
The condition is what has to be true. Time, access, a decision from someone else, a thing off your plate. This is the part people leave out because it feels like haggling.
The consequence is what happens if the condition is not met. Not a threat. A fact. "If the spec is not final by Wednesday, this lands the following week instead."
Put together it reads like this: "Yes, I can do the migration plan. I need schema access by Tuesday. Without that I start Thursday, which pushes delivery to the 20th."
Nothing in that sentence is aggressive. It is a yes that will survive contact with reality.
Five conditions people leave silent
The conditions that go unsaid are surprisingly repetitive, and naming any of them out loud takes one clause.
- Say which week you will start, rather than only that you will start.
- Say which part of the request you are taking and which part you are leaving.
- Say what you need from someone else before you can begin.
- Say what will slow down because this is now in your queue.
- Say whether they are getting a rough pass or a finished one at this speed.
That last one is swallowed most often. If somebody asks for something in two days that deserves a week, the honest answer is neither yes nor no. It is "yes, at two-day quality, and here is what that looks like".
Make the condition something both of you can check on Friday
A condition only counts if the other person can tell, without asking you, whether it was met.
"If things calm down" fails that test. "If I get the API keys" passes it. "As long as nothing urgent comes up" hands you an excuse and hands them nothing, because urgent things always come up.
The consequence needs the same treatment. "It might slip" is noise. "It lands the 20th instead of the 13th" is a date somebody can plan around.
Sounding cooperative instead of lawyerly
A conditional yes fails on tone far more often than on content, and the repair is to lead with the yes and phrase the condition as a request.
A conditional yes written defensively reads like an alibi under construction. It gets long. It piles on caveats. It reaches for "provided that" and "subject to", and by the end the reader is not sure whether you agreed to anything at all.
The wording that keeps it warm is a request, not a disclaimer. "I need the schema access by Tuesday" lands as a colleague asking for something. "I cannot be held to this unless I have schema access" lands as somebody drafting a defense in advance.
Compare the two versions. "Happy to take the deck. Send me the Q3 numbers by Monday and you will have it Thursday." Against: "I can potentially assist with the deck, provided that all necessary inputs are received in a timely manner." Same conditions. One of them sounds like a colleague.
When someone gives you a conditional yes
Treat the condition as the actual message. That is where the information is.
If a teammate says they can do it once the audit is finished, "great, thanks" leaves you with a hope rather than an agreement. Say the condition back: "the audit ends Friday, so I will expect it the week after", or "the audit is not ending soon, so let us find another way".
People who condition their yes are doing you a favor. They are showing you the shape of their week. The alternative is a cheerful yes from someone who has already agreed to four other things and told none of you about any of them.
Three replies do most of the work when a condition lands on you.
- Confirm it, by naming the date the condition will be met.
- Kill it, by saying the condition will not happen so you will find another route.
- Trade it, by asking what they would need in order to start without it.
Anyone who builds things knows the failure mode, and I make Unvent, so I am not above it. You say yes to a small change. You mean yes if it turns out to be small. They read yes. The condition exists clearly in your head and nowhere at all in the message, which is a difficult position to be annoyed about with anyone except yourself.
Try it on the next request that lands in your inbox. Write the yes, then ask what would have to be true for that yes to survive the month, and put the answer in the same message. The four seconds of awkwardness you are avoiding by leaving it out is the cheapest thing in this whole exchange.
Agree in a voice that sounds like agreeing
Unvent rewrites what you are typing, in place, in the tone you pick. The conditional yes goes out sounding cooperative instead of lawyerly, which is most of the difference.
Add Unvent to Chrome