Mark Korotin
Product Architecture

Architecture is a product decision

Building leverage into the foundation so teams ship faster for years, not just for the next sprint.

Stable · · 8 min read

Most architecture conversations happen in the wrong room. They happen in engineering planning, after the product decisions have already been made, when the question has shifted from "what should we build?" to "how do we build what we already decided to build?"

By that point, the most consequential architectural decisions have already been made by default. The data model reflects the first feature, not the system. The API reflects the first client, not the contract. The boundaries reflect the first team, not the domain.

Architecture is a product decision because it determines what is easy, what is hard, and what is permanently impossible. It shapes what the team can ship in year two as much as it shapes what they ship in month one.

More in Product Architecture