For Leaders
Leadership is not a style. It is a set of functions that must be performed for the work to succeed. How We Excel helps you identify what those functions are, where gaps exist, and how to lead through complexity — not around it.
Two different situations — two different entry points
The challenges of a new leader without an established infrastructure are genuinely different from those of an experienced leader in a complex environment. Choose the situation that fits.
New Leader — Building from scratch or very little
You are leading for the first time, or leading with minimal existing structure, resources, or established team. You need to build foundations before anything else will work.
Jump to this section →
Experienced Leader — Navigating complexity, phase transitions, or persistent problems
You have led before. The challenges you face are not about basics — they are about phase-aware complexity, systemic misalignment, or situations where traditional approaches keep failing.
Jump to this section →
Leading without an established infrastructure
Early leadership decisions can create durable effects. A disciplined sequence—understanding the Need, the work, and the required access before committing to solutions—can reduce avoidable rework.
Resist the urge to assess the team you inherited or start building the team you want until you know who is affected by the work. Who uses the outputs? Who maintains them? Who funds, approves, resists, or lives with outcomes? That map shapes everything that follows.
What must this team be able to do for the work to succeed? List functions — not roles, not job titles, not names. The functions drive the team design. A team assembled around available people who have not been assessed against required functions has not been designed — it has been populated.
New leaders are often handed a problem statement that was defined before the right people were in the room. Do not inherit it uncritically. Spend time at requirements definition — with stakeholders present — before moving to solutions. This is the stage most new leaders skip. It is also where most costly failures are created.
Decisions that are not documented are decisions that will have to be re-made — often at higher cost, under worse conditions, without the people who were in the original room. Start a simple decision log. Who was involved? What information was present? What was decided and what was not decided? This protects you and your team.
Teams default to the cognitive approaches of their most senior or most vocal members. This produces systematic blind spots. Structure for cognitive diversity from the beginning — not because it is politically appropriate, but because work done without the full range of cognitive approaches reliably misses something important.
Recommended starting tools for new leaders
Stakeholder Validity Canvas
Map who is affected before deciding who should be on the team or what the work is.
Function / Subfunction Guide
Name what the team must do before deciding who should do it.
NavV Canvas
Structure any bounded work effort from need through sustainment before beginning.
Phase-aware leadership — beyond style, beyond technique
If traditional approaches keep producing the same problems, the issue is usually not skill. It is usually that the leader is applying the right technique to the wrong phase of the work.
Premature problem definition is a consequential leadership risk. A team missing required stakeholder knowledge, authority, or evidence may define the problem incorrectly without recognizing what it cannot yet see.
The solution is not better problem-solving. It is returning to requirements — with the right people in the room — before the work goes further. That feels like going backward. It is the only way to go forward correctly.
Individual components can each pass their own tests and still fail when combined. The design layer may be contributing: how authority is structured, how information moves, how decisions are documented, and how handoffs are managed. People and relationship factors may also require attention.
The How We Excel architecture provides a framework for diagnosing integration failures without blaming individuals — and for designing the coordination structure that prevents them. Leaders who use this framework stop asking "why can't they work together?" and start asking "what does the architecture require that we haven't built yet?"
Every V stage makes different demands of the leader. Requirements definition requires patience, stakeholder management, and tolerance for ambiguity. Implementation requires precision, accountability, and issue resolution. Validation requires humility — the willingness to test whether you actually built the right thing, not just whether you built it correctly.
Leaders who apply a single style across all phases — consistently pushing for results in requirements definition, or consistently consulting when implementation needs decisive action — create systematic problems. Phase-aware leadership asks: what does this stage require of me right now, as distinct from what I am most comfortable doing?
Leaders are responsible for designing collective access — making required stakeholder knowledge, expertise, authority, resources, and cognitive contributions reachable, usable, appropriately evaluated, coordinated, and used when needed. When only certain cognitive approaches are rewarded, the team may underuse contributions needed for particular functions.
This is not a soft issue. Heavy reliance on Effectiveness while discounting Harmony can weaken attention to stakeholder effects; reliance on Insight while suppressing Accuracy can leave assumptions insufficiently tested; reliance on Exploration while dismissing Effectiveness can delay convergence on a workable path. CAP-5 offers one bounded lens for noticing such patterns. It does not diagnose team performance, establish causation, measure competence, or assign authority.
Most leadership frameworks treat approval as the end of the work. NavV treats it as the beginning of the right side. A solution that cannot be maintained, adapted, or sustained in the receiving environment — regardless of how well it was designed or how enthusiastically it was approved — has not succeeded.
Experienced leaders who have watched good initiatives fail after launch recognize this pattern. The question is not just "did we build it correctly?" (verification) or "did we build the right thing?" (validation) but "can it live in the real world without us holding it up?" Transition into use is leadership work, not a handoff event.
Browse the full tool index
All tools are listed with their function, readiness status, and intended audience. Start with what is available and track what is coming.