What to Do When You Miss the Top Ten

Most launches do not reach the top ten. That is not a pessimistic claim, just arithmetic: there are only ten places and many entrants. If you had hoped for a podium and finished in the middle of the table, you will feel flat for a day or two. That is human. What you do next determines whether the experience was wasted or whether it makes the next attempt better.

This article offers a calm routine for the days after a result you did not want.

First, give it a day

Do not write a post, send an email or change your product on the evening a week closes. Let the disappointment pass. Decisions made in the first few hours tend to be either too harsh or too defensive. Take a walk, thank your helpers and sleep.

Take the screenshot and the numbers

On the next working day, gather the facts.

• A dated screenshot of your final position, with the method note visible.
• Your analytics for the week: visits, sources, sign-ups, comments.
• The board's top entries, for comparison.
• Any feedback you received, copied into one document.

Evidence beats memory. Weeks later, you will not remember what happened on day three.

Hold a retrospective

A retrospective is a meeting, even if the meeting is just you, that looks back at a period to discuss what went well, what could be improved and how to apply the lessons. In agile teams it is a regular habit, and it works for launches too.

Use three headings.

What went well

Write down everything, even small things. Perhaps the listing text was clear, the first comments were warm, the page loaded quickly or a teammate handled support smoothly. These are habits to keep.

What could be improved

List the problems without blame. Perhaps the launch was timed in a crowded week, the screenshots were weak, nobody answered comments for six hours or the sign-up flow lost people. Be specific.

What we will change

Convert each improvement into a concrete action with an owner and a date. "Better screenshots" is vague. "Redo the three main screenshots with real data by the end of the month" is an action.

Judge the launch by what it did for you

Rank is one outcome. Other outcomes may matter more:

• Visitors and sign-ups. How many people came, and how many did something?
• Feedback. Did you learn something about what people want?
• Contacts. Did you gain subscribers, followers or partners?
• Content. Did you create assets you can reuse?
• Links and mentions. Did anyone write about you?

Goodhart's observation applies: a measure that becomes a target stops being a good measure. Position on a board is a measure of relative attention in a week. A launch with a modest rank but strong sign-ups and useful feedback may have achieved more than a high rank with nothing behind it.

Look honestly at what the leaders did

Study the top entries without envy. Open each one and note:

• The headline and first sentence
• The images and how many there are
• The clarity of what the product does
• How quickly they replied to comments
• The timing of their launch
• Whether they had an existing audience

You are not copying them. You are noticing what readers saw. Often the difference is in the first ten seconds: a clear promise, a good image and a fast, friendly response.

Check for obstacles you could not see

Sometimes a poor result is caused by something fixable and invisible. Check:

• Technical problems. Did your page break on some phones? Did a form fail? Run tests on different devices.
• Accessibility problems. Could everyone use your page?
• Discoverability. Was your listing in the right category? Does it use words people search for?
• Confusing messaging. Ask three people who did not see your launch to describe the product after reading your page. If they struggle, there is your lesson.

Google's guidance on helpful content asks whether a page gives readers what they came for, with clear information about who is behind it. A page that fails that test will struggle anywhere.

Keep what you built

A launch week creates assets even if the rank disappoints. Keep and reuse:

• Your listing text, edited with what you learned
• Images and short videos
• Quotes from users
• A list of people who engaged
• A dated record that you launched

Add a short note to your own site if it fits: "We launched on this date and here is what we learned". Honest stories attract goodwill.

Resist the shortcuts

After a disappointing week, shortcuts can look appealing. Buying votes, creating extra accounts or trading votes in a group might promise a quick rank. Votes here cannot be bought, and votes that look artificial are flagged and not counted. The deeper problem is that a rank earned dishonestly tells you nothing about your product, so you learn nothing, and you risk your reputation.

If you want paid visibility, there is an honest route: a labelled placement. The pricing page lists current options. It is advertising, and it is presented as such. Keep it separate from your goal of earning votes.

Decide what happens next

You have three sensible options.

1. Improve and relaunch later. Wait until you have something substantially new. Prepare a better listing and a stronger plan.
2. Shift your focus. If the launch revealed that the audience is elsewhere, redirect your effort to where people respond.
3. Pause the launch effort. Spend time on the product, and return when it is ready.

Whichever you choose, write the decision and the reason in your notes.

Tell people what you learned

Sharing lessons builds credibility. A short, honest post, "What we learned from our first launch week", is useful to other founders and to your own customers. It shows maturity and gives people a reason to follow your next step. Keep it factual, avoid blaming the system and include your numbers where you can.

Take care of yourself

Launch weeks are tiring. If you feel low after a result that did not match your hopes, remember that one week does not define the business. Plenty of well-known products had unremarkable first launches. Rest, talk to someone who understands and then return to the work.

A one-page recovery plan

• Day one: rest and thank helpers.
• Day two: collect screenshots, numbers and feedback.
• Day three: run a retrospective with three headings.
• Day four: study the leaders and look for obstacles.
• Day five: choose next actions with dates.
• Week two: publish a short lessons post, if appropriate.
• Month two: decide whether to relaunch.

An example of a retrospective note

To show how brief a useful retrospective can be, here is a note a small team might write after finishing in the middle of a weekly board.

Went well: the listing text was clear, and three people said the product solved a real problem. Support replies were quick on day one. The page loaded fast on phones.

Could be better: we launched in a week with a very large entry, which took much of the attention. Our screenshots showed an empty account, so they did not convey the value. We did not reply to comments between evening and morning, and two went cold. Our sign-up form asked for too much.

Changes: redo the screenshots with realistic data by the fifteenth; set a rota so someone replies within two hours; cut the sign-up form to two fields; check the launch calendar before choosing the next week; ask four users for a short quote.

That took fifteen minutes to write, and it converts a disappointing result into a plan. Keep it where you will see it before the next attempt.

Talking to your audience about it

Do not hide the result. If people supported you, thank them honestly, say where you ended up and tell them what you will do next. Most people respond warmly to openness, and some will offer help. A modest result, handled graciously, can strengthen the relationships that later launches depend on.

Turning the result into a credible line

If you want to mention the result at all, find an honest way to say it. A middle-of-the-table finish is not a badge worth displaying, but the experience is still worth describing in plain terms: "We launched in March, collected our first hundred users and learned what our listing needed." That sentence has no ranking in it and yet it says something real. Customers who read it learn that you ship, listen and improve, which is more persuasive than any position. Save the board claims for results that deserve them, and describe each one precisely when you do.

Frequently asked questions

How soon can I appear on the board again? That depends on the platform's rules about repeat entries. Check the launches page and the rules for relaunching.

What if I think the result was unfair? Read the method, and if you suspect an error, contact support politely with evidence.

Is there any value in finishing low? Yes. It gives you data, a record and a baseline to improve on.