The Servant Leader — Atlas Squad's First Six Weeks

A four-round, intermediate leadership simulation set inside Polder Digital B.V., a Rotterdam data-and-product consultancy (220 staff, ~EUR 34M revenue). You have just been promoted from star individual contributor into your first team-lead role, taking over the 8-person Atlas squad mid-flight: a contracted client acceptance milestone is due Friday 19 June — six weeks out — and slipping it triggers a EUR 180,000 penalty and threatens a EUR 2.4M renewal with Atlas's largest account, a Dutch bank. The squad is talented but strained. A fresh pulse puts engagement at 71 (down from 78 firm-wide), the meaningfulness score at 6.1/10, and turnover risk 'elevated' for 3 of 8 members. Three dilemmas hit at once: the strongest engineer (who owns the critical path) has gone quiet — an exit slips the milestone 3–4 weeks and costs ~EUR 95,000 to backfill; two high-potential mid-level members were promised ~40 hours of development time the crunch tempts you to cancel; and a previously solid engineer has missed sprint commitments because of a caregiving situation at home. Across four two-week rounds you (1) read the team — diagnosing the underlying need behind each dilemma rather than the symptom and choosing where to spend scarce one-on-one time; (2) empower or direct the disengaging star and decide whether the development promise survives pressure; (3) hold the underperformer's standard humanely — diagnosing cause before escalating and protecting well-being while keeping the bar — and allocate remaining capacity at the milestone; and (4) land the milestone and present the resolved outcome to a Polder partner. The math is built on Dirk van Dierendonck's servant-leadership model (empowerment, stewardship, humility, accountability) and his 2023–24 work linking servant leadership, meaningfulness and flow as an upward spiral. Each classic error measurably underperforms: directive-only pressure starts a downward spiral and triggers the exit that blows the milestone; empowerment-as-abdication lets the underperformer slide while the team watches; cancelling development burns two flight risks; escalating without diagnosing cause signals that struggle is punished; and one fixed style applied to an expert, two high-potentials and a struggling junior costs you on at least one. Four KPIs — team engagement, meaningfulness, performance index, and turnover risk — are tracked before and after, alongside the milestone outcome (hit, partial, or slipped) and the star's stay/leave decision.