Who Owns Landing? Right Now, Nobody

If landing is the constraint and landing is the expensive column, the next question is the one that actually decides outcomes. Who owns it? Look at almost any org chart and the honest answer is nobody. That is not an oversight. It is the whole problem, and it is structural.

The short version

Landing falls into the seam between four functions, each of which hands off before the customer's behavior actually changes. Product owns shipping and lets go at GA. Marketing owns the launch and moves to the next one. Sales owns the close and moves to the next quota. Success owns the renewal, which is three quarters away. The ninety days that decide whether a launch mattered belong to no one, because the org chart was drawn when building was the constraint and every function was optimized around the moment of release. A Head of Landing with no authority is the weakest fix. The strong fixes are structural: give landing to whoever owns the outcome and remove the handoff, or change the pricing so revenue only arrives when the customer uses the product, which makes landing everyone's job by making it the only way anyone gets paid. The first move is small and clarifying: name one person accountable for the durable-adoption number of your last launch, and forbid the handoff. If you cannot name them, you have found your answer.

The relay race with no anchor leg

Watch how a product actually moves through a company and you see a relay. Product builds it and hands off at general availability. Marketing takes the baton, runs the launch, and hands off to sales. Sales closes the deal and hands off to the account. Success picks it up somewhere around the first renewal conversation. Each runner is good at their leg. Each hands off cleanly. And there is no anchor leg, because the part of the race that matters most, the stretch where a customer either changes their behavior or does not, sits between marketing's finish and success's start, and neither one is running it.

Every handoff in that relay happens before landing. That is the structural fact. Product's definition of done is "shipped." Marketing's is "announced." Sales' is "signed." Success does not really engage until there is a renewal to protect, and by then the landing already happened or failed months ago. The customer's behavior change, the actual point, occurs in a window that every function has already handed off out of.

So landing does not fail because people are bad at their jobs. It fails because it is nobody's job. It is the thing that lives in the seams, and organizations are extremely bad at owning what lives in the seams.

Why the chart looks like this

The current org chart is a fossil of the era when building was the constraint. When getting the thing built and announced was most of the work, it made sense to staff heavily around the moment of release and treat everything after it as follow-through. Landing was real, but it was small relative to the build, so you could assume it. Nobody needed to own a rounding error.

Then the ledger inverted. Building fell to near-zero and landing became the mountain. But the org chart is sticky. Reporting lines, budgets, and function definitions all still assume the old constraint. We rebuilt our tooling for cheap building and left the org design pointed at a bottleneck that moved. The result is a company perfectly optimized to produce launches and structurally unable to own landings, which is exactly what twelve builders shipping zero landings looks like from the inside.

The fixes, weakest to strongest

There are three ways to put a name on landing. They are not equally good.

The weak fix: a Head of Landing. Create a title, make someone accountable for adoption. This mostly fails, and it fails predictably, because a Head of Landing with no authority over the product, the pricing, or the GTM motion is a person accountable for a number they have no levers to move. You have not created an owner. You have created a scapegoat with a dashboard. Titles without authority make the org feel like it addressed the problem while changing nothing about who can actually act.

The better fix: outcome ownership without handoff. Give landing to whoever owns the outcome, and remove the handoff. The same person or pod that shipped the thing stays on the hook until it lands. This is the Product Builder logic extended past launch: you own the surface, and owning a surface means owning whether a customer actually adopts it, not just whether it shipped. No baton pass, because the runner who built it also runs the anchor leg. This works because it deletes the seam instead of hiring someone to stand in it.

The strongest fix: make the business model do it. Change what you charge for so revenue only arrives when the customer actually uses the product. Under consumption pricing, no function can book its win until the customer's behavior changes, because nobody gets paid for a signup that never becomes usage. The pricing model does the accountability work the org chart could not, and it does it to everyone at once. This is why the company I profile in the next post lands so much better than its peers: it did not out-organize the landing problem, it re-priced its way out of it, so that landing is simply how the company makes money. When the check only clears on adoption, adoption becomes everyone's job without a reorg.

The uncomfortable part for product leaders

If you run product, the outcome-ownership fix lands on you, and it is uncomfortable, because it extends your accountability past the line where your job used to end. "We shipped it" stops being a complete sentence. The Product Builder who owns a surface owns it through the month-two silence, which means owning a period where the levers are messy, GTM is involved, and the metric is slow. That is a harder job than shipping, and it is the job now.

The instinct is to push landing onto GTM, and GTM's instinct is to push it back to product, and that push-pull is the seam reproducing itself in a meeting. The way out is not to win the argument about whose job it is. It is to notice that as long as it is an argument, it is nobody's, and to just put a name on it.

Try this week

Take your last launch and try to name the one person accountable for its durable-adoption number. Not the person who shipped it and moved to the next thing. Not the marketer who ran the announcement. Not the CSM who will inherit the renewal in three quarters. One person who is on the hook, today, for whether a real customer's behavior changed and stuck, and who is not allowed to hand it off.

If you can name them, check that they have the levers to actually move the number, or you have built the weak fix by accident. If you cannot name them at all, sit with that, because you have just found the reason your launches do not land, and it was never a marketing problem or a product problem. It was an empty box on the org chart, right where the most expensive work now happens.