The Tuesday report
A November 2024 account of the weekly delays report at Ankur Warikoo. The 348 tasks and 20 delays describe the week discussed in the original post.
Every Tuesday, I send our team at Ankur Warikoo a report that would make most managers uncomfortable: a transparent list of everyone’s delays, visible to all.
Most companies treat delays like secrets — hidden in private messages, hushed in meetings, or smoothed over in reports. We put them on full display.
It sounds harsh until you see the results: Last week, our team handled 348 tasks. Total delays? Just 20.
The surprising truth is that exposing delays creates excellence — not through pressure, but through systems.
Here’s what we learned from building our transparency machine:
➤ Most Teams Solve the Wrong Problem
When tasks start slipping, companies often react with more meetings, check-ins, and “urgent” follow-ups. They try to solve an information problem with attention. It doesn’t work.
➤ Transparency Over Authority
Every task lives in Asana. Every delay is tracked. Every Tuesday, everyone sees everything. There’s no need for constant updates or reminders — the system handles it.
➤ Excellence Lives in the Margins
We build buffers and failsafes into every process. A two-day delay doesn’t derail our content engine because our systems are designed to absorb minor setbacks. When you expect imperfection, you create space for consistency.
➤ Data, Not Drama
Delays aren’t failures — they’re data points. If someone consistently delays certain tasks, it’s a sign to refine processes or provide training. We use transparency as a tool for optimization, not blame.
This level of transparency scares most leaders. They worry it’ll hurt morale or foster blame.
The reality? It builds ownership. When everyone can see the machine working — or where it’s slipping — they become invested in making it run better.
Most content operations run on chaos and hope. We built ours on systems and transparency.
The result? A team that doesn’t need constant management, because they can see exactly what needs to be done.
Want to know the real secret to scaling content? Stop hiding problems. Build a machine that makes them impossible to ignore — and watch them start solving themselves.