Example
How to plan a data-migration cutover when clean totals hide broken workflows
Clean counts can hide a broken Monday. Colin must recommend a Friday cutover, a one-week delay, or a segmented migration only after every path names affected people, support wording, specialist coverage, rollback evidence, and unknowns.
Choose a cutover path whose workflows, support plan, rollback boundary, and owners are all explicit
What customers and support must be able to do Monday
Keep Monday's usable workflows, support coverage, and rollback boundary as the release promise
Keep the green total visible beside Monday's promise without letting it erase workflow failures
Friday, delayed, and segmented paths Colin can recommend
Compare Friday, one-week delay, and a segmented cutover
The three people-facing workflow failures and who they affect
Name the three failures that matching record totals do not reveal
Name which people and Monday workflows each failure would affect
Support implications, specialist coverage, rollback evidence, unknowns, and accountable owners for each path
Map support wording, rollback boundary, and remaining unknowns for Friday, delay, and segmented cutover before Colin recommends one
Keep the specialist's Friday cutoff beside support and rollback planning
Keep the missing control visible before choosing Friday
In You.one’s Superboard view, the Cutover evidence Board separates Monday’s promise, three paths, workflow failures, support and rollback work, and checks that authorized people have actually verified.
Open Friday, delay, or segmented cutover as the Room with the Cutover-choice brief and the green record count kept beside the three failures.
After an explicit request, Ava can compare only the visible evidence but cannot run a migration, approve cutover, certify rollback, or declare a workflow verified. Colin recommends within his authority; business owners, support, and the vendor specialist own their commitments.
Matching totals are not Monday-ready if three workflows still fail after the specialist is gone
The mission is specific: Choose a cutover path whose workflows, support plan, rollback boundary, and owners are all explicit.
The consequential choice is not something a board or an AI should quietly make: Whether to cut over Friday, delay one week, or migrate the clean segment and hold the edge cases.
You.one can keep the work, several kinds of evidence, and “Friday, delay, or segmented cutover” decision visible through its Superboard view. The organized facts support Colin; they do not replace Colin's judgment: Colin owns the cutover recommendation, coordination, and rollback brief within his approved authority. Business owners, support, and the vendor specialist own their validations and commitments.
Available today
Cutover evidence: the working map
The Cutover evidence Board gives this mission one durable operating picture. Colin can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.
The Lists separate what Colin can move now, what is evidence, what is already waiting on a named person or event, and what still needs a decision.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Monday promise | What customers and support must be able to do Monday |
| Cutover path | Friday, delayed, and segmented paths Colin can recommend |
| Workflow failures | The three people-facing workflow failures and who they affect |
| Support and rollback | Support implications, specialist coverage, rollback evidence, unknowns, and accountable owners for each path |
Available today
Open one decision: Friday, delay, or segmented cutover
Opening the Card gives the visible item durable depth. Stage can hold Cutover-choice brief: Place workflow tests, support implications, specialist coverage, rollback evidence and unknowns, and business timing together. Live choice: Whether to cut over Friday, delay one week, or migrate the clean segment and hold the edge cases. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Colin will decide whether to cut over Friday, delay one week, or migrate the clean segment and hold the edge cases.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Friday, delay, or segmented cutover” from the visible evidence. Ava can work from the context Colin deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Colin's call remains explicit: Colin owns the cutover recommendation, coordination, and rollback brief within his approved authority. Business owners, support, and the vendor specialist own their validations and commitments.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Cutover-choice brief: Place workflow tests, support implications, specialist coverage, rollback evidence and unknowns, and business timing together. Live choice: Whether to cut over Friday, delay one week, or migrate the clean segment and hold the edge cases |
| Chat | Keep Colin's request and Ava's attributed response with the work |
| Pulse | Open decision: Colin will decide whether to cut over Friday, delay one week, or migrate the clean segment and hold the edge cases |
Useful Ava requests, with the boundary intact
These requests stay with the facts Colin has made visible around “Friday, delay, or segmented cutover.” Colin supplies the evidence, checks Ava's work, and decides what belongs in the Room.
Current Ava can prepare help after an explicit request. She cannot make the choice, represent Colin, watch other work on her own, or contact anyone.
Colin owns the cutover recommendation, coordination, and rollback brief within his approved authority. Business owners, support, and the vendor specialist own their validations and commitments. Ava cannot run the migration, approve cutover, or declare workflows verified.
A cutover path where matching totals cannot stand in for passing workflows, a support script, and a named rollback.
- Request idea: from this Room only, draft a neutral comparison for Friday, delay, or segmented cutover. Cite only notes visible in this Room, name missing evidence, and do not decide or contact anyone.
- Request idea: use only the Cutover-choice brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Friday, delay, or segmented cutover,” show which visible fact could reverse the current choice
The limit of a migration checklist
A migration checklist can be enough while the situation stays simple: record counts, people-facing workflows, support wording, rollback, and specialist coverage all agree for Monday.
It starts to break when matching totals look green while three workflows still fail and the specialist disappears after Friday.
The Cutover evidence Board earns its place only when the familiar tool—a migration checklist—can no longer keep the reason, Cutover-choice brief, conversation, current state, decision, and history connected.
A practical way to start the Cutover evidence Board
Colin should rename every List or Card that feels artificial. This recipe succeeds when “Friday, delay, or segmented cutover” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
Swipe or scroll sideways to see every column.
| Step | Action |
|---|---|
| 1. Write Monday's promise | Put the usable-workflow rule and Record counts match on Monday promise |
| 2. Card the workflow failures | Put all three failures and affected people on Workflow failures |
| 3. Map support and rollback | Put the Friday specialist cutoff, unnamed rollback, and support implications for all three paths on Support and rollback |
| 4. Card the cutover paths | Friday, one-week delay, and segmented cutover belong on Cutover path |
| 5. Choose with the unknowns visible | Open Friday, delay, or segmented cutover after each path's support and rollback implications are named |
Where this example stops
- This is a fictional example, not a customer story.
- This fictional example is not data-integrity, privacy, security, continuity, rollback, vendor, or technical advice; qualified owners verify the real migration and protect the people affected.
- It does not show Ava completing external actions or contacting anyone for Colin.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.