How do we make architecture more user centered?
summary
A multi-year legacy displacement program shows that applying specific user-centered practices — day in the life workshops, empathy maps, storyboards and service blueprint maps — uncovers hidden workarounds (spreadsheets, email workflows, post‑its and macros) and prevents “scope icebergs.” The claim is that these tactics let teams build a viable alternative incrementally, measure success by KPIs like “operate without legacy reliance,” and materially reduce big‑bang risk on real projects.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:23Meet the speakers
- 5:06What are we covering
- 12:35How do we make architecture more user centered
- 14:55Day in the Life
- 18:40The Benefits
- 25:37Moving beyond decommissioning
- 31:54Questions
related talks
08mUX Architecture
47mExperience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt
49mCo-creating with UX and Software
49mCultivating Architecture
45mDemocratising Software Architecture
46mThe final frontier - how to engage business users in agile.
25mLeapfrogging from Good to a Great Architect
41mBeyond "it depends" - How much architectural work do we need?