Recognition can wait when a paying customer is blocked on work only the founder can finish. In release week, the right response is to protect the customer commitment, record the nomination deadline, and return to it after the product is safely delivered.
In April 1970, Apollo 13 was losing a different kind of race. An oxygen tank had exploded on the way to the Moon, forcing astronauts Jim Lovell, Jack Swigert and Fred Haise into the lunar module. The mission had become a survival operation.
Carbon dioxide was building inside the spacecraft. The command module had square lithium hydroxide canisters, while the lunar module used round openings. The crew had the filters they needed, but they did not fit the system keeping them alive.
NASA engineer Ed Smylie and a team on the ground had to build an adapter from materials already available aboard the spacecraft. NASA’s history of Apollo 13 documents the improvised device and the instructions sent to the crew. At the point the team began working, nobody had proof that their solution would work in flight.
That is the part of the story I return to. The materials existed. The capable people existed. What mattered was directing both toward the constraint that could end the mission.
The email changed the week without changing the constraint
The ECOWAS nomination email arrived during release week.
Recognition has weight, especially when you are building across African, European and US markets where credibility often travels ahead of a founder. A nomination can help a future customer decide to take a meeting. It can reassure a possible partner in Accra, Berlin or the US that the work deserves attention.
It also creates immediate administrative work. Someone has to read the requirements, collect evidence, check the language and decide how much of the company’s story belongs in the submission.
Meanwhile, a paying customer was waiting on the product. The remaining work sat with me.
That detail settled the order. The nomination could strengthen the credibility around the business later. The release determined whether the customer could use what they had already agreed to pay for now.
This was the same constraint shape NASA faced in 1970, with incomparably lower stakes. Several important tasks were available. One of them controlled whether the immediate commitment survived.
Recognition creates work before it creates value
A nomination feels like an outcome because somebody external has noticed you. Operationally, it begins as another request.
You may need to confirm eligibility, assemble supporting material, rewrite product language for judges, find evidence and coordinate approvals. None of that is unreasonable. It still consumes the same hours available for testing a release, resolving a broken workflow or answering the customer who found the edge case nobody saw in the demo.
The danger is subtle because recognition work feels strategic. Shipping can look smaller by comparison. One produces a polished account of progress; the other may involve spending an afternoon tracing why a customer action fails after the second step.
The second task can matter more.
I have seen the same tension behind other founder decisions. A shortlist sends attention toward a product before a small team is ready to receive it. That is why fixing the path new visitors will use often deserves priority over preparing for the attention itself.
A nomination can create visibility. It cannot repair a release for the customer already waiting.
Protect the work that only you can do
The useful distinction was not “important versus unimportant.” Both pieces of work mattered.
The better question was: which task becomes blocked if I do not handle it now?
If another person can gather nomination evidence, move that work. If the deadline allows a later submission, reserve a specific time for it. If the release depends on a technical or product decision only the founder can make, protect that decision first.
This is especially important in a solo or small team. Founder attention can become the scarcest production input without appearing on any project board. Every attractive request competes for it: an award, an investor introduction, an overseas contract, a partnership call or a customer issue.
Write down three facts before changing the week:
- What breaks if this waits?
- Who else can complete it to an acceptable standard?
- Which commitment already has money, trust or a working relationship attached to it?
The answers make priority visible. They also prevent the nomination from disappearing into a vague promise to handle it later. Give it an owner, an evidence list and a return point. Then go back to the release.
Credibility begins with the promise already made
The Apollo 13 adapter worked because Smylie’s team focused on the material, interface and time available inside the actual spacecraft. They did not solve the broader question of how filtration systems should have been designed. They solved the fit problem standing between three astronauts and a safe return.
Release week needs the same discipline.
The ECOWAS email mattered. I recorded what it required and preserved the chance to respond. Then I returned to the customer commitment that depended on me.
Recognition may help someone trust the work before they know me. Finishing the product gives that trust something solid to rest on.
When the next nomination, shortlist or invitation lands during a release, do not measure it by prestige. Find the task that only you can finish, put the external opportunity somewhere it will not be lost, and close the constraint first.
Comments
No comments yet.