Generated banner for Dt Curriculum
Generated logo for Dt Curriculum

Dt Curriculum

MicrosoftOfficialPublished by Microsoft

  • Skill
  • Guidelines
  • Education and learning
  • MIT
  • No issues found

From the author

Design Thinking learning curriculum covering nine progressive modules across the full Problem, Solution, and Implementation Space methods plus a shared manufacturing reference scenario for teaching and practice
— the description by Microsoft

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

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/dt-curriculum/download
  2. Unzip 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.

ReferenceWhen to load
curriculum-01-scoping.mdTeaching Method 1: Scope Conversations (Problem Space).
curriculum-02-research.mdTeaching Method 2: Design Research (Problem Space).
curriculum-03-synthesis.mdTeaching Method 3: Synthesis (Problem Space).
curriculum-04-brainstorming.mdTeaching Method 4: Brainstorming (Solution Space).
curriculum-05-concepts.mdTeaching Method 5: User Concepts (Solution Space).
curriculum-06-prototypes.mdTeaching Method 6: Low-Fidelity Prototypes (Solution Space).
curriculum-07-testing.mdTeaching Method 7: High-Fidelity Prototypes (Implementation Space).
curriculum-08-iteration.mdTeaching Method 8: User Testing (Implementation Space).
curriculum-09-handoff.mdTeaching Method 9: Iteration at Scale (Implementation Space).
curriculum-scenario-manufacturing.mdAlongside 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.md through curriculum-09-handoff.md — one module per Design Thinking method.

    • curriculum-scenario-manufacturing.md — shared factory-floor reference scenario used across all nine modules.

Files

references/curriculum-04-brainstorming.md


title: 'DT Curriculum Module 4: Brainstorming' description: DT curriculum reference for Module 4 brainstorming; load when teaching divergent-convergent phases, constraint-driven creativity, and philosophy-based clustering.

Brainstorming is the entry point to the Solution Space. After the Problem Space established what problems exist and for whom, brainstorming generates the widest possible range of approaches before evaluating any of them. This module teaches learners why strict phase separation and quantity-first thinking produce stronger solution portfolios than careful early filtering.

Key Concepts

Divergent vs convergent phases — Brainstorming operates in two strictly separated phases. Divergent thinking generates as many ideas as possible without evaluation. Convergent thinking then groups and selects from that pool. Mixing the phases — evaluating ideas while generating them — causes premature convergence where early ideas anchor thinking and psychologically safer options dominate. Learners often believe they can generate and evaluate simultaneously; research consistently shows this produces fewer and less creative ideas.

Constraint-driven creativity — Environmental limitations from research become creative drivers rather than barriers. "Operators have greasy hands" is not a dead end — it is a creative prompt that leads to voice activation, gesture control, foot pedals, and elbow-operated interfaces. Learners commonly treat constraints as reasons solutions will not work rather than as parameters that shape novel approaches.

Philosophy-based clustering — Ideas are grouped by underlying solution approach ("hands-free interaction," "collaborative knowledge sharing") rather than surface features ("voice chatbot," "wiki page"). This reveals solution themes where each theme represents a different philosophy for addressing the problem. Learners tend to group by technology ("AI solutions," "mobile solutions") which obscures the underlying design intent.

Minimum idea threshold — Teams generate at least 15 ideas before any evaluation begins. The threshold pushes past obvious first responses into creative territory. Learners resist this, believing their first 5 ideas cover the space; in practice, the most innovative concepts typically emerge in the second half of ideation.

Techniques

AI spring-boarding uses AI to generate a rapid initial set of ideas that the team then builds on, redirects, or inverts. The AI output is a starting point for human creativity, not the answer. Good output is a set of AI-generated starters that the team has modified, combined, or used as inspiration for entirely different approaches. The pitfall is accepting AI output as the final idea set.

Perspective multiplication reframes the problem from different stakeholder viewpoints: "How would a night-shift operator solve this?" → "How would a safety officer solve this?" → "How would a new hire solve this?" Each perspective generates ideas the others miss. Good output is ideas tagged by the perspective that generated them. The pitfall is defaulting to the most powerful stakeholder's perspective.

Scenario expansion takes a single idea and maps it across different use cases: normal operation, emergency situations, shift changes, training new workers. This reveals whether an idea is robust or fragile. Good output is a set of ideas stress-tested against realistic scenarios. The pitfall is only considering ideal conditions.

Comprehension Checks

  1. A team generated 8 ideas and immediately began voting on the best one. What two problems does this approach create?

  2. During brainstorming, a team member says "Voice control would never work, it is too noisy." Explain why this statement is harmful during the divergent phase and how it should be handled.

  3. A team clustered their ideas into "AI solutions," "mobile solutions," and "hardware solutions." What is wrong with this clustering approach, and how should they recluster using philosophy-based grouping?

  4. Why does the manufacturing scenario constraint of greasy hands improve brainstorming rather than limit it? Provide an example idea that exists only because of this constraint.

Practice Exercises

Exercise: Constraint-to-idea generation — Starting from three manufacturing constraints (85-90 dB noise, greasy hands, limited floor space), generate at least 5 ideas per constraint. Then identify which ideas address multiple constraints simultaneously — these are often the strongest candidates.

Exercise: Philosophy-based clustering — Given these 10 ideas for the manufacturing scenario: (1) voice-activated repair guide, (2) buddy system app for shift pairs, (3) AR overlay on equipment, (4) senior operator video library, (5) predictive maintenance alerts, (6) gesture-controlled display, (7) mentor matching across shifts, (8) vibration-pattern notifications, (9) knowledge capture during repairs, (10) foot-pedal interface. Group them into 3-4 philosophy-based themes and name each theme.

Learner Level Adaptations

Beginners should focus on the divergent-convergent distinction and practice generating ideas without evaluation.

Intermediate learners benefit from comparing philosophy-based and technology-based clustering approaches and understanding how synthesis themes from Method 3 scope the brainstorming space.

Advanced learners should explore how group dynamics (seniority, personality, domain expertise) affect which ideas get generated and suppressed, and analyze when a brainstorming session signals the need to return to Method 2 for more research.

  • 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