Draw the Lines Before the Reorg Draws Them for You

You run a product team, and the lines on your org chart are getting fuzzy. Who owns the story? Who decides when to pivot? Who has the nerve to kill a product that still makes money? Nobody wrote it down, so it defaults to chaos or it defaults up to your CEO. Let me catch you up on what changed and what to settle before someone else settles it for you.

The story keeps hitting the floor

The split between product managers and product marketing managers started as a clean division of labor. The PM owns what to build and why. The PMM owns who hears about it and how it lands. On paper, sane. In practice, the go-to-market handoff became a relay race where the baton keeps hitting the floor.

The cost is not the org chart reshuffle. It is the silence where a narrative should be. Jay Stansell watched a founder lose a deal because he stumbled through specs while the buyer stared blankly. Nobody had turned the product into a story someone could buy.

AI made this sharper. It can draft positioning, write launch copy, and summarize calls in minutes. So the question shifted from "PM or PMM?" to "does anyone need to own the story?" The answer: yes, a human still decides which boxes matter. The tool fills them in.

Stop guarding lanes, name an owner

Here is the move. Treat the PM-PMM boundary as a place where they work together, not a fence. But pick an explicit owner for the things that fall in the gap, because the gap is where money leaks.

Pricing is the clearest example. Pricing expert Dan Balcauski argues product marketing should own pricing because pricing is a function of positioning, with the PM as a key stakeholder, not the owner. His warning lands: when nobody owns a thing, "the CEO comes in and yells at everyone" and nothing changes.

So do this on Monday. Write down who owns positioning, who owns pricing, and who owns the launch narrative. Get sales and channel in the room early, and get one executive sponsor. The teams that get this right sit with the same data building the same story, instead of arguing over who writes the doc.

The pivot bill nobody adds up

Everyone loves a pivot story. Slack, Airbnb, Brex. What nobody puts in the case study is the invoice. The Startup Genome Project found startups with one or two pivots saw 3.6x better user growth and raised 2.5x more capital than those with zero or more than two. Past two pivots, performance drops hard.

The hidden costs are real. Every pivot resets your customer acquisition engine, so the positioning you spent months on is gone. Your best people do not quit at the announcement. They quit three months later, after the second pivot tells them their work does not matter. And the technical debt is invisible for months until old database schemas become constraints on the new thing.

Before you change direction, add up the full bill: the CAC reset, the morale drain, the trust erosion, the abandoned upside, and the tech debt. If the new direction still wins after honest math, pivot with conviction. If not, the cheaper move is to do the hard work you have been dodging.

The product that's afraid to die

Kodak invented the first digital camera and held the patents. They filed for bankruptcy in 2012 because they were too afraid to cannibalize their own film business. Apple looked at the iPod, its biggest hit, and shipped the iPhone anyway. Same decade, opposite instinct.

Your roadmap is the tell. It is full of new features and growth bets. It almost never lists sunsetting or deletion as a priority. John Utz got mad about this and built a fix: a reverse roadmap. His rule is plain. Spend as much time planning what you will get rid of as what you will add. Adobe, Atlassian, and Salesforce all keep retirement roadmaps.

This is a courage problem, not a spreadsheet problem. The honest test, borrowed from Balcauski: is the new thing talking to the same buyer? If yes, you are creating a choice, and if the new thing is better, the old thing has to go. Sentiment about the old product becomes a liability.

Motion is not progress

Growth teams show the same trap in miniature. Okay teams ship dozens of experiments a week, changing button colors and moving pixels. Brian Hale, now Chief Growth Officer at DoorDash, is blunt that this is wrong. What's missing is why the hell that thing mattered in the first place.

DoorDash had a strong zero-delivery-fee offer, yet new users still hesitated over fees. The win was not a new offer. It was making the existing one impossible to miss. Hale's frame: it is not growth hacking, it is product growth. Find where the user is stuck and why, then fix that.

Watch your metrics too. Orders and sessions climb because power users drive them, while new and price-conscious users go invisible. That is why excellent teams anchor on people-count metrics like MAU. It forces the question of whether you are still earning new relationships.

The deep cut

The thread tying all of this together is the same one David Fischer drew about sales: the people who win are the ones who refuse to gloss over a harsh truth. He looked at a rep's blowout quarter and asked whether they truly earned it or just pulled spend forward that would crater next quarter.

That is your real job in the next review. Not the new feature. The uncomfortable accounting. Whose name is on the story when the deal is at risk. What the pivot actually costs after morale and CAC. Which paying product you keep alive out of fear. Which growth wins are real and which are power users flattering your dashboard. Write the lines down now. A reorg will draw them for you later, and it will not ask what you think.

Three questions for your team

1. If a deal is on the line and the buyer needs the story, whose name is on it: the PM, the PMM, or nobody? Settle that this week.
2. For the next pivot or AI bet on our roadmap, have we added the full invoice (CAC reset, morale, trust, tech debt), or just the build cost?
3. What is one product or feature we are keeping alive out of fear, and what would a reverse roadmap say we should sunset?