Ship the feature set
Rooms, chat, scheduling — then chase performance later. Familiar roadmap. Risky first impression.
Case study · Product · Real-time
When “fast enough” is a business promise
You’re a student waiting for a counsellor. Every blank second feels like doubt. You’re the product owner: the session has to feel live — not “eventually consistent.”
Scene
A live student–counsellor session. The room is digital. The anxiety is real. Latency isn’t a metric here — it’s trust.
~100ms was not a vanity target. It was the line between “present” and “broken conversation.”
Before polishing UI chrome, prove the interaction feels immediate under real network messiness.
Many architectures could “work.” Only some could keep the conversation alive when load and edge cases arrive.
From PoC to live sessions — with enough clarity that the team could own what shipped.
Rooms, chat, scheduling — then chase performance later. Familiar roadmap. Risky first impression.
Protect latency and session integrity as the product core. Features grow around a feeling that already works.
Business need: students and counsellors in a session that feels live. So the path was presence first — then expand.
A real-time counselling platform taken from prototype through production handover — built around the moment that mattered most.