Mini-MBA in HR — capstone: synthesise your own HR operating system

A library of articles, no matter how good, is not the same as a synthesis. The capstone is the synthesis. You force yourself to make decisions, take positions, and commit them to paper. That is what a Mini MBA actually buys you in a classroom — and what you can manufacture for yourself here, in four hours, if you are willing to write your own thinking down.

Why a capstone exists

In real Mini-MBA programs the capstone matters more than any single course, because it is the only assignment that requires integration. You cannot copy-paste anyone else's. You cannot half-do it. Every decision in the document reveals what you actually believe about how HR should work — which is exactly the gap between knowing a model and being able to use it.

Most HR pros never do this. They read books, attend conferences, save articles. The reading rarely consolidates into a coherent operating point of view. The capstone closes that gap in a single sitting. The output is useful; the writing is the real value.

The deliverable, defined precisely

A 5-page document titled 'My HR Operating System'. No template — your structure, your voice. Five sections, roughly one page each. Readable in 10 minutes by another HR leader. Clearly distinct from anyone else's version: if a peer can't tell yours apart from a generic playbook, you haven't gone deep enough.

The 5 sections, with prompts

The 4-hour writing process

1. Hour 1 — Section 1 (strategy on a page). The hardest section. Most of the synthesis lives here. Resist the urge to polish; finish the boxes.
2. Hour 2 — Sections 2 and 3 (principles and rhythm). These are mostly recall and decision-making, not invention. Write fast.
3. Hour 3 — Sections 4 and 5 (metrics and learning plan). Be honest about what you actually track and what you'll actually do.
4. Hour 4 — Re-read the whole thing in one sitting. Cut 20% of the words. Ask: does this document say something a generic HR playbook doesn't? If not, find the place to be more specific.

Peer review — where the actual learning happens

Find one peer (inside or outside your company) and trade documents. 45 minutes each way: read, ask 5 hard questions, push back. The peer review is where the real learning lands, because someone who didn't write your doc can see the unargued assumptions inside it.

• Best peers: someone at similar seniority but different industry. Different enough to spot blind spots, similar enough to engage with the substance.
• Worst peers: your direct boss (politics distort feedback) or your direct report (incentives distort feedback). Pick laterally.
• Best questions to ask of someone else's doc: 'What would have to be true for this strategy to fail?' 'Which principle do you think you'll break first?' 'What's the metric you should be tracking but aren't?' 'Where are you being too modest?'
• Best questions to ask of your own doc after their feedback: 'What surprised me?' 'What did I defend hardest, and why?' 'What changed my mind?'

Examples of strong sections

• Strong principle: 'We never run a re-org without first updating the comp bands and leveling rubric that support it. Lesson learned 2023.' Specific, dated, and clearly reflects experience.
• Weak principle: 'We value people.' Means nothing operationally.
• Strong metric: 'Voluntary attrition in engineering, target 12% (currently 17%), refreshed monthly, owned by VP Eng + me.' Concrete, owned, actionable.
• Weak metric: 'Engagement score.' Which one? What target? On what cadence? Who acts on it?
• Strong learning bet: 'Deepen people-analytics skills via the [specific course] by Q2; co-design one causal analysis with our data team by Q3.' Specific, calendared, testable.
• Weak learning bet: 'Read more about AI.' Won't survive contact with a busy quarter.

FAQs