I kept watching the same movie: entrepreneurs and senior leaders frustrated by peers. Smart peers. Capable peers. People who could analyze and evaluate a problem all day long, but couldn’t take the next step and build the thing that solves it.
That step came naturally to the entrepreneurs, and it was genuinely confusing to them why everyone else couldn’t do it. A weird little educational philosophy finally explained it to me, and it has saved me years of frustration. It’s called Bloom’s taxonomy.
The missing distinction
Bloom’s taxonomy describes levels of cognitive work, and the one that matters here is the line between analyze and evaluate and create.
Analyzing a problem, evaluating options, spotting what’s broken: that’s real, demanding work. Creating is different work. Creating means producing the system, the process, the playbook that solves the problem you identified, where none existed before. Diagnosing the mess and inventing the machine that cleans it up are two different jobs, and a person can be brilliant at one while struggling with the other on any given day.
Most of the frustration between founders and their leadership teams lives on that line. The founder hands over a gnarly, unstructured problem and says “figure it out,” believing they handed over a task. What they actually handed over was create-mode work, while the role, the training, and every prior assignment asked that leader for analyze-mode work.
Modes of work, not types of people
Be careful with this idea, because the tempting version of it is wrong. This is not a sorting hat. There are no “create people” and “apply people,” no ceiling stamped on anyone’s forehead. These are modes of work that a piece of work demands, not categories of brain.
The same person moves between modes all day. Your controller runs the close process in apply mode, analyzes a margin problem in the afternoon, and might build your first pricing playbook from scratch if given the reps. Founders themselves apply someone else’s playbook every time they follow their lawyer’s checklist. And create is learnable: people grow into it with exposure, coaching, and progressively harder building assignments. What’s true in any given moment is narrower: this assignment demands this mode, and this person has or hasn’t yet demonstrated that mode on this kind of problem.
Every company needs all the modes running at once. Someone has to build the playbooks, someone has to diagnose and prioritize with them, and someone has to execute them well. None of that is a ranking of intelligence or worth. Things fall apart in one place: when a role demands a mode the person in it hasn’t developed, and nobody names that out loud.
Why this keeps burning founders
If you’re an entrepreneur, creating is so natural to you that it’s invisible. You see a problem and your brain starts producing the system that fixes it before you’ve finished describing the problem. So you assume “figure it out” is a fair assignment.
Then the cycle starts. Your leader comes back with an excellent analysis and no solution. You wonder if they’re lazy or don’t care. They wonder why you keep handing them impossible assignments. Neither of you is wrong about the other’s competence. You’re mismatched on the mode the work demands, and nobody has said so.
The leader’s actual job
Your job isn’t to label brains. It’s to match the mode a role demands to the mode a person has demonstrated, and to keep updating as they grow.
Diagnose before you delegate. Before handing someone an open-ended problem, ask: does this assignment require creating a playbook, or running one? Then ask what evidence you have that this person has done create-mode work on problems like this. If the evidence isn’t there, either change the assignment, pair them with someone who has the reps, or make it an explicit development assignment with support. What you can’t do is hand over create-mode work silently and grade them as if it were apply-mode.
Hire against the mode the seat demands. If a seat requires building systems from scratch, screen for demonstrated building: ask candidates about playbooks they’ve created, not just results they’ve delivered. Results can come from running someone else’s system.
And stop punishing strong analysis for not being creation. A leader who can ruthlessly analyze and prioritize is exactly who you want running a department with a good playbook in hand. Give them the playbook, and give them building reps on smaller problems if create-mode is where you want them to grow.
The frustration you feel with the smart leader who “just can’t get there” is rarely a character problem. It’s a mismatch between the mode the work demands and the mode the person has demonstrated so far. Name the mode, match the work, invest in the growth, and most of the frustration disappears.