Playbook
0 / 10 complete0%
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08
  9. 09
  10. 10
Step 08 of 10 4-6 weeks· advanced

Step 8: Pilot with a Subset of Users

Move 5-10% of users to the new app exclusively. Watch their behavior. Fix what breaks. This is where the workflows nobody mentioned (because they were "obvious") surface.

What you're doing in this step

Identify pilot users, onboard them with support, run daily / weekly check-ins, triage and prioritize issues, deploy fixes, and measure satisfaction before expanding.

Recommended prompts

Use one of these to do the work in your IDE

Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.

Primary recommendation 0.5 day

Feature Flag Rollout Strategy for Migrations

Use feature flags to safely route traffic between legacy and new systems during migration with controlled rollout and instant rollback.

View template
Template· Template 1-2 days

Behavior Parity Test Suite

Generate tests that lock down current legacy behavior so the new system doesn't accidentally change it during migration.

Use this when: Pilot reveals parity gaps — record more golden tests for the affected flows

View template
Recommended skills

Drop these into Claude Code for this phase

Skills auto-trigger on the right kind of request. Install once; they apply to every prompt that fits.

Skill· Skill 5 min setup

Performance Profiler Skill

Claude Code skill that diagnoses performance issues — slow queries, slow renders, memory leaks — with measurement-first methodology.

claude-code
Skill· Skill 5 min setup

Code Reviewer Skill

Claude Code skill that performs comprehensive code review on PRs and diffs, prioritized by severity with concrete fixes.

claude-code
Recommended MCP configs

Wire these tools into Claude Code first

MCP servers give Claude Code direct access to external systems (Jira, browsers, databases). Configure once.

MCP config· MCP config 10 min setup

Azure DevOps MCP for Evoke

Pre-configured Azure DevOps MCP server for Claude Code — work items, repos, PRs, and pipelines from chat.

claude-codemcp
MCP config· MCP config 10 min setup

GitHub MCP for Evoke

Pre-configured GitHub MCP server for Claude Code — issues, PRs, code search, and Actions from chat.

claude-codemcp
When you're done

Verify these in your own work before moving on

This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.

  • Pilot users identified, onboarded, supported
  • Daily / weekly check-ins with pilot users
  • Issues triaged and prioritized
  • Fixes deployed
  • Pilot user satisfaction acceptable to expand
Common pitfalls

What goes wrong at this step

  • No pilot phase — going from internal testing to 100% rollout misses real-world issues
  • Pilot users not representative — picking "tech-friendly" users hides issues real users will hit
  • Ignoring pilot feedback — if pilot users hate something, real users will too
← Previous step

Command Palette

Search for a command to run...