Month 1 through 6, everything is new. The wins come fast because the bar is low.
Month 7 through 12, the early chaos settles into patterns. The metrics look promising. People notice.
Month 14, the ground shifts.
———
In management, they call this second-year syndrome. A team has a breakout first season, and the second year, everything falls apart. The environment adapted. Opponents studied the playbook. The element of surprise is gone.
The same thing happens in projects and companies. Year one, you’re the underdog. Year two, you’re the incumbent. Your own success sets the expectations. And scrappy execution, founder energy, and sheer novelty were never supposed to scale into year two.
———
The systems you built for month 6 are breaking at the month 14 volume. The team that ran on excitement is grinding through repetition. Stakeholders want results they can put in a board deck.
You look at the metrics and can’t tell if you’re consolidating before the next jump or slowly dying. From where you’re sitting, both look identical.
Here’s the part nobody says out loud: quitting at month 14 feels rational. You have real data now, and it’s underwhelming. The original excitement wore off months ago. Every alternative looks better because you haven’t lived through its month 14 yet.
The people who kill good projects at this stage are making reasonable decisions with incomplete data. They’re reading the dashboard correctly. The dashboard is just lying to them.
———
I’ve watched good projects die here, and bad projects survive. The difference between persistence and denial only becomes visible in hindsight. You can’t tell which one you’re in while you’re in it.
What carries you through month 14 is the systems you built during the good months. They keep producing while you figure out whether the strategy still makes sense. Motivation died around month 10. Systems don’t need motivation. They just run.
Having been through it before helps too. The first time, you think something is broken. The second time, you recognize the feeling. Third time, you build for it from day one.
Most case studies skip from “we launched” to “we scaled.” Fourteen months of confusion compressed into “after some initial challenges.” I’d trust the ones that describe the trough more than the ones that pretend it didn’t happen.