by Braden Kelley and Art Inteligencia
What Soft Landing Moves Help Hard Technology Rollouts? (Short Answer)
Nine soft-landing moves for hard technology rollouts: (1) write the soft landing in human terms, (2) fund work redesign equal to the tech workstream, (3) name one success behavior per cohort, (4) practice on real work before cutover, (5) appoint a BAU receiving owner before go-live, (6) kill-date the old path, (7) run a dual-truth scorecard, (8) gate waves on behavior — not only the calendar, and (9) bridge hypercare into maintenance. Soft landings keep hard tech from becoming shelfware with a ribbon.
Hard technology needs a soft landing — humans succeeding in the new way of working, not only a green cutover.
What Is a Soft Landing for a Hard Technology Rollout?
ERP, platforms, AI tools, and big-bang cutovers are hard technology: high coupling, high stakes, loud go-lives. Soft landings are not softer project management. They are designed moves so the median person can succeed — named behavior, redesigned work, practice, BAU ownership, old-path kill, dual truth, progressive gates, and maintenance after hypercare.
I define the broader more-human fork in The AI Soft Landing. This piece is the rollout playbook: how to land hard stacks without leaving humans on the spreadsheet. When adoption design is skipped, good tools become shelfware — see 12 Adoption Mistakes That Turn Good Tools Into Shelfware.
| Move | Without it | Soft landing forces… |
|---|---|---|
| 1. Write the landing | Vendor roadmap as strategy | Human success named |
| 2. Fund redesign | Tool on broken work | Jobs/incentives change with stack |
| 3. Name behavior | Awareness as adoption | One doable proof per cohort |
| 4. Practice before cutover | Completions theater | Time-to-confidence |
| 5. BAU owner pre-go-live | Orphan after cake | Transfer with teeth |
| 6. Kill-date old path | Immortal dual-run | Retirement as value |
| 7. Dual-truth scorecard | Green RAG, red floor | Human success can veto |
| 8. Behavior-gated waves | Big-bang calendar | Scale on adoption proof |
| 9. Hypercare → maintenance | Relapse surprise at day 90 | Reinforcement owner |
Ship the stack only as fast as humans can land.
1. Why Write the Soft Landing in Human Terms Before Cutover?
Move: One page — what machines and systems absorb, what humans must do differently, what dignity and confidence look like after go-live.
Hard without it: Vendor milestones impersonate strategy; “go-live success” is the only story.
How: Soft vs hard landing side-by-side for this rollout; sponsor signs it.
Signal: Steering can answer “who succeeds how?” without opening the RAID log. For investment-gate cousins of this move, see 10 More Human Future Tests for Any AI Investment.
2. Why Fund Work Redesign Equal to the Tech Workstream?
Move: Budget and staff job redesign, handoffs, incentives, and policy changes with the build — not after.
Hard without it: Shiny system on unreformed process; denser leftovers.
How: Dual workstream plan; redesign owners named; equal visibility in steering.
Signal: Process and incentive changes have dates beside config dates. Many post-pilot stalls start here — see 9 Reasons Digital Transformations Stall After the Pilot.
3. Why Name One Success Behavior per Cohort?
Move: For each major role group, one observable success behavior — for example, complete in the new system without dual entry.
Hard without it: Training percent and logins called adoption.
How: Put behavior on the scorecard from day one, thirty, and ninety.
Signal: Flat behavior triggers design diagnosis — not “resistance” lectures. For the full post-go-live scoreboard, see 6 Metrics That Prove Change Worked — Beyond Go-Live Day.
4. Why Practice on Real Work Before Cutover?
Move: Practice and coaching on real transactions and jobs before the switch — not only e-learning and town halls.
Hard without it: Completions green; floor confidence red.
How: Protected practice time; manager as coach; rehearsal environments with real constraints.
Signal: Time-to-confidence improves by cohort before or immediately after cutover. Informed is not enabled — a core thread in 5 Steps of Human-Centered Change.
5. Why Appoint a BAU Receiving Owner Before Go-Live?
Move: Named operator who will run the new way after the PMO leaves — handoffs, support, reinforcement.
Hard without it: Project owns it forever; orphan after cake.
How: Signed transfer card; receiving owner in steering before cutover.
Signal: Someone to escalate drift to on day thirty-one. Ownership coverage lives in 8 Roles That Make or Break Enterprise Transformation.
6. Why Kill-Date the Old Path on Hard Rollouts?
Move: Time-boxed coexistence with an explicit stop for legacy process and shadow tools.
Hard without it: Immortal dual-run celebrated as kindness; shelfware beside the new system.
How: Kill date on the plan; retirement volume tracked; incentives stop rewarding the old way.
Signal: Legacy volume toward zero; workarounds retired or adopted on purpose.
7. What Is a Dual-Truth Scorecard for Technology Rollouts?
Move: Score cutover and system health and human success; green RAG cannot close a red experience.
Hard without it: Deck theater; floor pain invisible.
How: Pair availability and defects with behavior, time-to-confidence, recontact, and escape to the old path.
Signal: Steering stops when human truth is red — even if cutover is green. When the program performs for the mirror instead, see 11 Signs Your Transformation Is Managing the Deck, Not the Work.
8. Why Gate Waves on Behavior — Not Only the Calendar?
Move: Progressive rollout waves advance on adopted-behavior proof, capacity, and transfer readiness — not FOMO dates alone.
Hard without it: Big-bang calendar politics; enterprise hard landing.
How: Wave scorecard; pause authority; kill/continue criteria per wave.
Signal: Later waves start cleaner because earlier waves taught the landing.
9. How Do You Bridge Hypercare Into Maintenance?
Move: When hypercare ends, reinforcement rituals, drift review, and relapse response already have an owner.
Hard without it: Applause → silence → old path returns at day ninety.
How: Maintenance plan equal to cutover plan; relapse triggers escalation, not surprise.
Signal: Post-hypercare usage holds; reinforcement coverage is real.
What Is the Pre-Cutover Soft-Landing Checklist?
Nine checks before the next hard tech go-live:
- Soft landing written?
- Redesign funded?
- Behaviors named?
- Practice done?
- BAU owner signed?
- Old-path kill dated?
- Dual scorecard live?
- Wave gates behavioral?
- Maintenance bridged?
Mantra: Make the technology as hard as it needs to be. Make the landing soft on purpose.
FAQ: Soft Landing Moves for Hard Technology Rollouts
What is a soft landing for a technology rollout?
A soft landing for a technology rollout is a designed path where hard systems go live while humans succeed — named behaviors, redesigned work, practice, BAU ownership, old-path kill, dual truth scoring, behavior-gated waves, and maintenance after hypercare — not only a green cutover.
How do you soft-land an ERP go-live?
Soft-land an ERP go-live by writing the human landing, funding work redesign with the build, naming success behaviors by cohort, practicing on real work, appointing a BAU receiving owner, kill-dating legacy paths, scoring human success beside system RAG, gating waves on adoption, and bridging hypercare into reinforcement.
What should you do before a hard cutover?
Before a hard cutover, confirm the soft landing is written, redesign is funded, behaviors are named, practice is done, a BAU owner is signed, the old-path kill date is real, dual scoring is live, wave gates are behavioral, and maintenance is bridged — not only that the cutover runbook is green.
How do you prevent shelfware after a platform launch?
Prevent shelfware after a platform launch by redesigning work with the tool, practicing before cutover, killing the old path on a date, measuring behavior not logins, and keeping a BAU owner reinforcing the new way after hypercare ends.
What is dual-truth scoring in change management?
Dual-truth scoring pairs system health (availability, defects, cutover RAG) with human success (behavior adoption, time-to-confidence, escape to the old path) — and refuses to close a green system review when the floor experience is red.
Image credits: ChatGPT
Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and Cursor to clean up the article, add images and create infographics.
Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.