Everything we run sits on one of three clocks. If a piece of work isn't on a clock, it isn't work yet — it's an idea in the backlog. This page is the whole system.
What happens when, and what it produces. Nothing else gets a standing slot.
Data lands Monday 09:00. Narrative written by 10:30. Meeting 11:00. Produces: a hypothesis and a countermeasure for each focus property — not a status update.
Each property through the P&L discrepancy tool. The month's one team focus is finished and signed off. New team focus named for next month.
Regional check against portfolio averages. Capex, location and contract decisions — the things a weekly meeting must never try to solve.
The sheet is the agenda. Sorted worst-first, so the running order is already decided before anyone speaks.
Nobody presents. Nobody reads cells aloud. Owners tick their open actions done or not-done while they read.
Actions marked overdue. One question each: what unblocks it?
Only properties whose review date has arrived. Did the number move — yes, no, or too early? A countermeasure that failed is a finding, not a fault.
Top of the sorted list, no active countermeasure. Owner gives the why, challenger pushes, room commits: hypothesis, countermeasure, review date.
Same complaint at three properties is a system problem, not three local ones. Then the scribe reads the commitments back.
Why the silent read: reading aloud runs about 150 words a minute, reading yourself about 250 — and eight people read at once instead of one at a time. Presenting the sheet is strictly the slowest option available.
Nobody just watches. Disengagement isn't an attitude problem — it's what happens when the format gives someone no job for 40 minutes.
Never your own property. Ask "why" until you reach a cause rather than a symptom — "guests complained about cleanliness" is a symptom; "the Friday turnover has 40 minutes for 6 units" is a cause.
You must push back at least once. Silence counts as not having done the job.
Writes the hypothesis, countermeasure, owner and review date into Asana during the meeting, not afterwards. Reads the commitments back out loud in the last two minutes.
Not written down = didn't happen.
Hard-stops each block at its minutes. Parks anything structural — capex, location, contracts — for the monthly instead of letting it run.
One property must never eat the hour.
Rotate all three every week and post the rota in the sheet. The point isn't ceremony — it's that a challenger who owns the property they're challenging will always go easy on it.
This is what stops the same property being diagnosed three weeks running while its fix is still in flight.
On the focus list, no countermeasure yet. Gets a full diagnosis.
Countermeasure open, review date not reached. Not discussed. Tick it and move on.
Review date reached. Did the number move? Worked, or new hypothesis.
Back above 8.0 for two weeks or more. Noted once, then off the list.
One rule decides the whole layout: sections hold what changes over a task's life; fields hold what it is. A task moves Backlog → WIP → Review. It never moves from "Major" to "Bonus" — that's an attribute, so it's a field.
Identical names to the property template, so there is nothing new to learn. The bundle already manages sections and mirrors each one to a tag, which is what makes section membership reportable and rule-triggerable.
| Section | Meaning |
|---|---|
| 00_Backlog | Not committed. No owner, no date. |
| 01_ready_for_action | Specced and ready to start. |
| 02_WIP | Actively being worked. |
| 03_Stakeholder | Waiting on someone outside the team. |
| 04_Approval | Waiting on a decision. |
| 05_Procurement_Deliveries | Ordered, waiting on delivery. |
| 06_review_and_qa | Done, being checked. |
| xx_Done | Closed on an outcome. |
Delete the old German sections (Hohe / Mittlere Priorität, In Bearbeitung, Zur Überprüfung, Blockiert, Abgeschlossen) — they mixed two taxonomies, restating the Priority field as columns. Also drop the stray To Dos section in the property template.
| Axis | Field | Values |
|---|---|---|
| Cadence | Tracker (exists) | Weekly · Quarterly · HSK Focus · Handover |
| Pillar | Typ (exists, multi) | Safety & Compliance · MNT · HSK · Guest Journey & Access · Product & Facilities · Commercial |
| Importance | Priority (exists) | High · Medium · Low — the bundle gate |
| Effort | Poker Score (exists) | number, written by the Ops Tagger |
| Stage mirror | d2d_stage (exists) | follows the section — bundle-maintained |
| Capacity | Commitment (ADD THIS) | Team Focus · Major · Bonus |
Commitment is the only new thing to build. Single-select, not a tag: tags allow several values per task, which makes "one Major per person" impossible to count. Everything else you need already exists on the property template.
| View | Setup | Answers |
|---|---|---|
| Pipeline | Board by section | Where is everything |
| Who's on what | Group by assignee, filter Commitment = Major / Bonus | What is everyone actually doing |
| Property focuses | Group by Tracker, sorted by project | What we're fixing, per property |
| By pillar | Group by Typ | Reporting |
| Workload | Asana Workload, effort = Poker Score | Who is genuinely overloaded |
Commitment counts how many; Poker Score measures how heavy. One Major worth 13 points is a bigger load than a Major and a Bonus at 3 each — which is why the capacity rule needs both.
| Trigger | Action | Why |
|---|---|---|
| → 02_WIP, no due date | Flag it | The report's overdue flag and the meeting's slippage block are dead without due dates. |
| → 06_review_and_qa | Notify + set review date | Starts the "did it work?" clock. |
| → xx_Done | Auto-create a follow-up due in 3 weeks: "Did this move the number?" | The one rule that structurally kills box-ticking — closing a task creates its own outcome check. |
| Added, no assignee | Notify | Triage gate, without needing a section for it. |
One Major, one Bonus, one team focus. That's the whole capacity rule — and the reason the backlog is allowed to be huge without being stressful. Open Berlin_Priorities
Ordered by what breaks the mechanism most if it stays missing.
Single-select: Team Focus / Major / Bonus. The only new field in the whole design — everything else already exists on the property template. Without it there is no capacity rule and no "who's on what" view.
Delete the German priority/status sections and the stray To Dos. Until this happens the board carries two taxonomies and the bundle's section→tag mirror reports on nonsense.
WIP-without-a-due-date → flag · Review → set review date · Done → auto-create the 3-week "did this move the number?" check. The third one is what makes closing on outcome automatic instead of a discipline problem.
It already writes Poker Score and the pillar. Priority is the field the bundle gates on, so letting the routine set it means tasks get pulled in on scored signal rather than manual guesses.
One per month, with a definition of done and a named owner, tagged Commitment = Team Focus. Otherwise it becomes everyone's optional extra and finishes never.