Product design is versioning and prioritization
Early in my career, when designing administrative products where business logic met interface decisions, I often heard: “This cannot be built,” “We cannot collect that data,” or “That does not exist here.” The disagreement usually began with an expectation to build the complete version immediately. I gradually learned that cost must be managed in stages. A development team cannot create a large set of capabilities instantly. This is where product design becomes versioning and prioritization: deciding what is required to understand the problem, what can be built later, and which assumption is not yet worth funding. Understanding is more important than execution. Rapidly building something we have not understood only takes us faster toward a more expensive version of the same uncertainty.