Overview

Create dt-method-09-iteration.instructions.md — the method-tier instruction file for Method 9: Iteration at Scale. This is the final method in the DT curriculum. Users systematically refine their prototypes based on Method 8 testing results, plan for scale, and prepare for organizational deployment. Method 9 covers organizational deployment — not just code deployment — addressing change management, stakeholder communication, and adoption planning.

Target File

.github/instructions/dt-method-09-iteration.instructions.md

Frontmatter

---
description: 'Design Thinking Method 9: Iteration at Scale — systematic refinement, scaling patterns, and organizational deployment'
applyTo: '**/.copilot-tracking/dt/**/method-09*'
---

Required Content

Method Purpose

Method 9 transforms tested prototypes into deployment-ready solutions. Users apply test findings (Method 8) systematically, plan for scale beyond the prototype context, and prepare the organizational ground for adoption. This method bridges DT's exploration mindset to production deployment reality.

Three Sub-Methods

Two Specialized Hats

Organizational Deployment (Not Just Code)

Method 9's deployment planning covers dimensions beyond technical release:

• Change management: Who is affected by this solution? What changes in their daily workflow? How do we prepare them?
• Stakeholder communication: How do we message the solution to different stakeholder groups (executives, users, support teams)?
• Training and onboarding: What does the first-use experience look like? What documentation or training is needed?
• Adoption metrics: How do we measure whether the solution is actually being used and creating value?
• Feedback loops: Post-deployment channels for ongoing feedback and iteration

Scaling Considerations

Moving from prototype to production introduces scaling questions:

• Technical scaling: Performance, reliability, edge cases not covered in prototype
• User scaling: Going from test participants to full user base — different skill levels, contexts, expectations
• Process scaling: Supporting processes (helpdesk, training, updates) that need to scale alongside the solution
• Constraint reassessment: Revisiting feasibility constraints from Method 5 at production scale

Method 9 Artifacts

Outputs stored at .copilot-tracking/dt/{project-slug}/method-09-iteration/:

• refinement-log.md — Prioritized test findings, iteration decisions, and re-test results
• scaling-assessment.md — Technical, user, and process scaling analysis
• deployment-plan.md — Organizational deployment plan with change management, training, and adoption metrics
• iteration-summary.md — Final iteration state and readiness assessment

Coaching Approach

The coach in Method 9:

• Maintains iteration discipline: "That's a new feature, not a refinement — should we revisit Method 4 for that, or save it for a future cycle?"
• Broadens perspective: "The technical work is solid — let's make sure the people side is equally prepared"
• Celebrates completion: "You've taken an idea from a rough scope conversation through structured testing to a deployment plan. That's a complete DT cycle."
• Bridges to handoff: "This looks ready for the Implementation Space exit handoff — want to generate the RPI transition artifact?"

Token Budget

Target: ~1,500-2,000 tokens (method tier)

How to Build This File

This is an .instructions.md file — use the prompt-builder agent (not task-implementor) for the authoring phase. The prompt-builder includes built-in Prompt Quality Criteria validation and sandbox testing specific to AI artifacts (.instructions.md, .prompt.md, .agent.md, SKILL.md).

Workflow: /task-research → /task-plan → /prompt-build → /task-review
Between each phase, run /clear to reset context.

Phase 1: Research

Gather source material for the iteration at scale method instruction file.

Source Material: design-thinking-for-hve-capabilities/guidance/09-iteration-at-scale.md
This file lives in the DT4HVE repository. If you don't have local access, ask the user to provide it or use read_file if the repo is cloned nearby.

Steps:

1. Read the source material above.
2. Read .github/instructions/prompt-builder.instructions.md for authoring standards.
3. Read any existing dt-method-* instruction files for structural precedent.
4. Gather content on iteration patterns, scaling strategies, organizational deployment frameworks, and change management approaches.

Starter prompt:

/task-research

Research for dt-method-09-iteration.instructions.md

Read the DT4HVE source material at design-thinking-for-hve-capabilities/guidance/09-iteration-at-scale.md. Extract:
- Iteration patterns for continuous improvement cycles
- Scaling strategies for expanding from pilot to organization-wide adoption
- Organizational deployment frameworks covering people, process, and technology
- Change management approaches for sustaining design thinking practices
- Metrics and feedback loops for measuring iteration effectiveness at scale

Also read .github/instructions/prompt-builder.instructions.md for authoring standards and any existing dt-method-*.instructions.md files for structural precedent.

Output: research summary from Phase 1 above

Phase 2: Plan

Plan the file structure and content organization using the research output.

Steps:

1. Review the research output from Phase 1.
2. Plan the instruction file structure — method purpose, three sub-methods, two specialized hats, organizational deployment sections, scaling considerations, coaching examples.
3. Define section ordering, token allocation, and applyTo targeting.

Starter prompt:

/task-plan

Plan for dt-method-09-iteration.instructions.md

Using the Phase 1 research output, plan the instruction file:

- Method purpose: sustaining and scaling design thinking through organizational iteration
- Three sub-methods: 9a Iteration Planning, 9b Scaling Assessment, 9c Organizational Deployment
- Two hats: Iteration Coach, Deployment Strategist
- Organizational deployment sections covering people, process, and adoption — not just code
- Scaling considerations with readiness criteria and risk mitigation
- Change management coaching for sustaining DT practices
- Section ordering and token budget allocation (~1,500-2,000 tokens)
- applyTo: '**/.copilot-tracking/dt/**/method-09*'

Output: plan at .copilot-tracking/plans/{date}-dt-method-09-plan.md

Phase 3: Build

Author the instruction file using the prompt-builder agent.

Steps:

1. Review the plan from Phase 2.
2. Author the instruction file using /prompt-build.
3. Organizational deployment is the defining feature — the file must go beyond code deployment to cover people, process, and adoption.

Starter prompt:

/prompt-build file=.github/instructions/dt-method-09-iteration.instructions.md

Build using the plan at .copilot-tracking/plans/{date}-dt-method-09-plan.md.

This is a method-tier instruction file for Method 9: Iteration at Scale. Key authoring notes:
- applyTo targets Method 9 artifact paths: '**/.copilot-tracking/dt/**/method-09*'
- Organizational deployment is the defining feature — go beyond code deployment to cover people, process, and adoption
- Three sub-methods with consistent table structure
- Two specialized hats with activation triggers
- Scaling assessment with readiness criteria and risk factors
- Change management coaching for sustaining design thinking practice
- Iteration discipline guidance — structured improvement cycles, not ad hoc changes
- Coaching examples demonstrate organizational-level thinking, not just technical iteration

Phase 4: Review

Validate the instruction file against the plan and prompt-builder standards.

Steps:

1. Review the built file against prompt-builder standards and the issue requirements.
2. Validate organizational deployment coverage, iteration discipline guidance, scaling assessment quality, and structural compliance.

Starter prompt:

/task-review

Review: .github/instructions/dt-method-09-iteration.instructions.md

Validate against:
- prompt-builder.instructions.md authoring standards
- Organizational deployment coverage — people, process, and adoption addressed
- Iteration discipline guidance — structured cycles, not ad hoc
- Scaling assessment quality with readiness criteria
- Change management coaching presence
- Token budget: ~1,500-2,000 tokens
- Frontmatter applyTo correctness
- Three sub-methods and two hats with consistent table structure

After Review

• Pass: Mark complete.
• Iterate: Address review findings, rebuild, re-review.
• Escalate: If blocked by missing DT4HVE source material or architectural questions, raise to the user.

Authoring Standards

Follow .github/instructions/prompt-builder.instructions.md:

• applyTo targets Method 9 artifact paths
• Three sub-methods with consistent table structure
• Two specialized hats with activation triggers
• Organizational deployment is broader than technical deployment

Success Criteria

• File created at .github/instructions/dt-method-09-iteration.instructions.md
• Frontmatter applyTo targets Method 9 artifact paths
• Three sub-methods defined (iteration planning, systematic refinement, deployment planning)
• Two specialized hats with clear activation triggers
• Organizational deployment covers change management, training, communication, and adoption metrics
• Scaling considerations address technical, user, and process dimensions
• Iteration discipline coaching prevents scope creep
• Token count within ~1,500-2,000 target
• Passes task-reviewer validation against prompt-builder standards
• Each prompt, instructions, or agent file registered in collections/design-thinking.collection.yml with path and kind fields
• Each prompt, instructions, or agent file registered in collections/hve-core-all.collection.yml with path and kind fields
• npm run plugin:generate succeeds after collection manifest updates