What if leadership updates in Confluence felt like LinkedIn posts?

[#1]

A few months ago, I wrote what I thought was an important leadership update for our team at Amoeboids.

One of those posts where you take a step back from iterative releases, reflect on progress, share a few lessons, and thank the team.

I hit publish on our Confluence page… and waited for the reactions to roll in. 

Nothing. A few polite likes. And that was it.

At first, I assumed maybe people were busy. But the reality was simpler - no one had even seen it.

The message wasn’t the problem. The medium was.

Confluence is fantastic for documentation and structured knowledge. All of our apps' documentation is in Confluence.

But when it comes to leadership communication - those small, human updates that keep a company connected - it often felt invisible.

Analytics told me who viewed the page, sure. But that’s after someone knows the page exists. Most people never even discovered it in the first place.

The post lived quietly inside our 'Company Updates' space - technically there, practically forgotten.

How we ended up here. 

During Covid, like many teams, we started relying on Confluence more heavily for team communication - persistent, longer updates that shouldn’t get lost in the chat noise.

We even created a dedicated space for it called Team Portal.

Slack became our place for transactional conversations - “Can you review this?” or “Quick call in 5?” - while Confluence was meant for the thoughtful stuff: reflections, announcements, milestones.

But soon, we found ourselves integrating Confluence with Slack just to make sure people saw new pages and posts.

Ironically, we were using Slack to tell people about Confluence content.

We even tried building landing pages for Confluence spaces - curated hubs of recent or important updates - hoping it would make content discovery in Confluence easier.

But it always felt like a patchwork solution rather than something that truly did the job.

Ideally, teams shouldn’t have to build complex navigation just to find what matters. The right content should be discoverable within Confluence, naturally.

And yet, here we were - duct-taping different features together, trying to turn Confluence into something it was never designed to be: a social communication hub.

That got me thinking.

If a founder’s update goes unseen, what about all the small wins and reflections from the rest of the team?

We want people to share more, but the blank Confluence page can feel intimidating.

It’s like telling someone to write a blog when all they wanted was to share a two-line thought.

And the irony? We’re all used to expressing ourselves on social platforms.

A short, casual post on LinkedIn or Twitter gets more engagement than an entire company update inside Confluence.

Those quick, authentic messages - written in the moment, without overthinking - build connection.

They make teams feel human. 

What if that experience could exist inside Confluence?

What if posting a quick update - a product milestone, a leadership reflection, a thank-you to the team - felt as simple as tweeting?

What if those posts appeared in a shared feed that everyone could see, react to, and comment on without opening several browser tabs just for Confluence?

Imagine your morning scroll - not of social media, but of what’s actually happening inside your company.

A space where the CEO’s reflection, a developer’s learning, and a designer’s small win all live together - creating the real pulse of the company.

That’s the kind of internal communication we wanted at Amoeboids.

Lightweight. Human. Effortless.

We’ve been experimenting with something along those lines.

Our goal is simple: make Confluence communication feel more human. Because great ideas and reflections shouldn’t die quietly inside wiki pages.

They should be visible, discussed, celebrated - by the people who make them happen.

I’ll share more about what we’ve been working on soon - but for now, I’m curious:

How do you make sure your leadership updates don’t go unnoticed in Confluence?

Or better yet - how do you keep the human side of communication alive in tools built for documentation?

[Peter_DevSamurai]

I really love this article and thank you for this insight of Confluence!