Design thinking - Revision history

Root: /* Summary table: Prototyping the Design Thinking Way */

2025-10-20T20:13:35Z

Summary table: Prototyping the Design Thinking Way

← Older revision		Revision as of 21:13, 20 October 2025
Line 95:		Line 95:
	<span id="summary-table-prototyping-the-design-thinking-way"></span>		<span id="summary-table-prototyping-the-design-thinking-way"></span>

	= Summary table: ~~Prototyping~~ the ~~Design Thinking Way~~ =		= Summary table: prototyping the design thinking way =
	{\| class="wikitable" table-width="760" layout="default" ac:local-id="0db589a9-44e8-4d20-94d4-36236974fdce"		{\| class="wikitable" table-width="760" layout="default" ac:local-id="0db589a9-44e8-4d20-94d4-36236974fdce"
	\|-		\|-
	! Design ~~Thinking Element~~		! Design thinking element

	! Contribution to ~~Prototyping~~		! Contribution to prototyping

	\|-		\|-
Line 113:		Line 113:

	\|-		\|-
	\| '''Rapid ~~Iteration~~'''		\| '''Rapid iteration'''

	\| Learn and adapt quickly		\| Learn and adapt quickly

	\|-		\|-
	\| '''Feedback ~~Loops~~'''		\| '''Feedback loops'''

	\| Integrate user reactions early		\| Integrate user reactions early
Line 131:		Line 131:
	<span id="build-to-learn-not-just-to-ship"></span>		<span id="build-to-learn-not-just-to-ship"></span>

	= Build to ~~Learn~~, ~~Not Just~~ to ~~Ship~~ =		= Build to learn, not just to ship =
	Design thinking reframes prototyping as a learning engine. You're not building for internal approval, you’re building to uncover the truth about what users want. With each sketch, wireframe, or clickable test, you get closer to a solution that’s not just functional, but ''valuable''.		Design thinking reframes prototyping as a learning engine. You're not building for internal approval, you’re building to uncover the truth about what users want. With each sketch, wireframe, or clickable test, you get closer to a solution that’s not just functional, but ''valuable''.

Root at 20:12, 20 October 2025

2025-10-20T20:12:22Z

← Older revision		Revision as of 21:12, 20 October 2025
Line 60:		Line 60:
	== Design thinking prototyping in action ==		== Design thinking prototyping in action ==
	Here are ways design thinking shapes prototyping across use cases:		Here are ways design thinking shapes prototyping across use cases:
	==== ~~'''~~1. Early concept validation~~'''~~ ====		==== 1. Early concept validation ====

	Before refining anything, teams create low-fidelity models (paper sketches, clickable wireframes, role-play scenarios) to explore multiple possibilities. This avoids getting too attached to one idea too soon.		Before refining anything, teams create low-fidelity models (paper sketches, clickable wireframes, role-play scenarios) to explore multiple possibilities. This avoids getting too attached to one idea too soon.
Line 66:		Line 66:
	<blockquote>Example: A mobile app team sketches three onboarding flows, tests them with users using simple clickable mockups, and tosses the least intuitive one after early feedback.		<blockquote>Example: A mobile app team sketches three onboarding flows, tests them with users using simple clickable mockups, and tosses the least intuitive one after early feedback.
	</blockquote><span id="testing-human-reactions"></span>		</blockquote><span id="testing-human-reactions"></span>
	==== ~~'''~~2. Testing human reactions~~'''~~ ====		==== 2. Testing human reactions ====

	Design thinking encourages ''provoking reactions'' rather than seeking praise. A prototype that confuses users tells you more than one they just say is “nice.”		Design thinking encourages ''provoking reactions'' rather than seeking praise. A prototype that confuses users tells you more than one they just say is “nice.”
Line 72:		Line 72:
	<blockquote>Example: A nonprofit prototypes a donation form with three layouts and watches where users hesitate. These friction points shape the next version.		<blockquote>Example: A nonprofit prototypes a donation form with three layouts and watches where users hesitate. These friction points shape the next version.
	</blockquote><span id="clarifying-the-problem-itself"></span>		</blockquote><span id="clarifying-the-problem-itself"></span>
	==== ~~'''~~3. Clarifying the problem itself~~'''~~ ====		==== 3. Clarifying the problem itself ====

	Sometimes, you’re not even solving the right problem. Rapid prototyping in design thinking helps reframe the challenge as you learn more about what users ''actually'' want.		Sometimes, you’re not even solving the right problem. Rapid prototyping in design thinking helps reframe the challenge as you learn more about what users ''actually'' want.

Root at 20:11, 20 October 2025

2025-10-20T20:11:45Z

Show changes

Maintenance script: Added category manage objectives

2025-10-19T17:51:43Z

Added category manage objectives

← Older revision		Revision as of 18:51, 19 October 2025
Line 180:		Line 180:
	<!-- From bodyContent 29556746.mraw -->		<!-- From bodyContent 29556746.mraw -->

			[[Category:manage objectives]]

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC Project/Project management/manage objectives/Design thinking to Design thinking: Cleaned title and categorized

2025-10-19T17:51:43Z

Maintenance script moved page UserDocumentation:Knowledge Central/KC Project/Project management/manage objectives/Design thinking to Design thinking: Cleaned title and categorized

← Older revision	Revision as of 18:51, 19 October 2025
(No difference)

imported>Unknown user at 06:48, 25 July 2025

2025-07-25T06:48:06Z

Show changes

imported>Unknown user at 06:48, 25 July 2025

2025-07-25T06:48:06Z

← Older revision	Revision as of 07:48, 25 July 2025
(No difference)

imported>Unknown user at 06:48, 25 July 2025

2025-07-25T06:48:06Z

New page

{{AttachmentsSectionStart}}
* [[Media:UserDocumentation_Knowledge_Central_KC_Project_Project_management_manage_objectives_Design_thinkingimage-20250725-064512.png]]
* [[Media:UserDocumentation_Knowledge_Central_KC_Project_Project_management_manage_objectives_Design_thinkingimage-20250725-064512.png]]

{{AttachmentsSectionEnd}}