Manifesto
What is architecture?
An architect is someone who intentionally shapes a system so people can inhabit it. Once that system was a building. Now it can just as easily be software, a business, or a life.
The frame
Architecture is about relationships, not components.
A builder creates. A designer shapes. An engineer makes it work. An architect holds the relationships, so the whole thing works together.
The material changes. The posture doesn’t. Traditionally the system was a building. It could just as easily be software, a business, a service, or a life.
The first artifact
The first artifact is no longer a wireframe. It is understanding. Everything else is negotiable.
The questions
A definition tells. These demonstrate. I bring them to everything I build.
- Should this exist?
- Does it belong?
- Is this making the system simpler or more complex?
- What happens five years from now?
- How does this affect everything else?
Why architecture
We used to think architects designed buildings. Now some of the most important structures in our lives are invisible. Products, services, algorithms, and intelligent systems that shape how millions of people think, decide, communicate, and trust. If these are the new infrastructure of everyday life, they deserve architects.
Applied to products
Software has become one of humanity’s primary building materials. AI has reunited disciplines that were once separated by specialization. I practice product architecture because I believe those systems deserve architects.
On the term
“Product architect” already exists as a title, and it means different things to different organizations. This isn’t an attempt to standardize a job. It’s an exploration of a way of practicing in the age of AI.
Architect is the word that matters. Product is just the current context. So the durable identity is a practice, not a noun: I practice product architecture. If the work outgrows “product,” the philosophy comes along.
Draft, in the open · Version 01