Shipped Tuesday, marketed three weeks late

At one series-B company, a senior engineer mentioned in passing that he had shipped a feature on a Tuesday. At that company the feature had taken 4 months to build, and it was the biggest user-facing change of the quarter. I asked whether marketing had announced it. He didn't know. I asked marketing. They had not. They found out that Tuesday afternoon, in a Slack message, from the engineer himself.

At that company, marketing produced a blog post 9 days later and the in-app announcement 11 days after that. By the time the campaign was in market, the feature had been live nearly three weeks. Customers had found it in a trickle, awareness stayed low, and adoption ran at roughly 40 percent of what the same feature had done at a competitor that shipped something similar six months earlier. The launch didn't fail on the feature. It failed because the feature launched without a launch.

This is one of the most common cross-functional failures at growth-stage companies, and it's structural. Engineering runs on a cycle that ends at ship: code in production. Marketing runs on a cycle that ends at announce: an audience that knows the capability exists. The two calendars are paced by different things. Engineering's runs on feature complexity and dependencies; marketing's runs on content lead times and channel availability. Without deliberate coordination the two dates almost never line up, and the default is engineering shipping first while marketing scrambles to catch up. It's the same handoff gap that loses a customer between sales and onboarding.

Marketing catches up rather than leads because engineering ship is harder to hold. Once the code is tested, engineers want it live. Holding it two weeks so marketing can prepare feels, from the engineering desk, like a tax on their delivery. The marketing team, who would gain from the hold, rarely has the standing to demand it. So engineering ships when ready, marketing lands when it can, and the launch shows up on average three weeks behind the code.

What fixes this is a launch checklist where marketing tasks are ship blockers, not afterthoughts. Engineering ship is the last line on the list, not the first. Before the feature goes to production the checklist clears: marketing copy reviewed and approved, in-app messaging configured, sales enablement shipped to the team, customer comms drafted, support briefed on the capability, analytics tracking deployed and verified, blog post scheduled. Every line has an owner and a status. The feature doesn't ship until the list is green. Skip the analytics line and you get a launch with spend you can't attribute.

That discipline needs a launch manager, even a part-time one. At growth-stage companies the product manager for the feature usually plays it. The manager holds the authority to delay engineering ship when marketing tasks aren't done. That authority is politically uncomfortable, and it's the point: the company should ship when the feature is ready to land in the market, not when the code is ready to land in production. It is the same move as refusing to ship an integration nobody owns.

Engineering shipped on Tuesday. The launch dribbled out over weeks, against a feature the team had already moved past. It deserved better. Build the checklist. Name the manager. The next launch lands on one day, not five.