Optimising for technical correctness without user value produces robust systems that nobody uses. Optimising for user value without technical correctness produces engaging products that eventually fail under their own success. The tension is real, and resolving it requires holding both objectives simultaneously rather than alternating between them.
The compounding nature of this tradeoff is important. Early architectural decisions that correctly model user behaviour are cheap to maintain. Early architectural decisions that incorrectly model user behaviour accumulate as technical debt that grows faster than the product does. A team that discovers at scale that their core data model does not match how users actually use the product faces a rewrite under time pressure, with live users on the system.
The most expensive architectural decisions are not the ones made under constraint. They are the ones made under incorrect assumptions.