Everything you've done that nobody can see.
Can't make it live? Register anyway. The recording goes to everyone.
Ask a capable woman what she's accomplished in the last two years and watch her go blank.
The usual diagnosis is imposter syndrome — that she's bad at recognising her own value. I think that's wrong, and I think it's insulting.
Here's what's actually happening. She can't name her work because she can't see it. It's on a Drive she lost access to. In a Slack she was removed from. Credited to "the team," or to whoever presented it upward.
You can't fix a possession problem by believing in yourself harder.
Not one of these is a confidence problem. Every one is a system keeping what you made.
You built inside systems somebody else owns. Access ended at 5pm on a Friday. The work is still running — you just can't reach it.
It became "the team's." Or it became whoever narrated it upward. Nobody lied. Credit just flows in a predictable direction.
Prevention leaves no artifact. The outage that didn't happen. The client who didn't churn. The process that stopped breaking. The women doing the most stabilising work in an organisation are frequently the least visible in it — not despite the stabilising, because of it. You made it look easy and everyone believed you.
You unblocked the thing. You got two teams shipping. Real, high-skill, load-bearing work that produced no file.
Three techniques most professionals have never been shown. You'll run all of them on your own history, live, in the room.
Your inbox is a searchable database of your entire career and nobody ever told you. We run real search operators, live, on your own Gmail and Drive.
That one takes eleven seconds and usually returns things you'd completely forgotten.
Not a document — a database. Structured fields, dropdowns, and one column that changes everything: where does the proof of this actually live?
A document is something you read. A database is something you ask questions of. Same information, completely different amount of power.
You'll build a form that writes to your ledger and save it to your phone's home screen. One tap, twenty seconds, timestamped forever.
It's the first real automation most people ever build, and it takes eight minutes. The reason you couldn't answer the question at the top of this session is that nobody was writing it down. After this, something is.
Twelve to twenty pieces of your own uncredited work, written down.
A number showing how much of it you can actually prove. It's the number that reframes everything.
Rerun them any time your memory goes blank — before a review, an interview, a raise conversation.
Yours, on your phone, running from that night forward.
And can't point to a single piece of public evidence of it.
If you've ever frozen in an interview on a question you should have been able to answer in your sleep — so what have you been working on? — this is built for you.
No technical requirement. If you can use email and a browser, you can do this. Nothing to prepare.
Yes, this ends with an offer. At the 80-minute mark I'll spend about two minutes on a paid weekend I run called Built by Sunday, and then I'll stop.
Nothing in the first 80 minutes changes based on whether you buy anything, and if you leave before the offer you'll have gotten the entire thing I promised. I'd rather tell you now than spring it on you later.
Strip the client name, the tool, and the exact figure, then describe the shape of the work. "A mid-size health system" and "cut review time roughly in half" is publishable and still impressive. The description of what you did is yours — no employment agreement revokes that.
Yes, and that blank is the exact reason it exists. Accomplishments aren't filed in memory under "accomplishment" — they're filed as ordinary Tuesdays. We use three retrieval questions that ask about consequences other people experienced rather than asking you to rate yourself. That's why they work when "list your accomplishments" produces a blank page.
Your personal inbox holds more than you think. Search operators surface praise you received, deliverables you sent, and status updates you wrote at the time. You lost access to their systems — you didn't lose your own correspondence.
A portfolio is evidence, not art. A spreadsheet that saved a team forty hours is portfolio. A process you fixed is portfolio. It has to be findable and clearly described, not beautiful.
Because nothing was writing it down as it happened — and because a large share of skilled work is preventative. The outage that didn't occur. The client who didn't leave. Prevention leaves no artifact, which is why the most stabilising work in an organisation is often the least visible.
Yes. No card, no catch. At the 80-minute mark there's a short mention of a paid weekend called Built by Sunday, and then it ends. Nothing before that depends on whether you buy anything.
Ninety minutes. You'll leave with a written record of work you'd forgotten you did, and a system that stops you losing the next two years the way you lost the last two.
Save my seat — it's free