Generated banner for Dt Methods
Generated logo for Dt Methods

Dt Methods

MicrosoftOfficialPublished by Microsoft

  • Skill
  • Guidelines
  • Business and productivity
  • MIT
  • No issues found

From the author

Design Thinking method coaching knowledge across all nine methods including per-method techniques, deep expertise, and industry context (energy, financial services, healthcare, manufacturing, nonprofit and social impact, pharmaceuticals and life sciences, professional services, public sector, retail and CPG)
— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The dt-methods skill provides a structured reference system for AI agents to coach teams through the Design Thinking process. It organizes guidance into three layers: core method references for day-to-day activities, deep references for advanced facilitation and recovery, and industry-specific context to tailor vocabulary and constraints. The skill covers nine major industries, including energy, healthcare, and financial services, ensuring that coaching is grounded in the specific operational realities and regulatory environments of the user's sector.

What it does

  • Provides step-by-step guidance for nine core Design Thinking methods.
  • Offers advanced facilitation techniques and recovery strategies for complex scenarios.
  • Maps Design Thinking concepts to industry-specific terminology and constraints.
  • Integrates telemetry expectations for session artifacts to ensure observable outcomes.
  • Supplies industry-specific empathy tools and stakeholder considerations.
  • Supports tailoring of coaching based on the active method and identified industry context.

When to use it

  • When facilitating a Design Thinking session and requiring method-specific guidance.
  • When a team needs advanced troubleshooting or recovery techniques during a workshop.
  • When applying Design Thinking within a specific industry to ensure relevant vocabulary and constraints are respected.
  • When defining telemetry or audit trails for Design Thinking session artifacts.

Advantages

  • Ensures consistent coaching across the entire Design Thinking lifecycle.
  • Reduces friction by using industry-appropriate language and concepts.
  • Provides a clear path for scaling from basic methods to advanced facilitation.
  • Integrates operational and regulatory awareness into the design process.

Usage examples

“How should I facilitate a brainstorming session for a team in the energy sector?”
The agent will load the brainstorming method reference and the energy industry context, providing guidance that uses energy-specific terms like 'reliability concern' and 'forced outage rate' while emphasizing safety and regulatory constraints.
“We are stuck during the user research phase; what advanced techniques can we use?”
The agent will access the deep reference for the Design Research method to provide advanced facilitation strategies and recovery techniques to help the team overcome their current roadblock.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/dt-methods/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip dt-methods.zip -d .agents/skills

Documentation by Microsoft

Design Thinking Methods Skill

Entrypoint for Design Thinking method coaching knowledge. The dt-coach agent loads the method reference matching the active method in coaching state, the matching deep reference when advanced technique is needed, and the industry reference when an industry context applies.

How to use this skill

  • Read the method reference for the method currently active in coaching state to ground day-to-day coaching.

  • Read the matching deep reference when the conversation needs advanced facilitation, recovery techniques, or expert frameworks beyond the core method guidance.

  • Read the industry reference when the team has identified one of the nine covered industries as their context, and weave its vocabulary, constraints, and empathy tools into method-specific guidance.

  • Read dt-coach-telemetry.md when DT session artifacts need observable telemetry expectations grounded in telemetry-foundations.

Method references

Industry context references

Load the matching reference when the team identifies its industry context.

ReferenceWhen to load
industry-energy.mdEnergy-sector vocabulary, constraints, empathy tools, and reference scenario.
industry-financial-services.mdFinancial services vocabulary, constraints, empathy tools, and reference scenario.
industry-healthcare.mdHealthcare vocabulary, constraints, empathy tools, and reference scenario.
industry-manufacturing.mdManufacturing vocabulary, constraints, empathy tools, and reference scenario.
industry-nonprofit-social-impact.mdNonprofit and social impact vocabulary, constraints, empathy tools, and reference scenario.
industry-pharmaceuticals-life-sciences.mdPharmaceuticals and life sciences vocabulary, constraints, empathy tools, and reference scenario.
industry-professional-services.mdProfessional services vocabulary, constraints, empathy tools, and reference scenario.
industry-public-sector.mdPublic sector and government vocabulary, constraints, empathy tools, and reference scenario.
industry-retail-cpg.mdRetail and consumer goods vocabulary, constraints, empathy tools, and reference scenario.

Skill layout

.
├── SKILL.md
└── references/
    ├── method-01-scope.md
    ├── method-01-deep.md
    ├── method-02-research.md
    ├── method-02-deep.md
    ├── method-03-synthesis.md
    ├── method-03-deep.md
    ├── method-04-brainstorming.md
    ├── method-04-deep.md
    ├── method-05-concepts.md
    ├── method-05-deep.md
    ├── method-06-lofi-prototypes.md
    ├── method-06-deep.md
    ├── method-07-hifi-prototypes.md
    ├── method-07-deep.md
    ├── method-08-testing.md
    ├── method-08-deep.md
    ├── method-09-iteration.md
    ├── method-09-deep.md
    ├── industry-energy.md
    ├── industry-financial-services.md
    ├── industry-healthcare.md
    ├── industry-manufacturing.md
    ├── industry-nonprofit-social-impact.md
    ├── industry-pharmaceuticals-life-sciences.md
    ├── industry-professional-services.md
    ├── industry-public-sector.md
    ├── industry-retail-cpg.md
    └── dt-coach-telemetry.md

Files

references/method-04-brainstorming.md


title: 'DT Method 04: Brainstorming' description: Design Thinking Method 04 (Brainstorming) for generating divergent solution ideas before convergence.

AI-assisted divergent and convergent thinking generates diverse solution ideas and organizes them into high-value themes. Without brainstorming, teams jump to the first obvious solution without exploring alternatives. This method serves as the essential entry point to the Solution Space.

Purpose

Transform problem understanding from Method 3 into multiple solution approaches through divergent ideation and convergent theme discovery, preventing teams from settling on first obvious solutions.

Coaching Identity Extension

Method 4 extends the foundational dt-coaching-foundation coaching-identity Think/Speak/Empower framework with brainstorming-specific guidance:

Think: Assess ideation momentum, constraint integration, and phase boundaries. Recognize when divergence has sufficient breadth or when convergence readiness emerges.

Speak: Share observations about constraint-informed creativity, theme patterns, and energy shifts. "I'm noticing your ideas are getting more detailed, want to stay rough for now?" or "These three ideas seem to share an approach..."

Empower: Offer process choices rather than idea judgment. "Ready to look for themes or generate more angles first?" Close with agency-preserving options.

Coaching Hats

Two specialized coaching hats provide focused expertise within Method 4. The coach switches hats based on activation triggers detected in user conversation.

Ideation Facilitator

Divergent thinking expertise. Guides constraint-informed generation, perspective multiplication, and premature-evaluation prevention.

Activation triggers:

  • User begins generating solution ideas or asks how to start ideation.

  • User is in sub-method 4b or setting up 4a session structure.

  • User evaluates or judges ideas during the divergent phase.

  • User generates overly detailed proposals instead of rough one-liners.

  • Conversation energy is high and generative with new ideas flowing.

Coaching focus:

  • Constraint catalyst technique: reframe environmental limitations as creative drivers rather than barriers ("Given greasy hands, what interfaces emerge?").

  • Perspective shifting: rotate through stakeholder viewpoints to generate ideas from different angles ("What if we approached from [stakeholder] angle?").

  • Lo-fi enforcement: redirect detailed proposals back to rough one-liners and parking-lot detailed thinking for later.

  • Evaluation blocking: intercept judgment language during divergent phases ("Save assessment for convergence phase").

  • Energy sustaining: introduce new constraint scenarios or perspective shifts when ideation momentum slows.

Convergence Guide

Theme discovery expertise. Guides philosophy-based clustering, pattern recognition, and Method 5 handoff preparation.

Activation triggers:

  • User has met divergent targets and asks how to organize ideas.

  • User begins grouping or categorizing ideas spontaneously.

  • User asks what themes or patterns are emerging.

  • Conversation energy naturally shifts from generation toward organization.

  • User explicitly requests convergence or pattern recognition.

Coaching focus:

  • Philosophy-based clustering: group ideas by underlying solution approach rather than surface feature similarity.

  • Theme discovery prompting: guide users to find connecting philosophies across different ideas ("What philosophies connect these different ideas?").

  • Rationale documentation: capture why ideas cluster together, not just that they do, for Method 5 handoff.

  • Creative momentum preservation: maintain generative energy while organizing insights, preventing convergence from killing creativity.

  • Reverse-transition detection: identify when clustering reveals ideation coverage gaps and recommend returning to divergent thinking.

Sub-Method Phases

Method 4 organizes into three sequential phases. Each phase produces distinct artifacts and activates different coaching behaviors.

Phase 1: Ideation Planning

Establish constraints, objectives, and session structure before ideation begins. Translate Method 3 synthesis outputs into a brainstorming strategy.

Activities: environmental constraint identification from Method 3 synthesis, divergent target setting (for example, "Generate 20 ideas before clustering"), AI collaboration pattern selection, stakeholder perspective identification for exploration.

Exit criteria: a session plan exists with documented constraints, divergent targets, chosen AI collaboration pattern, and stakeholder perspectives to explore.

AI pattern: Silent Observer for processing planning inputs and session design.

Coaching hat: setup phase (foundational coaching identity, no specialized hat).

Phase 2: Ideation Execution

Generate diverse solution ideas using AI as creativity springboard. Maintain strict separation between generation and evaluation.

Activities: ideation technique application with AI assistance, lo-fi quality enforcement (rough one-liners only), multiple perspective and constraint scenario exploration, divergent target progression tracking.

Exit criteria: divergent targets are met (minimum 15 ideas generated), ideas span 4-6 different solution categories, multiple stakeholder perspectives are represented, and lo-fi quality is maintained throughout.

AI pattern: all three patterns available based on team preference and session dynamics.

Coaching hat: primarily Ideation Facilitator.

Phase separation: strict "generate first, evaluate later" boundary enforcement.

Phase 3: Ideation Convergence

Discover themes through philosophy-based clustering and prepare Method 5 handoff artifacts.

Activities: philosophy-based idea grouping, theme identification (3-5 distinct solution themes with rationale), theme characteristic documentation, Desirability/Feasibility/Viability preview for Method 5.

Exit criteria: 3-5 distinct solution themes are documented with rationale, each theme includes representative ideas and constraint integration notes, and Method 5 handoff artifacts are complete.

AI pattern: Silent Observer for pattern recognition, limited Backup Generator for clustering assistance.

Coaching hat: Convergence Guide.

Reverse-transition: return to Phase 2 when clustering reveals missing solution categories, fewer than 3 distinct themes emerge, or a stakeholder perspective is unrepresented in the idea set.

AI Collaboration Patterns

AI as Prep + Synthesis

Individual preparation, natural team brainstorming, AI pattern analysis afterward

  • "AI, analyze these 20 ideas—what themes emerge? What philosophies connect different approaches?"

AI as Backup Generator

Natural ideation first, AI intervention during energy stalls, return to human momentum

  • "We're hitting a wall. AI, given these constraints, what are 5 different angles we haven't explored?"

AI as Silent Observer

AI processes conversation, provides convergent synthesis, validates emerging patterns

  • "AI, you've been listening—what solution categories are emerging from this discussion?"

Ideation Techniques

Constraint-Informed Generation

Use environmental limitations as creative drivers, not barriers

  • "Given [specific constraint], what creative approaches emerge?"

  • "How might we solve this if [limitation] was our primary design challenge?"

Perspective Multiplication

Generate ideas from multiple stakeholder viewpoints and contexts

  • "Approach this from [user role] perspective, then [different stakeholder] perspective"

  • "What if we optimized for [specific user context] first?"

Scenario Expansion

Context-specific adaptations and constraint variations

  • "How does this idea adapt to [different environment/situation]?"

  • "What variations emerge under [different constraint set]?"

Convergence Guidance

Philosophy-Based Clustering

Group ideas by underlying solution approach rather than surface similarities:

  • "Hands-free interaction" (voice, gesture, audio guidance)

  • "Visual guidance" (AR, displays, alerts)

  • "Collaborative knowledge" (peer networks, shared solutions)

  • "Proactive assistance" (predictive, preventive, maintenance)

Theme Documentation Requirements

For each theme, document:

  • Core solution philosophy

  • Representative ideas within theme

  • Environmental constraint integration

  • Stakeholder value implications

  • Method 5 concept development potential

Divergent-to-Convergent Transition
  • Numerical targets met (15+ ideas generated)

  • Energy naturally shifts toward organization

  • Explicit team readiness for pattern recognition

  • Diminishing returns on new idea generation

Quality Standards

Lo-Fi Enforcement

Ideas remain rough one-liners, not detailed proposals or implementations. When users begin over-detailing, redirect to capturing the core concept and parking detailed thinking for later.

Phase Separation

Strict boundaries between generation and evaluation maintain psychological safety. During divergent phases, intercept judgment language and redirect to idea generation.

Constraint Integration

Every idea accounts for environmental and business limitations discovered in Method 3. Constraints serve as creative catalysts rather than barriers.

Quantitative Targets

Generate a minimum of 15 ideas before evaluating any. Diversity target: ideas spanning 4-6 different solution categories. Convergence target: 3-5 clear, distinct themes. Fewer than 3 themes suggests premature convergence. More than 5 suggests insufficient analysis.

Multiple Philosophies

Successful sessions produce themes representing distinct solution approaches, not variations of a single approach. Themes must span different solution strategies with clear rationale for each.

Method 5 Readiness

Themes provide sufficient foundation for concept development without premature convergence on a single solution. Each theme includes representative ideas, constraint integration notes, and concept development potential.

Brainstorming Goals

Accomplish
  • Divergent breadth: generate ideas from multiple angles and solution philosophies before any evaluation.

  • Constraint-informed creativity: use environmental and business limitations as creative drivers, not barriers.

  • Philosophy-based clustering: group ideas by underlying solution approach rather than surface feature similarity.

  • Lo-fi fidelity: maintain rough one-liner quality throughout ideation, deferring detailed proposals.

Avoid
  • Premature evaluation: judging or filtering ideas during divergent phases.

  • Single-philosophy convergence: settling on variations of one approach rather than exploring distinct solution strategies.

  • Detailed-proposal drift: allowing rough ideas to expand into implementation proposals during ideation.

  • Convergence without sufficient divergence: clustering before meeting minimum divergent targets.

Success Indicators

During Brainstorming
  • Divergent targets progressing toward 15+ ideas.

  • Ideas represent multiple stakeholder perspectives and constraint scenarios.

  • Lo-fi quality maintained with rough one-liners, not detailed proposals.

  • Phase separation enforced with no evaluation during divergent work.

After Brainstorming
  • 3-5 distinct solution themes documented with clustering rationale.

  • Themes represent different solution philosophies, not surface variations.

  • Each theme includes representative ideas and constraint integration notes.

  • Method 5 handoff artifacts are complete and ready for concept development.

Input from Method 3

  • Affinity clusters with labeled themes and representative evidence

  • Insight statements explaining why patterns matter

  • Problem definition with scope, affected stakeholders, constraints, and success signals

  • How-might-we questions bridging problem understanding to ideation

  • Environmental and workflow constraints documented with design implications

Output to Method 5

  • Clustered solution themes with philosophy-based rationale for each grouping

  • Representative ideas within each theme demonstrating the approach

  • Constraint integration notes showing how environmental factors shaped ideation

  • Stakeholder value implications for each theme

  • Concept development entry points identifying where each theme can evolve

Artifacts

Create and maintain Method 4 brainstorming artifacts under the folder:

  • .copilot-tracking/dt/{project-slug}/method-04-brainstorming/

Within this folder, produce and update these files:

  • .copilot-tracking/dt/{project-slug}/method-04-brainstorming/session-plan.md Document the ideation session structure including constraints from Method 3, divergent targets, chosen AI collaboration pattern, and stakeholder perspectives to explore.

  • .copilot-tracking/dt/{project-slug}/method-04-brainstorming/divergent-ideas.md Capture all generated ideas as rough one-liners organized by generation round or perspective. Include the constraint scenario or stakeholder angle that produced each idea.

  • .copilot-tracking/dt/{project-slug}/method-04-brainstorming/theme-clusters.md Document the philosophy-based clustering results. For each theme, include the core solution philosophy, representative ideas, clustering rationale, constraint integration notes, and concept development potential.

  • .copilot-tracking/dt/{project-slug}/method-04-brainstorming/session-notes.md Capture session observations including energy shifts, phase transitions, coaching interventions, and reverse-transition decisions.

These artifacts are the primary structured outputs handed off to Method 5 for concept development.

  • 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-methods · 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-methods.zip