What This Means

Add To It, Don't Replace It

Nothing in this thesis has been an argument to stop working on your resume.

That would be bad advice, and it would contradict Chapter 3. The system genuinely requires a resume, and it isn't going anywhere. What I'm arguing is different: the resume was never going to be enough by itself, and treating it as the whole job search is how good people stay invisible. The fix isn't subtraction. It's addition. Keep the resume. Add the thing that actually shows who you are.

What that addition looks like depends on what you do, and for some fields it's obvious once you say it out loud. A designer has a portfolio. A marketer has real campaigns, content, results people can see. A developer has code, real repositories, real commits, not a bullet point claiming proficiency. A builder, anyone who makes things, has what they built and what happened because of it. None of that is a resume. All of it is proof.

And this isn't just a hunch about what feels persuasive. Ask anyone who's actually made a hiring decision what changed their mind, and it's rarely a bullet point. It's the moment a candidate showed real evidence instead of a claim: a shipped project, a specific decision made under real pressure, an outcome that's just true, checkable, not asserted. A portfolio beats a paragraph describing someone's taste for the same reason a set of real commits beats a line that says "proficient in Python." Evidence outweighs a claim about the same thing, every time, and you don't need a research citation to see it, you need to look at what's actually in front of you. An Impact Page works on that same principle: not a formal assessment of any kind, just real, checkable evidence in a place a compressed resume line never had room for.

What If Your Job Doesn't Have a Portfolio

But here's the question I hear the most, and it's a fair one. What if your job doesn't come with an obvious portfolio? What does proof of work look like if you're in sales, or operations, or finance, or customer success, or HR?

I built the answer to this, and not for this thesis. Running a career concierge this year, one person at a time, I'd get on a call with someone and pick a single line from their resume, just one bullet point, and instead of moving on, I'd stay there. What was the real situation. What did you have to work with. What did you do, specifically. What went wrong along the way. What did you do about it. What happened at the end. Then I'd turn that one conversation into a single page: the real story behind the bullet point. I called it an Impact Page. Think of it like a case study, the kind a consultant or an agency writes about a project they shipped, just built for a person instead of a company. Nothing like it exists by default for most roles, portfolios work for designers and developers because their work is naturally visible; everyone else is stuck with bullet points.

One thing worth addressing directly: Chapter 2 said no version of a block of text fixes the resume, and here I am recommending a page. The difference is what it's doing. A resume compresses an entire career into fragments competing for the same few seconds. An Impact Page gives one single moment the whole page, with nothing else competing for it. One story told fully beats ten crushed into bullets.

Everyone has at least one moment like that, a real challenge with a real before and after, that never survives compression into a resume line. Turn it into a page, and you have something no portfolio site could give a salesperson or an ops manager: real, specific proof of how you think and work, not a claim about it.

Worth being clear about why this doesn't run into the same problem as AI-polished writing everywhere else. An Impact Page isn't safe because a person wrote it; it's safe because of what it's built from, a real, specific situation with a real outcome, not an adjective about yourself. AI can help you phrase it better. It can't hand you a challenge you never actually faced or an outcome that never actually happened.

So if you're a job seeker reading this, the takeaway isn't complicated. Keep the resume, it's still required. But stop treating it as the whole story. Add the portfolio if your field has one. If it doesn't, build your own Impact Page around the moment you're proudest of. Either way, give someone something to look at that a page alone was never going to show them.

Start Before You Need To

One more thing worth saying plainly, because it changes when this work should happen, not just what it looks like. Almost nobody builds any of this, a portfolio, a network, an Impact Page, while they're happily employed. It doesn't feel urgent until the day it suddenly is, a layoff, a bad manager, a company that stops working, and by then there's no time left to build anything real. You reach for whatever's fastest, and the resume is always what's fastest, because it's already sitting there. The cost of relearning any of this doesn't disappear by waiting. It just lands on a worse day, one where the bills are already due instead of one where they aren't.

The actual fix isn't a better crisis response. It's not waiting for the crisis. Buy the domain before you need it. Start the portfolio, the writing, the case studies, while you still have a job and no deadline pressing on you. Treat your own career the way you'd treat anything else worth building, continuously, not as an emergency the week you're laid off. I'm writing this thesis, building this site, while I'm not looking for anything. That's not a coincidence. That's the actual point.

And if you're on the hiring side, this means requiring more than a resume, a cover letter, a portfolio, real signal you can actually score. This is the same ask, aimed the other way. When a candidate hands you proof of work instead of just a claim, notice it. Weight it. That's not the candidate showing off. That's real evidence, and real evidence is worth more than a claim standing in for it, every time.

Need over paper. Whichever side of the table you're on, the paper is a stand-in for something real, never the thing itself. Define the need instead of the title. Show the person instead of the page.

This thesis is itself an example of everything above. Nobody assigned it to me, and it isn't attached to a resume line. It's the closest thing I have to proof of how I actually think about a problem I've spent years building against, in public, before anyone asked for it. If it made you see something differently, whether about your own search, your hiring, or where hiring itself is headed, I'd genuinely like to hear about it. Reach out, tell me where you disagree, tell me what you're building. No agenda, just a real conversation. Find me on LinkedIn.