Training & Capability Building
Your second line is the control nobody designed. Every governance structure eventually rests on a manager’s judgement.
Operational capability is usually treated as a training problem and solved with a course. The failures it is meant to fix are not knowledge failures. A manager who escalates everything is not short of information; a manager who escalates nothing is not being brave. Both are responding to a system where the cost of raising something is higher than the cost of absorbing it quietly.
Four failure modes recur, and they are diagnosable rather than cultural. MIS without insight — a manager who can report the number but not tell you what it means. Reviews without closure — a meeting held every week that decides nothing. Escalation without ownership — the problem is passed on rather than passed up. And supervision without accountability — presence on site mistaken for control of it.
Twenty-one years in the Air Force and twenty-eight in field operations is where this comes from: the second line either holds under pressure or it does not, and the difference is almost always something structural that was never designed.
How I work it
Assess the second line against the four failure modes, using their own review meetings and escalation history rather than a questionnaire.
Programmes built on the actual failure mode — operational decision-making, review discipline, escalation judgement, accountability and span of control — delivered against your own cases, not case studies.
Coaching after the programme, a capability scorecard reviewed with each manager, and the reviews observed rather than reported on.
Tools and frameworks
Placed against the stage each one serves, and against the artefact it leaves behind. A framework that produces no artefact is a word.
| Framework or instrument | Analyse | Act | Adhere | Artefact it produces |
|---|---|---|---|---|
| Manager capability assessment, four failure modes | ● | – | – | Capability profile per manager, with the mode named |
| Review-meeting observation | ● | ○ | – | Observation record — decisions per meeting, closure rate |
| Escalation history analysis | ● | ○ | – | What was escalated, what was absorbed, and what it cost |
| Programme design against real cases | ○ | ● | ○ | Eight programmes, built on your incidents not case studies |
| Enterprise coaching, ILA-certified | ○ | ● | ● | Coaching record per manager against the capability profile |
| Capability scorecard and cadence | – | ○ | ● | Scorecard reviewed with each manager, quarterly |
The responsibility matrix — capability as a control
The artefact the Act stage produces. “As found” is what a typical intake looks like — not a description of your operation.
| As found — typical intake | As governed — on exit | |||
|---|---|---|---|---|
| Control activity | Accountable | Evidence | Accountable | Evidence |
| Defining required capability per role | Job description | JD on file | Function head | Capability standard per role, with observable behaviours |
| Assessing the second line | Annual appraisal | Rating | HR with function head | Capability profile against the four failure modes |
| Review-meeting discipline | Held weekly | Attendance | Chair of the review | Decisions per meeting and closure rate |
| Escalation judgement | Individual instinct | None | Operations head | Escalation criteria, written and known |
| Post-programme retention | Feedback form | Happy sheet | HR / L&D | Behaviour observed on site 90 days later |
A scoped, paid assessment of the second line against the four failure modes — using their own reviews, escalations and decisions as the evidence.
Monthly coaching for named managers, with their reviews observed rather than reported on.
What good looks like
The state a completed engagement leaves behind — the definition of done we agree at the start. Not a result already achieved.
| Area | What good looks like | How you would know |
|---|---|---|
| Standard | Each role has a capability standard written as observable behaviour, not as a competency word. | Capability standard |
| Assessment | Managers are assessed on their own decisions and reviews, not on a questionnaire. | Capability profile |
| Reviews | Every review meeting ends in decisions with owners, and the closure rate is known. | Decisions log |
| Escalation | What must be escalated is written down, and absorbing it quietly is not an option. | Escalation criteria |
| Retention | The behaviour is still observable on site 90 days after the programme. | 90-day observation |
Each role has a capability standard written as observable behaviour, not as a competency word.
Managers are assessed on their own decisions and reviews, not on a questionnaire.
Every review meeting ends in decisions with owners, and the closure rate is known.
What must be escalated is written down, and absorbing it quietly is not an option.
The behaviour is still observable on site 90 days after the programme.
Thirty minutes, and you will know whether this is worth pursuing
A structured conversation about where your operation is losing money, not a sales call. Mon–Sat, 09:00–18:00 IST, on Google Meet, in English or Hindi. Nothing is required from you in advance.
Book a Capability DiagnosticRate your second line against four failure modes: MIS without insight, reviews without closure, escalation without ownership, and supervision without accountability.
↓ Download · PDF, 3 pp