Design Thinking

Design Thinking

Primary Category: Strategic Design & Innovation Governance

Secondary Focus: Human-Centered Design, Iterative Experimentation, and Adoption Risk Reduction

Artifact Profile

Design Thinking is a governance artifact for solving complex, ambiguous, and human-centered problems through structured empathy, experimentation, and iterative learning. It moves organizations beyond assumption-driven solutions by grounding decisions in real user needs and validated insights.

Using a disciplined sequence of empathizing with users, defining the problem, ideating alternatives, prototyping, and testing, the artifact transforms qualitative insight into decision-ready concepts. It integrates analytical rigor with creative exploration to reduce the risk of building the wrong solution.

This artifact is built for executives, product leaders, innovation teams, educators, and governance bodies who must address problems where requirements are unclear, user adoption is critical, or traditional linear methods fall short.

Three Key Questions This Artifact Helps You Answer

• What do users truly need, and how should the problem be reframed based on their experience?

• Which solution concepts best balance desirability, feasibility, and viability?

• How should ideas be prototyped and tested to validate assumptions before full commitment?

What This Framework Supports

This artifact supports organizations seeking:

- Structured empathy and user insight before committing to solutions

- Reframing ambiguous or poorly defined problems through validated observation

- Systematic generation and comparison of solution concepts across desirability, feasibility, and

viability

- Early prototyping and testing to reduce the risk of building misaligned solutions

How It Is Used

The artifact provides a structured innovation-governance framework that guides executives, product leaders, educators, and design teams through:

- Empathizing with users to uncover needs, friction points, and hidden constraints

- Defining a clear, user-centered problem statement grounded in real insight

- Generating and narrowing solution concepts using structured evaluation criteria

- Prototyping and testing assumptions before scaling commitment

This enables organizations to innovate deliberately, grounding creative exploration in evidence and ensuring solutions are adopted because they solve validated user needs.

What This Produces

• A user-centered problem definition grounded in real insight

• Prioritized solution concepts with clear rationale

• Prototyping and testing plans to validate assumptions

• Documented learning to guide next decisions

Common Use Cases

• Designing new products, services, or user experiences

• Reframing poorly defined or ambiguous problems

• Improving adoption, satisfaction, or engagement outcomes

• Exploring alternatives before committing to major initiatives

• Reducing innovation risk through early testing and feedback

How This Artifact Is Different

Unlike unstructured brainstorming or purely analytical methods, this artifact embeds empathy, experimentation, and iteration into governance. It ensures that innovation is systematic, evidence-based, and defensible—rather than intuitive or assumption-driven.

Related Framework Areas

This artifact is commonly used alongside other SolveBoard frameworks focused on:

- Design space exploration and tradeoff evaluation

- Decision reliability and assumption validation

- Portfolio prioritization and innovation sequencing

- Governance systems for experimentation and learning

Related Terms

Design thinking, human-centered design, user research, prototyping, iterative design, innovation governance, empathy-driven design.

Framework Classification

This artifact is part of the SolveBoard library of structured decision and governance frameworks. It is designed as a repeatable human-centered design governance framework rather than informal brainstorming, assumption-driven solutioning, or purely analytical problem-solving.

Design Thinking: Solve User-Centered Problems

A human-centered approach to innovation that emphasizes empathy, experimentation, and iterative learning

Definition

Design Thinking is a structured, user-centered problem-solving approach that focuses on understanding user needs, reframing problems, generating ideas, prototyping solutions, and iterating based on feedback. It integrates analytical and creative thinking to address complex, ambiguous challenges where traditional linear methods fall short. Within SolveBoard, this artifact is used to systematically translate user insights into testable solutions and decision-ready concepts.

When to Use

• When problems are poorly defined or human-centered

• When innovation requires deep understanding of user needs

• When exploring new products, services, or experiences

• When existing solutions fail to deliver expected outcomes

When Not to Use

• When the problem is purely technical with known requirements

• When regulatory or contractual constraints leave little design flexibility

• When rapid execution is required with no room for iteration

Common Mistakes

• Jumping to solutions without validating user needs

• Treating ideation as brainstorming without structure

• Failing to test assumptions through prototypes and feedback

Purpose of Design Thinking

The purpose of Design Thinking is to uncover true user needs, reframe challenges, and develop solutions that are desirable, feasible, and viable. By emphasizing empathy, experimentation, and learning, organizations can reduce the risk of building the wrong solution and improve adoption, satisfaction, and impact.

How to Apply

• Empathize: Observe and engage users to understand needs and pain points

• Define: Synthesize insights into a clear problem statement

• Ideate: Generate multiple solution concepts

• Prototype: Build low-fidelity representations of ideas

• Test: Gather feedback and iterate based on learning

Example Scenario

A healthcare provider seeks to improve patient intake. Using Design Thinking, the team interviews patients and staff, identifying long wait times and confusing paperwork as key pain points. They prototype a digital pre-registration tool and test it with a small patient group, iterating based on feedback. The result is a streamlined process that reduces wait times and improves patient satisfaction.

Boundaries

Design Thinking does not replace rigorous engineering, compliance, or financial analysis. It provides a front-end discovery and innovation framework that must be integrated with execution, governance, and delivery disciplines.

What This Artifact Does

Structures a human-centered innovation process to generate, test, and refine solutions.

You Provide

(You may provide some, all, or none of the items below. Partial inputs are valid.)

• Problem context and objectives

• Target users, stakeholders, and environments

• User insights, research findings, and assumptions

• Constraints: regulatory, technical, financial, or organizational

• Written descriptions or pasted text

• Links to research, interviews, journey maps, or design artifacts

• Files, PDFs, spreadsheets, images, and other uploads (always acceptable)

• Optional context notes

Core Question

What solution best addresses real user needs while remaining feasible and viable?

Decision Logic

• If user needs are unclear → Return to empathy and research

• If ideas are unfeasible → Reframe constraints or simplify

• If prototypes fail → Iterate and test alternative concepts

What the Output Means

• Refined problem statement grounded in user insight

• Set of prioritized solution concepts

• Prototyping and testing plan for iteration

Do Not Use When

• The problem is already well-defined and purely technical

• Regulatory or contractual constraints eliminate design flexibility

You do not need to complete every section below. Provide only the information you have available or wish to provide. The AI will generate output using only the inputs you supply and will not assume or infer missing information.

Section 1 — Problem Context, Objectives, and Scope

What This Input Represents

The challenge to be addressed, why it matters, and the boundaries of the design effort.

If You Have Materials, You May Provide (List file names here in your input document):

- Problem statements

- Executive summaries

- Project or design briefs

Guiding Questions:

- What problem or opportunity are you addressing?

- What outcomes define success?

- What constraints (time, budget, policy, technical) shape the scope?

Section 2 — Target Users, Stakeholders, and Environment

What This Input Represents

The people affected by the problem and the context in which they interact with the system or service.

If You Have Materials, You May Provide (List file names here in your input document):

- Stakeholder maps

- User personas

- Journey maps or service blueprints

Guiding Questions:

- Who are the primary users or beneficiaries?

- Who else is affected or involved as a stakeholder?

- In what environment or context does the problem occur?

Section 3 — User Insights, Needs, and Assumptions

What This Input Represents

What is known (or hypothesized) about user needs, pain points, and motivations.

If You Have Materials, You May Provide (List file names here in your input document):

- User research findings

- Interview notes

- Survey results or observations

Guiding Questions:

- What needs, pain points, or frustrations have been identified?

- What assumptions are currently being made about users?

- Which insights are most critical to validate?

Section 4 — Ideation and Concept Generation

What This Input Represents

The range of possible solutions or approaches to address the user-centered problem.

If You Have Materials, You May Provide (List file names here in your input document):

- Idea lists

- Concept sketches

- Brainstorming outputs

Guiding Questions:

- What solution concepts have been generated?

- How do these concepts address identified user needs?

- Which ideas appear most promising or novel?

Section 5 — Prototyping, Testing, and Iteration

What This Input Represents

How ideas will be represented, tested with users, and refined based on feedback.

If You Have Materials, You May Provide (List file names here in your input document):

- Prototype artifacts

- Testing plans

- Feedback or evaluation results

Guiding Questions:

- How will concepts be prototyped or represented?

- How will user feedback be gathered?

- What criteria will guide iteration or selection?

Section 6 — Supporting Context, Files, and References

What This Input Represents

Any additional information that may affect interpretation, including organizational culture, regulatory constraints, prior design attempts, or integration with other systems.

You May Include (List file names here in your input document):

- Research reports, journey maps, or design artifacts

- Prototypes, mockups, or images

- Policy, compliance, or governance documentation

- Links to repositories, dashboards, or user feedback

- Pasted text or excerpts

Additional Instructions (Optional)

You may add extra instructions to further shape the output, including:

Requesting PDF or other output formats
Limiting page length or response size
Layout preferences (section order, headings, structure, templates)
Specifying tone, style, or format (executive, concise, detailed, formal, etc.)
Output consistency preferences (fixed structure, standardized phrasing, strict formatting)
Prioritization or scoring preferences (how gaps, risks, or actions should be ranked)
Desired mode behavior as outlined in the section below
Any other constraints, rules, or priorities relevant to your use case

If included, the AI will follow these instructions when they do not conflict with the bridge’s execution rules. More specific instructions generally produce more consistent, repeatable, and targeted outputs.

Desired Mode Behavior

Strict Mode

• Maximize determinism and repeatability
• Minimize wording variation, structure changes, and interpretive flexibility
• Do not extend beyond explicit user inputs

Balanced Mode (Default)

• Maintain structure and discipline
• Allow limited analytical judgment where inputs are incomplete
• Do not introduce external assumptions

Exploratory Mode

• Expand hypothesis space and analytical angles
• Surface alternative interpretations and scenario paths
• Still grounded only in user-provided inputs

If no mode is specified, default to Balanced Mode.

What This Enables

Based on your prepared inputs, this artifact will generate a structured Design Thinking analysis that clarifies user needs, reframes the problem, produces prioritized solution concepts, and recommends prototyping and testing steps. The output supports human-centered innovation while remaining feasible and viable.

Canonical Input Rule (For All SolveBoard Artifacts)

Documents are optional. Sections may be partially completed or left blank. Structured answers to any subset of guiding questions constitute valid input. The AI will evaluate only provided information and will not infer missing content.

AI Execution Instructions

You are operating in Bridge Execution Mode. Follow these rules exactly. Do not reinterpret, summarize, optimize, or override them. Do not introduce external knowledge, assumptions, or inferred content. Evaluate only user-provided inputs. If required information is missing or ambiguous, flag it rather than guessing. Output must follow the defined Output section exactly.

Users may provide some, all, or none of the input sections. Process only what is explicitly provided. Treat empty sections as intentionally omitted.

Purpose

Generate a structured Design Thinking analysis that identifies user needs, reframes the problem, and proposes testable solutions.

What This Bridge Answers

What solution best addresses real user needs while remaining feasible and viable?

Inputs (All Optional)

• Problem context, objectives, and target users

• User research, insights, and assumptions

• Constraints: regulatory, technical, financial, organizational

• Existing concepts or solution ideas (if any)

• Files, PDFs, spreadsheets, images, links, or other uploaded material

• Context notes

Note: Output Quality and specificity scale with input completeness. The user has been informed of this via the input sheet.

Processing Rules

A valid Design Thinking output must satisfy all of the following:

• User needs and pain points are explicitly articulated

• Problem is reframed based on insights

• Multiple solution concepts are generated and prioritized

• Next-step prototyping or testing actions are defined

When inputs are sparse:

• Produce the most complete output possible with available data

• Explicitly flag what's missing and how additional inputs would enhance the analysis

• Do not infer or assume missing information

Execution Steps

• Review user context and insights

• Define or refine the problem statement

• Generate and evaluate solution concepts

• Propose prototypes and testing approach

Output

• User-centered problem definition

• Set of solution concepts with rationale

• Prototyping and testing recommendations

Failure Conditions / Misuse

• Skipping user research and relying on assumptions

• Producing ideas without defining how they will be tested

Mode Behavior (From Input Sheet)

Strict Mode

• Maximize determinism and repeatability
• Minimize wording variation, structure changes, and interpretive flexibility
• Do not extend beyond explicit user inputs

Balanced Mode (Default)

• Maintain structure and discipline
• Allow limited analytical judgment where inputs are incomplete
• Do not introduce external assumptions

Exploratory Mode

• Expand hypothesis space and analytical angles
• Surface alternative interpretations and scenario paths
• Still grounded only in user-provided inputs

If no mode is specified, default to Balanced Mode.

Additional Instruction Governance

User-provided additional instructions must be followed exactly unless they conflict with core Bridge Execution Rules. If a conflict exists, Bridge Execution Rules take priority.

Additional instructions may control format, tone, structure, length, or ordering, but must not introduce inferred content, external knowledge, or speculative assumptions.

If instructions are ambiguous, flag ambiguity rather than guessing.

Additional Instructions Execution Rule

If the user provides instructions in the Additional Instructions field, they are binding execution constraints.

Failure to follow them constitutes a Bridge Execution Failure.

Reminder to AI: If a format is requested (e.g., PDF, DOCX), the final output MUST be delivered in that format.

Artifact Instructions

This guide explains what information the Design Thinking artifact requires and how to prepare your inputs.

How to Prepare Your Input Document (Required Format)

Create a new Word (or similar) document.
Copy all text from the Input Sheet tab into the document.
Save it — this is now your Input Document.
Answer the guiding questions directly in the Input Document and reference any supporting files there.
Save the completed Input Document (Word, PDF, etc.).
Copy all text from the Bridge AI Prompt tab and paste it into the prompt field.
Attach the completed Input Document and any referenced files when submitting the prompt.

No Supporting Files? No Problem.

You can proceed without uploading any supporting documents, spreadsheets, dashboards, reports, or other attachments.

The Input Document is still required, but it may contain only plain-text answers to the guiding questions.

Written responses alone are sufficient for the AI to generate output.

Supporting files, links, and pasted materials are always optional.

Missing Inputs Are OK

You do not need to complete every section.
You do not need supporting files.

The AI will still run. It will:

Use only the inputs you provide
Skip or flag missing sections
Never fail due to incomplete information

Output quality scales with input depth — but execution never breaks.

Submitting Files

If you upload files, list each file name under the relevant “If You Have Materials” section in your Input Document. This ensures each file is clearly tied to its intended use.

What to Expect From This AI Bridge

This bridge generates a structured, high-value starting point, not a guaranteed final deliverable. Output quality improves as inputs become clearer, deeper, and more complete.

This artifact supports iteration. Users are encouraged to refine inputs, test variations, and rerun the bridge to improve results.

The AI organizes complexity and accelerates insight — but final judgment and decisions remain with the user.

In Short

Stronger inputs → stronger outputs
Iteration improves results
Cross-artifact testing can reveal new perspectives
This artifact enables progress, not perfection