Writing Effective Project Briefs

Imagine you have finished several real projects and you are ready to share them. Before a hiring manager reads a single line of your code or your write-up, they have to decide whether your work deserves more of their time. That first decision is made quickly.

A forty-five-second window means the reviewer will not read everything. Whatever they encounter first carries most of the weight. The useful question for a portfolio author is therefore not what is in the portfolio, but what a reviewer will see in the first moments and whether the most convincing work is among them.

In the illustration, a reviewer who finds the strongest project at the top of the list has a chance to form a judgment. A reviewer who has to dig through weaker or unrelated work to find it may move on before reaching it. This is why arrangement is a deliberate act rather than a simple chronological list.

Because the review window is so short, the first presentation decision is selection. The source directs you to spend the window on three projects that demonstrate the work. Three is the number the source names, and the point behind it is focus. A reviewer who meets three well-chosen projects can form a clear picture of what you can do, while a reviewer handed twelve projects must decide for themselves which ones matter.

Choosing the three means asking two questions. First, which projects show the skills the reviewer cares about? Second, which of those projects show the skills most convincingly? A project can be impressive to its author and still be a weak choice if it does not demonstrate the work a reviewer is looking for.

Choosing three projects is not enough if a reviewer cannot get into them quickly. The source names the README as the tool that makes each project scannable. A scannable project is one a reviewer can survey at a glance. They can tell what the project is, what problem it addresses, and where to look next, without reading every line.

The README does the surveying work on the reviewer's behalf. Because the reviewer may only spend seconds on it, a README that opens with a clear statement of purpose and points the reader to the key work gives the reviewer what they need. A README that makes them hunt for the purpose wastes the window, and this is where a presentation is won or lost.

The third demand in the source is evidence. A portfolio has to show that the projects are real and that you built them. A reviewer who sees polished work will still wonder whether it came from you, so the presentation should answer that doubt directly.

Selection, scannability, and evidence are not independent checklist items. Each one feeds the next. The selected projects give the reviewer something worth looking at. The README lets the reviewer grasp each project quickly. The authorship evidence lets the reviewer believe what they have grasped. Only when all three are present does a short review turn into a confident judgment.

The second half of the source introduces project briefs. A project brief is a document that outlines the details of a project. The source presents two worked briefs and says to use them as templates for your own. Each brief has a particular shape. It is written by a candidate before the work begins, and it is followed by a critique that explains what would make the project a strong portfolio piece and what would make it a weak one.

Reading a brief this way teaches you to plan a project so that it can be presented well later. The pre-work half asks you to commit to what the project is before the work begins. The critique half shows you what separates a strong portfolio piece from a weak one, so you can aim for the strong version from the start.

The source's first worked brief is titled Invoice triage for a regional accounting practice. The title alone tells you the domain and the kind of work involved. The source does not reproduce the full text of this brief in the material available here, so the walkthrough below applies the three demands to a brief of this kind rather than quoting its details.