January 4, 2026
The Three Clocks Framework: Designing Real-Time Systems
Every real-time platform runs on three clocks — user time, system time, and business time. Most teams only design for one. That's why systems feel fast but fail under pressure, or feel consistent but never scale.
All week I’ve been writing about clarity, architecture, and the foundations that help teams move fast without breaking trust. Today’s idea brings those themes together.
Every real-time platform runs on three clocks.
Most teams only design for one.
This is why systems feel fast but fail under pressure — or feel consistent but never scale.
Real-time behavior is not about milliseconds alone. It’s about coordinating three very different timelines. Here are the three that matter.
1. User Time
This is the world users believe they live in. Actions feel instant. Feedback must match what they expect, not what the back end is doing.
If a user thinks something happened, the system needs to reflect that belief in a predictable way. Latency here becomes a trust problem, not a technical one.
2. System Time
Services do not live in the user’s world.
They process events at their own pace. They retry when needed. They apply back-pressure, handle load spikes, and resolve ordering and concurrency issues.
System time is where the real work happens.
3. Business Time
This is where correctness lives.
Ledgers, settlements, compliance, reporting, and audit trails care about the exact order and truth of events — even if finalization takes longer.
A payment may feel instantaneous to a user, but may not be fully settled until later. Business time governs rules and truth, not clicks.
Where Most Failures Come From
Most failures in real-time systems happen because a team optimizes for one clock at the expense of the others.
Optimize only for user time, and your ledger gets corrupted. Optimize only for business time, and your users abandon the flow. Optimize only for system time, and neither users nor auditors trust what they see.
What Good Looks Like
When you design with all three clocks in mind:
- UIs become predictable
- Event workflows become resilient
- Ledgers stay trustworthy
- Failures become localized
- Scale becomes a property of architecture, not hardware
Real-time platforms succeed when they respect the idea that time is not single-threaded. The system must reconcile three timelines into one coherent experience.
Once you see the three clocks, you start designing differently.
This framework pairs naturally with what I’ve written about starting with good and Lister’s Law more broadly. Real-time systems succeed when these three timelines stay aligned.
Related reading
February 28, 2026
AI Doesn't Write Bad Code. It Writes Convincing Code.
A working hypothesis after a month of putting Claude Code through its paces inside a structured mono-repo environment. AI performs dramatically better inside opinionated, well-documented systems. Without that structure, it amplifies chaos.
December 31, 2025
Start With Good: Where Quality Actually Begins
A follow-up to Lister's Law. Good doesn't start with testing. It starts with understanding — the problem, the user, and why the work matters. Shift Left Quality in practice.
Have a project this connects to? Let's talk about it.