How to plan a product launch
Eight weeks before the Booking Tool goes live, Priya Nair, who owns the product, has a date and a list. Calder Group moves its 120 people into a new headquarters on Monday, February 1, and Sam Rivera, the CEO, wants everyone booking desks and meeting rooms in the tool from Monday, January 18. The list reads "desk map, screens, security, sign-in, training". Leo Tan leads the engineering with Nina Shah, Maria Santos leads the design, and Jo Park draws the floor map icons between two other clients.
A launch rarely slips in one big moment. The date is set before the work is sized, so one chain never fits. "Security" sits on the list as a topic, so nobody books the review. Nina is sent a date but never agrees to it. None of this looks late until the week it is, and by then the only choice left is a later launch.
The method below catches those signs in time, and it's how Arkscape, a project collaboration and task management tool, lays out a launch.
Work back from the launch date
Write down what must be true on launch morning. For the Booking Tool: all 120 staff can sign in with their work accounts, every desk and room on the map matches the finished floors, and the security review is signed off.
Then walk back from each one to the last day its inputs can finish. Start with the longest chain, which for software usually ends in someone else's review:
- Launch day, when everyone can book: Monday, January 18.
- Staff training done: Friday, January 15.
- Single sign-on live with Calder's IT team: Friday, January 8.
- Security review signed off before the holidays: Friday, December 18.
- Release candidate sent to Calder's security team, who need two weeks: Friday, December 4.
- Desk map, room data, and Maria's screens approved by Priya: Wednesday, November 25.
The last line is the usual surprise: the desk map is due this week. That chain runs through the fit-out, because the map comes from Daniel Reyes's drawings. Last week a comment from Aiko Mori, the engineer, moved a second-floor wall and turned one meeting room into two. Ben Ortiz, the builder's site lead, hasn't said which rooms will be finished on move-in day.
Keep the buffer at the end of each chain, where you can see it being used. And if a chain starts before today, the date or the scope is wrong. Eight weeks out is the cheapest moment to launch desk booking first and add meeting rooms in March, or to move the date.
In Arkscape, the launch lives in the Booking Tool group, an external group because Leo's team works outside Calder. Invite people from the Members tab with Invite others via email; the people you invite join free. On the group's Arkboard, add one column per stage in launch order (Map and design, Build, Security and sign-in, Training and launch) and give every card a due date.
Give every task one owner who has said yes
Each task gets one name. "Floor map icons: Maria and Jo" means each assumes the other is drawing them. If two people do the work, one is responsible and the other helps. Write titles that say what done means: "Floor 2 room list sent to Leo" is a task; "Rooms" is a topic.
Then ask for a yes. Sending Nina a date is not Nina agreeing to it. A no with a reason is the most useful thing a plan can get: "Calder's IT team needs a week to set up a test sign-in" moves your build chain while there's room to absorb it. Ask a freelancer which days she has free, not whether she can fit it in.
In Arkscape, choose each card's Responsible person with Assign to.... The request reaches their Ark Requests, where they choose Accept or Decline, and until they answer, the card shows "Invited, not yet accepted". Once Nina accepts, the same card sits on her own Ark. It's placed there, not copied, so a date changed on either board shows on both.
Set the checkpoints that catch a slip
You don't need to watch forty tasks. Pick the four or five dates where a slip moves the launch: desk map approved, release candidate sent, security sign-off, single sign-on tested, and ten staff booking from their own phones. For each, decide in advance what you'll do if it's missed: move the date, cut scope, or add help.
Between checkpoints, watch for the quiet signs that come before anything is late:
- A task nobody owns.
- A request nobody has answered after two days.
- A due date pushed back, even by a day.
- A task with no date that hasn't changed in two weeks.
Also look for a finished feature waiting on one code review. Fix each sign the same day you see it. Give the task an owner, have the conversation, or move the date and tell the people who build on it.
In Arkscape, open the group's Reports tab. Its overview counts Overdue, Due in 7 days, No one responsible, Not accepted yet, and Quiet for 14 days; select a count to see its cards. On the Target completion card, use Set a target date for launch day. The forecast uses the cards finished per week over the last 4 weeks and shows On track or At risk, so give it a week or two.
Progress by phase reads each column as a phase, from its earliest card start date to its latest due date, and shows Behind when a phase is more than 10 points short of where its dates put it today. A pushed-back due date shows in the board's Activity, in its ... menu, the day it happens.
A weekly launch routine in Arkscape
- Make a "Launch review" card due Monday and set Repeat to weekly; the next appears when you complete it.
- Monday: open the group's Reports tab and read Target completion and Progress by phase.
- Select Not accepted yet and No one responsible. Message each person today, or give the card an owner.
- Read Deadlines for the next 14 days and check the next checkpoint. If it will be missed, move the date, cut scope, or add help, and tell Leo or Jo the same day.
- Open Activity from the board's ... menu, choose 7 days, and look for pushed-back due dates.
- Friday: choose 7 days in the report and use Copy as text under Completed for the team's update.
Group reports follow the plan of the group's owner. Every Business plan includes them, so a group Calder creates has them; on Personal plans, Connect and above do.
Where this method stops
Arkscape has boards and reports, not a Gantt chart. If moving one date should move twenty others on its own, you need scheduling software with dependencies; here you move them yourself. Code and bug reports stay in your issue tracker, which Arkscape doesn't sync with. Arkscape has no timesheets, budgets, or invoicing.
No plan rescues a launch whose date was set before the work was sized. If the chain from today doesn't fit, the honest answer is a smaller launch or a later date, decided this week.
Common questions
How far in advance should you plan a product launch? Far enough that the longest chain fits with a week to spare. For an internal tool that's usually the security review and single sign-on, so count them back before you announce the date.
What should a product launch plan include? The launch date, what must be true on launch morning, every task behind it with one owner and a due date, and the four or five checkpoints where a slip would move the launch.
How do you keep an outside development team or freelancer on schedule? Put their tasks on the same plan as everyone else's, with dates they have agreed to, and review the next checkpoint with them each week.
When should you move a launch date? As soon as a checkpoint is missed and neither a cut in scope nor added help wins the time back. Moving it in week two costs an email; moving it in the last week costs the plans of everyone you've already told.
Read next: how group reports work, how to delegate tasks to team members, and how to manage multiple projects at once.