Dt Curriculum
MicrosoftOfficialPublished by Microsoft
- Skill
- Guidelines
- Education and learning
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The DT Curriculum is a structured educational framework designed to guide learners through the full Design Thinking lifecycle, spanning the Problem, Solution, and Implementation spaces. It provides nine distinct modules that cover essential methods from initial scoping and research to prototyping, testing, and final handoff. To ensure consistent application of these concepts, the curriculum integrates a shared manufacturing reference scenario, allowing learners to apply theoretical knowledge to a realistic, evolving context throughout their training.
What it does
- Provides nine progressive modules covering the complete Design Thinking methodology.
- Uses a shared manufacturing reference scenario to maintain context across all learning modules.
- Teaches core techniques like stakeholder mapping, contextual inquiry, and frozen request unfreezing.
- Includes comprehension checks and practice exercises for each design method.
- Structures learning from the Problem Space through to the Implementation Space.
- Offers specific guidance on moving from stakeholder assumptions to user-validated reality.
When to use it
- When teaching or learning the end-to-end Design Thinking process.
- When you need a structured curriculum to train teams on problem-space scoping and solution-space design.
- When you want to use a consistent, realistic manufacturing scenario to practice design methods.
- When you need to bridge the gap between stakeholder requests and actual user needs.
- When you are preparing for design research, prototyping, or user testing phases.
Advantages
- Progressive structure ensures learners build skills logically from problem to implementation.
- Shared scenario provides a consistent baseline for comparing different design methods.
- Focuses on practical techniques like unfreezing requests and conducting contextual inquiry.
- Encourages discipline in staying within the problem space before jumping to solutions.
- Includes built-in assessment tools like comprehension checks and exercises.
Usage examples
- “I am starting Module 1 of the Design Thinking curriculum. Can you load the scoping module and the manufacturing scenario?”
- The agent loads the scoping module and the manufacturing scenario, then presents the first comprehension check regarding frozen versus fluid requests.
- “I need to practice unfreezing a request. Use the manufacturing scenario to give me an exercise.”
- The agent provides a specific request from the manufacturing scenario and asks the user to write three progressive questions to uncover the underlying problem.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/dt-curriculum/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip dt-curriculum.zip -d .agents/skills
Documentation by Microsoft
DT Curriculum — Skill Entry
This SKILL.md is the entrypoint for the Design Thinking learning curriculum.
The dt-learning-tutor agent loads this skill to teach Design Thinking concepts, run comprehension checks, and assign practice exercises. The curriculum spans nine progressive modules — one per Design Thinking method — and a shared manufacturing reference scenario that threads through every module so learners build on consistent context as they advance from the Problem Space to the Implementation Space.
Curriculum references
Load the module that matches the method the learner is studying. Load the manufacturing scenario alongside any module that uses scenario-based checks or exercises.
| Reference | When to load |
|---|---|
| curriculum-01-scoping.md | Teaching Method 1: Scope Conversations (Problem Space). |
| curriculum-02-research.md | Teaching Method 2: Design Research (Problem Space). |
| curriculum-03-synthesis.md | Teaching Method 3: Synthesis (Problem Space). |
| curriculum-04-brainstorming.md | Teaching Method 4: Brainstorming (Solution Space). |
| curriculum-05-concepts.md | Teaching Method 5: User Concepts (Solution Space). |
| curriculum-06-prototypes.md | Teaching Method 6: Low-Fidelity Prototypes (Solution Space). |
| curriculum-07-testing.md | Teaching Method 7: High-Fidelity Prototypes (Implementation Space). |
| curriculum-08-iteration.md | Teaching Method 8: User Testing (Implementation Space). |
| curriculum-09-handoff.md | Teaching Method 9: Iteration at Scale (Implementation Space). |
| curriculum-scenario-manufacturing.md | Alongside any module using scenario-based comprehension checks or practice exercises. |
Skill layout
SKILL.md— this file (skill entrypoint).references/— the DT curriculum knowledge documents.curriculum-01-scoping.mdthroughcurriculum-09-handoff.md— one module per Design Thinking method.curriculum-scenario-manufacturing.md— shared factory-floor reference scenario used across all nine modules.
Files
- ATTRIBUTION.mdAdded by AutoGineer877 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md3.5 KiB
- references/curriculum-01-scoping.md4.7 KiB
- references/curriculum-02-research.md5.0 KiB
- references/curriculum-03-synthesis.md5.6 KiB
- references/curriculum-04-brainstorming.md5.7 KiB
- references/curriculum-05-concepts.md5.8 KiB
- references/curriculum-06-prototypes.md5.9 KiB
- references/curriculum-07-testing.md6.1 KiB
- references/curriculum-08-iteration.md6.6 KiB
- references/curriculum-09-handoff.md6.4 KiB
- references/curriculum-scenario-manufacturing.md8.3 KiB
references/curriculum-02-research.md
title: 'DT Curriculum Module 2: Design Research' description: DT curriculum reference for Module 2 design research; load when teaching contextual inquiry, environmental observation, and discovery questioning.
Design research bridges stakeholder assumptions and user reality within the Problem Space. Where scope conversations collect secondhand accounts from decision makers, design research generates firsthand evidence from the people who experience the problem daily. This module teaches learners how to observe, interview, and validate in context.
Key Concepts
Genuine need discovery — Uncovering actual problems users face rather than confirming assumed needs. Research questions must be open-ended and curiosity-driven ("Walk me through your process when X happens") rather than leading ("Don't you think a dashboard would help?"). Learners often confuse validating a hypothesis with genuine discovery; validation seeks confirmation while discovery seeks surprise.
Environmental context understanding — Physical, technical, and organizational constraints affect every aspect of solution design. A solution that works in a quiet office may fail on an 85-90 dB production floor. Learners tend to research user needs in isolation from the environment where those needs occur, missing critical constraints.
Universal discovery sequence — Environmental observation → workflow interviews → constraint validation → unmet need exploration. This progression builds understanding from broad context to specific gaps. Learners often skip observation and jump directly to interviews, losing the ability to notice things users have normalized and stopped mentioning.
Stakeholder-to-user bridge — Moving from what stakeholders believe about users (Method 1 output) to what users actually experience. The gap between these perspectives is often significant and always informative. A common misconception is that stakeholder descriptions are close enough to user reality that direct user engagement is optional.
Techniques
Contextual inquiry combines observation and interview at the user's actual work location during real work. The researcher watches, asks questions about observed behaviors, and notes environmental factors. Good output includes both stated needs and unstated workarounds. The pitfall is conducting interviews in conference rooms detached from the actual work environment.
Environmental observation involves documenting physical conditions, workflow patterns, and tool usage before asking any questions. Watch for 15-30 minutes without interrupting. Good output is a constraint inventory the user never articulated because they have adapted to limitations. The pitfall is observing too briefly to see natural variation.
Cross-source validation compares findings from different research methods and different user groups. Agreement strengthens a finding; disagreement reveals context-dependent factors worth exploring. Good output is a set of validated themes with confidence levels. The pitfall is treating one interview as representative of all users.
Comprehension Checks
A team conducted 10 phone interviews with operators and concluded they need a mobile dashboard. What critical research step did they skip, and what constraints might they have missed?
Why does the universal discovery sequence place environmental observation before workflow interviews?
A researcher asks "Would a voice-controlled system help you during repairs?" Explain why this is a leading question and rewrite it as a discovery question.
When stakeholder descriptions from Method 1 contradict user observations in Method 2, which should take precedence and why?
Practice Exercises
Exercise: Observation plan — Design a 30-minute environmental observation protocol for the manufacturing plant floor during a night shift. Identify what you would document (noise levels, lighting, hand conditions, tool usage, communication patterns) and explain why each observation matters for solution design.
Exercise: Leading question conversion — Convert these leading questions into discovery questions: (a) "Wouldn't a touchscreen kiosk help?" (b) "Do you have trouble finding information in manuals?" (c) "Would you prefer voice commands over typing?" For each conversion, explain what the discovery version can reveal that the leading version cannot.
Learner Level Adaptations
Beginners should focus on the distinction between leading and discovery questions and the importance of environment-based research.
Intermediate learners benefit from comparing contextual inquiry with remote research methods and understanding how environmental constraints discovered here feed into brainstorming constraints in Method 4.
Advanced learners should explore ethical dimensions of research (power dynamics with observed workers, consent in workplace settings) and analyze how research design choices bias the findings.
All DT coaching artifacts are scoped to
.copilot-tracking/dt/{project-slug}/. Never write DT artifacts directly under.copilot-tracking/dt/without a project-slug directory.
Requirements and compatibility
Written for: GitHub Copilot, Claude Code
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/hve-core · .github/skills/design-thinking/dt-curriculum · commit f425e94
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download dt-curriculum.zip