Dependency Risk

What it works from

• Role profiles and responsibility descriptions
• Process documents and operating procedures
• Organisation charts and reporting structures
• Team data on staffing, workload and responsibilities

What you get back

• Dependency risk diagnostic report
• Map of critical activities, systems, relationships and decisions to the people who hold them
• Risk rating and supporting evidence for each dependency
• Findings on undocumented knowledge and workload concentration lower coverage risks

Why this is expensive by hand

Key-person dependencies are often hidden across role descriptions, informal responsibilities and established working relationships. In practice it shows up as reviewing business continuity risks: reveals critical activities, systems and relationships that rely on a single person. Provides risk ratings and practical cover options to support continuity planning. It is the kind of work that decides whether a recommendation survives scrutiny — and the kind that quietly eats 1–2 weeks of senior time whenever it comes round.

How this Skill produces it

As a Skill, the work is already sequenced. You bring the evidence, and the run produces dependency risk diagnostic report plus map of critical activities, systems, relationships and decisions to the people who hold them. The criteria, ordering and review points that make the answer trustworthy are encoded in the Skill itself — which is the difference between a structured method and a prompt someone pastes in. In effect, 1–2 weeks of senior time compresses into ~15 minutes — and the output is comparable across clients, quarters and colleagues instead of shaped by whoever ran it.