Distinctions
Is
- A guiding principle that says a solution is not fully solved until the relevant system can understand, maintain, adopt, and act on it.
- A warning against treating individual brilliance as sufficient for system-level success.
- A reminder that effective solutions must become shared capability, not private mastery.
Is Not
- An argument against expertise.
- A claim that every decision must be made by consensus.
- A reason to slow every expert down to the pace of the least experienced person.
- A rejection of individual contribution.
Boundary
- Solving Alone Is Not Solving applies when one person can create or understand a solution, but the surrounding system cannot sustain it.
- It does not apply to temporary solo work that is later made understandable, transferable, and maintainable.
Systems
- Part of team cognition, product development, and organizational resilience.
- Relevant when a team relies on an exceptional individual instead of building shared understanding.
Relationships
| Relationship | Concept | Rationale |
|---|---|---|
| can produce | Single-Point Expertise | Solving alone can concentrate critical understanding in one person. |
| degrades | Bus Ratio | If only one person can support the solution, the system becomes fragile. |
Perspectives
- From the expert’s perspective, solving alone can feel efficient: fewer meetings, fewer explanations, fewer compromises.
- From the team’s perspective, the solution may feel imposed, opaque, or unsafe to change.
- From the system’s perspective, individual intelligence becomes a constraint when it produces solutions the surrounding system cannot understand, maintain, challenge, or evolve.