What a Portfolio Proves
Learn what employers look for when they open your portfolio, and what they skip.
What you will be able to do
By the end of this lesson, you can name the four things a portfolio must prove and pick your best two or three projects.
A portfolio answers one question
The question is: "Can this person do the work we need?"
A portfolio is not a scrapbook. It is not every project you ever touched. It is a short set of proof, picked for the job you want.
The four things it must prove
- You can solve a real problem. Show the problem first, not the tool.
- You can explain your thinking. Why did you choose this approach? What did you try that failed?
- You can finish. A finished small project beats a big half-done one.
- You can work with people. Who was the client? Who gave feedback? What did you change because of it?
Notice that "uses the newest tool" is not on the list. Tools change every year. Judgment lasts.
Quality over quantity
Two or three strong case studies are enough. More than five, and the best ones get lost.
To choose, ask of each project:
- Does it match the kind of work I want next?
- Can I explain every part of it?
- Do I have permission to show it? (See Module 1.)
- Is there a real result?
Example: two San Antonio portfolios
Andre wants an entry-level marketing role. He has seven projects. He picks three: a social media plan for a barbershop on the East Side, a flyer series for a church food drive, and an email newsletter for a youth robotics club. All three match marketing. He drops the video game mod he made for fun.
Lupe works at a nonprofit and wants to move into operations. She picks two: a volunteer schedule she rebuilt in Google Sheets, and an intake checklist that cut errors at her community center. Neither is flashy. Both show she can fix a system.
Pick your portfolio projects
0 of 4 doneGo deeper: Read Product Management: Building the Right Thing (and Getting People to Use It). It explains why outcomes matter more than features. The same idea applies to your portfolio.