.png)
Your To-Do List Is Fine. Your Yes Is Broken.
The yes takes about a second. The work it commits you to takes hours, sometimes weeks, and the list you write afterwards to get on top of it all is a tidy inventory of decisions that have already been made.
That is the problem with nearly everything anyone has ever told you about prioritising, including a short post I wrote in 2023 that recommended making lists, setting boundaries and saying no politely while offering an alternative. All three are reasonable. All three start after the yes. And the yes is where the damage is done.
So this piece is not about the list. It is about the second before it. There are six sentences people say to themselves in that second, and I am going to put each one in the dock, read the evidence against it, and give you the sentence to say instead. Then we can talk about what the list is actually for, which turns out to be something useful and not at all what the productivity books claim.
What you will get out of this
The six sentences that run through your head before you say yes, and the research on why each one is wrong in a predictable direction
How badly you overestimate what a no will cost you, measured in seven studies and 2,132 people
Why the request finds you, specifically, and what the evidence says about who gets asked
Why urgent beats important even when the important thing pays more, and what the diary study found actually gets done in a working week
What a list is for, which is not deciding, and the one change that made difficult goals three times more likely to get done
The wording of a no that lands, the one excuse that measurably backfires, a one-page script card, and a gate to run every request through
"It will only take ten minutes"
What it assumes. That you know how long things take.
What the evidence says. You do not, and neither does anyone else, and the error runs one way. In the study that named the planning fallacy, people were asked to predict how long their own tasks would take, academic and otherwise. They were too optimistic across the board. When the researchers listened to people thinking aloud while they estimated, they found the reason: people build a best-case plan for this task and ignore what happened last time. When they were made to connect the estimate to their own past experience, the bias disappeared.
Two later findings make it worse for anyone in a support role. First, breaking a task into its parts before estimating produces longer estimates, and for complex tasks more accurate ones, which means the ten-minute figure is what you get when you do not think about the parts. Second, power makes it worse. Across four studies, people primed with power or holding actual control over outcomes gave more optimistic and less accurate time predictions. The person with the most authority in the room, the person most likely to be asking you, is the worst judge of how long the thing will take. When they say "it will only take you ten minutes", that is not an estimate. It is a symptom.
What to say instead. Nothing, yet. Name the parts. Most ten-minute tasks have four, and one of them involves waiting for somebody else.
"I will have more time next month"
What it assumes. That the future is roomier than the present.
What the evidence says. It is not, but you will believe it is every single time. Seven experiments established that people expect their slack, the spare capacity they have for a task, to be greater in the future than now, and that this expectation is stronger for time than for money. You would not agree to spend money you expect to have in a month. You agree to spend time you expect to have in a month constantly, and then the month arrives with exactly the amount of time this one has.
This is why a request for next quarter gets a yes that the same request for this week would not. The request has not changed. Your imagined calendar has.
What to say instead. Decide as if it were due on Thursday. If the answer to "could I do this by Thursday?" is no, the answer to "could I do this in March?" is also no; you simply cannot see it yet.
"They will think I am not a team player"
What it assumes. That the person asking will read a no as a verdict on you.
What the evidence says. This is the sentence with the most research against it, and the research is unusually consistent. In seven studies covering 2,132 people, plus four more covering 1,470, people who refused a request overestimated the negative consequences they would face, in hypothetical settings, in real life and when money was on the line. The overestimation came from wanting to avoid those consequences: the more you dread the fallout, the bigger you imagine it. When that desire was weakened, the overestimation shrank or vanished.
A separate line of work on invitations found the same shape. People who declined overestimated how angry the inviter would be, how much the decline signalled they did not care, and how much less likely they were to be invited again. Part of the mechanism is that the person declining assumes the other person is fixated on the decline itself, when in fact the other person is thinking about it far less than you are, and is somewhat aware that you had to weigh it.
And from the other side: in a programme of studies in which participants asked more than 14,000 strangers for things, the people asking underestimated the chance of a yes by 48% on average. They had no idea how awkward it is to refuse. Which means the person asking you has priced in a no that you have not. They asked expecting you might decline. You said yes expecting they would be devastated. One of you is wrong, and it is not them.
What to say instead. The no you are afraid of is not the one they will hear. Say it plainly, once, and watch what does not happen.
"It is urgent"
What it assumes. That urgent and important are the same axis.
What the evidence says. They are not, and you will choose urgent anyway. In five experiments, people chose a task with an objectively lower payoff over one with a higher payoff when the lower-payoff task was framed as expiring sooner, and they kept doing it when every sensible reason for preferring urgency was controlled for. The researchers called it the mere urgency effect, and "mere" is doing a lot of work: the urgency did not have to be real. It had to feel like a closing window.
Then there is the diary study, which is the one I would frame if I could. Twenty-nine engineers logged 878 planned tasks and whether each got done. Three things predicted completion: the task's priority, its urgency, and its being less important. Workload did not predict completion. Planning did not. Perceived control over time did not. Read that again. In a real week, the thing most likely to get finished is the urgent, less important thing, and no amount of planning changed it.
What to say instead. "Urgent for whom, and what happens on Friday if it is not done?" Most urgency is a deadline somebody else set to make their own list feel shorter.
"It is quicker to do it myself"
What it assumes. That doing is cheaper than explaining, delegating or declining.
What the evidence says. It feels cheaper, and the feeling is the trap. Six years of emergency department records showed that under heavier workloads physicians reached for the easier cases first. It looked like higher throughput until the researchers adjusted for the complexity of what was completed, after which it was worse, and it came with less learning over time. In the laboratory the same thing happened for two reasons: fatigue, and the sense of progress that finishing something gives.
The pull towards the small thing is older than that. In an incentive-compatible game, people started with the smaller task and kept choosing smaller tasks even when the larger one was the efficient choice, and the people who did it most performed worst. And in nine experiments on walking and reaching, people picked up the nearer bucket and carried it further, taking on extra effort to get the sub-task off their mind sooner. The researchers called it precrastination. Every "I will do it quickly myself" is a nearer bucket.
What to say instead. "Who is closest to this?" Not "who is best at it": who is closest. The answer is rarely you, and when it is, that is a different sentence.
"I said no last time"
What it assumes. That there is a quota, and you have used it.
What the evidence says. There is no quota. There is a belief about who says yes, and the belief is the whole mechanism. In a series of experiments on tasks everyone would rather someone else did, the kind with no promotion attached, women volunteered more than men, were asked to volunteer more, and accepted more when asked. The driver was not preference. It was the belief, held by everyone in the room including the women, that women were more likely to say yes. Put people in single-sex groups and the difference disappeared.
I am not going to tell you what that means for your organisation, because I do not know your organisation. I will tell you what it means mechanically. The request does not go to the right person. It goes to the person believed most likely to say yes. Every yes you give trains that belief, and the belief is held by people who are not counting. There is no ledger in which your last no earns you this yes. There is only the running estimate of how easy you are to ask, and you are the only person keeping it accurate.
What to say instead. Nothing about last time. The last time is not evidence in this case.
The uncomfortable claim underneath all of this
You do not have a prioritising problem. You have an intake problem.
Every one of the six sentences leans towards yes, and not one of them is judgement. You think the task is smaller than it is. You think the future is roomier than it is. You think the refusal will cost more than it will. You think urgent means important. You think doing it yourself is the efficient choice. You think your last no bought you something. All six vote before you have said a word, and then you sit down with your list and try to prioritise the result.
The list cannot fix this because the list is downstream. The best prioritising system in the world, applied to work that should never have been accepted, produces a beautifully ordered week that was lost the moment it was agreed to.
Why the list comes too late
I want to be fair to lists, because I told you to make them in 2023 and I still make them. What the evidence says is that they are good at one thing and useless at another, and the productivity industry has the two backwards.
The thing a list is useless at is deciding. Go back to the diary study: urgent and less important got done, and planning made no difference to what got finished. Go back to the emergency department: under load, the easy thing got picked. A list does not stop either of those. A list is a menu, and you order from a menu with the same appetite you walked in with.
The thing a list is good at is quieting your head, and this is real and measurable. Unfinished goals interfere with tasks that need concentration; that is the old finding, and it replicates. What is newer is that making a specific plan for the unfinished thing, where and when and how, removed the interference without the thing being done. In a study of 103 employees and 1,127 work goals, people found it hardest to switch off in the evening from goals that were incomplete and mattered to them, and an end-of-day plan for where, when and how the goal would be finished improved detachment among the people who normally cannot.
So the list is not a decision tool. It is a container. It is where you put the thing so you can stop carrying it. That is worth having. It is not prioritising.
What the list is for, done properly
If you want the list to change what gets done rather than how you feel, the evidence points at one change. Stop writing tasks. Write conditions.
A task on a list is a goal intention: "do the board pack". The research on what it calls implementation intentions attaches a when, a where and a how: "when the 2pm meeting ends, at my desk, I open the pack and write the first section before anything else". In the original study, difficult goals were completed about three times more often when they carried this form. Across a meta-analysis of 94 tests, the effect on goal attainment was medium to large, at 0.65 in the units researchers use, which in plain terms means most people who did it beat most people who did not. And in a direct test on the planning fallacy, people who made this kind of plan did not only predict more optimistically; they finished more often than they predicted, which cut the fallacy, and the reason was fewer interruptions.
That last point is the one for anyone whose diary belongs to somebody else. The if-then plan does not give you more time. It makes the time you have harder to interrupt, because you already know what happens at the trigger.
The no, worded
None of the above helps if you cannot get the sentence out. So here is what the evidence says about the sentence.
Say "I don't", not "I can't". In two studies on refusal, "I don't" was the more persuasive frame because it signals conviction, and conviction is read as identity rather than circumstance. "I can't take that on this week" invites negotiation about the circumstance. "I don't take on new drafting the week before the board" describes a person.
Never say "I don't have time". This one surprised me. Across six studies, "I don't have time" was a worse excuse than "I don't have the money", because time is seen as within your control and money is not. Time excuses were read as less trustworthy, reduced how close people felt to the excuse-giver, and reduced their willingness to help. And the people giving the excuse did not predict any of it. If you have been saying "I'm so busy" as your no, you have been lowering trust with every use.
Name what you are doing instead. Not a list of everything, one thing. "This week is the board pack" is specific and uncontrollable in the way the research says works. "I'm swamped" is neither.
Offer one alternative, not three. A date, a person or a smaller version. Three alternatives is a negotiation; one is a decision.
Ask for the afternoon. The single most useful line in this whole piece, and it is neither a yes nor a no: "Let me look at the week and come back to you by three." It moves the decision out of the second in which all six sentences vote, and into a moment when you can see the calendar. Almost nobody objects to it. Almost nobody uses it.
Download: The No Script Card
One card, three pages, and it lives in the drawer or the notes app rather than in your head, because your head is where the six sentences are.
What is inside | Why it is there |
The six sentences with their replacement lines | So that the replacement is available in the second, not afterwards |
A box for the parts of the task | Because unpacking is what corrects the ten-minute estimate |
The four moves of the no, with fill-in lines | "I don't" framing, what you are doing instead, one alternative, the afternoon line |
The lines that measurably backfire | "I don't have time", "I'm so busy", and a stacked apology |
The if-then form for anything you do accept | When, where, how, so that the yes at least gets done |
Free, no email wall. Print it or keep it open.
Frequently asked questions
Is this telling me to say no to my executive?
No. It is telling you to say the real time, the real date and the real alternative to your executive, which is a different thing. The evidence says the person with the most authority is the worst judge of how long a task takes. Correcting the estimate is a service, not a refusal.
What if it really is urgent?
Then say yes, with the real time attached and something moved. The problem is not urgent work; it is the mere urgency effect, in which a closing window makes a lower-value task win. Ask what happens on Friday if it is not done. If the answer is specific and bad, it is urgent. If the answer is "well, they wanted it", it is a window.
I am the person people come to. Is that not the job?
Being the person people come to and being the person believed most likely to say yes are different reputations that look identical from the inside. The first is earned by judgement. The second is earned by never testing whether a no is allowed. The volunteering research is clear that the request goes to the second person, and that the belief driving it is held by everyone in the room.
Does "I don't" not sound rude?
In the study it sounded convinced, and convinced was what made it persuasive. Rude is usually the stacked apology that follows a weak no. State it, name what you are doing instead, offer one alternative, stop talking.
Should I stop making lists?
No. Make them for the reason they work: to put the unfinished thing somewhere so it stops interfering with your concentration and your evening. Stop expecting them to decide anything. And for the things that matter, write the condition rather than the task.
Where does this connect to the afternoon problem?
The 4pm piece is about the decisions you make when you are tired. This one is about the decisions you make in a second, at any time of day, because a request arrived. Both are downstream of the same thing: a calendar that fills faster than your judgement can check it. The afternoon line, "I will come back to you by three", solves a little of both.
Run the next request through this before you answer
Where to start
Take the next request that arrives, from anyone, and do not answer it in the second. Say "let me look at the week and come back to you by three." Then, before three, name the parts, decide as if it were due Thursday, and answer with "I don't" or "I do", one alternative, and no mention of how busy you are. Do this for one week. Count the number of times anything bad happens. It will be smaller than the number you predicted, and the gap between those two numbers is the whole piece.
The ability to protect your capacity without losing the trust of the people who depend on you is one of the things the Connected Leader Assessment measures under Influence and Stakeholder Trust. It is free, it takes about twelve minutes, and it will tell you whether people trust you because you say yes or because your yes means something.
And if you want to build the wider skill, holding a boundary in the room, negotiating the date rather than the task, and saying no to the work that will never be promotable, that is what our Skill Sprints are for. One topic, built properly, an hour or two, and you come out having made something rather than having been talked at.
Meg ✌️
Free tools
The gate, the interactive tool in this post, free
The No Script Card, the download in this post, free
The Connected Leader Assessment, twelve minutes, free, with a read on Influence and Stakeholder Trust, the dimension this post sits in
P.S. Want to Go Deeper on Saying No?
If this resonated and you want to go further, here is the evidence the piece is built on. These are the papers that shaped my thinking on why the yes happens before judgement gets a vote, and what actually changes it, and they are well worth your time.
Every DOI below has been checked. Where I could not confirm a figure from the paper itself, I have left the figure out rather than guess.
📃 Buehler, Griffin and Ross (1994) The planning fallacy: people underestimate their own completion times, build best-case plans and ignore last time. Connecting the estimate to past experience removed the bias. https://doi.org/10.1037/0022-3514.67.3.366
📃 Kruger and Evans (2004) Unpacking a task into its parts produces longer and, for complex tasks, less biased time estimates. https://doi.org/10.1016/j.jesp.2003.11.001
📃 Weick and Guinote (2010) Four studies. Power makes time predictions more optimistic and less accurate. https://doi.org/10.1016/j.jesp.2010.03.005
📃 Zauberman and Lynch (2005) Seven experiments. People expect more spare time in the future than now, more so for time than for money, and discount delayed commitments accordingly. https://doi.org/10.1037/0096-3445.134.1.23
📃 Lu, Fang and Qiu (2023) Seven studies, 2,132 people. Rejecters overestimate the negative consequences of refusing, and the overestimation comes from wanting to avoid them. https://doi.org/10.1037/xap0000457
📃 Givi and Kirk (2024) People who decline invitations overestimate how angry, hurt and unlikely to ask again the inviter will be. https://doi.org/10.1037/pspi0000443
📃 Bohns (2016) The review of more than 14,000 requests to strangers. Requesters underestimate compliance by 48% because they do not appreciate how awkward it is to say no. https://doi.org/10.1177/0963721415628011
📃 Flynn and Lake (2008) Help seekers underestimate by up to 50% the chance that a direct request will be granted, attending to the cost of yes rather than the cost of no. https://doi.org/10.1037/0022-3514.95.1.128
📃 Zhu, Yang and Hsee (2018) The mere urgency effect, five experiments. People choose a lower-payoff task over a higher-payoff one when the lower one feels like it is expiring. https://doi.org/10.1093/jcr/ucy008
📃 Claessens, van Eerde, Rutte and Roe (2010) Daily diary, 878 tasks, 29 engineers. Priority, urgency and lower importance predicted completion; workload, planning and perceived control of time did not. https://doi.org/10.1111/j.1464-0597.2009.00390.x
📃 KC, Staats, Kouchaki and Gino (2020) Six years of emergency department data. Under load, physicians completed easier tasks first; it looked productive and was not, and it came with less learning. https://doi.org/10.1287/mnsc.2019.3419
📃 Rusou, Amar and Ayal (2020) The smaller tasks trap. People start with the smaller task and keep choosing smaller tasks even when it is the less efficient choice. https://doi.org/10.1017/s1930297500007518
📃 Rosenbaum, Gong and Potts (2014) Precrastination. Nine experiments in which people took on extra effort to get a sub-task off their mind sooner. https://doi.org/10.1177/0956797614532657
📃 Rosenbaum, Fournier, Levy-Tzedek, McBride and Rosenthal (2019) The review linking precrastination to the mere urgency effect. https://doi.org/10.1177/0963721419833652
📃 Babcock, Recalde, Vesterlund and Weingart (2017) Tasks with low promotability. Women volunteer more, are asked more and accept more, driven by the belief that women say yes; in single-sex groups the difference disappears. https://doi.org/10.1257/aer.20141734
📃 Masicampo and Baumeister (2011) Unfulfilled goals interfere with tasks that need executive function. https://doi.org/10.1016/j.jesp.2010.10.011
📃 Masicampo and Baumeister (2011) Consider it done. A specific plan for the unfulfilled goal removes the interference without the goal being completed. https://doi.org/10.1037/a0024192
📃 Smit (2016) 103 employees, 1,127 goals. An end-of-day plan for unfinished work improved switching off among people who usually cannot. https://doi.org/10.1111/joop.12137
📃 Gollwitzer and Brandstätter (1997) Difficult goals completed about three times more often when the intention carried a when, where and how. https://doi.org/10.1037/0022-3514.73.1.186
📃 Gollwitzer and Sheeran (2006) Meta-analysis, 94 tests. Implementation intentions have a medium-to-large effect on goal attainment, 0.65. https://doi.org/10.1016/s0065-2601(06)38002-1
📃 Koole and van't Spijker (2000) Implementation intentions raised actual completion more than predicted completion, cutting the planning fallacy through fewer interruptions. https://doi.org/10.1002/1099-0992(200011/12)30:6<873::aid-ejsp22>3.0.co;2-u
📃 Patrick and Hagtvedt (2012) "I don't" is a more persuasive refusal than "I can't" because it signals conviction, which is read as identity. https://doi.org/10.1016/j.ijresmar.2012.04.004
📃 Donnelly, Wilson, Whillans and Norton (2021) Six studies. "I don't have time" is a less trusted excuse than "I don't have money", because time is seen as controllable, and excuse-givers do not predict the cost. https://doi.org/10.1002/jcpy.1226
P.P.S. Why Do I Even Have the Nerve to Write This?
Fair question.
I am someone who has spent years working alongside remarkable executives, navigating chaos, translating vision into structure and figuring things out, sometimes beautifully and sometimes the very hard way. I have had the privilege of being the steady right hand to leaders who move fast, take risks and expect a lot. That environment has shaped me more than any classroom ever could.
I also happen to have an MBA, and I am studying psychology because people fascinate me. How we work. Why we disconnect. What actually holds us together when the pressure rises.
But really, none of that is the point.
I am here because I have lived the erosion and rebuilt from it. I have seen the cost of carrying too much and the relief that arrives when you finally stop disappearing inside your own competence.
So I share what I have learned in case it helps someone else. Take what is useful. Leave the rest. And remember this one truth that professionals like you often forget:
You are probably doing far better than you give yourself credit for.
Comments