Annual or quarterly planning
Cascade a strategy document into owned, dated objectives without a week of workshops to get the first draft.
— Organisation & Workforce
Decomposes a strategy document into owned, dated objectives and key results, then runs a dependency pass to expose the critical path and capacity conflicts.
2–3 days → ~15 minutes
For one complete, review-ready pass
No coding required
— USE CASES
Cascade a strategy document into owned, dated objectives without a week of workshops to get the first draft.
Expose the key results that cannot all happen at once before commitments are published.
Identify owners carrying more critical-path work than they can deliver in the horizon.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Ambiguities about the organisation in scope are resolved with you up front, so the run does not quietly assume the wrong scope.
Findings on the organisation in scope are written up as a document that reads like professional output, with each claim tied back to a role.
Each role is assessed against explicit criteria you control, so the same standard is applied across the organisation in scope on every run.
Facts and fields are lifted out of org data and role documentation and held in a consistent shape, role by role.
Most OKR cascades fail on dependency, not on drafting. Annual or quarterly planning is the typical trigger — cascade a strategy document into owned, dated objectives without a week of workshops to get the first draft. Get it right and the conclusion holds up in the room; get it rushed and it gets picked apart. Either way it costs roughly 2–3 days of experienced attention.
Skillsize turns that work into a Skill: you supply the material, and what comes back is objectives and key results with owners and dates, with a dependency map and critical path. 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, 2–3 days of senior time compresses into ~15 minutes — and the output is comparable across clients, quarters and colleagues instead of shaped by whoever ran it.
Strategy → OKR cascade + dependency map exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Redesigns workflows and roles around the practical use of AI, producing a board-ready plan with task-level recommendations, costed capacity gains and clear workforce implications.
Keeps a standing read on the risk universe in scope, working through risk registers, controls and policy documents on a regular cycle to show where each risk stands, what has moved since the last run and which items now need an owner's attention.
Matches available consultant capacity against the work coming down the pipeline each week, showing where people are about to sit idle, where demand will outstrip the skills you have and which pairings genuinely fit.
Runs a recurring skills survey across the workforce on a set cycle, building a living view of skills and utilisation by department that leadership can track month over month.
Ranks candidate locations against weighted workforce and business criteria, tests how cost assumptions affect the result, and produces a board-ready recommendation with a traceable evidence base.
Reviews a workforce metrics pack and states what the measures actually imply, rather than restating the numbers.