The answer is no, not yet. A better-paid role that appears right as your startup starts dropping coordination is usually a market signal that your company has quietly stopped working, and taking it is often a sideways move that solves the wrong problem. I know this because I watched a founder almost make that exact call, and the reasoning she used is worth unpacking before your Monday deadline.
The offer that looks like a promotion
The designer, let's call her Amara, had been at the Lagos startup for eighteen months. She owned the product's feel, the flows, the polish. The offer came from a larger fintech, a genuine step up in title and a salary that would have changed her rent situation. The recruiter's line was smooth: "You've outgrown the startup, come build at scale."
On the surface it read as a career move. Product operations at a company with actual process, a team that ran standups that stayed on time, a roadmap that survived contact with the CEO. Every pull factor a founder would envy.
The real signal was the last two months
The problem was what had happened in the two months before the offer arrived. The startup's demo day pushed the roadmap sideways. The engineering lead left, and no one replaced him. The CEO started approving features directly, bypassing the designer entirely, and three overlapping Figma files appeared for the same screen. Amara was spending her week in alignment meetings that produced new alignment meetings.
The offer felt like an escape hatch. But that is the trap. A company that has stopped coordinating itself will make the people who notice feel like the problem, and a recruiter's email feels like validation that you were right to feel restless.
The history of the escape hatch
This pattern is old. Consider the 1986 Challenger disaster, documented in Richard Feynman's appendix to the Rogers Commission report. The night before the launch, engineers at Morton Thiokol argued against launching in the cold, warning that the O-rings, the rubber seals between the shuttle's segments, had never been tested below a certain temperature. Management overrode them, in part because the schedule was tight and the pressure to fly was immense. The shuttle launched, and seventy-three seconds later it broke apart.
The mechanism that matters here is not the tragedy. It is that the engineers who had the clearest view of the system's fragility were the ones whose warnings were overridden. Their expertise was real, but the system that should have channeled it had stopped working. The failure was not a single bad decision. It was a coordination breakdown that made the bad decision look like the reasonable one.
Amara was in that position. She could see the system was failing, and the system responded by making her feel like the unreliable part.
What to check before Monday
The test is not whether the offer is better paid. It is whether the startup has a coordination problem that is fixable, or a structural one that is not.
Ask what the last two months actually broke. If the team lost a critical person and no one is replacing them, that is structural. If the CEO bypassed process once under deadline pressure, that is a fixable lapse, and your leverage to fix it has never been higher, because you now have an alternative.
Ask who else noticed. If you are the only one who sees the fragmentation, you might be the one who can name it. If three senior people have quietly updated their CVs, the ship is listing, and you are not the captain.
Ask what the offer actually buys you. Product operations at a larger company is a real job, but if you are leaving because you are running from disarray rather than toward a specific skill, you will import the same frustration into a new building. The better question is what you want to be true in eighteen months, and whether either path gets you there.
The decision that is actually on the table
Amara's real choice was not "stay or leave." It was whether to spend her remaining runway, and her leverage, forcing the coordination conversation with her CEO, or whether to take the cleaner offer and let the startup burn without her.
She took the weekend. She drafted the email to the CEO, not accepting or declining, but laying out the three overlapping Figma files and the missing engineering lead, and asking what the plan was. The CEO, confronted with the specifics, finally named the problem he had been avoiding, the engineering hire he had been putting off, and the ownership gaps on the roadmap.
The offer was still on the table Monday. But she had changed the terms of her own decision. She now knew what the startup was willing to fix, and what it was not. She could negotiate from evidence instead of from fear.
The engineers on the night before Challenger could not change the launch decision. But they did the only thing that was theirs to do. They put the warning on the record, clearly, in writing, before the deadline. Amara's version of that is not to storm out. It is to name the fragmentation to the one person who can fix it, and to know your own price for staying.
If you are holding an offer that arrived at the exact moment your team stopped coordinating, the offer is not the decision. The decision is whether you are willing to be the person who names the problem out loud before you walk.
Comments
No comments yet.