Architecture Files #26 · Part of Binary and Beyond. LinkedIn newsletter edition follows.
Consumer apps train a cruel instinct.
Tap. Instant. Undo if you hate it.
Enterprise software asks for a second confirmation, waits on another system, shows pending, and refuses to pretend the warehouse agreed when it has not. People call that slow. Sometimes it is accidental bureaucracy.
Often it is the product telling the truth about a multi-party world.
The demo that felt faster and lied
Picture a retailer that rebuilt order status as a single green badge.
The old screen showed payment, pick, ship, and invoice as separate states. It felt dated. The new screen collapsed them into "complete" as soon as payment authorised. Conversion meetings celebrated the cleaner UX.
Monday morning, support fielded customers who were "complete" while the warehouse still held the order and finance had not posted. The badge was fast.
The business was dishonest (Why Eventual Consistency Is Usually Correct, The Hidden Cost of Synchronous APIs).
Speed that erases disagreement is not speed.
It is a loan against the support queue.
What the slowness is paying for
Enterprise latency and ceremony often purchase:
Authority checks. Who may approve this amount, in this region, for this customer class.
Reconciliation windows. Time for sibling systems to catch up without inventing a second truth (The Myth of a Single Source of Truth).
Auditability. A reconstructable path for regulators, partners, and your future self.
Multi-party state. Dealers, warehouses, carriers, and ERPs do not share one clock (Every Integration Is a Distributed System).
Safe refusal. Better to block than to guess when the dependency is brown.
Consumer-grade instant usually assumes one writer, one reader, and a cheap undo. Enterprises rarely have that luxury.
Accidental slowness vs honest slowness
Not all friction is virtuous.
Accidental: N+1 queries, synchronous calls that could be async side effects, approval chains that exist because nobody deleted a 2014 workaround, UI that makes pending look like failure.
Honest: waiting on an exclusive reservation, dual control on irreversible money movement, explicit pending while ERP posts, human review on regulated language.
The craft is separating the two. Kill accidental friction ruthlessly. Keep honest friction visible and explained. Hide it and you train users to bypass the only controls that matter.
How this shows up in delivery
On legacy modernisation and multi-system programmes, we spend as much time naming pending states as we do shaving milliseconds. Dealer and warehouse paths only feel "slow" when the UI refuses to lie about partner latency. That design is the product (legacy application modernization).
A checklist when stakeholders demand "make it feel consumer"
- Which waits are authority or reconciliation, not bad code?
- What would a green badge hide that support would rediscover?
- Is undo real, or is compensation a finance project?
- Whose clock are we waiting on, and is that written down (Why Time Is the Hardest Dependency)?
- Can we make pending feel intentional instead of broken?
- Which ceremony can die without increasing blast radius?
If the plan is only "fewer clicks," you may be deleting honesty.
Designing for felt speed without lying
Honest systems can still feel responsive.
Acknowledge immediately. Show named pending states. Give ranges instead of fake precision. Let users continue other work while a partner clock runs. Prefer async confirmation for side effects that are not on the critical commitment path.
What you should not do is collapse four systems into one green lie. Users will route around you with spreadsheets, and those spreadsheets become the real system of record.
Felt speed is a UX problem layered on honest state.
It is not a license to delete state.
Related reading
- Why Eventual Consistency Is Usually Correct
- Why Time Is the Hardest Dependency
- Designing Software for Partial Failure
- The Problem with Shared Databases
Architecture Files #26 · Part of Binary and Beyond. LinkedIn newsletter edition follows. Designing enterprise UX that stays honest under multi-system reality? Start a conversation.