Stage profile · Management

Manager of Managers

Within actual authority, leads managers to deliver across teams and is accountable for resource direction and organizational capability; strategy, budget, and reorganization authority depend on the role mandate.

Read these as observable expectations across repeated work, not as a checklist for a single project. First distinguish whether the role expects the work, whether the person had a chance to demonstrate it, and whether the evidence supports the claim. Lack of opportunity or evidence is not itself a negative judgment. AI use is judged by verified outcomes, sound boundaries, and the quality of decisions; choosing not to use AI can be sound.

Four complementary evaluation lenses

These lenses and the A–H capability map answer different questions. One experience may provide evidence across lenses, but do not count the same result multiple times.

Business outcomes

Understand the people served and intended outcomes, make evidence-based trade-offs, and verify contribution. For platform, infrastructure, reliability, and safety work, cost, efficiency, risk reduction, and internal-user outcomes count; direct revenue ownership is not universal.

Domain expertise

Apply relevant knowledge to diagnose, design, implement or review, validate quality, and make evolution decisions. The professional leaves required depend on the role.

Team influence

Help others work effectively through communication, coordination, review, shared methods, coaching, or organizational mechanisms. IC influence is not measured by direct reports; managers also own formal people responsibilities.

Human competitiveness

Observe questioning, reasoning, learning transfer, judgment updates, relationship handling, and recovery in work. This is not a fixed personality or potential verdict; do not infer it from extroversion, fluent speech, or willingness to overwork.

Evidence to verify

Use this structure to understand a real example. Strong judgment can appear in a failed project; a successful result alone does not prove personal causation.

  1. Context and goal
  2. Role and authority
  3. Judgment and trade-offs
  4. Actions and collaborators
  5. Outcome and guardrails
  6. Attribution limits
  7. Counterevidence and adjustment

The labels beside capability references describe that capability’s role in this standard; they do not make the whole standard optional. Any role or scenario condition is stated separately.

Business outcomesView progression
  1. Within organizational mandate, translates business direction into multi-team outcomes, portfolio priorities, and adjustable investment plans; executive strategy or budget authority is not assumed.

    Evidence to inspect: Team goals form a coherent portfolio and outcomes/resources are revisited regularly.

    Capability map and its role here：PlanningDifferentiating hereInvestment choicesDifferentiating hereBusiness outcomes and validationDifferentiating here
  2. Makes organization-level trade-offs across growth, efficiency, reliability, safety, and long-term capability.

    Evidence to inspect: Names downside scenarios, risk owners, and conditions for changing course.

    Capability map and its role here：Market and economic judgmentDifferentiating hereQuality, security, and safetyRelevant when context applies
  3. Establishes consistent outcome measurement and review so leaders adjust direction using evidence.

    Evidence to inspect: Cross-team measures are interpretable; attribution limits and misses are transparent.

    Capability map and its role here：Metrics and causal reasoningDifferentiating hereBusiness outcomes and validationDifferentiating here
  4. Within actual authority, connects annual direction, phased portfolios, and recurring reviews while making assumptions, resource limits, and exit conditions explicit; cadence follows the decision cycle.

    Evidence to inspect: Planning horizons are traceable, and cross-team conflicts can trigger portfolio changes.

    Capability map and its role here：PlanningDifferentiating here
  5. Stops ineffective investments when business direction or portfolio assumptions fail and manages resource shifts and team transitions.

    Evidence to inspect: Stopping and redirection include prior evidence, transition cost, and subsequent results.

    Capability map and its role here：Investment choicesDifferentiating here
Domain expertiseView progression
  1. Ensures clear ownership and controls for critical technical, product, privacy, and security risks, adding proportionate evaluation and oversight when AI is involved.

    Applies when: The AI governance portion applies only where the organization actually uses or provides AI.

    Evidence to inspect: Critical risks have decision owners, monitoring, review, and response mechanisms.

    Capability map and its role here：AI evaluation and governanceDifferentiating hereQuality, security, and safetyDifferentiating here
  2. Sets cross-team quality and operational standards proportionate to business risk.

    Evidence to inspect: Standards reduce incidents or regressions without unnecessary process burden.

    Capability map and its role here：Engineering systemsDifferentiating hereReliability and incidentsDifferentiating here
  3. Engages experts on long-term domain and technical choices and understands business, user, and organizational consequences.

    Evidence to inspect: Can compare paths and reversibility without substituting for specialists on details.

    Capability map and its role here：System designRelevant when context appliesModel evolutionRelevant when context appliesProduct judgmentDifferentiating here
  4. Governs cross-domain technical roadmaps, connecting platform, architecture, and data investment to business direction, and evaluates AI investment and alternatives where relevant.

    Applies when: AI project count or adoption is not a goal; explain the basis for adopting, declining, or deferring it.

    Evidence to inspect: The portfolio has expert review, dependency sequencing, and long-term maintenance ownership.

    Capability map and its role here：Engineering systemsDifferentiating here
Team influenceView progression
  1. Within actual authority, hires, coaches, and evaluates managers and establishes management calibration and leadership handoff practices; organizational scale and succession outcomes depend on opportunity and mandate.

    Evidence to inspect: Managers independently own team results and grow the next layer of leaders.

    Capability map and its role here：Manager of managersDifferentiating hereDelegation and successionDifferentiating here
  2. Adapts organizational boundaries, decision rights, and collaboration to business and architecture changes.

    Evidence to inspect: Reduces structural dependencies and local optimization; ownership and resources match goals.

    Capability map and its role here：Team designDifferentiating hereDelegation and successionDifferentiating here
  3. Builds organization-wide mechanisms for strategic communication, conflict resolution, and decisions.

    Evidence to inspect: Key trade-offs have clear decision owners and teams understand shared direction and limits.

    Capability map and its role here：Stakeholder influenceDifferentiating hereConflict navigationDifferentiating here
  4. Plans organizational capability, key roles, and management spans with relevant decision-makers; headcount, budget, and formal succession decisions depend on actual authority.

    Evidence to inspect: Organizational plans support the business portfolio and review capability gaps against outcomes.

    Capability map and its role here：Team designDifferentiating here
  5. Leads reorganizations, leadership handoffs, and resource contraction while maintaining delivery and testing new accountabilities.

    Evidence to inspect: Transitions include communication, handoffs, risk protection, and organizational review.

    Capability map and its role here：Manager of managersDifferentiating here
Human competitivenessView progression
  1. Makes careful decisions under high uncertainty and competing interests, owning consequences and correction.

    Evidence to inspect: Decisions account for long-term risk, ethics, and counterevidence, not only short-term metrics.

    Capability map and its role here：Product judgmentDifferentiating hereIntegrityDifferentiating here
  2. Builds organizational trust and candor so information travels upward and bad news surfaces early.

    Evidence to inspect: Risks from different levels reach decisions and commitments remain transparent.

    Capability map and its role here：CommunicationDifferentiating hereFeedbackDifferentiating here
  3. Turns reviews and external change into organizational capability renewal rather than one-off action items.

    Evidence to inspect: Practices evolve with evidence and learning transfers across teams.

    Capability map and its role here：Learning transferDifferentiating hereStructured reflectionDifferentiating here
  4. Builds independent feedback and checks on major people and resource decisions to prevent concentrated information and interests.

    Evidence to inspect: Escalation, dissent, and correction mechanisms are demonstrably usable.

    Capability map and its role here：BoundariesDifferentiating here
  5. Maintains truthful information and decision quality through major failure or prolonged crisis and rebuilds organizational recovery capacity.

    Evidence to inspect: Crisis reviews explain recovery pacing, support arrangements, and mechanism changes.

    Capability map and its role here：Resilience and recoveryDifferentiating here