Leadership Review
Use this workflow when an engineering leader needs a concise, decision-oriented review of an initiative, portfolio, team operating rhythm, launch, AI-assisted engineering rollout, or delivery risk.
Lead with the decision or risk that needs attention. Separate facts, assumptions, evidence confidence, risks, decisions, owners, dates, and follow-up actions. Do not turn activity measures into individual productivity scores.
Select The Review Cadence
- Use a weekly review for flow, blockers, near-term risks, and owner/date actions.
- Use a monthly review for trends, operational health, portfolio drift, dependencies, and capacity.
- Use a quarterly review for strategy, investment allocation, organization design, and stop-or-defer decisions.
Review Shape
Frame the decision.
- State the expected business or customer outcome, decision owner, deadline, and why the decision matters now.
- Name non-goals and constraints.
Assess evidence and confidence.
- Separate observed facts, reported signals, and assumptions.
- Rate confidence in decision-critical evidence and state what would change the recommendation.
- Prefer trends and system outcomes over isolated snapshots or activity counts.
Review execution and operating health.
- Assess delivery confidence, quality, reliability, security/privacy, performance, operational readiness, customer impact, and support burden.
- Identify the limiting constraint and any hidden operational or interruption work.
Reconcile portfolio and capacity.
- Compare committed work with actual capacity and cross-team dependencies.
- Recommend what to continue, accelerate, reshape, defer, or stop.
- Make every tradeoff and displaced investment explicit.
Make the decision.
- Compare viable options, including reversibility, blast radius, and cost of delay.
- Identify the decision maker and distinguish reversible from difficult-to-reverse choices.
- Capture the result in a decision log with rationale and review trigger.
Secure follow-through.
- Convert the decision into owner/date actions with evidence of completion.
- Record risks with likelihood, impact, mitigation, owner, and trigger.
- Set the next review date and the signals that should cause earlier escalation.
Output Contract
Return:
- a concise executive summary led by the decision or highest-severity risk;
- an evidence and confidence table;
- options, recommendation, and explicit tradeoffs;
- a decision log and risk register;
- a follow-through table with owner, due date, completion evidence, and review trigger.
1---2name: leadership-review3description: Run evidence-based engineering leadership reviews across strategy, portfolio and capacity, delivery, quality, architecture, launch readiness, security risk, AI-assisted engineering adoption, organizational health, and follow-through.4license: Apache-2.05---67# Leadership Review89Use this workflow when an engineering leader needs a concise, decision-oriented review of an initiative, portfolio, team operating rhythm, launch, AI-assisted engineering rollout, or delivery risk.1011Lead with the decision or risk that needs attention. Separate facts, assumptions, evidence confidence, risks, decisions, owners, dates, and follow-up actions. Do not turn activity measures into individual productivity scores.1213## Select The Review Cadence1415- Use a weekly review for flow, blockers, near-term risks, and owner/date actions.16- Use a monthly review for trends, operational health, portfolio drift, dependencies, and capacity.17- Use a quarterly review for strategy, investment allocation, organization design, and stop-or-defer decisions.1819## Review Shape20211. Frame the decision.22 - State the expected business or customer outcome, decision owner, deadline, and why the decision matters now.23 - Name non-goals and constraints.24252. Assess evidence and confidence.26 - Separate observed facts, reported signals, and assumptions.27 - Rate confidence in decision-critical evidence and state what would change the recommendation.28 - Prefer trends and system outcomes over isolated snapshots or activity counts.29303. Review execution and operating health.31 - Assess delivery confidence, quality, reliability, security/privacy, performance, operational readiness, customer impact, and support burden.32 - Identify the limiting constraint and any hidden operational or interruption work.33344. Reconcile portfolio and capacity.35 - Compare committed work with actual capacity and cross-team dependencies.36 - Recommend what to continue, accelerate, reshape, defer, or stop.37 - Make every tradeoff and displaced investment explicit.38395. Make the decision.40 - Compare viable options, including reversibility, blast radius, and cost of delay.41 - Identify the decision maker and distinguish reversible from difficult-to-reverse choices.42 - Capture the result in a decision log with rationale and review trigger.43446. Secure follow-through.45 - Convert the decision into owner/date actions with evidence of completion.46 - Record risks with likelihood, impact, mitigation, owner, and trigger.47 - Set the next review date and the signals that should cause earlier escalation.4849## Output Contract5051Return:5253- a concise executive summary led by the decision or highest-severity risk;54- an evidence and confidence table;55- options, recommendation, and explicit tradeoffs;56- a decision log and risk register;57- a follow-through table with owner, due date, completion evidence, and review trigger.
agent-packs