Product Design & Value Delivery

← Back to Domain-Specific Families

Abstractions about business models, requirements, feature scope, onboarding, procurement, efficiency, and the alignment of technology with customer value.

16 abstractions in this family — domain-specific abstractions that sit near one another in structural-signature space (k-means over structural-signature embeddings). Each is shown with its short description.

• Business Model Canvas — Osterwalder's nine-block single-page template that renders a venture's operating logic all at once — segments, value, channels, revenue, resources, activities, partners, costs — so its components and their interdependencies become simultaneously visible and testable as hypotheses.
• Ecosystem Mismatch — Explain why a technically sound innovation stalls on deployment not by a flaw in the artifact but by the absence of one specific complementary asset its operating context tacitly required — leaving it complete-but-functionally-blocked.
• Feature Creep — Explain why a product accretes capabilities past net benefit as a governance failure, not a quality one — an approval gate that judges each addition in isolation against its stated cost while structurally blind to the compounding global cost of all additions together.
• Gold Plating — Diagnose a delivery overrun as producer-side unilateral scope expansion — quality or features added beyond the authorized envelope without the principal's sanction — whose real cost lives not in the polish but in the unbudgeted second-order burden it drags into downstream processes.
• Golden Hammer Anti-Pattern — Diagnose a team applying its familiar technology to a poorly-fitting problem because the acquisition cost of an alternative is visible while the misfit cost is diffuse and downstream, so fluency reshapes what counts as the right tool before fit is ever asked.
• Iron triangle of health care — A health system's three objectives — access, quality, and cost — stand in a trilemma bound by production economics: within a fixed productivity frontier, improving any two forces worse performance on the third, so any all-corners promise is really a frontier-shifting productivity claim.
• Market Pull — The innovation situation in which articulated demand-side need — customers naming a problem and willing to pay — directs the search of developers and investors and pulls solutions into existence; the demand-side pole of the push/pull dichotomy, keyed to where the binding constraint sits.
• Maverick Spend — Read off-contract buying not as indiscipline but as rational channel selection — local units declining a coordination tax that exceeds the central channel's marginal value — so the lever is closing the friction differential, not policing, and enforcement-only pushes spend further underground.
• Onboarding cliff — Diagnose first-use abandonment as a geometry of two curves — cumulative cost crossing the user's willingness-to-invest before cumulative value crosses willingness-to-stay — separating first-contact complexity from steady-state complexity and naming exactly two levers.
• Overprocessing Waste — Name the waste of effort, precision, or handling that exceeds what the downstream receiver will use or pay for — relocating the definition of value from the performer to the receiver and making the effort-value gap a measurable target for removal.
• Productive Efficiency — The condition of producing a chosen output at the lowest feasible input cost — operating on the production frontier — with any interior point measuring recoverable waste as its distance inside, held strictly apart from the allocative question of whether the right mix is produced.
• Requirements Volatility — Treat frequent, substantive change in a system's requirements as a measurable churn rate matched against the team's absorption capacity, then flatten Boehm's cost-of-change curve so late changes force only local rework rather than cascading redesign.
• Scope Neglect — Explain why elicited valuations stay flat across hundredfold changes in magnitude — the count is replaced by a single affect-laden prototype, so the number is understood but never priced in.
• Solow Computer Paradox — The puzzle that heavy IT investment coincided with a productivity slowdown, not an acceleration — resolved as a deployment-to-impact lag: the headline measure waits on the complementary intangible stocks (process redesign, retraining, standards) a general-purpose technology must accumulate first.
• Technology Push — The innovation posture in which a technical capability is developed first and a search for problems it can address follows — the inverse of demand pull, fixing the technology and ranging over problem spaces, with the multi-year match step as the load-bearing risk.
• Value Proposition — Articulate, in a structured object with named slots, what benefit an offering delivers for a specific customer segment under a specific constraint and why it beats named alternatives — a targeted, contrastive, capability-honest statement that serves as the shared referent for aligning product, pricing, marketing, and sales.