Volume trend
Week-on-week activity — baseline health.
DATA SIMULATION · INDIVIDUAL + TEAM · 10–50 PLAYERS
You have the data.You have 20 weeks.When do you act?
Not only what you decide — when you decide, and what you let pass while waiting for certainty.
- Format
- Individual + Team
- Duration
- 2–3 hrs
- Players
- 10–50
- Skill
- Data-driven decisions
Quick answer
20 Weeks is Tryitowl's project management simulation: you receive noisy data across twenty weekly decision points and must choose when to act, not only what to decide. It trains timing judgement and escalation habits — the gap between analysis and commitment.
Data doesn't decide. People do. Often too late.
74%
of executives want more data before deciding (MIT, 2024)
38%
miss the optimal window waiting for it
20
weeks — each with a cost to waiting
It rewards the player who knew when the data was good enough — not the most analytical deck.
Data literacy teaches how to read dashboards — rarely when to stop waiting and act.
20 Weeks pairs live data, fixed targets, and twenty sequential weeks. The window narrows; timing is scored alongside accuracy.
How the session runs
Structured phases keep energy and learning tight — from brief through play to debrief.
Block 1 · W1–5
The Baseline
Sparse data, ambiguous trends — expensive quiet if nobody moves.
Signals easy to miss
Block 2 · W6–10
The Signal
Divergence appears — act now or rationalise it away until week 15.
Act or wait
Block 3 · W11–15
The Pressure
Targets at risk — measured recovery beats reactive lurches.
Cost of lateness
Block 4 · W16–20
The Reckoning
Final levers — individual report on decisions, timing quality, and optimal path comparison.
Outcome report
Dashboard moments (examples)
- Option: Act on partial data now.
- Option: Wait for confirming samples.
Consequence: Optimal window can close by week 14.
The five data streams
Conversion rate
Leading pipeline signal — easy to underweight early.
Anomaly flag
One-off events that may or may not matter.
External index
Market signal often ignored until too late.
Team input
Qualitative ground truth — competes with charts.
What the dashboard judges
Target achievement
% weekly hits
Decision timing
Early / on-time / late
Signal response rate
Speed on detectable shifts
Recovery cost
Ground lost to late corrections
Archetypes
The Analyst
Waits for certainty — misses windows.
The gut player
Acts early — high variance, occasional brilliance.
The balanced executor
Threshold rules — consistent.
The overcorrector
Waits, then swings big — penalised.
Facilitator debrief
- Which week did you realise you were waiting too long?
- What signal did you dismiss that later mattered?
- Where did timing beat perfect analysis in your decisions?
- What does this mirror in your quarterly planning rhythm?
- One timing rule you'll adopt next cycle — specific.
Also in the experience
- Facilitator-led debrief tied to platform data
- Digital delivery, configurable cohort sizes
Frequently asked questions
What is the 20 Weeks project management simulation?▼
A facilitator-led data simulation where participants interpret shifting metrics across twenty weekly rounds and decide when to intervene. The design measures timing and conviction under incomplete information — not spreadsheet accuracy alone.
Who is 20 Weeks best for?▼
Project leaders, product owners, and operational managers who delay decisions while waiting for certainty. Common cohorts include PMO communities, transformation teams, and leadership programmes building execution discipline.
What skills does 20 Weeks develop?▼
Decision timing, signal versus noise discrimination, escalation judgement, and team alignment when data is ambiguous. Debrief maps patterns to real roadmaps, stakeholder updates, and incident response.
How long does a 20 Weeks session run?▼
Most enterprise sessions run two to two-and-a-half hours including briefing, simulation rounds, and facilitated debrief. Virtual and in-person formats are available.
Let's talk about your team
Book a facilitated session — we'll match group size, format, and outcomes to the right simulation.