How to Document Your Progress Without Looking Like You're Bragging

Nobody wants to follow someone who just brags. But you need to share your wins — building in public requires it. There's a way to do both, and once you understand the difference, sharing wins actually becomes one of the most useful content you can create.

The difference isn't about the size of the win. It's about what you do with it.

"Look How Great I Am" vs. "Here's What Worked and Why"

These are the two modes of sharing wins, and the gap between them is significant.

"Look how great I am" sounds like: "Just hit $10K in a single month. Grateful and humbled." There's a number, an emotion, and nothing else. No context, no lesson, no utility for the reader. The only purpose served is personal validation.

"Here's what worked and why" sounds like: "Hit $10K this month for the first time. Three things drove it: I ran a limited discount to my email list for the first time, I published a post that hit the front page of a niche aggregator I'd been targeting for months, and I updated the sales page copy on my highest-priced product. Breaking down each one in the replies." There's the same number — but now the reader has something to actually use.

Same win. Completely different post. The second version builds your credibility and your audience simultaneously. The first version just puts a number in the feed.

The "Teach Through Your Experience" Framework

The framework I use for almost every win post: treat your experience as a case study, not a milestone.

A milestone is: "I did X." A case study is: "I did X, here's how, here's why I think it worked, here's what I'd do differently."

Case studies serve your audience. Milestones serve you. Build in public using case studies.

In practice, this means: every time something good happens in your business, before you post about it, ask yourself three questions.

1. What specifically caused this result?
2. What did I do or decide that someone else could replicate?
3. What would I do differently if I were trying to repeat this?

If you can answer those questions, you have a post worth writing. If you can't, wait until you can.

Specific Examples From My Own Business

When I first hit a $1K month from my MadeThis storefront, I posted about it. But not as a revenue flex — as a lesson breakdown: here's the product that drove most of it, here's the traffic source that converted, here's what I tried that didn't contribute anything, and here's the one thing I'd do first if I were starting from zero with that goal.

That post got shared more than almost anything I'd published to that point. Not because $1K is impressive — plenty of people were making far more. But because the breakdown was specific enough to be useful, and because it was honest about what hadn't worked.

The same principle applied when I had a bad month. I posted the drop in revenue, explained the three things I thought contributed to it, and outlined what I was changing. That transparency built more trust than the winning month post, because it demonstrated that I wasn't just sharing results when they looked good.

How to Share Setbacks Alongside Wins

This is the part that most people skip because it's uncomfortable: posting the bad months with the same specificity you bring to the good ones.

The win posts without the loss posts look like careful curation. The combination looks like honesty.

A useful framework for setback posts: "Here's what happened, here's what I think caused it, here's what I'm changing, and here's what I'd tell someone trying to avoid the same situation." Same structure as the win post — cause, context, lesson. The emotional tenor is different, but the utility is the same.

One thing to watch: don't over-dramatize setbacks. The "I almost gave up" genre of content is tired. A bad month is a bad month. State what happened, analyze why, describe your response. The audience respects matter-of-fact honesty far more than performed despair.

The Long-Term Benefit of Consistency Over Time

Here's the thing that's easy to miss when you're early: the cumulative effect of consistent transparent posting is qualitatively different from the sum of the individual posts.

Each post is useful on its own. But after 3 months of consistent posting, you've created something more valuable than a collection of posts — you've created a track record. Your audience can see the arc. They've watched you try things, iterate, fail, and improve. That's not something you can fake, and it's not something that happens overnight.

That track record is what makes your recommendations credible. When I mention that the platform I use has been the most reliable part of my business infrastructure, it lands differently for someone who's been reading my posts for six months than for someone who found me yesterday. The new reader takes it as a recommendation. The long-term reader takes it as evidence — they've watched me use it, they know I'm not just repeating ad copy.

That's the long game. Each post builds on the ones before it. Consistency is the mechanism.

The Practical Version

Before you share a win:

• State the number or milestone clearly and early
• Give at least two specific causes you can attribute it to
• Include one thing that didn't work or that you'd do differently
• End with something actionable — a takeaway the reader can use

Before you share a setback:

• State what happened plainly, without overdramatizing
• Identify what you think caused it (be specific, not vague)
• Describe one concrete change you're making in response
• Keep the tone matter-of-fact — resilience, not performance

For more on what the building-in-public experience actually looks like in practice — including the engagement patterns and what actually drives business outcomes — see my honest review of building in public on Twitter/X. That post gets specific about what types of posts actually work and which ones I've retired.

You can share wins without bragging. You just have to serve the reader, not yourself.