Skip to content
← Ritual Library

Weekly ritual

Early Signal

An eight-minute slot at the start of an existing weekly meeting where anyone can name one delivery risk — and the leader responds with help, an owner and a date.

Why it matters

In many teams, people stop raising concerns because the messenger got treated as the problem. Silence feels safer, so problems surface only after deadlines slip. Early Signal makes raising a risk an act of care for colleagues and customers — and the leader’s response, not the question, is what rebuilds trust.

How to run it

  1. Name one risk, or pass (0–2 min). Each person can surface one delivery risk. Passing is always fine.
  2. Clarify the help needed (2–4 min). What are you seeing, what do we know, and what help would change the situation?
  3. Agree an owner and a date (4–8 min). Record it as one row in the action log.
  4. The leader responds — in four moves:
    • Acknowledge: "Thank you for raising this before it became harder to fix."
    • Understand: "What are you seeing? What do we know, and what help would change the situation?"
    • Commit: "I will own this decision. We will come back to you by Thursday, even if the answer is still incomplete."
    • Close the loop: "Here is what changed, what did not, and why. Did our response help?"
  5. Respond within two working days (a suggested pilot rule — agree a realistic local standard before launch).
  6. Review after four sessions. Track risks raised before a missed commitment, response time and time spent.

Busy-week version: one short message per risk in the team channel — risk, impact and help needed — then an acknowledgement, an owner and a reply date in the same log.

Follow-through carries more weight than the script. Trust builds when people see the response change.

From the free playbook: Operationalising Rituals Using the Büdaya Framework — with the canvas, pilot plan and review signals to run it well.

Watch out for

  • People attend but stay silent — repair the leader’s response first, and offer a private route
  • Public blame, premature reassurance or promises the leader can’t keep
  • Actions piling up faster than leaders can handle — limit scope and clear the backlog before expanding

When not to use it

Urgent risks should still use normal escalation, and harassment or serious misconduct always needs a protected, private route — never a public ritual.

Sources

Keep exploring

Story

The Bank That Gave Junior Employees Permission to Challenge the Boss

How did DBS Bank turn meetings from a source of bureaucracy and silence into a catalyst for innovation? Discover MOJO, a simple ritual that empowered junior employees to challenge senior leaders, improved meeting effectiveness and helped lift employees' reported share of voice from 40% to 90%.

DBS BankFinancial Services · Singapore