Green, yellow, red status

Send status even when nothing dramatic happened. Silence makes stakeholders invent stories — usually worse than reality. A boring green update with next week's plan still earns trust.

Status is not a diary of tasks completed. It is a forecast of launch plus what you need from others. Pair it with written communication: short, concrete, active voice, one ask per message.

Walking through a yellow update

Template that works in Slack or email:

Status: YELLOW
Summary: Core export path in staging. Blocked on FraudSvc allowlist (ticket #4821, pinged Tue).
Done this week: Schema + streaming upload; flag wired.
Next week: Permissions + QA if unblock; else cut to internal-only milestone.
Asks: @fraud-oncall approve service account by Friday, or we slip self-serve by 1 week.
Risks: Vendor rate limit undocumented — spike Thursday.

• Green: on track for the committed milestone; no help needed.
• Yellow: at risk; you have a mitigation or a clear ask with a date.
• Red: will miss unless leadership changes scope, date, or priority this week.

Managers hate surprises more than bad news. Yellow on Tuesday beats red on the day before launch.

Keep a personal stuck list visible: three bullets max in the project channel topic or epic description. When something leaves the list, say so. Visibility of blockers invites help. Private stuckness invites surprise slips.

Compare two Fridays. Busy-green: "Shipped schema, flag, and tests. Lots of progress." Forecast-yellow: "Core path in staging. FraudSvc allowlist still open; if it misses Friday we cut to internal-only and slip self-serve one week. Ask: approve the service account by EOD." The first trains people to ignore you. The second lets them help.

Common mistakes

• Green as a social habit. You were busy, so you painted it green.
• No ask on yellow. At-risk without a date and an owner is just anxiety.
• Silence on quiet weeks. People invent a worse story.

Check yourself

You wrote a lot of code but the launch date just became unbelievable. What color?

Yellow or red. Green is about the outcome date, not the volume of work.

You will miss unless someone changes priority this week. What color, and when?

Red, this week — not the day before launch.

Key takeaways

• Status is green, yellow, or red about the outcome, with asks and dates.
• Yellow on Tuesday beats red the day before launch.
• Busy is not on-track. Green is a forecast, not a mood.
• Keep blockers visible so help can find you.

Further learning

Next: dependencies and unblocking.