You have done the work. The case study is finished, the samples are in order, and then you reach the paragraph that stops most people cold: the few lines that have to explain why any of it matters. Write it plainly and you seem to vanish. Write it with any enthusiasm at all and you risk sounding like the worst kind of motivational post. There is a middle path, and it mostly involves moving the spotlight off yourself and onto the work.
What a portfolio blurb is actually for
A blurb on a project page, case study or about page has three jobs: give the reader enough context to care, say what you did, and hand them a reason to look at the images or read the next paragraph. That is the whole brief.
It is not a testimonial, a CV or a statement of creative philosophy. Readers skim. They are usually trying to answer one question — could this person do the thing I need doing? — and they will answer it from evidence, not adjectives.
Length matters more than you think. A project blurb of 40 to 120 words is usually plenty: two sentences of context, two of action, one of outcome. About pages can run longer, but the same instinct applies. Say less, and make what you say count.
Let the work carry the praise
Compare two openings:
I am a passionate designer with a strong eye for detail and a track record of delivering innovative solutions.
The shop had a large product catalogue and a checkout that lost people on the third screen. I rebuilt it around a single-page form.
The second says nothing about talent and leaves you in no doubt that the person can do the job. That is the trade. Adjectives are claims the reader has to take on trust; specifics are proof they can check.
It feels risky to leave the self-praise out. It is not. A portfolio is already an argument that you are good at what you do, and the samples make that argument for you. Your job in the blurb is to explain what the reader is looking at, why it was hard, and what changed as a result.
Three structures that keep you honest
If you are staring at a blank page, borrow one of these. Each forces you towards facts.
Problem, move, result
State what was wrong or missing, describe the decision you made, then say what happened. This suits case studies and client work, where the before-and-after is the point.
Constraint, decision, outcome
Name the thing that made the project difficult — a tight deadline, a small budget, an awkward legacy system, a nervous stakeholder — then explain the choice you made and what it produced. Constraints make your judgement visible.
Role, scope, what changed
Useful when you worked as part of a team. Say what you were responsible for, how far your remit stretched, and what was different afterwards. Being precise about your role is not modesty. It stops the reader guessing, and it stops you implying you did work you did not.
Words that do you no favours
Some words have been used so often in this context that they have stopped meaning anything. Swap them for something a reader can picture.
- Passionate — everyone is, apparently. Show the interest by describing the part of the work you clearly spent too long on.
- Results-driven — say which results, and for whom.
- Innovative, cutting-edge — describe what had not been done before, or cut the word.
- Seamless — usually a claim about something the user never noticed. Fine if you can point to the work that made it so.
- Helped with — vague and self-erasing. Did you write it, design it, run it or advise on it?
- Leveraged, utilised — "used" is a better word. "Built" is better still.
The verbs worth hoarding are the plain ones: wrote, redesigned, cut, tested, rebuilt, interviewed, shipped, reduced, rewrote. Keep a list beside your draft and reach for those first.
The about page is where the cringe lives
Project blurbs are awkward. About pages are worse, because there is nothing to hide behind.
Three things help. Write in the first person: "I design..." reads as a person, whereas "Alex is an experienced..." reads as a press release, unless you are a studio writing about a team. Lead with what you do and who you do it for, then add the details that make it specific — where you have worked, the tools you actually use, the sort of project you turn down. Finally, allow yourself one human detail. A genuine preference is disarming. Three of them is a personality blog.
If it helps, write the boastful version first, privately, then delete it and write the factual one. Most people find the second draft much easier once the first is out of their system.
The editing pass that fixes most of it
Once a draft exists, you can stop worrying about tone and start editing. Work through these in order:
- Read it aloud. Anything that makes you wince when spoken is doing the same to a reader.
- Delete the first sentence. It is usually throat-clearing.
- Circle every adjective. Replace it with a fact or remove it.
- Find every "helped" and "worked on", and say what you actually did.
- Check that the verbs are active and the subject is clear.
- Cut a quarter of the words. Whatever survives, keep.
Then ask someone who does not know the project to read it, and to tell you where it starts to sound boastful. They will usually point at something you assumed was the modest part.
Before you publish
Confidence in a blurb comes from evidence, not volume. If every claim in your draft is attached to something concrete — a decision, a number, an artefact the reader can see — you can write it plainly and it will still read as assured.
Run one last check. Does the blurb tell the reader what they are looking at? Does it say what you did? Does it avoid asking them to take your word for anything? If the answer to all three is yes, publish it and move on. You can tighten it later, and most portfolio blurbs improve on the second or third pass anyway.
Photo: Kawê Rodrigues / Pexels
