Skip to content

Design thinking

A family of human-centered design approaches that iteratively frame ambiguous problems, study users, generate alternatives, prototype and learn from testing.

Version
v1 · 2026-09-08 · History
Domain-specific #
4125
Origin domain
design methodology
Subdomain
design methodology

Core Idea

Research on designerly cognition, professional design methods and commercial innovation toolkits use the label differently; iteration, reframing and situated evidence matter more than a fixed stage diagram. Teams alternate divergent and convergent inquiry, externalize tentative solutions as prototypes and use stakeholder feedback to revise both the problem frame and proposed intervention. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

Design thinking belongs to design methodology and is useful where the analyst can specify the typed design methodology carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the design context and stakeholders, version of the method, research evidence, problem frame, ideation and selection, prototype fidelity, test and feedback, iteration and decision criteria are explicit. The scope is broad within that domain but bounded by the need for the design context and stakeholders, version of the method, research evidence, problem frame, ideation and selection, prototype fidelity, test and feedback, iteration and decision criteria are explicit. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity

The abstraction clarifies a crowded vocabulary by making the design context and stakeholders, version of the method, research evidence, problem frame, ideation and selection, prototype fidelity, test and feedback, iteration and decision criteria are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Design thinking can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Design thinking. Design thinking compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed design methodology carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the design context and stakeholders, version of the method, research evidence, problem frame, ideation and selection, prototype fidelity, test and feedback, iteration and decision criteria are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of design methodology because they reuse the typed design methodology carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, Teams alternate divergent and convergent inquiry, externalize tentative solutions as prototypes and use stakeholder feedback to revise both the problem frame and proposed intervention., and type the carrier, state every parameter and convention in the definition, test that the design context and stakeholders, version of the method, research evidence, problem frame, ideation and selection, prototype fidelity, test and feedback, iteration and decision criteria are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Design thinkingParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Design thinkingDOMAINPrime abstraction: Design — is a kind ofDesignPRIME

Current abstraction Design thinking Domain-specific

Parents (1) — more general patterns this builds on

  • Design thinking is a kind of Design Prime

    The proposed strict upward parent is prime:design.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Design thinking sits in a crowded region of the domain-specific corpus (6th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Engineering Design & Requirements (47 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08