Get on the Boat and Row: A Leader's 3-Factor Framework for Turning Requests Into Outcomes

Factor 1: Commitment — The Distance Between Knowing and Rowing

Telling someone what you want produces knowing. Knowing is not the same as rowing. Most leaders treat "I told them" as equivalent to "they got it." That gap is where most delegation quietly fails. Closing it takes two more steps most leaders skip: validating understanding, and securing agreement and ownership.

From Knowing to Understanding

As George Bernard Shaw is credited with saying, "The problem with communication is the illusion that it has taken place." That illusion can come from either side of the exchange. A leader can believe they were clear when they weren't. A listener can believe they understood when they didn't.

Start with the leader's side of it. Most leaders overestimate how clear they were to begin with. A deadline given as "soon" or "whenever you get a chance" isn't a deadline, it's a guess the other person must make on their own. Leaders often use vague platitudes without noticing, quietly expecting the listener to read between the lines and land on the same meaning that was in their head.

The other half of the illusion sits with the listener. Most people make unconscious assumptions to close gaps in their understanding, or out of politeness or habit, simply nod along rather than ask clarifying questions. Consequently, even when leaders do deliver a perfectly clear instruction, they still have no idea how it was interpreted on the other end.

The fix to this illusion is a closed-loop conversation. After you've made the request, ask the person to restate it back to you in their own words: what they understood the task to be, why it matters, and by when. Listen for gaps, not just agreement. If what comes back doesn't match what you meant, you've just caught a misunderstanding to correct before it results in weeks of wasted effort.

From Understanding to Agreement and Ownership

Understanding is not the same as agreement, and agreement is not the same as ownership. Someone can repeat your instructions back to you word for word and still not be bought in. This is where a leader has to explicitly convert understanding into commitment, rather than assuming it happened automatically.

That means asking directly: can I count on you to deliver this, by this date? It means treating "I'll try" or "I'll do my best" as an answer that still needs a follow-up question, not as a definitive yes. Leaders should also be on the lookout for people who agree reflexively without weighing what follow-through actually requires. For them, ask what might get in the way before it becomes the reason they miss the deadline.

My ACCORD delegation framework builds this out in more detail, particularly the Confirm and Obligate steps. But the underlying principle is simple: a leader's job isn't finished when the message is sent. It's finished when they confirm the other person owns it as theirs.

Factor 2: Context — Building the Boat Itself

Even a person with total clarity and genuine buy-in will not row well in a boat with a cracked hull, a rudder that doesn't respond, or a performance management system that quietly rewards heading the opposite direction. This is a factor leaders often miss, because it requires looking at the system instead of the person. It's also where a modified version of Elsbeth Johnson's "step up, step back" model earns its place in this framework. Johnson built it for organizational change. Here, it's adapted for individual delegation.

Step Up: Set the Destination and Build the Guardrails

Before a leader can responsibly step back, the leader has to step up. That means two things. First, establish absolute clarity about the what and the why: not just the task, but the destination it serves and the reason it matters now. Second, align the systems around that destination so the person isn't fighting the current while rowing toward it. This second part is where most leaders underinvest. Communication channels need to carry consistent signals. Resourcing needs to match the size of the ask. Performance management needs to actually reward the behavior being requested, not a competing priority left over from last quarter.

Guardrails are what make that autonomy safe to grant. They're the outer limits within which the person can act without coming back to you: a budget ceiling, a scope boundary, and a clear line between decisions they can make alone and ones that need your sign-off. Guardrails aren't a leash. They're what let you hand someone real authority without gambling the outcome on a single conversation you had once at the start. Set them too narrow, and the person still has to run everything by you, guardrails or not. Set them wide and clear, and the person can move fast inside them without needing to come back to you for every little decision.

A leader who doesn't adequately step up promotes mixed signals, friction, and misaligned incentives. The other person's effort was never the real problem, but it gets sabotaged anyway. A salesperson told to prioritize long-term client relationships while still being measured on this quarter's volume isn't confused or difficult. They're just getting two different instructions from two different sources of information, and the system will almost always drown out the leader.

Step Back: But Don't Check Out

Once the destination is set and the guardrails are in place, the leader's job changes. This is where most leaders go wrong by continuously inquiring about the details of execution. Before long, their habit of constantly checking on the other person ceases to be oversight and starts being a signal of distrust. It teaches a capable person to stop exercising judgment, because their judgment clearly isn't being trusted.

The opposite failure does just as much damage. Checking out, disappearing until the deadline and being disappointed by what comes back, isn't trust. It's neglect. Both failures erode ownership, one through control and the other through abandonment.

The way through is to let the person design a reasonable check-in cadence instead of the leader. Something like an OKR structure works well here. The person proposes the key results they believe will deliver the objective you delegated, along with a schedule for reviewing progress against the key results to assess whether things are on track. The leader agrees to check in on that schedule rather than showing up unannounced. This turns the leader's oversight into a shared operating rhythm instead of oppressive micromanagement.

Guardrails aren't set once and forgotten, either. The check-in cadence is also where they get revisited. If someone is bumping against the budget ceiling, running into the scope boundary, or hitting a decision that exceeds the authority you gave them, that's not a sign the guardrails failed. It's exactly the information a check-in is supposed to surface, and it's the leader's job to decide whether to hold the line or widen the lane. What doesn't work is silence. A guardrail that quietly stops fitting the work but never gets revisited becomes a hidden source of the very friction Context is supposed to eliminate.

Factor 3: Being — Rowing the Way They're Wired

You've made the ask clear. You've aligned the systems and set the guardrails. And someone still hesitates. Not because of what you're asking, but because of how you've framed it. People have different natural orientations toward change and risk. One useful lens for this, drawn from the MindTime® framework, is that some people think in terms of precedent and evidence and want proof before committing. Others think in terms of stability and continuity and want to know how a change protects what's already working. Still others think in terms of possibility and want to know what a change makes possible.

There's a second layer to Being, and it has less to do with how someone processes change and more to do with who agreeing would require them to become. A person who has built real value around being the expert, the fixer, or the one who always delivers doesn't hear "hand this off" as a logistics request. They hear it as a threat to the identity that got them here. I've written elsewhere about this same attachment becoming a ceiling for leaders themselves, see The Five Leadership Ceilings, and the mechanism is identical when you're asking someone else to step outside a title, role, or skill set they've built their self-image around. What looks like reluctance is often attachment.

None of this, cognitive orientation or identity attachment, is something to argue someone out of. Both are forces to work with, not obstacles to overpower. A request framed purely around risk mitigation will land differently depending on which of the three MindTime® orientations someone leans toward. A request that quietly threatens someone's sense of who they are will meet resistance no matter how sound the logic behind it. A leader who frames every ask the same way, and never asks what saying yes might cost the other person, will keep mistaking a Being issue for a Commitment issue. They'll keep re-explaining a task that was already understood.