By Andreas Pettersson, Founder, Leaders ADAPT
"Could you possibly take a look at the onboarding thing when you have a minute?"
I said versions of that sentence for years and thought I was being a considerate boss. "Instead of saying" is the whole fix, and it took me a decade to learn it. What I was actually doing was handing someone a task with no outcome, no authority and no date, and then being surprised when it came back to my desk unfinished. The sentence was the leak.
I run Leaders ADAPT and wrote the 5-Minute Leader for managers whose teams wait on them. The rule in its Delegation Protocol is blunt: unclear delegation is not kindness, it is cruelty, because it sets people up to miss expectations you never stated. The 40 swaps below are that rule applied to the sentences managers say every day. Each one names the protocol it belongs to and the leak it closes.
Quick answer: Instead of saying "could you possibly" or "when you get a chance", say the outcome, the authority level and the date: "You own the vendor scorecard, decide the format, tell me before it goes to finance, first version by the 15th." Instead of "how are things", say "What is on your mind?" Instead of "let me know if you need anything", set a check in at 25 percent.
Why the sentence is the delegation
A manager swap is a replacement for a habitual sentence that leaves out the outcome, the authority or the date, so that the new sentence carries all three and the work stays where it was put. The soft version feels polite. It is actually a transfer of guesswork.
The Delegation Protocol I teach runs a three minute conversation in four blocks: context, outcome, authority level, verification. Most of the swaps on this page are one of those blocks said out loud instead of left implied. The rest come from the 1:1, Accountability and Rhythm protocols, and each section says which.
Delegation swaps: outcome, authority, date
| Instead of saying | Say | The leak it closes |
|---|---|---|
| "Could you possibly look at the onboarding thing?" | "Onboarding churn is 30 percent at sixty days. Map the sixty days, find the drop off points, proposal by end of month. You own it" | No outcome, no date |
| "Would you mind handling the report?" | "You own the board report. Decide the format. Tell me before it goes out. Due the 15th" | Authority level never stated |
| "If you have time, maybe you could..." | "This is yours. It is the priority over the audit this week" | Optional versus required |
| "Send the monthly report to the board" | "Make sure the board has complete visibility into our performance and feels confident about where we are going" | Task instead of outcome |
| "Just do it however you think is best" | "Level 1. Decide and inform me after. Update me weekly for visibility, not approval" | Vague authority reads as a trap |
| "Run it by me before you do anything" | "Level 2. Decide, but tell me before you implement" | Permission for everything |
| "What do you think we should do?" | "Level 3. Bring me three options by Friday and I will decide" | Decision rights unclear |
| "Does that make sense?" | "Say back to me what you are taking on, and why it matters" | A nod is not comprehension |
| "Let me know if you need anything" | "I will check in Wednesday, at about a quarter of the way through. Come with blockers" | The 25 percent rule, missing |
| "Can I see what you have so far?" | "How is it going, what is blocking you, what do you need from me?" | Check in becomes oversight |
| "I'll just do it myself, it is faster" | "Watch me do it once, then you own the next one" | The 70 percent test, failed |
| "Are you sure you can handle this?" | "What could go wrong with this approach?" | Silence hides doubt |
| "It is not a big deal if it slips" | "If the date will slip, I hear it before the date, not after" | Permission to be late |
| "Thanks, I'll take it from here" | "What do you need from me to finish it?" | Work boomerangs back |
The first row is the one I got wrong most. The soft version has no situation, no complication and no deadline. The rewrite is the SCQA framing from the protocol, and it takes fifteen seconds longer to say.
1:1 swaps: calibration, not status
| Instead of saying | Say | The leak it closes |
|---|---|---|
| "How are things?" | "What is on your mind?" | Invites "fine" |
| "Give me an update" | "What else?" (asked twice) | Turns the 1:1 into a status meeting |
| "How can I help?" | "On a scale of 1 to 10, what is your energy right now?" | Assumes they need help, hides the number |
| "You seem a bit off" | "What would it take to get you to an 8?" | Guessing instead of asking |
| "Anything else?" | "What are you struggling with that you have not told me about?" | The real item stays unsaid |
| "Sounds good" | "What are you committing to between now and next week?" | No commitment leaves the room |
| "We should talk about that sometime" | "Quick feedback from yesterday. Got two minutes?" | Feedback older than 48 hours is archaeology |
| "You were great in that meeting" | "Strong close. Next time, get a commitment before you hang up" | Praise with no behavior attached |
| "Let's push the 1:1 this week" | "Same time, 25 minutes instead of 45" | The cancelled 1:1 that becomes a habit |
| "I'm sure it is fine" | "Give me a color, green, yellow or red" | Cannot read energy on video |
The energy question is the single swap I would keep if I could keep only one. A number gets past the performance of "fine" where an open question does not.
Boomerang check: does your work stay delegated, or does it come back?
Three questions, scored to the protocol that fixes the leak. The 5-Minute Leader is the four protocols, Delegation, 1:1, Accountability and Rhythm, written down so a manager can run them in about five minutes a day, so tasks stop boomeranging back half done.
Get the 5-Minute Leader or see what is inside the 5-Minute Leader.
Accountability swaps: warm but firm
| Instead of saying | Say | The leak it closes |
|---|---|---|
| "I don't want to make a big thing of this, but..." | "I am invested in your success, which is why I need to be direct about something" | Pre discrediting the message |
| "Maybe try to be a bit more on top of things" | "In yesterday's client meeting you interrupted three times. They shut down. Going forward, let them finish before you respond" | No softening, no maybe or perhaps |
| "You always miss deadlines" | "Two commitments from August and September were neither delivered nor renegotiated" | "Always" is not evidence |
| "Why didn't this get done?" | "I have noticed a pattern. When things do not happen, there are explanations instead of ownership. Reasons are not results" | Invites a reason instead of ownership |
| "No worries, we'll sort it out" | "What do you need from me to make this shift?" | Drops the standard to keep the peace |
| "You're being defensive" | "Help me understand what I am missing. And here is what I observed regardless" | Escalates instead of landing |
| "Why are you taking it personally?" | "I can see this is landing hard. Take a moment. This conversation is because I believe in your potential" | Retreating when someone gets emotional |
| "We'll revisit this later" | "Starting now. Can you commit to that?" | Later means never |
The first row is the mistake I see most in otherwise good managers. The prequel, "I am not perfect either", feels humble. It tells the other person the message is negotiable.
Meeting and rhythm swaps
| Instead of saying | Say | The leak it closes |
|---|---|---|
| "Let's skip stand up today, nothing new" | "9:15, fifteen minutes, as always" | Skip once becomes skip when needed |
| "Let's make the meeting longer so we can cover everything" | "Anything over five minutes goes offline" | Rhythms die from bloat |
| "Senior people can skip if they are busy" | "Same time, everyone, no exceptions" | Skipping says it does not matter |
| "Let's solve this now while we are all here" | "Surface it now, solve it after" | Stand up becomes a working session |
| "Thanks for being awesome, everyone" | "Recognition: one person, one specific behavior, one specific impact" | Praise nobody can repeat |
| "When did this become urgent?" | "What is blocking you?" (asked daily) | The sentence the stand up is built to kill |
| "Let's be flexible on timing" | "Same time to the minute" | Whenever means never |
| "Sorry to bother you, quick question" | "Two minutes on the forecast, now or at 2?" | Apologizing makes the ask optional |
How to install the swaps without sounding like a script
Pick one row per week. Say it until it is automatic, then take the next. The Delegation Protocol version of this is a first week that runs Monday to Friday: one small handover using the full conversation, one bigger one verified with a repeat back, three things written down that someone else could own, the one you have been telling yourself is faster to do yourself, and a Friday count of what stayed delegated. Three of four is the pass mark.
The swaps are not about being blunt. The outcome, the authority level and the date are the courtesy. The polite version was the unkind one, because it left the other person guessing. The full handover conversation is on how to delegate, and the pattern where the work walks back to your desk is on reverse delegation.
The four protocols behind the forty swaps
Every swap on this page is a line from one of the four protocols in The 5-Minute Leader. I wrote it after scaling a company to more than 150 people, when I realized my managers had copied my meetings but not my sentences. Delegation, 1:1, Accountability and Rhythm, each written so a manager can run it in about five minutes a day, so the work stops boomeranging back.
The Delegation Protocol holds the three minute conversation the first table comes from, with the three authority levels and the 25 percent rule. The 1:1 Protocol holds the energy question and the 24/48 Rule. The Accountability Protocol holds Warm but Firm and the scripts for the three conversations managers avoid.
There is one swap not on this page, the one for the person who says "I think I can do that," and it is four words long.
Instead of saying FAQ
Instead of saying "could you possibly", what should a manager say?
Say the outcome, the authority level and the date. "You own the vendor scorecard. Decide the format yourself and tell me before it goes to finance. First version by the 15th." The polite opener sounds kind, but it hides whether the task is required, who decides, and when it is due, which is why the work comes back half done.
What should you say instead of "how are things" in a 1:1?
Say "What is on your mind?" and then "What else?" twice. "How are things" invites "fine" and the meeting becomes a status update. The open question hands the first part of the meeting to the employee, which is where the problems you do not know about surface. Follow it with the energy question, a number from 1 to 10.
What should you say instead of "I think I can do that"?
If an employee says it, ask for a commitment: "I need you to commit or tell me you cannot. Which is it?" Think means will not. If you are the one saying it, replace it with either "I will have it by Thursday" or "I cannot take that on this week." Half commitments are how work boomerangs back to the person who asked.
What should a manager say instead of "sorry to bother you"?
Say what you need and by when. "Two minutes on the Q3 forecast, now or at 2?" Apologizing for a work request teaches the team that your asks are optional. The time and the choice of slot are the courtesy, not the apology. The same swap applies to "when you get a chance", which means never.
What should you say instead of "let me know if you need anything"?
Set a check in at 25 percent of the work and say so: "I will check in Wednesday, come with blockers." The open offer puts the burden on the employee to interrupt you, which most will not do until the deadline. A planned check in at a quarter of the way through catches a wrong direction while it is still cheap.
Why does the way a manager phrases things matter so much?
Because the phrasing is the delegation. "Could you possibly" leaves out whether the task is required, who decides and when it is due, and the employee fills the gaps with guesses. Clear phrasing is not blunt for its own sake. It is the difference between work that stays delegated and work that returns to the manager unfinished.
Listen to yourself for one day
Tomorrow, count how many times you say "could you possibly", "when you get a chance" or "let me know if you need anything." Each one is a task that will probably come back. Replace one of them with the outcome, the authority level and the date, and watch whether that piece of work stays where you put it. Instead of saying the soft version, say the clear one once, and the difference is visible by Friday.
Which of the 40 do you say most, and what has it cost you this quarter?
