UI is a function of your organization
User interfaces are argued to mirror the structure, incentives, and communication patterns of the organizations that create them, echoing Conway’s Law that systems copy their makers’ communication structures. Commenters use examples like Domino’s pizza tracker, fast-food order systems, and Apple’s shifting UI quality to show how metrics, misaligned incentives, and organizational silos can produce misleading or frustrating interfaces. Several voices also contrast rigid digital workflows with the flexibility of paper-based processes and suggest that examining a product’s UX can reveal an organization’s internal dysfunctions and history.
Conway’s Law, Org Structure, and Systems
- Many tie the article’s thesis to Conway’s Law: systems mirror organizational communication structures.
- Some argue it’s nearly impossible to find true counterexamples; when software fights the org, progress becomes painful.
- Others stress it’s more correlation than causation and that orgs are themselves shaped by business requirements.
- Changing orgs leave “scar tissue” in code: distinct generations of services, half-finished migrations, and architectures that map to past reorgs.
- Several note you can often infer an org’s structure and history from its UI/architecture (e.g., Windows volume controls, repeated chat apps).
Domino’s Tracker, Metrics, and Misaligned Incentives
- Multiple comments question whether Domino’s tracker is real-time or just a timer; experiences differ by location and chain.
- There are stories of fast-food staff marking orders “ready” early to hit metrics, making status UIs misleading.
- Concerns: fake telemetry corrupts analytics, leads to bad operational decisions, and erodes trust.
- Some suggest being explicit about averages instead of faking precision (“up to X minutes” plus a timer).
UI as a Function of Organization (and Its Limits)
- Many agree that real-time or process-reflective UIs are only possible when the org and backend are aligned to capture reality.
- Others say most bad UIs stem less from missing data and more from poor design priorities; any UI can be made to show something, accurate or not.
- There’s discussion of “shipping” and “buying” the org chart: large, dysfunctional orgs both build and procure similarly bloated systems.
Apple and Desktop UI Quality
- Several argue Apple’s product UIs have regressed: System Settings vs. the older System Preferences, hidden document proxy icons, and mobile patterns forced onto desktop.
- Others respond that old designs were also flawed and that search-first navigation may be inevitable as settings proliferate.
Paper, Margins, and Unstructured Workflows
- Commenters praise paper-based processes: visible margins, annotations, crossed-out text, and front-line autonomy.
- Digital systems often lack an equivalent, forcing rigid schemas and side-channel feedback.
- Examples from healthcare and customer support underline how loss of unstructured “margin” space harms real-world workflows.