Quality Over Quantity¶

The Number Problem¶

One of the first questions students ask when building a portfolio is: how many projects should I include?

It is a reasonable question. It has no single correct answer. And the attempt to answer it with a specific number — five projects, eight entries, at least three case studies — produces portfolios optimised for a number rather than for the argument they are meant to make.

The more useful question is:

How many pieces of work can I present honestly, specifically, and at a standard that would hold up in a professional conversation?

The answer to that question varies by person, by stage, and by discipline. For a first-year student, it might be one or two. For a final-year student with three years of substantive work, it might be four or five. For a postgraduate researcher, it might be three deeply documented outputs and several referenced publications.

What it almost never is, for a student, is ten or more — not because ten projects are not available, but because ten projects documented to a genuine professional standard is an enormous body of work. If the choice is between ten entries at surface level and four entries at real depth, the four entries win every time.

What Quality Means in a Portfolio Context¶

Quality in a portfolio is not the same as quality in an academic submission.

Academic quality is assessed by markers against criteria — correctness, completeness, engagement with literature, technical execution. A project can score highly on academic criteria and still be weak portfolio material, because portfolio quality is assessed by a different reader against a different question:

Does this work tell me something meaningful about how this person thinks?

Portfolio quality has three components.

Ⅰ — Depth of Explanation¶

The most consistent difference between a strong portfolio entry and a weak one is not the quality of the underlying work — it is the depth of the explanation surrounding it.

A strong entry explains: ◆ what the project was trying to achieve and why
◇ what decisions were made and why those decisions, over alternatives
◆ what went wrong and how it was handled
◇ what the outcome was and what it demonstrates
◆ what changed in the student's thinking as a result

A weak entry describes: ◆ what the project was
◇ what technologies were used
◆ what the final product looked like

The second list is not worthless. But it is a project description, not a case study. It answers the question what did you do? without touching how did you think?

Depth of explanation is the primary quality marker because it is the hardest to fake. Anyone can write a project description. A specific, honest account of decisions and learning requires that the decisions and learning actually happened — and were paid attention to.

Ⅱ — Specificity¶

Specificity is the quality marker that most directly signals professional seriousness to an experienced reader.

Compare these two extracts from portfolio entries on the same project:

"I worked on a web application for a client and learned a lot about full-stack development and working in a team."

"The most significant decision in this project was the choice to implement OAuth 2.0 rather than build a custom authentication system. We evaluated custom JWT handling but concluded that our team lacked the security expertise to audit it responsibly. The OAuth integration introduced constraints on the user experience — particularly a third-party consent screen we could not control — but these were accepted in exchange for substantially reduced security risk. The trade-off was deliberate and defensible."

Both describe real experiences. One is generic. One is specific.

Specificity cannot be manufactured from vague recollection. It requires that the decisions were paid attention to at the time — which is why record-keeping during the project, as Vestigia supports, produces dramatically better portfolio material than reconstruction after the fact.

Ⅲ — Honesty¶

Honesty is not the same as full disclosure. It does not mean sharing every mistake, every failure, every moment of uncertainty.

In a portfolio context, honesty means:

◆ not presenting work as better than it was
◇ not erasing difficulty in order to present a smooth narrative
◆ not claiming decisions as yours when they were made by others
◇ not describing outcomes that did not happen

Portfolio entries that are scrubbed of all difficulty do not read as impressive. They read as suspicious. An experienced reader — someone who has done the kind of work you are presenting — knows that significant work involves significant difficulty. A portfolio that claims otherwise implicitly claims that either the work was not significant, or the account is not honest.

Honesty about difficulty, handled well, is a quality marker — not a weakness. The entry that says "the authentication flow broke in production and here is how we diagnosed and resolved it" is more credible and more interesting than the entry that implies everything worked the first time.

The Right Number of Entries — by Stage¶

These are not rules. They are calibrated expectations based on what is realistic at each stage and what serves the reader at that stage.

The lower end of each range, documented to genuine depth, outperforms the upper end documented superficially.

Applying the Quality Filter¶

When you have identified your candidate pieces — the projects you are considering including — run each one through this quality filter before committing.

Can you explain the problem it was solving in two sentences for someone outside your discipline?
If not, the framing needs work before the entry is ready.

Can you name one significant decision and explain why you made it instead of the alternatives?
If not, the entry does not yet meet the depth of explanation standard.

Can you describe one thing that was genuinely difficult, and what you took from it?
If not, the honesty layer is absent — and the entry will read as shallow.

Would you be comfortable if a senior professional in your field asked you to expand on this entry in a ten-minute conversation?
If not, the entry is not ready — or does not belong.

Work that passes all four is portfolio-ready. Work that fails one or more needs either more development or honest reconsideration of whether it belongs.

When All Your Work Feels Equally Strong — or Equally Weak¶

Two situations produce real difficulty in quality assessment.

Everything feels strong. You have multiple projects you are proud of and cannot decide between them. In this case, return to the narrative anchor — which pieces serve the professional story you are telling most directly? Among those, which can you explain most specifically and defend most confidently? Those are the ones that belong.

Nothing feels strong enough. You look at your work and find nothing that meets the quality standard you think a portfolio requires. This is extremely common, and it usually signals one of two things: either the standard you are applying is unrealistic for your stage, or the documentation of the work is thinner than the work itself warrants.

A project that was genuinely engaged with — where real decisions were made, real problems were encountered, real learning happened — is almost always portfolio-ready at its stage. The gap is usually in the documentation, not in the underlying work. This is what Retrospective Gathering addresses directly.

Continue to Retrospective Gathering →