Tenet VI of VI · Evolution · 6 of 6
The role you have today has to become more truthful.
Designers, frontend developers, design engineers — the labels are being asked to carry broader work on some teams. The Product Architect is a proposed practice for holding that work, not a universal replacement for specialist roles. The path forward is not to defend the old title or inflate a new one. It is to name the value more truthfully, build evidence of it, and reposition into it without pretending you were always there.
— · Chapters that argue from this tenet
Introduction — When the Role Stops Fitting
How to examine the gap between your role, attention, and evidence.
Introduction ·Unread· 7 min· RevisedBuild Evidence of a New Identity
The new role becomes legible to others when there is something to point at.
Chapter 12 ·Unread· 12 min· RevisedRepositioning Without Pretending
Move into the role you can defend, not the role you want.
Chapter 13 ·Unread· 11 min· RevisedThe Practice of Product Authorship
Authorship is the practice that holds the role across years.
Chapter 14 ·Unread· 11 min· Revised
Newsletter · monthly
One Field Note a month.
What changed in the book, the latest episodes, one framework in practice.
Opens a message to joost@studio-jz.nl in your email app. Send it to subscribe.
Software Behavior · Manifesto · Tenet VI
VI / VI