Interview · Success Quarterly · 2026
Architecture Is Employee Experience
A profile on the practical evolution of workforce technology: why data flow, integration reliability, and absorbed complexity decide the employee experience.
Read it at Success Quarterly ↗What it argues
- Employee experience is not a UI layer. It is the sum of every integration that either works or silently fails.
- When data does not flow, people become the integration — and that work never shows up in a roadmap.
- Modernization succeeds when it removes steps from a manager's day, not when it refreshes a screen.
Why I wrote it
The interview covers the argument I keep returning to: the quality of an employee's day is decided upstream, in architecture decisions nobody in that building ever sees.
A schedule a manager cannot trust is not a training problem. It is a data problem wearing a training problem's clothes.