Spans and layers

What it works from

• Org map, headcount or structure export
• Your span and layer targets
• Any scoping (function, entity, geography)

What you get back

• Computed spans, layers and ratios with outliers bucketed
• Named structural opportunities
• A table and report ready for an exec discussion

Why this is expensive by hand

Spans and layers analysis is arithmetic plus judgement, and the arithmetic is usually the part that gets fudged. In practice it shows up as cost and structure reviews: quantify layers, spans and manager-to-IC ratios before proposing a structural change. It is the kind of work that decides whether a recommendation survives scrutiny — and the kind that quietly eats 2–3 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 computed spans, layers and ratios with outliers bucketed plus named structural opportunities. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. Net effect: 2–3 weeks down to ~40 minutes, no drift between runs, and every conclusion traceable back to the evidence behind it.