The best work your company does is probably invisible.

Every week, across every team, people are shipping things worth knowing about. A product team that found a clever workaround. An engineer who built a tool that saves three hours of manual work. A customer success manager who cracked a difficult renewal conversation and wrote up exactly how they did it.

None of this gets seen by more than five people.

Not because the work isn't good. Not because people don't want to share. But because there's no channel designed for it. Slack is too ephemeral. Email is too formal. A presentation to the whole company requires slides and thirty minutes of someone's time and enough confidence to ask for them.

So the work stays local. The insight stays in the team. The experiment that worked - or didn't, and could save someone else from repeating it - gets buried in a Slack thread that nobody searches.

The duplication nobody knows about.

One of the most common and most expensive consequences of invisible work is duplication.

Two teams, in different parts of the same organisation, solving the same problem independently. Not because they're siloed in some cultural sense - they're in the same Slack workspace, they're on the same all-hands - but because there's no way to know that the problem you're about to spend three months on was already solved last quarter by a team you've never had reason to interact with.

This happens constantly in companies above a certain size. And the cost isn't just the wasted time - it's the signal it sends about whether sharing is worth the effort. If you share something and nothing happens, if it disappears into a feed and earns a handful of emoji reactions before being replaced by something else, you share less next time.

What happens when visibility is designed in.

Companies that have invested in internal demo days and innovation showcases consistently report the same thing: the bottleneck to innovation isn't ideas, it's transmission.

When teams know they're going to demo what they built, two things happen. They build more carefully, because they know someone will see it. And they learn more from each other, because they see what everyone else is working on.

The demo day creates a ritual around contribution - a moment where showing your work is expected and celebrated, where feedback is structured and positive, where the act of building something and sharing it is treated as a valuable thing to do.

The best version of this is searchable: a library of past demos, organised by team, topic and date, so that a year from now someone asking "did we ever try this?" can find the answer in seconds rather than spending three days asking in Slack.

What gets celebrated gets repeated.

Recognition and contribution are more connected than most companies realise.

When someone shares their work and nothing happens - no reactions, no follow-up, no acknowledgement beyond a polite thanks - the signal is that sharing wasn't worth it. When someone shares their work and it's voted on, discussed, recognised and surfaced to the rest of the company, the signal is that contribution is valued here.

The companies with the strongest cultures of internal innovation aren't the ones that tell people to innovate. They're the ones that make contribution visible, make sharing easy and make recognition automatic when good work is shared.