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://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-nonprofit-social-impact.md


title: Nonprofit and Social Impact Industry Context description: Nonprofit and social impact industry context, vocabulary, and constraints for tailoring Design Thinking methods to this sector.

Load this file when the team identifies nonprofit, nongovernmental organization, or social impact sector as their industry context. It provides sector-specific vocabulary, constraints, empathy tools, and a reference scenario that the coach weaves into method-specific guidance.

Industry Profile

  • Sector: Nonprofit and social impact (philanthropic foundations, NGOs, humanitarian and development organizations, advocacy organizations, faith-based organizations, community-based organizations, social enterprises, impact investing vehicles)

  • Key stakeholders: Program officers, grants managers, monitoring and evaluation staff, development and fundraising staff, executive directors, board members, beneficiaries and service recipients and communities served, volunteers, field staff, country directors (international NGOs), implementing partners, donors (institutional, individual, major, government), foundation program officers, advocacy and policy staff, communications and marketing, finance and CFO, lived-experience advisors, equity and inclusion leads, accreditation bodies (BBB Wise Giving, Candid/GuideStar, Charity Navigator)

  • Decision cadence: Program delivery (daily), grant cycle planning (annual to multi-year), donor cultivation (continuous), fundraising campaign (seasonal), board governance (quarterly to annual), advocacy and policy windows (election and legislative cycles), evaluation and learning (grant-tied and continuous)

  • Regulatory environment: IRS 501(c)(3) and 501(c)(4) status and 990 reporting and UBIT and private-foundation rules (5% payout, expenditure responsibility, prohibited self-dealing under IRC §4941-4945), state attorney general charitable registration and oversight, GDPR and CCPA, anti-terrorism financing (OFAC and USA PATRIOT Act for international NGOs), donor-advised fund (DAF) rules, lobbying limits (h-election), EU and international NGO sector regulation variance, IRS group exemption rules, FCPA compliance for international operations, UN Sustainable Development Goals as reporting framework, IRIS+ and GIIN impact metrics, B Corp and social enterprise legal form variants

  • Missing voices to seek out: Beneficiaries and service recipients (especially those furthest from decision-making), field staff and frontline workers (especially those in remote locations or seasonal roles), volunteers (high turnover, often underutilized), recent donors and lapsed donors, implementing partners and subgrantees (power dynamics), marginalized communities (language, access, historical exclusion), lived-experience advisors when genuinely co-designing (not tokenism)

Vocabulary Mapping

Bridge DT language and nonprofit/social impact language bidirectionally. Use sector-specific terms when coaching nonprofit teams.

DT ConceptNonprofit and Social Impact Term
Stakeholder mapStakeholder analysis, community advisory board, theory of change actor map
Pain pointUnmet need, service gap, equity gap, beneficiary friction, "voice gap"
User journeyService journey, beneficiary lifecycle, donor journey (cultivation-solicitation-stewardship)
Observation / field studySite visit, program observation, community listening, asset mapping, ride-along
PrototypePilot program, demonstration project, learning cohort, design lab, prototype intervention
IterationProgram cycle, grant cycle, learning agenda, adaptive management cycle (USAID CLA)
EmpathyCommunity co-design, lived experience, field-based perspective, frontline staff reality
Success metricOutputs vs. outcomes vs. impact (logic model), reach, depth, equity, dollars-per-outcome, beneficiary dignity score, donor retention
Workflow mappingBeneficiary flow, donor cultivation pipeline, program delivery process, grant cycle workflow
Risk assumptionSafeguarding risk, do-no-harm violation, mission drift, reputational risk, donor pullout, equity risk
Constraint-driven designGrant deliverable, logframe, results framework, restricted vs. unrestricted funding, donor reporting, safeguarding policy, IRB compliance
Alert system conceptSafeguarding incident, beneficiary complaint, audit finding, donor escalation, equity incident
Integration timingGrant cycle, fiscal year, fundraising calendar (year-end, GivingTuesday), election and legislative cycle

Constraints and Considerations

Power Asymmetry Between Funder and Grantee

Funders hold the financial power in nonprofit relationships; what they measure and reward shapes program design, often in ways that diverge from beneficiary need. Restricted funding distorts organizational priorities — organizations chase funding that fits funder agendas rather than community voice. "What gets measured by the donor" becomes what the organization optimizes for, even when beneficiary outcomes point elsewhere. Community priorities are often invisible in funder reports. Design thinking must include funder involvement (as stakeholders) but also surface beneficiary priorities independent of funder framing. Challenge power asymmetries explicitly; do not reinforce them through extraction-based research.

Beneficiary Dignity and Do-No-Harm

"Nothing about us without us" is both ethical principle and operational constraint. Beneficiaries are not research subjects; they are experts in their own experience. Any research, observation, or co-design with community members requires reciprocal value (honoraria, learning opportunity, tangible benefit), informed consent, and power-aware facilitation. Extractive research — collecting data and leaving — is anti-pattern. Prototypes and pilots targeting vulnerable populations (children, refugees, people with disabilities, survivors of violence) require safeguarding review and often IRB or ethics committee approval. Design decisions affect real people; treat this weight accordingly.

Chronic Resource Scarcity and the Overhead Myth

Nonprofits operate with dramatically fewer resources than commercial equivalents. Donor preferences for "low overhead" penalize operational investment — infrastructure, systems, staff development, and innovation all get flagged as "overhead" and deprioritized. Teams are chronically understaffed; staff burnout is endemic. DT time feels like a luxury when staff are already overextended. Fundraising campaigns consume staff energy that could go to program delivery. Frame DT not as added work but as time freed up through efficiency — reduced beneficiary friction saves staff time, standardized processes reduce rework. Budget for DT infrastructure investment explicitly; do not ask overextended teams to absorb it.

Mission Orthodoxy and Board Governance

Nonprofit boards can be cautious; founder influence can be strong and long-lasting. Board members often have limited diversity in sector expertise (they are selected for wealth/networks, not sector knowledge). Mission drift is a real risk — expanding into adjacent services can dilute core mission. Design thinking recommendations that suggest mission adjacent shifts face governance friction. Solutions that require board buy-in move slowly. Involve board leadership early; understand that innovation has to pass a mission-fit gate, not just a financial gate.

Safeguarding as Binary Gate

Organizations serving children, refugees, people with disabilities, or other vulnerable populations operate under strict safeguarding requirements. Safeguarding is not a nice-to-have governance concern; it is a compliance requirement. Pilot programs, new partnerships, and operational changes require safeguarding review before launch. Child protection policies, background checks, mandatory reporting, and incident documentation are mandatory frameworks. Design activities involving vulnerable populations must build safeguarding review into the timeline and cannot proceed without clearance. Shortcuts here carry reputational and legal risk that boards will not tolerate.

Measurement Burden and Double Measurement Doom

Nonprofits conduct two types of measurement: donor reporting (to satisfy funder requirements) and program learning (to improve delivery). Donors often require standardized metrics disconnected from program reality; frontline staff know this but still invest time in donor reporting. Organizations measure the same outcomes through multiple frameworks (donor logframe, internal evaluation, impact evaluation, SDG alignment, IRIS+ metrics). This measurement burden competes with learning cycles and staff bandwidth. Solutions requiring additional data collection face staff resistance unless they replace existing measurement overhead. Simplify; do not add.

Empathy Tools

Community Listening and Co-Design Session

Bring beneficiaries and community members into design as co-creators, not research subjects. Recruit lived-experience advisors and compensate them for their time and expertise (honoraria, not token stipends). Use power-aware facilitation: balance speaking time, surface whose voices dominate, explicitly invite quiet voices. Frame co-design as "we have a problem and we need your expertise" rather than "we have a solution, what do you think?" Use participatory methods (mapping, photo voice, ranking exercises) alongside conversation. Document agreements and decisions; follow up on commitments. Repeat listening sessions as co-design cycles iterate; beneficiary involvement should extend through implementation, not stop at prototype feedback.

Field Site Visit and Service Observation

Conduct multi-site visits to understand variation in how services are delivered and experienced. Avoid "Potemkin village" donor visits (scripted, cleaned-up contexts). Spend time with frontline staff and beneficiaries, not just leadership. Observe during natural operations, not special events. Sit in on service delivery, case management meetings, or community sessions. Note where staff improvise, where protocol breaks down, where beneficiary needs exceed resource availability. Notice who is missing — which populations are underserved or not appearing. Ask field staff what they would change if they had resources (often surfaces equity gaps masked by scarcity). Compare field reality to board expectations and funder reporting; the gap usually indicates design opportunity.

Donor and Funder Interview

Conduct cultivation conversations with donors and funders (foundation program officers, major donors, government funders) to understand their mental models, theory of change, and reporting expectations. Funders often have unstated assumptions about how change happens; surfacing these assumptions helps explain why certain metrics matter and others do not. Ask what success looks like from their perspective and what concerns keep them awake at night. Ask how they measure impact and what evidence convinces them. Funder interviews are empathy tools for understanding constraints and incentives; use them to inform how DT activities should be framed to secure funder buy-in and resource commitment.

Frontline Staff and Volunteer Shadow

Spend time working alongside frontline staff and volunteers in their delivery context. Observe where they make judgment calls, where resources constrain service, and where beneficiary requests exceed their capacity. Shadow during high-stress periods (fiscal year-end, emergency response, seasonal peaks) to see how systems behave under pressure. Note where staff create workarounds, bypass steps, or bend protocol to serve beneficiaries. Observe volunteer retention — high volunteer churn signals service design problems (confusing processes, unclear impact, poor coordination, beneficiary friction that volunteers feel acutely). Debrief with staff and volunteers after observation to understand their perspective on barriers and opportunities. Frontline staff know what needs to change; they often lack the platform to say it to leadership.

Reference Scenario

Context: A workforce-development nonprofit achieves high program completion rates (85%) but faces disappointing 6-month job-placement outcomes (42%, vs. sector benchmark of 65%). The team has invested in case management, skills training, and job search support. Leadership is under funder pressure to improve placement metrics without additional funding.

Discovery (Methods 1-3): Scope conversations reveal the initial request is "build a job-matching platform or job board to connect graduates with employers." Community listening sessions with recent graduates (compensated for their time) and frontline staff shadows surface the real problem: the gap is not job availability or job searching — it is post-program isolation and structural barriers. Graduates lack the social capital that hiring managers screen for (networks, professional references, mentorship). Transit access to job sites is inconsistent; some graduates cannot reliably reach interview locations. Childcare coverage during job interviews is missing. These barriers are outside the funded program scope that the donor's logframe rewards the organization for delivering against. Job board addresses symptoms, not root causes.

Solution (Methods 4-6): Brainstorming generates solution themes: extended mentorship network, structured employer networking, integrated transit and childcare logistics, and post-placement employment coaching. Lo-fi prototypes reveal tensions: donors want "low-overhead" job board; organization wants sustained support. Prototypes reveal that employers care about soft skills and network introduction, not platform features. Staff prototypes surface that organization lacks capacity to manage extended support; solutions require new staffing and donor commitment. Community co-design reveals that graduates want longer-term career coaching, not just immediate placement.

Implementation (Methods 7-9): Hi-fi prototype pilots extended support model (3-month post-placement coach-ins, employer networking cohorts, transit support subsidy) with one cohort. Placement rates improve to 72% at 6 months in pilot; job retention at 12 months improves from 55% (historical) to 71%. Organization needs to renegotiate with donor to reframe theory of change — shift from "placement numbers" to "employment quality and retention"; this requires funder alignment on outcome metrics. Post-pilot iteration focuses on volunteer mentor recruitment and employer partnership sustainability. The real work is organizational change (funder renegotiation, staffing model redesign, equity integration) rather than platform features.

  • 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 or Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download dt-methods.zip