Who Not How

Who Not How is a conceptual framework developed by Dan Sullivan and documented in the 2020 book co-authored with Benjamin Hardy. It addresses a specific cognitive trap that afflicts high achievers: the reflexive tendency, when faced with a goal, to ask “How will I do this?” rather than “Who can do this for me or with me?”

The shift from How to Who is not merely a delegation technique. It represents a fundamentally different relationship with capability, time, and ambition — one that scales, where “How” thinking does not.

The Core Mechanism

“Whenever you imagine a bigger and better future, there’s a problem. You don’t currently know how to achieve the goal, because it’s bigger and better than your current situation and capabilities.” — Who Not How

The logical implication is direct: if your goal is truly new territory, then you — by definition — do not yet know how to achieve it. Asking “How?” in this context locks you into your current capabilities. Asking “Who?” unlocks access to capabilities that already exist elsewhere.

“That’s the power of having a Who—you instantly get access to knowledge, insights, resources, and capabilities that are not currently available to you. ‘How’ is linear and slow. ‘Who’ is non-linear, instantaneous, and exponential.” — Who Not How

This framing recontextualizes procrastination: “Procrastination is a very powerful signal telling you that it’s time to get another Who involved. You’re stuck. You need help.” Resistance is often not laziness — it is wisdom about a mismatch between the capability required and the capability available.

The Vision-Who Relationship

The framework places vision-clarity as the leader’s primary obligation. Not execution — vision.

“That’s what real leadership is: Creating and clarifying the vision (the ‘what’), and giving that vision greater context and importance (the ‘why’) for all Whos involved. Once the ‘what’ and ‘why’ have clearly been established, the specified ‘Who’ or ‘Whos’ have all they need to go about executing the ‘How.‘” — Who Not How

The deeper insight is that a clearly articulated vision is itself an attractor for the right Whos. People want to contribute to missions they understand and believe in. Vague or uninspiring visions repel potential collaborators because there is nothing compelling to attach to.

“When the vision is important enough, the right team of Whos will come together.” — Who Not How

This creates a virtuous cycle: clearer vision attracts better Whos, better Whos deliver superior results, superior results enable bolder vision.

The Investment Mindset

Sullivan distinguishes sharply between a transactional mindset and an investment mindset toward people:

  • Transactional: People are a cost to be minimized; you pay for their time and work and receive defined output
  • Investment: People are a resource whose contribution can multiply the value of your vision by 10x, 100x, or more

“Rather than viewing people or services as a ‘cost,’ as in the transactional mind-set, everything is viewed as an investment, with the possibility of 10X, 100X, or even bigger returns and change.” — Who Not How

This shift in framing changes the calculation around hiring and collaboration. The question is not “How much does this cost?” but “What does this enable?” A virtual assistant who handles scheduling for 24,000 annual expense — they are the mechanism that frees 10 hours per week for highest-value work. If those 10 hours are worth $500/hour, the return is 20x.

The Micromanagement Trap

Who Not How makes a precise point about the relationship between the leader and the Who: once you have defined what done looks like (the result), you must relinquish control over how it gets done.

“That’s one of the biggest mistakes entrepreneurs and leaders make: micromanaging their Whos and insisting that they do their jobs in a particular way, when the only thing that matters is the end result.” — Who Not How

Micromanagement is the practical failure mode of Who Not How adoption. Leaders who can intellectually embrace the concept but cannot emotionally release control over process will get the worst of both worlds: they pay for a Who but retain all the cognitive burden of the How.

The framework notes that this often stems from identity — from a deep conviction that competence and worth are demonstrated by personal execution rather than by the quality of the results you produce regardless of how they are achieved.

The Impact Filter

Sullivan’s practical tool for operationalizing the framework is the Impact Filter — a one-page document that structures the handoff from leader to Who:

  1. What is the project?
  2. Purpose: What do you want to accomplish?
  3. Importance: What’s the biggest difference this will make?
  4. Ideal Outcome: What does the completed project look like?
  5. Best Result: If you do take action?
  6. Worst Result: If you don’t take action?
  7. Success Criteria: What has to be true when this project is finished?

The Impact Filter serves two functions simultaneously: it forces the leader to clarify their own thinking (often discovering ambiguities they did not know existed), and it gives the Who everything they need to pursue the result autonomously.

“Every time you have a new goal to achieve, or have a specific project you want done, complete the one-page Impact Filter to clarify your thinking, define the vision, and ultimately, find the right Whos to execute the vision.” — Who Not How

The 90-Day Operating Rhythm

Sullivan recommends 90-day cycles as the temporal unit for Who Not How execution:

“You can’t achieve massive goals in a day. Some of your goals may be so big that they take years to achieve. Even still, you can make massive progress every 90 days. Breaking down your goals into 90-day increments is good for focus and motivation.” — Who Not How

The Moving Future process — a quarterly review asking what you’ve achieved, what you’re confident about, and what excites you most about the next 90 days — creates momentum by making progress visible and ensuring the next set of Whos is already identified before the current cycle ends.

Relationship to Come Up for Air

Nick Sonnenberg’s Come Up for Air echoes the Who Not How logic from an operational perspective. Sonnenberg explicitly cites Sullivan and Hardy:

“For more information on delegation and ‘the power of no,’ I’d suggest reading Who Not How by Dan Sullivan and Benjamin Hardy. It’s a quick read that will shift your thinking around what you should and shouldn’t be doing.” — Come Up for Air

Sonnenberg’s framework connects through the concept of Unique Ability — the activities that represent your highest contribution, where you experience flow and produce disproportionate value. Investing time saved through Who Not How delegation back into Unique Ability activities is identified as a core efficiency principle.

The Prerequisite: Vision Clarity

Who Not How breaks down when the leader has not done the work to define what they actually want. Whos cannot execute vague intentions. Organizations that attempt to delegate prematurely — before the leader can clearly articulate outcomes and success criteria — typically create confusion, rework, and frustration that leads leaders to conclude delegation doesn’t work. The root cause is not the Who framework; it is insufficient investment in defining the What and Why. The Impact Filter exists precisely to force this clarity.