Day 14. Community leader has refused site access. Materials arrive in 72 hours.
Palette & type system.
Brand hexes lifted straight from Qquench guidelines. Three families: Fraunces for display, DM Sans for body, DM Mono for chips, badges, and instrumentation.
Every instructional container floats.
Three dots, centred mono title, hairline border, soft shadow. On hover the whole window rises 3px and the close dot darkens. This is the only chrome we use for primary content.
"Day 14. The materials are crossing the border. You don't have site access yet."
Hover this window — the whole container lifts 3px and the shadow blooms. The close dot darkens to confirm hit area.
Which PRINCE2 principle is being tested when a Project Manager raises an Exception Report?
Window chrome is identical to scenario containers — what changes is the chip in the body, never the frame. Consistency is non-negotiable.
Five modules, each its own folder colour.
Three-layer construction: tab, back panel, content peek, front panel. Spring easing on hover — front slides down, peek floats up. Tactile, instantly readable.
Six learners. Six field lenses.
Each card is a UNOPS field credential — lanyard hole, gradient avatar, location pin, italic challenge quote, status chip. Hover for the holographic shine sweep.
Contractor filed a variation order exceeding tolerance. Donor wants answers.
Government partner is over-reporting outputs. Mid-term review in 3 weeks.
Three projects show the same early-warning pattern. Nobody is connecting the dots.
Security incident. Site suspended. Donor wants written response in 2 hours.
You were procurement. Now you are Acting PM. Project Board meeting in 2 weeks.
Marginalia, tilted on purpose.
Used for principle callouts, field tips from archetypes, reflective prompts. Never primary content. Alternate rotations. They straighten and lift on hover.
"Manage by exception" — set tolerances, then only escalate when they're breached. Saves everyone's calendar.
The first 30 minutes of any incident are about information triage, not solutions.
Outputs are what you produce; outcomes are what changes for someone because you produced them.
Recall a time you reported activity when you should have reported outcome. What were you protecting?
Pattern-spotting across a portfolio is the highest-leverage PMO skill. Single projects rarely surprise you twice.
Six dimensions: scope, time, cost, quality, benefits, risk. Lose track of any one and you lose your defence.
Highlight Report — periodic update from PM to Project Board, summarising stage progress against plan.
For UNOPS, the Project Board is typically the Donor + Programme Manager + Country Director.
Read the situation, commit to a choice.
Pull-quote in italic Fraunces, scenario body in DM Sans, choices that slide right on hover. The Next button stays disabled until you commit. Post-it sidebar carries supporting PRINCE2 context.
"No project survives first contact with reality unchanged."
You are at the end of Stage 1. Your tolerance band on cost is ±5%. The Stage 1 actuals come in at +7.2%. The donor liaison wants to see "stable burn" before the next disbursement. Your Project Board meets in 6 days.
What do you do next?
An Exception Report is not a confession — it's a forecast. You're showing the Board the future they need to choose against.
Cost tolerance band on this stage: ±5%. Current variance: +7.2%. Breach confirmed.
"Donors don't want surprises in PowerPoint. They want decisions in writing."
Four dials that respond to choices.
After each scenario the dials animate. Schedule (blue), Budget (yellow→orange), Stakeholder Trust (teal→blue), Risk (red→cherry). Status dot + percentage make state legible at a glance.
Where you are, where you're going.
Step nodes — done (filled blue), active (pulsing ring), locked (grey). Connector fills as you advance. Track-name chip on the right.
37 terms, three frameworks.
Click any term to expand the definition. Items slide right on hover and shift the left border to teal. Filter chips at top toggle framework scope.
A formal report from the Project Manager to the Project Board when a forecast variance is predicted to breach an agreed tolerance. Contains: cause, impact, options, recommendation.
Templates, downloadable.
Each card lifts 3px on hover, border shifts to primary blue. Coloured icon box signals document type. File format spelled out in DM Mono.
Dark mode. Live simulation.
Three-panel layout: inbox triage, live dashboard, document tray. Countdown timer, archetype badge. Background is Deep Sea — never the light theme.
Pause without losing the thread.
Triggered from the ⋯ in the nav bar. Dark overlay on the grid, four options. Auto-save is non-negotiable — learners can leave and return mid-scenario without losing state.
"You can leave at any time. The course remembers exactly where you were."
Click the button to open the live overlay. Tap outside the panel or hit Esc to dismiss.
The vocabulary, at a glance.
Every chip, badge, and button used across screens. Buttons rise on hover. Chips never. Status chips always carry a 5px coloured dot.