At VinSolutions, I was famous for one thing that had nothing to do with writing code. Every single time we shipped a release, I posted about it. On social media, to customers, inside the company, anywhere people would look. Here's what's new, what we added, and what we fixed. I'd even post the numbers: how many new features shipped, how many bugs we knocked out that release.

I wasn't doing it to brag. I was doing it because the work was real and almost nobody outside the engineering team knew it was happening.

Then something I didn't plan for happened.

Just by sharing the information, we built a reputation. Customers started describing us as innovative, as a company that listened, fixed their problems, and got things done. We earned some of that by doing the work.

But we earned just as much of it by telling people we did the work.

Here's the same problem from the other direction, happening in my own company right now.

We were in an executive meeting recently, talking about how big one of our internal project teams had gotten. At some point I stopped and asked the room a simple question. Does anyone know what this team has actually accomplished in the last six months? Name one thing.

We sat there. A virtual meeting full of executives, and not one of us could come up with a single accomplishment.

So I asked the obvious follow-up: Then why are we still investing in this team?

That's a hard question to land on, and it wasn't entirely fair to the team, because I'm sure they've been working hard the whole time. But that's exactly the point.

If the people who fund the work can't name a single thing it produced, the work might as well not exist.

The root of it isn't that the team did nothing. It's that they did the work and stopped there.

They built, and nobody ever made sure the value was visible to the people deciding whether to keep paying for it.

That team isn't unusual, and neither is my company. It's what most engineering teams get wrong.

They pour everything into building and almost nothing into getting value out of what they built.

The team ships a feature and rolls straight to the next ticket.

The customers never hear about it in a way that lands. The rest of the company never hears about it at all. The work is real, and it stays invisible, which means most of the value in it never gets collected.

To the people funding engineering, a team like that becomes a black hole. Money goes in every month, and from the outside it's hard to see what comes back out. Not because the team isn't producing, but because nobody is telling the story of what they produced.

Building the thing creates the value. Promoting the thing is how you actually collect it.

Release notes are the obvious version of this, but they are only one channel.

The same instinct shows up in your product marketing, in a social post when a feature ships, in the internal company update, even in how you train your own support and sales teams on what changed. Every one of those is a way to get the story out about the hard work the team is doing, and a way to wring the full value out of it. The customer-facing versions do double duty, because when customers hear what you shipped, it drives the reputation of the entire company. That was the whole VinSolutions lesson. The posts didn't just announce features. They told the market who we were.

There's a morale payoff too. Engineers almost never get to see their own progress, since the day-to-day is one ticket after another until the wins blur together. Writing down what the team accomplished, and saying it out loud, is one of the few moments anyone stops to recognize the work.

The point isn't to list what you did. It's to show why it mattered.

Here's what's changed since my VinSolutions days. Teams ship more now than they ever have. AI writes a huge share of the code, and the volume coming out of a strong team is honestly kind of absurd.

You'd think that makes the team's value obvious. It does the opposite.

When the output doubles, the gap between what you shipped and what anyone outside the team understands you shipped only gets wider. You push more commits, more pull requests, and more features than ever, and you still get the same blank stare from the person paying for it. Volume was never the story anyway.

Output is not the same as value. A team that ships fifty things and can tell you which three moved the business is worth more than a team that ships a hundred and can't tell you what any of them did. The promoting is how you prove you know the difference.

One caution, because this cuts both ways.

There's such a thing as too much change. If you are constantly shifting things around on people, you stop being innovative and start being the disruption. Most customers and users just want to do their job, and a product that moves under them every week is exhausting no matter how good each change is.

So this isn't a license to ship loud changes constantly and trumpet every one of them. The goal is to maximize the value of the work, and sometimes that means shipping less often and letting people actually settle into what you built. Do the work, tell the story, but don't mistake constant disruption for progress. Chaos is not the goal.

The best engineers I've ever worked with weren't the fastest typists. They could stand in front of the people who fund the work and explain, in plain language, what changed and why anyone should care. That skill has always mattered, but when the people paying for the work can't see it, it becomes the difference between a team that gets their budget increased and one that gets cut.

This is the whole idea behind Product Driven, and it's how we run Full Scale. The engineers our clients value most have never been the ones who crank out the most code.

They're the ones who can tell you what they shipped and why it mattered. When your team is spread across the world the way ours is, that matters even more, because a client who can't see the work is the first one to wonder what they are paying for. The fix is the same for any team: do the work, then make sure the value is visible.

So put on your marketing hat and tell people what you shipped!

Nobody is going to value the work you won't talk about.