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/industry-professional-services.md


title: Professional Services Industry Context description: Professional services industry context, vocabulary, and constraints for tailoring Design Thinking methods to this sector.

Load this file when the team identifies professional services as their industry context. It provides professional services–specific vocabulary, constraints, empathy tools, and a reference scenario that the coach weaves into method-specific guidance.

Industry Profile

  • Sector: Professional services (management consulting, legal services, accounting/audit/tax, engineering and architecture, marketing and advertising, staffing, IT services and systems integration)

  • Key stakeholders: Partners, practice leaders, principals, managing directors, project managers, engagement managers, consultants, associates, analysts, senior managers, audit engagement partners, tax practice leaders, lawyers (partners, associates, paralegals), knowledge management and research librarians, business development and proposal teams, conflicts and intake specialists, ethics and independence officers, finance and billing staff, talent and HR, learning and development, client-side relationship sponsors, legal operations, professional indemnity insurers

  • Decision cadence: Engagement delivery (daily to weekly), resource allocation (weekly to monthly), pursuit and proposal (campaign-based, 2-12 weeks), methodology refresh (annual to biennial), rate and partner economics (annual), regulatory compliance (continuous and annual/multi-year cycles)

  • Regulatory environment: PCAOB and AICPA and IFAC (audit), SEC oversight of auditors, state bar associations and ABA Model Rules of Professional Conduct (confidentiality, conflict of interest, fee splitting, unauthorized practice of law), IRS Circular 230 (tax practitioners), state engineering boards and PE licensure and AIA contract documents, FTC advertising rules, GDPR and CCPA, anti-money-laundering rules (legal and accounting), attorney-client privilege and work-product doctrine, accountant-client privilege variants, emerging AI governance (ABA Resolution on AI, auditor AI guidance), data residency and cross-border engagements

  • Missing voices to seek out: Junior staff in years 2-3 (attrition risk), night/weekend workers on distributed teams, staff in underrepresented roles (diversity hires, women in partnership tracks), junior lawyers and paralegals facing competency hurdles, recently departed staff, contract workers and temporary resources during capacity peaks, client-side experience beyond sponsor level, frontline delivery teams separated from partner visibility

Vocabulary Mapping

Bridge DT language and professional services language bidirectionally. Use professional services terms when coaching professional services teams.

DT ConceptProfessional Services Term
Stakeholder mapEngagement team roster, client steering committee, relationship sponsor
Pain pointUtilization drag, realization rate, write-off, scope creep, client churn
User journeyEngagement lifecycle (pursuit-proposal-delivery-close-renewal)
Observation / field studyEngagement shadow, court observation, partner meeting observation, "second chair"
PrototypePilot engagement, accelerator, lab, sandbox client, alpha methodology
IterationEngagement retro, methodology refresh, knowledge harvest cycle
EmpathyClient voice, frontline staff experience, junior attrition signal
Success metricUtilization %, realization rate, billable hours, gross margin per engagement, win rate, NPS
Workflow mappingMatter lifecycle, engagement workflow, knowledge capture and review process
Risk assumptionProfessional liability (E&O), independence violation, conflict of interest, malpractice, reputation risk
Constraint-driven designEthical wall, conflict check, independence requirement, billing code, WBS, scope statement, SOW
Alert system conceptConflict-check hit, budget burn alert, scope-creep flag
Integration timingAudit busy season (year-end), tax filing deadlines, billing cycle, fiscal-year sales push

Constraints and Considerations

Professional Ethics and Privilege

Professional conduct codes are non-negotiable scope boundaries. Attorney-client privilege, work-product doctrine, and accountant-client privilege prevent teams from sharing matter details externally or across clients without explicit consent. Ethical walls (Chinese walls) for conflicts of interest can physically separate teams within the same firm. DT research and prototyping must respect these boundaries: case studies and learnings require de-identification or client approval; pilot testing cannot cross ethical walls; interviews must exclude details that trigger privilege concerns.

Billable-Hour Utilization Model

Partners and resource managers allocate time to billable engagements and non-billable overhead. Time invested in design thinking is lost billing opportunity — hours spent in discovery, prototyping, and iteration do not generate client revenue. Partners resist dedicating scarce high-cost time to innovation work unless directly tied to client delivery or competitive advantage. Reframe DT activities as improving realization rates, reducing write-offs, or accelerating delivery — metrics partners understand and fund.

Partnership Governance

Partnership decisions require consensus or super-majority agreement among equity partners. Individual partners have veto power over methodology changes affecting their practices. New partners take 5-10+ years to earn equity; incentives heavily favor partners over staff. Senior partners often carry the weight of practice leadership and client relationships that give them disproportionate influence. DT coaching must engage practice leaders as stakeholders and sponsors, not just sponsors of delivery. Understand that cultural change in partnership-governed firms is slow; expect implementation horizons measured in years, not quarters.

Client Confidentiality and Conflict Restrictions

Firms cannot test solutions across clients in the same industry without addressing conflict-of-interest restrictions. Some clients have engaged the firm specifically because competitors are excluded. Research insights from one engagement cannot be freely applied to another in the same sector without client consent. Design activities must map to specific engagements or sandbox contexts (internal labs, accelerators) rather than broad cross-client discovery. This constraint makes benchmarking and cross-client learning difficult and drives boutique expertise models.

Knowledge Work Autonomy and Expertise Scarcity

Professionals build personal brands around specialized expertise. Partners fear that codifying expert knowledge (in tools, processes, or junior-ready methodologies) commoditizes their expertise and threatens their differentiation and leverage model. AI and automation add a layer of threat — if expertise can be systematized, AI may eventually substitute for the expertise itself. Design thinking work that threatens to expose, simplify, or automate expert work faces cultural resistance. Frame redesign as enhancing expertise (enabling quicker, higher-quality delivery) rather than replacing it.

Cross-Jurisdiction Regulatory Variance

Audit firms navigate PCAOB (US) alongside IAASB (international) standards. Law firms operate under state bar associations (50+ US jurisdictions with varying confidentiality and conflict rules) plus international bar associations (UK SRA, EU, etc.). Tax practitioners face federal IRS rules plus state tax board rules. Engineering firms must respect PE licensure requirements across states and countries. No single regulatory framework applies globally; variance is intentional and binding. Solutions requiring global rollout must account for jurisdiction-specific compliance checkpoints.

Empathy Tools

Engagement Shadow

Sit as second-chair or observer on a live engagement delivery team across the full engagement lifecycle. Observe partner client meetings, internal team huddles, evidence gathering, and deliverable production. Shadow review cycles to watch how senior partners allocate feedback time and how juniors experience feedback cycles. Observe how deliverables are built: What information sources do delivery teams use? Where do they pull together? Where do workarounds appear? Debrief after key moments to understand decision logic. Engagement shadowing reveals gaps between documented methodology and actual delivery practice.

Time-Entry and Billing Diary Mining

Analyze de-identified time-entry records and billing diaries (with partner consent and audit compliance) to understand where actual effort is concentrated. Time entries often reveal where staff spend time on unplanned activities, rework, and workarounds. Compare expected effort (from proposals and budgets) versus actual effort consumed. Billing analysis surfaces utilization drag, margin leakage, and client relationship risk. Look for narrative patterns in time-entry descriptions: common phrases like "rework," "client delay," "process bottleneck," or "systems integration" flag design opportunities. Billing data tells a truth-telling story that interviews sometimes miss.

Client Voice Interviews

Conduct post-engagement interviews with client-side sponsors and stakeholders (with partner mediation if needed). Clients are often more candid to third-party researchers than they are to the partner who will sell them the next engagement. Ask what went well, what was slow, where communication broke down, and what surprised them. Ask what they would change about process and team interaction. Ask about their experience with other service providers — competitive context. Client voice often surfaces friction that internal team members have normalized or accepted. Combine this with partner perspective to triangulate design requirements.

Knowledge Harvest Session Observation

Firms invest in knowledge capture and dissemination but often struggle with execution. Observe knowledge harvest sessions where experts teach others, internal seminars, and mentoring sessions. These sessions surface the gap between documented methodology and tacit expert knowledge. Watch which insights the expert teaches but didn't document in the SOP. Watch where the junior struggles to follow. Observe where informal workarounds get explained. Observe where knowledge transfer fails across shifts or time zones. Knowledge harvest observation reveals both what needs to be systematized and how to make systematization stick.

Reference Scenario

Context: A mid-market accounting firm experiences accelerating junior staff attrition in years 2-3 despite competitive compensation, benefits, and ostensibly strong mentoring programs. Turnover is double the industry benchmark for this tenure band. Exit interviews cite "disconnected systems," "unclear career path," and "partner bandwidth" as top reasons.

Discovery (Methods 1-3): Scope conversations reveal the initial request is "build a better mentorship and coaching program." Engagement shadow of three junior staff over two-week periods uncovers the real problem: information fragmentation and hidden friction. Juniors use three separate systems to log billable time, file workpapers, and route deliverables for partner review. Each tool has different access patterns, sync timing, and error states. Time-entry mining shows juniors spend 15-20% of their week on system navigation and rework rather than productive work. Time-entry narratives reveal repeated "system sync issues" and "reverted draft" entries. Client voice interviews from recently closed engagements note junior responsiveness lags but don't blame individuals — they blame visibility gaps. Alumni exit interviews reveal the attrition cohort felt isolated from partner feedback and lacked clear skill-progression markers.

Solution (Methods 4-6): Brainstorming generates solution themes: unified engagement workflow, asynchronous review queuing, skill-based task routing, and partner-time-efficient feedback loops. Lo-fi prototypes reveal that partners fear efficiency improvements will pressure them to cut rates to clients or accelerate delivery timelines. Juniors worry that streamlining = commoditization of their expertise. Financial analysis surfaces that current write-offs and junior rework cost the firm 8-12% of engagement margin per junior annually. Prototyped workflow integrations uncover that partners actually want more visibility into junior work (for quality assurance) but lack lightweight ways to spot-check without high-touch review overhead.

Implementation (Methods 7-9): Hi-fi prototypes validate integrated workflow with asynchronous review tooling and skill-progression dashboards, piloted with two engagement teams over a quarter. User testing reveals that partners use the visibility feature more than expected (quality concern, not just mentoring); juniors report 30% time savings on system navigation and clearer feedback cycles. Iteration focuses on feedback velocity and skill-progression transparency. Six-month post-pilot data shows pilot cohort attrition drops to industry benchmark; the firm rolls out to all audit teams and begins assessing methodology refresh for tax practice (different tools, similar fragmentation problem).

  • 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