ShipDojo

Opening your checklist…

A case · you decide

Zara's app launch on Friday

Zara, 15 — planning to share her homework-planner web app with her class on Friday

The idea in play: a launch checklist turns "is it ready?" into steps you can check off, in an order that finds problems before your users do.

It is Wednesday. The app works on Zara's laptop. She has not tried it on a phone, the sign-up page still says 'Lorem ipsum', and she has not decided where people send bug reports.

Ready is not a feeling. It is a short list of things that have actually been checked.

The cheapest problems to fix are the ones found before anyone else sees them.

What goes at the top of the checklist?

On Thursday she finds a layout bug on small phones and a typo on the help page. Time for one fix tonight. Which one?

Friday morning she notices her sign-up page asks classmates for an email and a password. The planner itself works without an account. What does she do?

Build a launch checklist →

What next? Pick a door

Chosen from what this app is about. What you open is remembered on this device only.