note
The constraint.
On the job coach dashboard, every intern on shift is placed in exactly one of four status cards: Doing well, Needs support, Struggling, or All interns. Tap the card, see who's in it. An intern appears in one card at a time. Never two. Never zero.
That sounds obvious. It wasn't always how it worked.
How it started.
The first version had separate counts for each status, but interns could be in multiple categories at once. A coach could flag someone as "needs support" without removing the existing "doing well" tag. The intuition was: maybe someone is broadly doing well but needs help with one thing.
What we observed in practice: when an intern was in two states at once, coaches didn't know what to do about it. They didn't know whether to escalate, monitor, or move on. The dashboard had become ambiguous about what it was telling them, and ambiguous dashboards get ignored.
The rewrite.
We made the status cards mutually exclusive and exhaustive. An intern is in exactly one bucket at a time. When a coach taps "I'm on it" on a struggling intern, the intern doesn't just leave the "Struggling" bucket — they actively move to "Doing well." The mental model is now: where is this person right now in the day?, not what tags are attached to this person?
What this enforces.
The constraint forces a useful behaviour: when an intern's situation changes, the coach moves them. They don't just add a flag. They make a decision about which state best describes where the intern is right now. That decision is the actual value of the dashboard.
It also means the count on each card is meaningful. Five interns in "Doing well" means five interns are, right now, doing well. Not five interns who have ever been doing well at some point today. The number reflects the present, not the history.
The "All interns" card.
The fourth card is a deliberate escape hatch. Sometimes a coach just wants to see the whole cohort, not filtered. The "All interns" card sits alongside the other three but behaves differently — it shows everyone regardless of status. We resisted the temptation to make it "neutral" status; it's not a status at all, it's a view.
The principle underneath.
Every dashboard we build asks the same question: what decision is this view supposed to support? Status cards on the coach dashboard support one decision: who needs my attention right now? Anything that makes that decision harder — overlapping categories, ambiguous tags, accumulated history — is design debt we shouldn't take on.