The analyst wants one more review cycle. The executor wants to ship yesterday. One worries about quality; the other worries about delay. This tension plays out constantly in fast-moving organisations, and I've watched it derail more projects than I can count.
The Tug-of-War Between Rigour and Speed
Reasoning's perspective: "If we don't get this right, we'll create bigger problems. More analysis reduces risk."
Doing's perspective: "Perfect is the enemy of done. We learn by shipping, not by planning."
Both are right. The tension arises from different risk assessments -- risk of error vs. risk of delay. And here's the thing: neither risk is imaginary. I've seen companies burn millions launching something that wasn't ready, and I've seen companies lose market position because they spent six months perfecting a proposal that their competitor shipped in six weeks.
What Each Style Brings to the Table
Reasoning contributes:
- Thorough evaluation
- Risk identification
- Quality assurance
- Strategic alignment
Doing contributes:
- Execution velocity
- Bias to action
- Learning through doing
- Momentum maintenance
Together, they deliver quality results quickly. Separately, each creates different problems -- and I've seen both failure modes up close.
The Patterns That Keep Repeating
Analysis paralysis: Reasoning's need for certainty prevents progress. One more data point, one more review cycle, one more stakeholder to consult. Sound familiar?
Reckless action: Doing's urgency leads to avoidable mistakes. Ship first, fix later -- except sometimes "later" never comes, and you're stuck with the consequences.
Mutual frustration: Each sees the other as either obstructive or careless. A director I coached last year at a logistics company in Penang described it perfectly: "My operations lead thinks I'm reckless, and I think she's a bottleneck. We're both probably right."
That kind of honest self-awareness is rare. Most teams never get there -- they just keep butting heads.
A Better Way to Work Together
Define "good enough" before you start
Establish explicit criteria for when analysis is sufficient. Don't leave it to interpretation. I tell teams to agree upfront: "What would we need to know to be 80% confident in this decision?" That number -- 80%, not 100% -- is the key. It gives Reasoning a clear target and gives Doing a realistic timeline.
Timebox the analysis
Give Reasoning adequate but bounded time. "We need your review by Friday" creates productive constraint. Open-ended analysis will always expand to fill available time. That's not a character flaw -- it's the nature of analytical work. The structure has to come from outside.
Iterate rather than perfect
Ship early versions, learn from feedback, improve. This satisfies Doing's need for action while Reasoning refines based on real-world data rather than hypotheticals. In my experience, this is the approach that actually resolves the tension, because both styles get what they need -- just in sequence rather than in competition.
Match the approach to the stakes
Low-stakes decisions: let Doing lead. High-stakes decisions: give Reasoning more room. Not every decision deserves the same level of analysis. But how many teams actually calibrate their process to the stakes? Most apply the same approach to everything, which means they're either over-analysing routine decisions or under-analysing critical ones.
What Leaders Should Do
If you manage both styles:
- Set clear decision timelines -- and stick to them
- Distinguish decisions that need thoroughness from those that need speed
- Help Reasoning accept that some uncertainty is acceptable
- Help Doing understand when caution is genuinely warranted
The real leadership skill here is knowing which mode the situation calls for. That judgement call is yours, not theirs.
When Speed and Rigour Stop Fighting
When Reasoning and Doing collaborate effectively, you get outcomes that are both timely and sound. You ship AND it works.
The best teams don't choose between speed and quality -- they manage the tension productively to achieve both. I've seen this transformation happen, and it's remarkable. The same two people who used to frustrate each other become the pair everyone wants on their project, because between them, nothing gets missed and nothing gets stalled.
That's the outcome worth working toward. Not eliminating the tension, but turning it into your team's greatest advantage.
