Designer Portfolio Deck
Specifications
- Slides
- 12 slides
- Aspect ratio
- 16:9 (Widescreen)
- File format
- PowerPoint (.pptx)
- Font
- Calibri
- Version
- 1.0
- Editing
- Fully editable
- Primary color
-
#334155
Style
Tags
About this template
What these 12 slides prove
A designer portfolio is not a gallery; it shows what process someone follows and what comes out of it. This file is built that way, and the cover subtitle says so: twelve slides running from the person behind the work through to trend analysis, with shapes and colors free to change. It suits a job application attachment, a freelance pitch or a first client meeting – not a design critique session.
Agenda and body match line for line
Cover, agenda, three divider-plus-body pairs, the before/after redesign slide, key figures, a trend slide and a closing page – twelve in total. The six agenda lines are the person behind the work, one project in depth, tools, before and after, key figures and trend analysis, and their order matches the body exactly. Only the first three have dividers (slides 3, 5, 7) with bodies on 4, 6 and 8; the last three are single slides 9, 10 and 11. Reviewers often stop early, so if the role you are applying for maps onto one project, move that section to the front and renumber the agenda with it.
- Write slide 6, the in-depth project, first – its lead line asks you to unfold one job end to end, and every other slide summarises it.
- Lock its three lines into problem, my role, result. The defaults – a twelve-week checkout redesign, three drop-off points narrowed, enquiries down 41% after launch – already sit close to that order.
- Then write slide 4, the person behind the work; its lead asks which problems you enjoy solving, so keeping only what the project demonstrates filters it for you. The seven years of B2B work in the default text is the same 7 as the card on slide 10, so change both.
- Write the tools section, slide 8, last. Its defaults are about handoff – building a Figma component library, validating with prototypes, writing spec documents for engineering – not about tool names. The repeated steps only become visible after the first two sections exist.
- The closing slide is two lines offering the original portfolio file, with no contact block anywhere in the deck. Add your email or site there.
Slide 9 states the result for you
The before/after slide pairs the left column (eleven buttons on one screen, six steps to complete a payment, body text failing contrast) against the right (three key buttons, three steps, WCAG AA contrast met). It is the single line about narrowing three drop-off points made visible, so when you swap in your own project the only rule is to pair the same item left and right. Countable things work best: screens, steps, accessibility criteria. A claim about being user-centered is what everyone writes and buys nothing here; numbers and durations carry far more in the same space.
Figure cards and discipline bars
Slide 10 holds 7 years of experience, a 41% drop in enquiries, a 12-week longest project and 6 repeat commissions. The first three are lifted straight from slides 4 and 6, so swapping the project means swapping the cards. Early in a career, change the labels rather than inflating values – for example 2 projects as lead, 4 engineers collaborated with, 40 design system components. Slide 11’s four bars (apps 58, web services 92, design systems 37, graphics 24) show where your work sits; they sum to 211, so they are not percentages – caption whether they are counts or shares, and order them so the hiring company’s core area reads highest. The bars are shapes: the baselines are aligned on one line, so rescale each top by value / largest value.
What gets filtered out in screening
- Listing tools – names alone distinguish nobody. Slide 8 already mentions writing handoff specs; expand that instead.
- Including every iteration; the body layout is spaced for three items, so extra images break it. One final plus one pivotal draft is enough.
- Omitting your scope on team projects – this is the first thing reference checks probe. Slide 4 does that job with its line about starting from definition without a product manager; write the project slide to the same standard.
- Editing the agenda and the divider titles separately; the same wording appears twice, on slide 2 and on slides 3, 5 and 7.