Product Thinking
Treating platforms and services as products with users and a lifecycle.
4 to work through
-
beginner
A grocery-delivery product in the mould of Instacart wants to replace "we will message you if an item is out of stock" with "we substitute automatically and you are never charged more". The product manager calls it a copy change. What has the business bought and what has it just agreed to pay for?
3 min answer -
beginner
An internal tool's users are required to use it. Which product signals still mean something, and which are worthless?
2 min answer -
intermediate
A workspace product's engineers propose an architecture optimised for flexibility, letting users model anything. What product-thinking questions should shape the decision?
2 min answer -
intermediate Multiple choice
How would you know whether an internal platform is succeeding?
2 min answer
4 terms in this topic
Captive User Signal
The small set of measurements that still carry information when users cannot choose an alternative - workarounds, time to first success, abandonment …
conceptGuarantee Surface
The set of customer-facing promises a product has made, each of which obliges the architecture to detect its own breach and pay for it - so this surf…
conceptOutcome over Output
Measuring and committing to changes in user or business behaviour rather than to the delivery of features.
conceptProduct Thinking
Treating what you build as something with users whose problems it must solve — applied to internal platforms as much as to customer-facing products.
Neighbouring topics
Business Architecture
General material on the business side of architecture.
Business Capabilities
What a business does, stated stably and independent of implementation.
Capability Mapping
Overlaying systems onto capabilities to expose duplication and gaps.
Business Processes
How work actually flows, including the handoffs nobody documented.
Value Streams
End-to-end delivery of an outcome, and where the waiting happens.
Domain Boundaries
Where the language of the business changes, and services should too.
Stakeholder Analysis
Who is affected, what they need, and who can block you late.
Business KPIs
The numbers a design is ultimately judged against.
Regulatory Constraints
Non-negotiable requirements that remove design options entirely.
Organisational Constraints
Team structure, skills and budget cycles as architectural inputs.
Time to Market
The constraint that dominates most products, and how to trade against it.
Build vs Buy
Differentiation versus table stakes, priced over five years.
Business Cases
Expressing an architecture proposal in the currency that gets funded.
Operating Models
How delivery, platform and governance functions fit together.
Team Topologies
Stream-aligned, platform, enabling and complicated-subsystem teams.
Platform as a Product
Adoption earned rather than mandated, with an owner and a roadmap.
Outcome Measurement
Knowing whether the thing you built achieved what it promised.
Portfolio Prioritisation
Choosing between investments with incomparable benefits.
Business Continuity
What the business does while the system is unavailable.