I want to build a portfolio but don't know how

You have heard "build a portfolio" a thousand times, and nobody tells you what that means. What goes in it, what format, how good is good enough, whether you even have anything worth showing.

Here is the truth: a portfolio is proof that you can solve real problems. It is not a collection of pretty mockups or school projects. The strongest portfolio in the world is a live product that people actually use. You cannot start there, so here is the path.

Everyone starts at zero. That is a starting point, not a problem.

Do spec work. Pick two or three apps you use daily, find one real usability problem in each, and redesign that flow.

Document your thinking, not just the output. The redesign is not the portfolio piece. Your reasoning is. What was the problem? What did you change? Why? What tradeoffs did you weigh?

Process beats polish at this stage. A reviewer does not want a beautiful screen. They want evidence you can think through a problem. Publish the write-up anywhere: your site, a blog, a public doc. The medium does not matter.

Spec work gets you started. Real work gets you hired. Take any work, even unpaid or barely paid, that lets you solve a real problem for a real person.

Small real work beats big fake work every time. Where to find it:

• Startups. They need help and cannot afford senior people. Perfect match.
• Nonprofits and student organisations. Real problems, grateful for any help.
• Freelance platforms. Start small, deliver excellently. Every satisfied client is a case study and a referral.
• Direct outreach. Find a small business online and offer to solve one specific problem.

The goal is getting your work into the world. One live thing, however small, is worth ten mockups.

Once you have some real work behind you, aim for work that ships. A live product is the portfolio piece nobody can argue with.

What to aim for:

• A startup role where you own a feature or a full product surface
• A freelance project that ends in a deployed site or app
• An open-source contribution that gets merged
• Your own product: a tool, an app, an extension that solves a problem you personally have

The move is from "I designed this" to "people use this."

Your work is only as good as your ability to explain it. Write about what you built, why you made each decision, and what you learned.

Good documentation answers four things:

• What was the problem? Real context, real constraints.
• What did you try? The process, including what did not work.
• What shipped? Screenshots, links, numbers if you have them.
• What did you learn? The honest takeaway.

This is the actual portfolio. Not the designs. The story of the designs.

A quick test. Which column does your portfolio sit in?

If you are on the left, you know what to do. Move right.

1. Place yourself on the stage 0 to 3 scale. Be honest.
2. Stage 0: pick one app, redesign one flow, document the reasoning, publish it this week.
3. Stage 1: reach out to three startups or small businesses this week and offer to solve one problem.
4. Stage 2: write a proper case study for your best project and publish it.
5. Whatever your stage: start documenting everything you build, today.

A portfolio is not a one-time project. It is a running record of your growth. Start now, update forever.