Back to Portfolio Preparation

What Should Not Be Here

Subtraction before addition.

Decision Table

01Does this project show something no other project shows?

If Yes

Keep

If No

Cut or merge with another project

02Can you articulate why you made each major design decision?

If Yes

Keep

If No

You will struggle in the interview. Cut it or rewrite the narrative

03Does the process documentation add signal or noise?

If Yes

Keep the process

If No

Show the result only

04Does this project address a different problem type than your others?

If Yes

Keep. Variety of problem domains matters

If No

Cut the weaker one. Panels notice repetitive portfolios

05Can you defend this project in 90 seconds verbally?

If Yes

Keep

If No

You will lose panel attention. Cut or simplify it

Hard Truths
1
Polishing never upgrades a weak signal
2
Clarity of intent beats novelty of concept
3
One deeply articulated project outweighs three surface-level ones
4
3-5 projects is the sweet spot. 2 is too few, 6+ is always too many
5
If you cannot summarize a project in 90 seconds, it does not belong
For Non-Design Backgrounds

You don't fail from lack of process. You fail from over-explaining irrelevant process.

Show process: ambiguous problems where decisions weren't obvious
Hide process: execution-heavy projects where the result speaks for itself
Tip: Weak projects can still signal strength if they show learning or pivots