What Career Professionals Can Learn from Show Your Work
Career professionals often keep their day-to-day work invisible to anyone outside their immediate team, assuming that only the finished deliverable — the report, the launch, the closed deal — is worth showing anyone. That habit means colleagues, managers, and a wider professional network only ever see the outcome, never the reasoning or effort that produced it, which makes it harder for anyone to vouch for how the professional actually works.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 4 selected
The core lessons, applied to you
Share your process and work-in-progress regularly, not just the polished result
Letting colleagues see a work-in-progress — a draft, a rough analysis, an early proposal — gives them a chance to weigh in before a decision is locked in, and gives you visible credit for the thinking, not just the final output.
An analyst works alone for weeks on a report, presents it fully formed at a meeting, and only then learns a key assumption was flawed. A ten-minute check-in earlier would have caught it and saved the rework.
Before a deliverable is finished, share a rough draft or outline with one relevant colleague and specifically ask what's missing or wrong.
Be generous with what you're learning — teach and share it, not just the finished outcome
A shortcut, template, or lesson learned on one project is often just as useful to a colleague on a different one, but only if it gets passed along.
A professional develops an efficient way to handle a recurring task, keeps using it privately, and later watches a teammate spend hours solving the same problem from scratch.
When you develop something reusable — a checklist, a template, a workaround — share it in a team channel or documentation the next time it comes up, not just in your own files.
Share thoughtfully, adding real value rather than promoting yourself relentlessly
Visibility at work should come from useful contributions, not from broadcasting achievements without substance.
A professional's updates to their manager and team consist mostly of listing accomplishments with little detail on how the work was done, so colleagues start to see the updates as self-promotion rather than useful information.
When updating others on your work, include one specific challenge you navigated or thing you learned, not just the result you delivered.
Handle criticism and stay consistent over the long haul
Making your process visible means occasionally hearing that an approach was inefficient or a decision was questionable, and professionals who hold up well treat that as useful input for the next project rather than a mark against their competence. Consistency matters here too — one impressive project rarely changes how colleagues see someone's reliability, but a steady pattern of visible, thoughtful work over years does. That reputation, built slowly, tends to open more doors than any single standout deliverable.
Showing early, unfinished work can feel risky in a competitive workplace where credit matters. In practice, sharing process openly with the right people — teammates, a manager, a trusted peer — usually earns more credit for the thinking involved than withholding it does, since it makes your contribution visible throughout the project, not just at the end.
Name one thing, honestly
What's one piece of your current work that only you can see right now, and who would benefit from seeing it sooner?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
When updating others on your work, include one specific challenge you navigated or thing you learned, not just the result you delivered.