Showing Your Work Without Sharing All of It
One of the biggest changes I’ve made to my professional life over the past 18 months is becoming more intentional about sharing my work publicly.
I write about creating demand generation campaigns and their performance, maintaining content programs, and mid-career lessons. I’ve started publishing monthly recaps of what I worked on, building out a portfolio on my website, and using LinkedIn to document ideas while they’re still fresh.
But there’s an obvious challenge that comes with showing your work on a very public platform: you can’t actually show all of it.
There are campaign strategies that belong inside the company. Customer details that should stay private. Internal conversations that aren’t mine to share. Performance data that may be useful to me but inappropriate to publish. And sometimes the work itself simply isn’t interesting enough to deserve a LinkedIn post.
Learning how to navigate that line has become part of my personal branding process.
For me, showing my work has become less about documenting everything I do and more about identifying the parts of the experience that can be useful outside the walls where the work happened.
Usually, that means focusing on the lesson.
Start with your learnings for the week
When I worked as a Yelp community manager over a decade ago, one of the things we would do as a team was email everyone our weekly priorities and share any learnings from the prior week. Doing that was a great opportunity to reflect on what went right (or wrong) and gave us lessons to remember for the future.
I realized this was a great way to consistently come up with content for LinkedIn.
As I started writing down my content ideas, I also noticed that the tasks in my project management platform provided some good topics I could derive my learnings from:
Campaigns I was launching.
Content I was creating.
Results I was analyzing.
Conversations I was having with sales.
Problems I was trying to solve.
A campaign might teach me something about audience fit. An A/B test could show me which type of subject line earns attention. A slow month might force me to look more carefully at seasonality and campaign inputs. Working on the podcast could teach me something about repurposing. A trade show sequence might reveal how much stronger email becomes when sales calls are layered into the outreach.
Those lessons are much easier to turn into content because they can stand on their own.
Specifics make the story better, but choose wisely
I’ve learned that my post performance tends to be stronger when I include specifics.
Simply saying “Campaign performance improved” doesn’t tell you very much.
Saying that my vertical campaign open rates increased from 20% to 31% gives the reader something tangible. Sharing that I launched a nurture campaign to more than 350 contacts gives useful context when I’m explaining why I was disappointed when it didn’t produce the outcome I wanted.
Specifics make the lesson more credible because they show what actually happened. But being specific doesn’t mean sharing every detail available to me.
Before including a number, campaign example, or internal experience in something public, I try to think about whether that information belongs to me to share.
There are plenty of details that might make a story more interesting but don’t make it more useful.
I don’t need to identify individual prospects. I don’t need to publish every revenue number, targeting decision, or piece of strategy behind a campaign.
The goal is to give enough context for the lesson to mean something without recreating the entire internal workstream for the internet.
I can still be specific as long as I’m intentional about it.
Sharing the process can be even more valuable
Another thing I’ve noticed is that the result isn’t always the most interesting part of the story. Sometimes, the process teaches me more.
Take outbound campaigns. I could share an email I wrote, but there’s usually a much bigger lesson in explaining how the campaign changed over time: becoming more specific to each vertical, testing subject lines, varying calls to action, introducing useful content, adding SDR call layers, and then using the performance data to improve the next round.
The individual email is one piece of evidence, but the process shows how I think.
The same is true with content. A podcast episode might be the finished product, but I’m often more interested in what happens around it: how one conversation becomes social copy, FAQs, TL;DRs, newsletter content, video clips, sales conversation starters, and eventually another idea entirely.
Sharing those processes gives people a clearer picture of my approach, plus tips they could apply to their own work, without requiring me to reveal everything that went into the original project.
Distance can make the lesson clearer
I’ve also learned that I don’t always need to share something while it’s happening.
Some experiences benefit from a little distance. When a campaign disappoints me, my first reaction may be frustration. A few days later, I can look more objectively at the audience, seasonality, campaign volume, messaging, and follow-up.
The lesson gets better once I’ve had time to understand what actually happened.
The same applies to career experiences. A difficult job, organizational change, layoff, leadership experience, or decision to leave can eventually become something worth writing about. But I don’t think every experience needs to become public while the emotions are still fresh.
Waiting also helps me separate what’s useful from what’s simply personal. There are parts of my career that have shaped me deeply but will probably never become content. There are others that became useful to share only after enough time passed that I could talk about the lesson instead of reliving the experience.
Showing my work has made me better at tracking my career
One benefit I didn’t anticipate is that creating content has made me more disciplined about keeping track and noticing patterns in my own career.
If I’m going to write about a campaign result later, I need to know what changed. If I want to explain how a program improved, I need to keep the earlier benchmark. If I want to turn something into a portfolio example, I need to remember the problem I was solving, the decisions I made, and what happened afterward.
This habit has become useful far beyond being active on LinkedIn. It makes a lot of other things easier, like:
Filling out my performance reviews
Keeping my resume updated
Providing material for my portfolio.
Explaining my work internally to those outside my department
More importantly, it reminds me of the progress I’ve made that would otherwise be very easy to forget. Documenting along the way keeps those experiences visible.
Build a public record, not a public diary
This is the best way to describe my current approach.
I want my online presence to create a public record of how my work and thinking change over time. Someone who spends time on my LinkedIn profile or website should be able to understand the kinds of problems I work on, the areas where I have experience, the lessons I’ve picked up, and the way I approach my career.
They don’t need access to everything that happened behind the scenes to understand that story.
Artfully showing your work requires some judgment. You have to decide what belongs to the company, what belongs to the customer, what belongs only to you, and what could genuinely help someone else.
For me, the sweet spot is usually somewhere between the project and the lesson. I share enough of the project to explain where the idea came from, then spend most of my time on what the experience taught me. That approach has made sharing my work feel much more natural.
Documenting what I’m learning as I go is more than enough to show people how I work without sharing the secret sauce behind it all.