learn-personal-branding-with-phoebe / Session 3 of 6
Learn Personal Branding with Phoebe · Session 3 of 6

Voice and proof: show the work

Your session 1 audit ended with two counts, and the second one, how many of your ten results show a piece of your work, probably read zero. Your session 2 line made a promise about who you help and how. Tonight you back the promise with something a stranger can open. We climb a four-rung ladder from claim to proof, borrow Austin Kleon's ten titles on showing process, pin down voice as a handful of choices you repeat, and then everyone turns one finished piece of real work into a public teardown with their name on it.

🟡 Core Anyone building a professional reputation Managers and mentors who coach them 45 min
0-3 · Welcome 3-20 · Proof, process, voice 20-42 · Build-along: one piece made public 42-45 · Q&A
Part 0

Where we start

The running case is still Ines Calloway, a constructed mid-career data analyst who forecasts demand for a regional grocery chain. She is invented for teaching, and everything she makes tonight is constructed; your work and your results will differ. Her session 1 audit found two of ten results that were hers and none that showed her work. Her session 2 line promised grocery planners forecasts they can check. Tonight she makes the first thing a stranger can actually check.

🎫 Clear all three quiz questions to stamp your passport Live = presented in the 45 minutes Self-study = the full depth, after class ★ Build-along = do it on your own work

★ What you walk out with tonight. One finished piece of your work, checked for anything confidential, written up as a four-part teardown with an artefact a stranger can open, a title that carries your name, a place on a profile you keep, a one-card description of your voice, and a written cadence for the next twelve weeks that session 4 will put on a bench.

Part 1 · covers proof over claims

A claim is a promise; proof is a thing you can open

6 min live

Every bio is full of claims, and a stranger cannot check any of them. The difference between a reputation and a self-description is what the reader can verify without asking you. The proof ladder is a working framework for that difference: four rungs, each asking the reader to take one less thing on trust.

FOUR RUNGS: WHAT A STRANGER CAN CHECK AT EACH ONE harder to fake 4 Artefact someone else used Ines (later): another planner reuses her method a stranger can check a second person vouches for it 3 Artefact a stranger can open tonight Ines tonight: the Easter stockout teardown a stranger can check open it, rerun it, judge it 2 Description Ines: I built a forecasting model for our stores a stranger can check only that you say so 1 Claim Ines: I am good at forecasting a stranger can check nothing but your word Constructed examples. Each rung up is one fewer thing a stranger has to take on trust.
🔍 Click to zoom - rung 3 is the first one a stranger can judge without you in the room, and it is the one you build tonight
LiveThe four rungs3 min▶

Rung 1, the claim. "I am good at forecasting." An adjective about yourself. It costs nothing to write, so it carries no information; everyone in your field can type the same sentence. Most profiles live entirely on this rung.

Rung 2, the description. "I built a forecasting model." Better: it names a thing that happened. But the reader still has only your word for it, and cannot tell whether the model was good, whether you built it or sat near it, or what you learned.

Rung 3, the artefact a stranger can open. A public teardown, a notebook on public data, a talk recording, a worked example. The reader can open it and judge the reasoning for themselves. This is the first rung that works when you are not there to explain, which is the whole point of a reputation.

Rung 4, the artefact someone else used. Somebody linked it, cited it, reused the method, or asked you about it in public. You cannot build this rung directly; it is what rung 3 earns over time. That is why the build-along aims at rung 3 and lets rung 4 follow.

Self-studyConfidential work: show the method, never the data3 min▶

Most of your best work belongs to an employer or a client, and the professional norm is simple: never publish their data, their numbers, their client names or anything a reader could trace back to them. That includes screenshots with the axis labels cropped, "anonymised" figures that are still recognisable, and the name of the client in a caption. If you would not show it to a competitor, do not show it to the internet.

What is yours is the method: the reasoning, the mistake you caught, the approach that fixed it. Rebuild that on public data or on a small toy example you make up, and say plainly that you did: "rebuilt on public data; the original was internal work". The rebuild is honest, it is shareable, and it often teaches better than the original because you strip it to the part that matters. When in doubt, ask whoever owns the work before you publish, in writing.

Real world

Two portfolios for the same job. One lists tools: a row of logos for languages, libraries and dashboards, and a line saying "experienced in forecasting". The other has one link: a finished teardown of a forecast that went wrong, what the analyst tried first, why it failed, and the chart that fixed it. The first asks a hiring manager to believe; the second lets them check in five minutes. The tool list sits on rung 1 however long it is. One teardown sits on rung 3.

Part 2 · covers showing process

Show the process, not just the product

6 min live

Austin Kleon's short book Show Your Work! (Workman, 2014) is the clearest map of how sharing process works in practice, and its ten chapter titles read as a checklist on their own. We list the titles only, as they appear on his site, and work out what each asks of you; the prose of the book is his to read, not ours to quote.

THE LOOP THE TEN TITLES DESCRIBE, AND WHERE IT LEAKS Do the work the actual job Share a small piece of the process People respond read, reply, correct Better work and more to share What keeps it turning Think process, not product Teach what you know Tell good stories Learn to take a punch Stick around the leak Human spam broadcast only, never read or help nothing comes back Kleon's titles drawn as a mechanism. Sharing feeds the loop only when you also read, reply and help.
🔍 Click to zoom - the ochre step is the habit; the dashed leak is what happens to it when nobody is listening back
LiveThe ten titles, and what each asks of you4 min▶

The chapter titles, as listed on austinkleon.com. The second half of each line is our reading of what the title asks of a working professional, not Kleon's text.

  1. You don't have to be a genius. You do not need to be the leading expert to share; being a careful practitioner who is still learning is enough to start.
  2. Think process, not product. The steps, drafts and dead ends are shareable long before the finished thing is.
  3. Share something small every day. A habit of small, regular pieces instead of waiting for a big reveal.
  4. Open up your cabinet of curiosities. Share what you read and learn from, with credit, not only what you make.
  5. Tell good stories. Frame work as problem, attempt, result, so a stranger can follow it.
  6. Teach what you know. Explaining a method gives it away and makes you the person who explained it.
  7. Don't turn into human spam. Read, reply and help as much as you broadcast; the figure above draws the leak.
  8. Learn to take a punch. Public work draws criticism; separate the useful correction from the noise.
  9. Sell out. It is fine to say plainly what you offer, once the work has earned attention.
  10. Stick around. Reputations are built over years, not launches; session 6 comes back to this one.
Self-study"Share something small every day" is a habit, not a growth claim2 min▶

The third title is the one that gets lifted out of context. Read with its neighbours, it is advice about a working habit: get your process out of your head in small pieces, often, so showing your work stops being an event. It is not a measurement. The title does not say that posting every day grows an audience, and a chapter title could not show that even if it did.

Whether a higher cadence actually buys more engagement is an empirical question with an answer you can count, not a matter of who said it with more confidence. Session 4 tests it on real public data. Until then, treat "share something small every day" as a way to make sharing routine, and keep the separate question of what cadence earns open.

Real world

A common pattern in any professional feed: an account that posts every day and never replies to a comment, never credits a source, never asks a question. The volume is high and the loop is broken, because nothing the readers say ever reaches the work. A quieter account that answers every reply and links what it learned from is running the loop Kleon's titles describe. Ines (constructed) notices she has been the first kind on the rare days she posts at all: announcements, no conversation.

Part 3 · covers voice

Voice is a set of choices you repeat

5 min live

Ask people to describe their voice and you get adjectives: warm, direct, authentic. Adjectives cannot be checked, and they cannot be followed on a tired Tuesday. A voice a reader can recognise is a small set of decisions you make the same way every time. Name the decisions and the voice becomes something you can keep.

SAME FACTS, BEFORE AND AFTER FIVE VOICE CHOICES Before: adjectives After: five choices she repeats We are passionate about leveraging cutting-edge AI to unlock actionable insights. Our innovative forecasting solution transformed outcomes and drove significant value across the business. I rebuilt our Easter forecast after it missed the holiday by a week. The fix: line years up by holiday, not by date. I think it holds for other moving holidays; I have not tested that yet. The idea came from Dana in store ops. Notebook below. we: the reader cannot tell who did the work passionate, innovative: adjectives, not choices transformed: by how much? no number, no link no doubt anywhere, no credit to anyone 1I, not we: the reader knows who did the work 2one hedge, placed exactly where the doubt is 3plain words: line years up, not leverage 4no claim she cannot show: transformed is gone 5credit by name: the idea came from Dana Constructed paragraphs (Ines and Dana are invented). The facts did not change; the choices did.
🔍 Click to zoom - the after panel is not more talented writing, it is five decisions a reader can see being made the same way twice
LiveFive choices that make a voice3 min▶

1 · Who you write as. "I" for what you did, "we" only for what a team did, and never "we" to blur who did what. Readers looking for a person want to know which part was yours.

2 · How you hedge. Hedging everything sounds unsure; hedging nothing sounds like a sales page. Put one hedge exactly where your evidence runs out, and state the rest plainly. A hedge in the right place is a signal of honesty, not weakness.

3 · How much jargon. Decide who you write for and use their words. For grocery planners, "line years up by holiday" beats "temporal alignment". Keep a term of art only when the reader would search for it.

4 · The claims you never make. Write down two or three: no result without a number or a link, no "thought leader", no "world-class". A short list of refusals shapes a voice faster than a long list of aspirations.

5 · How you credit others. By name, specifically, every time the idea was not wholly yours. It costs one clause and it is the single most trusted signal on a page about your own work.

Length and format are choices too; pick a length you can sustain and keep it. Writing craft itself, sentence by sentence, lives in the communication course, and drafting, repurposing and AI writing tools live in the AI content course. Here the point is narrower: decide the five, so that every piece sounds like the same person.

Self-studyWrite down your voice in one card3 min▶

Take your three best pieces of writing, anything public or private you were proud of. For each of the five choices, write what you actually did, not what you wish you did. Where the three disagree, pick one and make it the rule. The result fits on an index card and you check every new piece against it before you publish.

★ Voice card · Ines (constructed)I write as: I for my work, we only for the team's, named I hedge: once, where the evidence stops ("not tested yet") Jargon: planner words; a term of art only if they would search it I never claim: a result without a number or a link; "thought leader" I credit: by name, in the sentence, not a footnote Length: under 600 words, one chart

Your card will differ. If a line on yours reads like an adjective ("friendly", "bold"), rewrite it as a decision someone could check.

Real world

A team handbook that says "our tone is friendly and professional" produces writing that varies by whoever wrote it, because nobody can apply an adjective. A handbook that says "we write in the first person, we name the person who found the bug, we never say a fix is permanent" produces writing that sounds like one place, because each line is a test you can run on a draft.

Build-along

One piece of work, made public

★ 22 min · everyone builds

Six steps that take one finished piece of your real work from private to findable, with Ines's constructed teardown alongside as the worked example. Work in a plain document. You will not publish in the room; you leave with a draft that is ready to publish and a place to put it.

FROM A PRIVATE PIECE OF WORK TO A RESULT A STRANGER FINDS 1 · Pick finished work done, not in progress 2 · Strip the private no employer data 3 · Rebuild on public public data or a toy 4 · Write it up four parts, plain words employer data and client names never leave 5 · Publish it your name in the title 6 · Link it from your profile 7 · It lands an O or R in the audit first page, session 6 The ochre stage is the point of the other six: one slot on your first page that shows your work.
🔍 Click to zoom - stage 2 is the one people skip and the one that can cost a job; stage 7 is the one the session 1 count was waiting for

Choose the piece. Finished, not in progress; small enough to explain in one page; and something where you made a decision a stranger could judge. A mistake you caught and fixed is usually better material than a success, because the reasoning is visible. Pick the one closest to the promise in your session 2 line.

★ Step 1 · choose the piececandidate: ______________________________ finished? yes / no one page? yes / no a decision a stranger could judge: ______________________ matches my session 2 line because: ______________________ Ines (constructed): the Easter forecast that missed the holiday by a week, and the fix that lined years up by holiday.

Run the confidentiality check. Go line by line through what you plan to show. Anything that belongs to an employer or client comes out: data, figures, names, internal tool names, screenshots. What is left is your method. If you are unsure about any line, it comes out, or you ask the owner in writing first.

★ Step 2 · confidentiality check[ ] no employer or client data, real or "anonymised" [ ] no figures a reader could trace to the business [ ] no client, customer or colleague names without consent [ ] no internal screenshots, dashboards or tool names [ ] what remains is the method, and it is mine to share [ ] the page will say: "rebuilt on public data; the original was internal work"

Draft the four-part teardown. Problem, first attempt and why it failed, what worked, what you would do next. The failed attempt is the part readers learn most from and the part most people leave out. Keep each part to a short paragraph, in the voice card from Part 3.

★ Step 3 · the four-part template1 Problem: what had to be decided, for whom, and why it mattered 2 First attempt: what I tried, and the specific reason it failed 3 What worked: the change, and how I checked that it worked 4 Next time: what I would do differently, and what I have not tested Ines (constructed): 1 Store planners kept running short the week of Easter. 2 I compared each week with the same week last year; Easter moves, so the comparison was off by a week most years. 3 Line years up by holiday instead of by date, then check the forecast against the actual holiday weeks on public data. 4 Try it on other moving holidays; not tested yet.

Make the artefact. One thing a stranger can open: a chart with its data source named, a notebook that runs on public data, or a worked example small enough to do by hand. This is what lifts the teardown from rung 2 to rung 3. If you rebuilt on public data, link the source; if you used a toy example, say it is a toy.

★ Step 4 · the artefacttype: chart / notebook / worked example data: public source (link) or toy example (say so) a stranger can: open it & check one claim in the teardown with it Ines (constructed): a notebook on a public retail sales dataset, two charts, before and after lining up by holiday. Her numbers are constructed; yours will differ.

Title it and place it. Put your name in the page title, because the page titles that tend to surface for a name search are the ones that carry it. Publish on a page you keep, ideally ground you own, and link it from the profile you actually maintain. That link is what lets a search engine connect the work to you.

★ Step 5 · title and placementtitle: <what you fixed> - a teardown by <your name> lives on: ____________________ (own site, or a platform page you keep) linked from: ___________________ (the profile you update) lands as: O (own ground) or R (rented ground) in the session 1 audit Ines (constructed): "Lining up Easter: a forecasting teardown by Ines Calloway", linked from her updated profile.

Plan a cadence for the next twelve weeks. Write down how often you intend to publish something, of what kind, and how many teardowns that adds up to. Make it a number, not a mood. Ines (constructed) plans five posts a week: one teardown a fortnight and short process notes in between. That is her plan, written down so it can be tested, not a recommendation. Session 4 puts that plan on a bench.

★ Step 6 · a twelve-week cadenceposts a week: ___ of which teardowns: ___ every ___ weeks the rest are: process notes / reading notes / replies twelve-week total: ___ posts, ___ teardowns Ines (constructed): 5 posts a week, one teardown a fortnight. 12 weeks = 60 posts, 6 teardowns. Bring this number to session 4.

Save the draft as teardown-1_YYYY-MM-DD, with the voice card and the cadence on the last page. When it is live, add its address to your session 1 audit sheet as the result you expect to see there in session 6.

Homework

Before session 4

60 min
  1. Publish the teardown. Run the step 2 checklist once more on the final version, then put it live with your name in the title and link it from your profile.
  2. Climb your bio one rung. Find the strongest claim in your current profile and replace it with a link to the teardown, so the sentence moves from rung 1 to rung 3.
  3. Run the loop once. Share one small piece of process from the teardown, then reply to every response it gets and comment usefully on two other people's work. Note what came back.
  4. Bring the cadence you planned to session 4, as a number of posts a week, written down before you see any data.
Check yourself

Three questions

Clear all three and session 3 gets stamped in your passport.

1 · Ines (constructed) publishes a notebook on public retail data that anyone can open and rerun, showing how she lined up holiday weeks. Nobody has cited it yet. Which rung of the proof ladder is it on?

The test is what a stranger can check. They can open and rerun the notebook, so it is rung 3. Rung 4 needs someone else to have used, cited or linked it, which has not happened yet.

2 · Your best piece of work is an internal forecast for your employer. What can you publish?

The data, figures and names belong to the employer, and blurring or cropping does not change that. The method is yours to show; rebuilding it on public data and saying so keeps it honest and shareable. C throws away your best material for no reason.

3 · A colleague says "Kleon's book proves you have to post every day to grow an audience". What is the accurate reply?

A title can give advice; it cannot measure an effect. Whether cadence grows engagement is a separate, empirical question, and session 4 tests it on real public data. C invents advice the titles do not give.

Sources covered

What this session teaches, and where it came from

✓Austin Kleon, Show Your Work! (2014), chapter titlesThe ten chapter titles, read at source on austinkleon.com; titles listed only, no prose from the book quoted; the readings of each title are ours
✓The proof ladderA working framework, taught as such: claim, description, artefact a stranger can open, artefact someone else used
✓Voice as five repeated choicesA working framework, taught as such: who you write as, how you hedge, jargon, claims you never make, how you credit
✓Ines Calloway, her teardown, voice card and cadenceConstructed for teaching, consistent with her session 1 audit and session 2 line; Dana in store ops is constructed too

Every fact on this page, and its verification tier, is recorded in the course's source map.

Session 3 cheat sheet · pin this

The proof ladderClaim · description · artefact a stranger can open · artefact someone else used.
Aim at rung 3Rung 4 is earned, not built. Rung 3 is the first that works without you there.
Method, never dataEmployer data, figures and names stay private. Rebuild on public data and say so.
Kleon's loopDo the work, share a small piece, read the replies, do better work. Broadcast only and it leaks.
Voice is five choicesI or we · where you hedge · whose words · what you never claim · how you credit.
The teardownProblem · first attempt and why it failed · what worked · next time. Name in the title.