The Brag Document Was the Right Idea. The Google Doc Wasn't.

A brag document is the right answer to a real problem.

The problem: your work disappears unless you write it down. Your manager forgets. Your peers forget. You forget. Six months in, you cannot reconstruct half of what you shipped. Twelve months in, you cannot reconstruct most of it. Three years and a job change later, you cannot reconstruct any of it.

The answer: keep a record. Update it as you go. Reach for it when the performance review hits, when the promotion case opens, when the recruiter asks what you have been working on, when the layoff lands on a Tuesday and the resume needs to be ready by Friday.

Almost everyone in knowledge work agrees this is a good idea. Almost no one actually does it. And the people who do — the disciplined ones, the ones who really update the doc every two weeks — find that the doc itself stops working when they need it most.

That is not a discipline problem. That is a vessel problem.

The practice almost everyone agrees with

The modern brag-document practice traces to a 2019 essay by software engineer Julia Evans titled simply Get your work recognized: write a brag document. The advice is plain. Maintain a document — call it a brag doc, a hype doc, a wins log, a work log, a list of stuff I did. Update it as you go. List the projects, the technical challenges, the cross-team contributions, the small wins, the metrics, the testimonials. When performance review season comes, read it. When the promotion case opens, share it with the people who write peer feedback. When you go to interview, mine it.

Six years on, the practice is canonical. Engineering, product, design, data, increasingly marketing and operations — the brag doc is widely recommended, widely linked, widely templated, widely Notion-ed. The Hacker News thread on Evans’ essay is full of senior engineers saying the same thing in different words: yes, do this, I have been doing this for years, the people who don’t do this are the ones who get passed over for the people who do.

This is the strongest possible signal. Smart, disciplined people across an entire industry agree the practice works.

And then most of them stop doing it within three months.

The five jobs a brag document is actually doing

Before talking about why the practice falls apart, it is worth being precise about what the practice is for. A brag document is not one job. It is at least five.

The promotion case. When you ask for the next level, you cannot expect anyone to remember what you did. The promotion committee does not know your work. Your manager has six other reports. Your skip-level has thirty. The brag doc is the artifact that makes your case legible to people who were not in the room.

The performance review. Different timing, often different audience, similar mechanic. The annual or semi-annual ritual of summarising six to twelve months of work in one document, under deadline, under pressure. The brag doc is the source material so you do not start from a blank page at midnight on Sunday.

The layoff response. Layoffs do not give notice. They give Tuesday. The CV needs to be current, the LinkedIn updated, the project list ready, the references warmed — not from scratch, in a panic, with the work email already cut off. A current brag doc compresses days of remembering into hours of editing.

The interview prep. Every interview asks variations of tell me about a time you… Your interviewer wants concrete projects with concrete outcomes. The brag doc is your library of those projects — the place you go to remember which one to tell.

The freelance pitch and recruiter response. A recruiter asks what you have been working on. A potential client asks for case studies. An advisor asks what makes you different. A flat answer loses. A specific, evidenced answer wins. The brag doc is what makes the specific answer possible without inventing it on the spot.

Same person, same year of work, same underlying record. Five different audiences, five different framings, five different shapes. A flat document serves none of them especially well.

Why the Google Doc fails the practice

The brag-doc literature is honest about one failure mode: the discipline tax. Evans, the Fountain Institute, Filip Danić — all the major guides say the same thing. Set a reminder. Block calendar time. Update it every two weeks. Every month. Every quarter. The work is in the maintenance.

This is true. It is also incomplete. Even when the discipline holds, the Google Doc fails the practice in five other ways the literature talks about less.

Discipline tax. Manual entry of every accomplishment, every metric, every testimonial, every link, every date. The cost is real and it is paid every two weeks for years. Most people do not pay it. The doc starts strong, accumulates a few entries, then sits stale until the week of the review — at which point you scramble to reconstruct nine months from memory and Slack search. The vessel demanded discipline that humans, on average, do not have.

Vessel rot. The brag doc lives in a Google account, a Notion workspace, an Apple Notes library — pick one. When you leave a company, the work-account version is gone, sometimes the next morning. The personal-account version drifts out of sync with the work that was happening on the work account. When you switch tools two years later, the export is messy, the formatting breaks, the links die. The doc you maintained for three years is now a folder of orphaned PDFs.

Flat-list shape. A brag doc is, structurally, a list of paragraphs. The skill you want to highlight is mentioned in one paragraph. The project that proves it is described in another. The testimonial that confirms it is in a third. The metric that quantifies it is in a fourth. None of them are linked. To make the case for the skill, you read the doc end-to-end and reassemble the connections in your head. The structure of the evidence — this skill was demonstrated in this project, witnessed by this person, measured by this metric — exists only inside your memory, not inside the document.

Single-audience tuning. A brag doc written for the promotion committee is the wrong shape for the recruiter. The version that opens the freelance pitch is the wrong shape for the layoff CV. So you copy, fork, rewrite, and now you have three brag docs, two of which are stale within a month. The flat list cannot be composed into different views without manual rewriting each time.

Witness lock-in. Half the strongest evidence in your career is not what you wrote — it is what other people wrote about you. The Slack message from your tech lead saying the migration came in clean. The performance-review comment from your skip-level naming the strategic call you made. The WhatsApp from a client at midnight thanking you for the save. The iMessage from your old manager when the deal closed. The LinkedIn recommendation. The screenshot of the tweet that quoted your work. The note from a peer in a Greenhouse review you will never see again. None of these live in your brag doc. They live in a dozen different systems and channels — Slack, Lattice, Workday, LinkedIn, X, WhatsApp, iMessage, Gmail, voice memos, paper — none of which travel with you when you leave. You can screenshot them. You lose attribution, date, original context, and the chain of authorship that makes the quote credible. The brag doc captures the work you did. The witnesses who confirmed the work are scattered across a dozen channels, slowly decaying.

Tool death. Google Docs is fifteen years old. Notion is six. The tool that holds your career record today may not exist, may be acquired, may pivot away from you, may price you out, may quietly deprecate the export format, may be the wrong shape for your career a decade from now. A brag doc that lives inside a single tool inherits that tool’s lifespan. Your career outlasts every tool you have ever used to manage it.

These six failures are not failures of effort. They are failures of architecture. The practice is right. The vessel is wrong. And the wrongness compounds — the longer you keep at it, the more painful the eventual rebuild.

What the brag document was always trying to be

Every brag-doc guide ends up gesturing at the same shape, even though none of them name it. Make it a living document. Update it regularly. Capture the evidence. Link to artifacts. Tag by goal. Filter by audience. Take it with you.

What is being described, in fragments, is a structured record. A database of career evidence — skills, projects, certifications, testimonials, artifacts — where each entry is its own object, each entry connects to the others, and the whole thing is queryable in any direction. The promotion case is one query against the database. The performance review is another. The layoff CV is a third. The freelance pitch is a fourth. The interview prep is a fifth. Same underlying records, five different views, no rewriting.

We have written the long version of this argument elsewhere. A structured, growing, owned record of your career evidence is what we call a Living Career Portfolio. The architecture has been theoretically possible for years. What changed recently is the cost of maintaining it.

Three things had to come together. A mature occupational and skill taxonomy — ESCO, the European taxonomy that covers every occupation in the labour market — so that the same skill in two records means the same thing. An open standard for evidence records — the Experience API (xAPI), originally built for learning records and now general-purpose — so that the records can move between tools without losing their meaning. And AI capable of reading messy career evidence and proposing structured records — so that the discipline tax that killed every previous attempt is paid by the machine, not the human.

Five years ago, you could have built this in theory. Almost no one would have used it, because the data-entry tax was prohibitive. Today, the extractor reads your CV, your LinkedIn export, your pasted-in Slack appraisal, your photographed certificate, your existing brag doc. It proposes structured records. You review them, correct what is wrong, approve what stays. The doc you have been keeping for three years becomes the seed for the structured Library you should have had all along.

The brag doc reborn — five jobs, served properly

Walk back through the five jobs. Each one is what the brag doc was trying to do. Each one is what a structured career record actually does.

The promotion case is a query. Show me every project I shipped, grouped by the strategic theme I have been focused on, with the metric that quantifies impact and the testimonial from the person who saw it close-up. In a flat document, you write that query out longhand by skimming twelve months of paragraphs. In a structured Library, the records compose into the case automatically, and the artifact you submit cites the project, the date, the link, the witness.

The performance review is the same shape with a different filter. Same records, narrowed to the review period, framed against the goals you set at the start of it. The annual blank page becomes an editing pass on something already drafted from your own approved records.

The layoff CV is a composition problem solved in minutes. The portfolio holds the full record; the CV is one view, generated in the language and the format the next employer reads, with every claim backed by an artifact in the underlying record. No reconstruction. No memory tax. No nine-place hunt for the project link.

The interview prep is a query in the other direction. For this role, show me the projects from my record that demonstrate the three skills the job description emphasises. The structured record knows which projects map to which skills, so the prep stops being remembering and starts being choosing.

The freelance pitch and recruiter response are the same problem with different framing. The portfolio holds the evidence; the writer composes the response that cites it. The case studies, the metrics, the named clients — all already in the record, ready to be assembled into the shape this audience needs.

There is also a category of evidence the flat-doc model loses entirely, and the structured Library handles natively. The testimonial — the praise from the person who actually saw the work — is the strongest claim type in any career record. The Library captures every one as a structured record, regardless of where it came from: the Slack message from the tech lead, attributed to them, dated, in the original language with a translation if useful. The performance-review comment from the skip-level. The WhatsApp thank-you from the client. The screenshot of the tweet. The iMessage from the old manager. The LinkedIn recommendation. The voice memo a peer left after a presentation. Each one is linked to the experience or the skill it speaks to, so when the writer composes a draft that needs witness backing, the right testimonial surfaces against the right claim. And — because the record lives in your portfolio rather than in a company HR system or a chat app you might lose access to — the testimonial survives the day you leave that company, change phones, or close that account. The praise from the manager you respected three jobs ago is still in your record at year fifteen. That is what durable witness looks like, and it is something a Google Doc cannot do.

You can see this working today. The public portfolio of Kitsuno’s founder is a live rendering of a structured Library — every experience entry surfaces its linked testimonials inline, attributed to the people who wrote them, in their original language. Nothing on that page is hand-maintained for the public view. The same underlying records also feed the Scorer when it matches jobs, the Writer when it drafts a cover letter, and any future tool the same data gets pointed at. The Library is the source. The portfolio is one rendering of it.

There is one more thing the structured record does that no flat list can. Tell me what skill keeps appearing in the roles I want, that I have no evidence for. That is a query a flat list cannot answer. It is the query that turns a record-keeping habit into a career-development tool.

The principle: your career evidence belongs to you

The reason a brag doc dies in an old Google account is the same reason a CV dies on a hard drive and a LinkedIn profile dies the day the platform deprecates a feature you depended on. Your career evidence is being held by something that does not have your interests as its first commitment. The tool is convenient. The tool is not yours.

A Living Career Portfolio is the opposite shape. The records are structured data, in open formats, that you can export at any time and take wherever you go next. ESCO is open. xAPI is open. JSON is open. The portfolio outlives the tool that helped you build it, including this one.

This is the eighth of Kitsuno’s ten principles: open standards, not walled gardens. It sits underneath the first principle — your data is your soul. The brag doc you have been keeping in a Google account is your data, sort of, until the day it isn’t. The portfolio is your data, fully, on terms you can verify. Kitsuno holds it in trust. We do not sell it, trade it, or use it to train models. You can export every record as JSON at any time, on any tier, including the free Kit tier. You can delete the whole Library in one action. If you leave, you take everything with you.

A brag document you cannot take with you is not really yours. A portfolio that survives the tool that built it is.

Start one this week

You can start the practice in the next ten minutes. Open whatever you already use — a Google Doc, a Notion page, an Obsidian vault, an Apple Note. Title it your brag doc. Write down five things from the past month: a project you shipped, a problem you solved, a metric that moved, a piece of feedback you received, a meeting where you led. Set a calendar reminder for two weeks from now to do the same thing again. The practice is the foundation. The practice always was.

When the doc reaches the point where it stops keeping up — when the discipline runs thin, when the structure fails, when the audience changes, when the tool starts to feel like the wrong shape for the work — that is when the structured version is waiting. The Library reads what you have written, proposes structured records, and lifts the practice out of the vessel that was always going to fail it.

The brag document was the right idea. The shape your career evidence has been quietly waiting for finally exists. You can keep both.

Frequently asked questions

What is a brag document?

A brag document is a personal, continuously updated record of what you have actually done at work — projects shipped, problems solved, metrics moved, feedback received. The term was popularised by software engineer Julia Evans in 2019 and is now common across tech, design, product, and increasingly any knowledge-work field. It is the single source of truth for performance reviews, promotion cases, job interviews, and the moment someone asks “so what have you actually been working on?”

How is a Living Career Portfolio different from a brag document in Google Docs or Notion?

Both serve the same goal — making sure your work survives your memory and your manager’s. The difference is shape. A Google Doc is a flat list of claims. A Living Career Portfolio is structured records — skills, experiences, certifications, artifacts, testimonials — each linked to evidence, queryable in any direction, exportable as data, and not trapped in a personal Google account that gets locked when you leave a company. The brag document is the practice. The portfolio is the architecture the practice was always trying to be.

Do I have to migrate my existing brag document?

No. Keep using whatever you keep — a Google Doc, a Notion page, an Obsidian vault, an Apple Note. Treat it as scaffolding. The structured Library inside Kitsuno reads from CVs, project descriptions, certifications, and pasted-in text — including your existing brag doc — and proposes structured records you can review and approve. The practice continues. The vessel changes underneath you.

Does this replace performance reviews or 1-on-1 prep?

It feeds them. Performance reviews ask you to summarise six or twelve months of work in one document, on a deadline, under pressure. A structured Library lets you compose that document in minutes from the records you already approved during the year — and back every claim with a linked artifact your manager can open. The review is still yours to write. The hunt for the evidence is gone.

What if I am not in tech — do I still need this?

Yes, and arguably more. The brag-document practice was popularised in tech because tech has frequent reviews, fast role changes, and remote work that makes contributions invisible. But teachers prepping for a Lehrprobe, nurses applying to specialise, consultants writing case studies, freelancers pitching new clients, executives preparing for board reviews — every one of them is doing the same job: assembling structured evidence of impact, on demand, from a year of scattered work. Kitsuno uses ESCO, the European taxonomy of every occupation, precisely because no field is exempt from this problem.

What about testimonials and recommendations — can I keep those too?

Yes, and this is one of the largest gaps in the way most people keep a brag document. Testimonials are first-class records in the Library — paste a Slack or WhatsApp message, screenshot an iMessage or a tweet, photograph a paper recommendation letter, upload a LinkedIn export, type out a client note — and the extractor proposes a structured testimonial record with attribution, date, context, original language, and the experience or skill it speaks to. Each one links to the work it confirms, so when the writer drafts a CV or cover letter it can surface the right witness for the right claim. And because the record belongs to you and not to the company’s HR system or a chat app you might one day lose access to, the testimonial from the manager you respected three jobs ago is still in your portfolio at year fifteen — long after the platform that originally hosted it has forgotten you exist.

References

Evans, J. (2019). Get your work recognized: write a brag document. jvns.ca/blog/brag-documents/ — the canonical modern statement of the practice.

Wampfler, P., Zimmermann, T., & Turkawka, G. (2019). Personal Learning Environments als Ressource in Lehr-Lern-Settings. In T. Zimmermann, G. Thomann, & D. Da Rin (Eds.), Digitalisierung und Lernen. Gestaltungsperspektiven für das professionelle Handeln in der Erwachsenenbildung und Weiterbildung. Bern: hep-Verlag. ISBN 978-3-0355-1334-9. Publisher page → — the architectural source for the “individual is the durable entity” principle that runs underneath this argument.

---

Published 2 May 2026. No affiliate links. No sponsored placements.