PDF + workbook + agenda · being packaged
Move the system. keep the product moving.
Scope the work, protect capacity and decide what must be true before each rollout. The five-chapter playbook, editable worksheets and a fully worked migration case help you turn the method into an operating plan.
or write to kir.zhukovsky@gmail.com — subject prefilled
No email, no form — the sample is a direct download.
Included in The Migrate Playbook:
- Five-chapter migration guide
- Editable planning worksheets
- Harbor Console worked case
- Release and rollback runbook
- A real decision trail
- The fictional Harbor Console case connects inventory, capacity, rollout gates and an unresolved exception. A successful slice does not imply global retirement.
- Blank and worked materials
- Keep the original print book and worksheets. Use the companion's filled records to understand what a defensible answer looks like.
Kiryl Zhukouskimaintainer of the Agent-Ready Index — a dated, source-linked reference for 37 systems.
The Migrate Playbook
or write to kir.zhukovsky@gmail.com — subject prefilled
What happens when capacity gets squeezed?
Protect capacity before promising a date. This free exercise shows the kind of work the kit helps you carry forward.
120 hours of illustrative work
15.0 productive hours per week
8.0 weeks
- 01Map the surface18 h
Inventory, owners and a bounded pilot · week 0.0–1.2
- 02Bridge the tokens26 h
Aliases, visual checks and a rollback path · week 1.2–2.9
- 03Move the pilot42 h
A migrated workflow and acceptance evidence · week 2.9–5.7
- 04Roll out and retire34 h
Adoption checks before removing the old path · week 5.7–8.0
A sequencing exercise, not a delivery estimate. These stages run in order; reviews and dependencies may add elapsed time. The companion case shows how to replace assumptions with your inventory and team constraints.
Nearly done is not the same as safe to retire.
The Harbor Console case carries an unresolved billing exception all the way to the final decision. It shows the tradeoff, the owner and the next review instead of making the example end perfectly.
Harbor Console, its people, inventory, estimates and weekly readings are fictional teaching data. No customer outcome, measured productivity gain or benchmark is claimed.
Harbor Console / Week 10
Same adopted files. Two very different denominators.
Decision: keep the legacy dependency.
Two scoped files still need the old grid. Reporting remains outside the first scope. The runbook records what would allow removal and who owns the next check.
- Included: filled case workbook and editable source records
- Included: capacity, rollout gates and decision records
- Included: measurement definitions and a case validator
A method, a worked case and the plan you make your own. follow the reasoning, then adapt the editable materials to your product.
- 01
44 pages — The print PDF
Cover, contents, the migration arc, five chapters at seven pages each, a closing page, a colophon and three operational field-note pages. A styled offline reader brings the editable case and runbook materials together.
- 02
11 figures — Drawn for print
The arc band, the cost-score ranking, the token tiers, the four waves and seven more — every caption labelled illustrative.
- 03
10 worksheets — Ruled fields, printed A4
Two at the end of every chapter, and they chain: 1B feeds 2A, 3B feeds 3A, 2B is line one of 5B.
- 04
12 sheets — The worksheets again, editable
Dropdowns and a cost-score formula, a worked example of 1A, and a final Migration plan sheet.
- 05
90 minutes — The workshop agenda
Timeboxes, who is in the room, which sheet at which step. Done means every plan row has an owner and a date.
- 06
Worked case — Follow an imperfect migration
Harbor Console: a fictional product with 120 UI source files, an 84-file first scope and an unresolved billing exception. The companion workbook connects inventory, target contracts, capacity and adoption.
- 07
Source records — Adapt the reasoning
A worksheet map, release runbook, decision records, measurement definitions, token-bridge example and validated source JSON. Follow each blank worksheet into the filled case.
- 08
1 licence — Team-shareable
One purchase covers internal use across your company. Publishing it publicly, reselling and bundling are not covered.
All 44 pages, rasterised from the file itself.
Seven of them at reading size below — one of each kind of page. The rest are one click away.
Cover, contents, the migration arc, a chapter opener, a figure page, worksheet 1A and the closing page — A4 proportions, nothing cropped.
Every other page in the file
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
One page at full size, annotated

Every chapter opens the same way: the number set large, the title, the tagline, a three-panel stat band, the intro paragraphs, one pull quote, and the four section headings you are about to read listed at the foot of the page. The stat panels here are labelled illustrative audit in the file itself — that label is printed, not added for this page.
- A4 portrait, 44 pages. The proportions are the real ones; nothing is cropped.
- Numbered footers. Every page carries designsystems.one, the book title and its page number — which is how the contents page can point at them.
- One colour per chapter. Crimson, amber, teal, indigo, green — the same five
--chart-*tokens the figures on this page use.

The cover
The rose field-guide cover: a large title, sculptural arches, Nanum Pen caption and an edition line naming the chapters, worksheets and operational field notes.

Worksheet 1A — Component inventory
Six columns, eighteen blank rows, one instruction line. Ruled and unshaded so it photocopies cleanly. This is the audit from chapter 01 turned into something you fill in with a pen.
Read chapter 01 in full before you pay for the rest.
Twelve pages, cut from the same PDF a buyer downloads — not a teaser rebuilt for the web. It ends with a page listing what the other four chapters cover.
Download the sample- The cover, the contents page and the how-to-use page
- The migration arc figure — chapter proportions at a glance
- Chapter 01 complete: opener, prose, figures, takeaways
- Both of chapter 01's worksheets, print-ready
- A closing page describing chapters 02–05
Who this is for, and who it isn't.
You have a product in production
…and a design system only part of it uses. The migration is the work, not the building.
You need to defend the order
Sequencing the work is the argument. The worked case exposes capacity, dependencies and release gates so your team can challenge the sequence.
You want it on paper, in a room
The audit and the wave planning run as a workshop, not as a doc nobody opens twice.
Three teams, three comparable answers
Hand the same worksheets to three teams and get back three things you can put side by side.
- You are starting a new product. The 90-day build track is the other one, and it is free.
- You want benchmarks to cite. Every figure here is a labelled worked example.
- You only want the words. They are free at /playbook/migrate and stay free.
- You want an automatic migration tool. The kit provides planning materials and a case validator; your team implements and verifies the changes.
Both tracks, free: /playbook/migrate · /playbook
Finished, being packaged for checkout.
The print guide, planning workbook, agenda and worked-case companion — the buy button appears here when checkout is live. The five chapters are free at /playbook/migrate — fine either way.
or write to kir.zhukovsky@gmail.com — subject prefilled
The web version stays free. All five chapters are readable in full at /playbook/migrate, before this PDF existed and after it. What $49 buys is the print edition, editable planning worksheets, workshop agenda and a complete worked case with its own workbook and source records.
- 14-day refund, no questions asked.
- Prices are in USD.
- Receipts and invoices come from the payment processor.
- One purchase covers internal use across your team (LICENSE.md ships in the download).
Need the business case before the sequencing? The ROI Kit ($29) makes it in an editable spreadsheet.
The long version.
The page-by-page ledger, the worksheets, one chapter worked end to end, and the questions people ask before buying.
Every page, and what is on it
What is on the pages, in the order they are bound.
Cover, contents, how to use it, the arc
The contents page lists every chapter, figure and worksheet with its page number. Page 3 is an introduction whose first line is that the web version is free. Page 4 is the whole migration arc as one proportional band.
Opener, prose, figures, takeaways, worksheets
Each chapter runs: an opener with the chapter's stat band and intro, two pages of prose across four sections, a full page of two figures, a takeaways page carrying the same 'use the system' references as the web chapter, and the chapter's two worksheets.
Drawn for print, labelled illustrative
The arc band, a surface-area before/after, a cost-score ranking, the three-tier token diagram, the bridge lifecycle, the prioritisation matrix, the four waves, the rollback flow, the codemod split, the coverage burn-down, and per-product adoption. Every caption says the numbers are a worked example.
Ruled fields, meant to be printed
Two at the end of every chapter: the component inventory and token-collapse tables, the alias map and retirement contract, the wave planner and a blank matrix to plot into, the sweep runbook and escape-hatch register, the enforcement ladder and the cutover checklist.
Five phases, sized by their share of an illustrative twenty-eight week migration. Counting is cheap, componentising is where the months go, and the enforcement tail runs longer than anyone budgets for. The phases overlap in practice — they are drawn end to end because the dependencies are strictly ordered, not because the calendar is.
--red-600: #82182eRaw value, named after what it is — never after where it is used.
--color-dangerNames the intent. The bridge aliases legacy names onto this tier, never onto tier 1.
--button-danger-bgScoped to one component. Only worth introducing when a component genuinely deviates.
The bridge in chapter 02 aliases legacy names onto tier 2, never onto tier 1 — aliasing onto primitives freezes every intent-level change the migration exists to enable.
The ten worksheets, and how they chain
Two at the end of every chapter. They chain — 1B feeds 2A, 3B feeds 3A, 2B is line one of 5B — so filling them in order produces a migration plan. They ship twice: printable pages in the PDF, and the same ten as sheets in the workbook. The 90-minute agenda runs them in a room; done means the workbook's Migration plan sheet is filled.
| Component | Resolves to (path) | Variants | Instances | Owner | API compat |
|---|---|---|---|---|---|
Four rows shown; the printed sheet has eighteen.
Eighteen blank rows on their own page, printed at A4 so it photocopies flat. Filling the ‘resolves to’ column is the whole point: the gap between what the import says and what actually renders is where the duplicate implementations hide.
- 1A/1B — component inventory; token collapse and cost score
- 2A/2B — the alias map; the retirement contract and bridge checklist
- 3A/3B — wave planner with exit criteria; a blank matrix to plot into
- 4A/4B — sweep runbook; escape-hatch register
- 5A/5B — enforcement ladder and adoption tracker; cutover ceremony checklist
Ruled fields, tables and checkboxes on their own pages so they photocopy cleanly — and one sheet each in the workbook, with dropdowns and formulas where the print version has checkboxes and a blank grid, a worked example of 1A filled with the book's illustrative audit, and the Migration plan sheet the workshop fills.
The five chapters
The sequence is the argument: audit before architecture, bridge before big-bang, primitives before composites, engineering path before enforcement, ceremony last. Each chapter is linked — verify before you buy.
- 01Audit the surface area
- 02Build a token bridge
- 03Componentize the right things first
- 04The engineering migration path
- 05Adopt and enforce
The PDF adds print typesetting, the figures and the worksheets. It does not add chapters.
Chapter 01, from opener to worksheet
“Audit the surface area” runs across pages 5 to 11 and has the same parts every chapter has: a stat band, four sections of argument, two figures, a takeaways page, and two worksheets. Here is the whole of it, so you know what the other four look like too. Read it in full, free, at /playbook/migrate/audit-the-surface-area.
6
Button implementations found where the team expected one
illustrative audit
~80
Distinct hex values, against an expected ~20
the usual gap
0
Lines of migration code written during the audit
counting is the work
These three panels are set at the top of the opener page, in these words. The first two are labelled illustrative in the file; the third is not a measurement of anything — it is the chapter's argument in one digit.
Before you migrate anything, count what's there — and what's pretending to be one component but is actually six.
- 01Inventory components, not pages
- 02Inventory tokens — primitives and semantics
- 03Map ownership
- 04Score the migration cost
The output is a flat spreadsheet, not a Figma file. Volume tells you sequence.
The pull quote is the one set on the opener page. The four headings are the same four the web chapter uses — the print edition adds paragraphs, not sections.
- Inventory components and tokens flatly — every variant, every instance, every hex value.
- Map current ownership of each component before proposing changes.
- Score migrations by complexity × instance count × API compatibility.
- Sequence cheap-and-high-impact first to build momentum before tackling the expensive cases.
The takeaways as the shared source carries them. The book sets them on their own page at the end of the chapter, with the same two “use the system” references the web chapter carries: the token generator and the maturity model.
Illustrative. Most teams expect around twenty colours and find around eighty. Migrating before you have counted means writing a plan about a codebase nobody has measured — which is the plan you throw out three months in.
Illustrative. Complexity × instance count × API compatibility. Teams that start with the component that has been embarrassing them in production start at the bottom of this chart and spend their momentum before they have any.
What $49 adds over the free track
All five chapters are readable in full, for nothing, at /playbook/migrate. They were free before this PDF existed and they stay free after it — no teaser chapters, no gated sections, no expiry. The $49 adds editable planning materials and a worked case that connects the decisions:
Print, properly typeset
44 A4 pages with a running footer, real page numbers, and a contents page that points at them. Generated from the same source content as the site, so the shared text never drifts apart.
Worksheets, not exercises
Ten printable pages of ruled tables, fields and checklists. The homework the web chapters describe, turned into something you can fill in with a pen and hand to whoever runs the audit.
A workshop, not homework
The same ten worksheets as a 12-sheet editable workbook — dropdowns, a cost-score formula, a worked example of 1A, a final Migration plan sheet — and the 90-minute agenda that runs them: timeboxes, who is in the room, which sheet at which step. Done means every plan row has an owner and a date.
A worked case you can interrogate
Trace all ten worksheets into the Harbor Console companion. Its final scoped adoption is 82 of 84 files, while reporting remains outside scope. The decision records explain why that still does not allow global retirement.
Team-shareable licence
One purchase covers internal use across your company. Print it, photocopy the worksheets, put the file in the shared drive. Not licensed: publishing it publicly, reselling it, or bundling it into another paid product.
Asked before buying
- What exactly is inside?
- One 44-page A4 PDF: cover, contents, an introduction, the migration arc, the five migrate-track chapters — the same chapters that are free on this site — eleven figures drawn for print, ten printable worksheets, a closing page, a colophon and three operational field-note pages. A styled offline reader brings the editable case and runbook materials together. Beside it: the 12-sheet workbook (the ten worksheets as editable sheets, a worked example of 1A filled with the book's illustrative audit, a final Migration plan sheet) and the 90-minute workshop agenda that runs them in a room, plus the licence and a checksummed manifest. The additional Harbor Console case includes a filled companion workbook, target contracts, capacity constraints, measurement records, a token bridge, release runbook and source-data validator. It shows how the planning tools connect to real decisions; its data is explicitly fictional.
- Is the web version still free?
- Yes, and it stays free. All five chapters remain readable in full at /playbook/migrate. Buying the PDF changes nothing about the site — it has never paywalled the track and will not start.
- Are the numbers in the figures real measurements?
- No, and every caption in the book says so. The figures are illustrative worked examples drawn from the shapes migrations tend to make — roughly eighty hex values where twenty were expected, the plateau around seventy per cent adoption. They are there so you recognise your own shape. The worksheets are where your real numbers go.
- What are the licence terms?
- Team-shareable: one purchase licenses internal use across your team or company — share the files, print them, distribute the worksheets internally. Not licensed: publishing the PDF publicly, reselling it, or bundling it into another paid product.
- Why buy it if the text is free?
- Buy it when the work needs a room: worksheets photocopied for a planning session, the 90-minute agenda to run it, the workbook on the shared screen, one licence covering everyone you hand a copy to. If reading on screen is all your migration needs, the free track already does that job.