With twelve hours left, fix the onboarding flow before finishing the award submission. Tomorrow’s new user will judge the product by whether it works; tonight’s judges can only judge the story you tell about it.
In 2011, Reed Hastings was facing a larger version of that conflict. Netflix had announced Qwikster, a separate business for its DVD service. The plan had a name, a strategy and an explanation from the CEO. It also asked customers to manage two websites and two accounts.
The announcement was complete. The customer experience was broken.
The decision hiding behind the deadline
A founder at 11:47 PM rarely sees two clean options.
The award application may be due at noon. Most of it is finished. Winning could bring attention, credibility or introductions. The onboarding problem may look smaller: one confirmation email fails, a form loses its state, or the first project opens without enough guidance.
The application has a visible deadline. The user problem does not. That difference makes the application feel urgent even when onboarding carries the larger consequence.
Netflix had already committed publicly to Qwikster. Reversing it meant admitting that the company had made the customer’s experience harder. Hastings did exactly that. In October 2011, Netflix abandoned the plan before completing the separation.
The New York Times reported the reversal after weeks of criticism from customers and investors. Netflix kept DVD rentals and streaming under the same name and website. The polished plan lost to the experience people would actually have to use.
That is the same decision facing the founder with twelve hours left. The award exists outside the product. The broken signup sits directly between a person and the value the product promised.
One user tomorrow carries more information
Awards can help. A credible third party can shorten a future conversation with an investor, buyer or potential hire. I would not dismiss that.
But an award application mostly tests how well the company explains itself. A new user tests whether the explanation survives contact with the product.
Suppose someone in Accra finds the product tomorrow through a founder’s recommendation. They create an account between meetings, reach the broken step and leave. The failure may never appear in a support inbox. There may be no angry message and no second attempt. The founder sees one incomplete signup and learns almost nothing about the opportunity that disappeared.
That quiet failure matters more than the unfinished paragraph asking why the company deserves recognition.
This is why I would choose the broken flow, even if the repair produces nothing worth posting. I would trace the first session from account creation to the first useful result. I would repair the earliest point where progress becomes impossible. Then I would test the path again with a fresh account, not the founder account that already has permissions, sample data and remembered settings.
The application can receive the remaining time. If it misses the deadline, the cost is visible. That does not make it larger.
Repair the path, then reduce the claim
The dangerous response is trying to complete both at full quality. Twelve hours becomes six for the product and six for the application. The founder ships an onboarding patch that has not been tested and submits a polished description of a product that still blocks users.
I prefer a narrower sequence.
First, define the minimum successful onboarding outcome. It could be creating a workspace, importing one record or generating the first useful result. Fix only what prevents that outcome. Avoid redesigning the entire journey overnight.
Second, test the repaired path from the user’s position. Use a new account. Read every instruction as if the next step were unknown. Check the failure state, not only the successful one. The lesson in Ama’s incomplete supplier record applies here: trust often breaks where the system accepts incomplete progress without making the gap clear.
Third, return to the award application and cut it to what the product can support tonight. Remove the claim that onboarding is simple if the evidence is still uncertain. A shorter, accurate application is stronger than a polished one built around a flow the team knows is unreliable.
What the calendar cannot rank for you
Deadlines create their own hierarchy. The task with a closing form, countdown or panel date rises to the top. Product failures rarely arrive with that machinery.
A useful test is to ask which decision still matters after the deadline passes.
Tomorrow afternoon, the award portal will be closed. The repaired onboarding flow will keep meeting every new user. It will affect activation, support requests, demos and the confidence of anyone evaluating the company before a partnership.
Netflix’s Qwikster reversal protected the path customers already understood. Hastings gave up a finished strategic story because using the service mattered more than preserving the announcement.
At 11:47 PM, open a fresh account. Follow the same path tomorrow’s user will follow. Fix the first place they cannot continue, verify it once more, and give whatever time remains to the judges.
Comments
No comments yet.