The German word that explains what product managers actually do

There's a German word that explains product management better than many others: Sinnstiften. Literally, it means "to donate meaning" or "to endow with sense." English doesn't have a clean equivalent. "Meaning-making" comes close. "Creating purpose" gets at part of it. But the German word carries something the translations lose: the idea that meaning is something you actively give to others, like a gift or a foundation you establish.

After twenty years in product, I've become convinced that this is the job. Not writing tickets. Not running discovery. Not managing roadmaps. Those are activities. The job underneath them is Sinnstiften.

Leading without authority is the whole game

Here's the uncomfortable truth every product manager learns in their first year: you can't tell anyone what to do. Engineers don't report to you. Designers don't report to you. Stakeholders certainly don't. You (hopefully) own outcomes without owning any of the people who produce them.

So what's left? You can make meaning. You can connect the work in front of someone to something larger that makes the work worth doing well. That's your entire toolkit, and it turns out to be enough.

You probably know the story of the three bricklayers. Asked what they're doing, the first says "laying bricks." The second says "building a wall." The third says "building a cathedral." It's the same task and material, but it generates a completely different relationship to the work.

A product manager's job is to get the team from the first answer to the third. And you do it with a story so coherent that people can locate their own contribution inside it.

What happens when meaning is made

Sinnstiften sounds fuzzy, but the mechanics are concrete. When it works, three things happen for the people on the receiving end.

First, coherence. The individual task gets a place in an intelligible story. "We're rebuilding onboarding because activation is where we lose most of our trial users, and activation is the bottleneck for everything downstream." Now the ticket becomes more than a ticket. It's a move in a game everyone understands.

Second, significance. People feel that their work matters. This is why bringing raw customer feedback into the team is one of the highest-leverage things a PM can do. A support ticket read aloud does more than any OKR review. A two-minute clip from a user interview changes how an engineer builds the feature.

Third, orientation. And this is the one I care about most, because it's where meaning replaces management. A team that shares the "why" can make good decisions without you in the room. They can resolve the hundred small trade-offs that come up during implementation, because they know what the work is for. A shared why makes control over the how unnecessary.

Flip that around and you get the diagnosis for most micromanagement I've seen: it's what leaders do when they've failed to make meaning. If you have to review every decision, you never gave people the story that would let them decide.

Sensemaking is not Sinnstiften

There's a related concept from organizational theory that often gets mixed up with this: Karl Weick's sensemaking. The two point in opposite directions, and the difference maps beautifully onto product work.

Sensemaking is inward and retrospective. It's the process of figuring out what's going on: interpreting signals, building a picture of reality from fragments. In product terms, that's discovery. Interviews, data, market signals, support tickets. You're making sense of the world for yourself.

Sinnstiften is outward. You take what you've understood and turn it into a story that gives other people direction. That's your product narrative, your goals, the way you frame priorities to the team and to stakeholders. You're making meaning for others.

A PM needs both, and they're different skills. I've worked with PMs who were brilliant at sensemaking and produced insight after insight that went nowhere, because they couldn't turn understanding into a story with pull. And I've seen the opposite: charismatic narrators whose stories were built on nothing, because they'd skipped the sensemaking. Insight without narrative doesn't move a team. Narrative without insight moves a team in the wrong direction, which is worse.

Why you can't mandate meaning

Here's the constraint that makes this hard, and that most purpose initiatives ignore: meaning can only be offered, never imposed. You can present an interpretation of why the work matters. Whether it becomes experienced meaning is decided by each person individually, and quietly.

This is why corporate purpose statements fail so reliably. They assert meaning instead of making it experienceable. Nobody has ever read "we empower our customers to achieve more" on a slide and felt like the third bricklayer.

What actually creates meaning is consistency. Do your decisions match your story? If you tell the team that customer retention is everything and then push a dark-pattern feature because a big account asked for it, you devalue every story you'll tell afterwards. The narrative and the decisions have to be the same thing.

Here's what surprised me about this work: it's the most fulfilling part of the job. Because to make meaning for others, you first have to find it yourself. You can't tell the cathedral story convincingly if you don't believe in the cathedral. So the daily practice of Sinnstiften keeps forcing you back to your own conviction: do I actually believe this matters? When the answer is yes, the practical work stops feeling like a chore and starts feeling like something closer to advocacy. Repeating the same why in every refinement session becomes an act of belief, not repetition (and the team is just starting to hear it anyway). Putting the customer quote in the sprint review is a chance to share something you find genuinely moving. Saying no to a stakeholder in front of the team, for the stated reason, is where you get to show that the story has teeth.

The two directions of the job

One more thing that took me years to see clearly: PMs make meaning in both directions.

Downward and sideways into the team, yes. But also upward and outward, toward stakeholders and leadership. Explaining why the team is working on X instead of Y is the same act with a different audience and a different story. The board doesn't need the cathedral metaphor; they need to understand how this quarter's work connects to the bet the company is making. Same mechanism. Translation of concrete work into a frame where it makes sense.

When people ask me what makes product management hard, this is my answer now. Not the frameworks, not the tools, not even the ambiguity. It's that your only real instrument is meaning, that meaning can't be commanded into existence, and that you have to earn it again with every decision you make.

The Germans got it right by making it a verb. Meaning isn't something a product has. It's something a product manager does.