Product Thinking
Treating what you build as something with users, a value proposition and a lifecycle, rather than as a project that completes.
The distinction from project thinking is ownership over time. A project has a scope, a budget and an end date, after which the team disperses and the thing becomes somebody's maintenance burden. A product has a continuing owner, a roadmap, and users whose satisfaction is measured.
Where this matters most for an architect is internal platforms. A platform built as a project is a mandated standard nobody wants to use; built as a product, it has to earn adoption — which forces the questions that make platforms good: who is the user, what problem does this solve for them, what is the alternative they would otherwise choose, and is our version actually better?
The practical test for any shared component: if teams were not obliged to use it, would they? If not, the mandate is hiding a design problem.