Operational Leadership Capability Framework & Self-Assessment

Purpose

This framework helps teams define, measure, and develop the leader behaviors that sustain continuous improvement. It translates the high‑level hunger — "Equip leaders with the routines, coaching skills, and metrics to sustain improvement" — into observable competencies, practical assessment questions, suggested development activities, and coaching checkpoints that teams can apply immediately.

How to use this framework

1. Read the competency definitions and behavioral indicators to align on what good looks like in your context.
2. Use the 20‑question self‑assessment to establish a baseline for a leader, team, or site.
3. Score and interpret results using the guidance below to identify priority development areas.
4. Create short development plans using the suggested activities and coaching checkpoints; repeat the assessment regularly to measure progress.

Competency areas (overview)

The framework groups leader capability into six practical competency areas. Each area contains a brief definition, observable behaviors, coaching checkpoints, and suggested development activities.

1. Daily Management & Huddles

Definition: Run short, predictable routines (daily huddles, visual reviews, escalation rules) that make work visible, stabilize operations, and enable quick problem escalation.

• Starts and ends daily huddles on time with a focused agenda.
• Uses visual boards to show current targets, variances, and follow‑ups.
• Escalates issues with agreed ownership and deadlines.

• Observe one daily huddle each week and give feedback on structure and focus.
• Review visual board accuracy each shift change.
• Verify that escalations have owners and due dates in the follow‑up list.

• Facilitation practice: run a 10‑minute huddle and receive peer feedback.
• Visual management workshop to design or simplify the board.
• Role play escalation conversations and handoffs.

2. Problem‑Solving Coaching

Definition: Coach teams through structured problem solving (root cause thinking, containment, countermeasures, learning) rather than providing quick fixes.

• Asks clarifying questions to help teams define problems before proposing solutions.
• Ensures experiments are documented and results shared.
• Checks that corrective actions address root causes and are verified.

• Attend a problem‑solving session monthly and coach the use of A3 or 5‑why techniques.
• Review action lists from recent problems and confirm verification steps.
• Spot‑check whether learnings were standardized into procedures or training.

• A3 writing and coaching practice sessions.
• Shadowing a senior coach during a root cause analysis.
• Facilitated experiment design workshop (plan–do–study–act).

3. Change Leadership

Definition: Lead transitions so improvements stick — align stakeholders, remove barriers, and reinforce new ways of working.

• Communicates the purpose and expected outcomes of change clearly.
• Identifies and works with key influencers to spread adoption.
• Allocates time and resources to stabilize new processes after change.

• Review stakeholder map and adoption risks for each change initiative.
• Confirm that training or standard work updates occurred at the point of change.
• Check early metrics to ensure the change is delivering expected results.

• Change management micro‑course focused on frontline application.
• Practice brief leader communications and feedback loops.
• Design adoption plans with measurable milestones.

4. KPI Literacy

Definition: Understand, interpret, and act on operational KPIs so teams can make predictable, measurable improvements.

• Explains what each KPI measures and why it matters.
• Distinguishes between lagging and leading indicators and acts on both.
• Uses data to direct daily discussions and prioritize efforts.

• Review how KPIs are displayed and whether teams can explain recent variances.
• Confirm that corrective actions link to measurable KPI changes.
• Check for root cause conversations when trends change, not only at month end.

• Practical KPI workshop using last month’s data to find improvement opportunities.
• Data storytelling practice to improve briefings at huddles.
• Hands‑on exercises distinguishing signal from noise.

5. Safety Leadership

Definition: Create and sustain an environment where safety is visible, prioritized, and integrated into daily decision‑making.

• Leads safety conversations in regular meetings and follows through on concerns.
• Responds to near‑misses with inquiry and system fixes, not blame.
• Allocates time and resources to address high‑risk issues quickly.

• Attend safety walkdowns and model curiosity over fault finding.
• Review near‑miss reports to ensure systemic actions are taken.
• Confirm PPE, permit, and LOTO compliance at random checks.

• Safety coaching simulations for difficult conversations.
• Root‑cause training focused on human and system factors.
• Cross‑functional safety improvement projects.

6. Talent Development

Definition: Build capability in others through structured on‑the‑job development, coaching, and deliberate practice.

• Creates brief learning objectives for shifts and validates competence.
• Delegates stretch assignments with clear expectations and coaching.
• Tracks development progress and adjusts plans based on observed gaps.

• Verify that each team member has a short development plan linked to operational needs.
• Observe on‑the‑job coaching interactions weekly and provide feedback.
• Ensure handovers include quick skill checks for critical tasks.

• Structured on‑the‑job coaching program with coach competency rubric.
• Shadowing and reverse‑coaching rotations.
• Micro‑learning and deliberate practice sessions for core skills.

20‑question self‑assessment (printable)

This short self‑assessment has four questions mapped to each competency area (4 competencies × 5 areas = 20). Use the following response scale when scoring: 0 = Never / Not yet, 1 = Sometimes, 2 = Often, 3 = Consistently. Total score range: 0–60.

1. Daily huddles start and end on time with a focused agenda. (Daily Management)
2. Visual boards reflect current performance and follow‑ups. (Daily Management)
3. Escalations are owned and tracked to closure. (Daily Management)
4. I facilitate huddles that result in clear next steps. (Daily Management)
5. I coach teams to define problems before suggesting solutions. (Problem‑Solving)
6. My team documents experiments and learns from outcomes. (Problem‑Solving)
7. Corrective actions address root causes and are verified. (Problem‑Solving)
8. I enable others to use a structured problem‑solving method. (Problem‑Solving)
9. I clearly explain the purpose and expected outcomes of changes. (Change Leadership)
10. I identify and engage key influencers for adoption. (Change Leadership)
11. I ensure resources are allocated to stabilize new ways of working. (Change Leadership)
12. I monitor early adoption metrics and act quickly on gaps. (Change Leadership)
13. I can explain what our top operational KPIs measure and why. (KPI Literacy)
14. I use leading indicators to prevent foreseeable issues. (KPI Literacy)
15. I focus discussions on data‑driven causes rather than symptoms. (KPI Literacy)
16. I support the team to translate KPI changes into actions. (KPI Literacy)
17. I lead meaningful safety conversations and follow through on concerns. (Safety)
18. I treat near‑misses as learning opportunities and fix systems. (Safety)
19. I model the safety behaviors we expect from the team. (Safety)
20. I check that risk controls are used and effective. (Safety)
21. I create short development objectives and review them regularly. (Talent Development)
22. I assign stretch tasks with coaching and follow up. (Talent Development)

Scoring guidance and interpretation

Calculate the total (0–60). Also calculate average per competency (0–12). Use these thresholds as a starting point:

• 0–20 (Emerging): Focus immediate coaching on the top two lowest competency averages. Start with daily management and problem‑solving basics.
• 21–40 (Developing): Create short development sprints (30–60 days) with specific coaching checkpoints and metrics.
• 41–60 (Established): Reinforce consistency, scale practices across teams, and coach others to adopt the behaviors.

Suggested learning modules and resources

• Short course: Effective Daily Management and Huddles (2–3 hours + practice).
• Coach the Coach: Practical Problem‑Solving Facilitation (workshop + A3 practice).
• Leading Change on the Shop Floor: Adoption & Standardization.
• KPI Clinic: Practical Data Use for Frontline Leaders.
• Safety Leadership: Conversations, Near‑misses, and System Fixes.
• On‑the‑Job Coaching Toolkit: Rubrics, Scripts, and Micro‑lessons.

Suggested KPIs and evidence of leader capability

• % of daily huddles run as scheduled (observed fidelity).
• % of corrective actions verified and sustained after 30 days.
• Adoption rate of new standard work after change (measured at milestone).
• Time to closure for escalated issues.
• % of team members with current development objectives and evidence of coaching.
• Number of meaningful near‑miss investigations with system actions.

Practical rollout options

1. Run the printable assessment to create a baseline for leader cohorts.
2. Create 30–60 day development sprints focusing on the top 1–2 competencies per leader.
3. Use weekly coaching checkpoints and a simple visual tracker for development actions.
4. Repeat the assessment quarterly to measure growth and adjust coaching plans.

Where this lives

Use this resource to seed capability building programs in Deck 1111. The material is intentionally modular so individual modules (e.g., huddle facilitation, A3 coaching, KPI clinic) can be extracted and adapted for local use.

Next steps to increase value (capability suggestions)

This Framework is intentionally actionable but will be substantially more useful if converted to an interactive, saveable assessment that stores results and tracks progress. Recommended enhancements are described below.