# The Present-Your-Work Round, Built From Your Projects to a Rehearsed Deck

*You will build a presentation-round deck with role-mapped projects, a slide spine keyed to what the panel scores, and a narrative rehearsed to your slot with tradeoff answers loaded.*

- Canonical URL: https://www.refolk.ai/candidates/guides/present-your-work-round-deck
- Pillar: Positioning and materials
- Format: Playbook
- Published: 2026-08-11
- Last reviewed: 2026-08-11
- Reading time: 16 min

You have been invited to a "present your work" round: a portfolio review, a case presentation, or a design deep-dive where a panel watches you walk through real projects and interrupts to test whether you actually did them. This guide is for the designer, analyst, or PM who has that session on the calendar and needs to pick the projects, build the deck, and rehearse it before the day. It treats deck construction as one repeatable job with a single slide spine and role-specific cuts, so you can execute it start to finish without improvising.

The reason this guide exists is that the good public answers are siloed by role. UX blogs teach the portfolio review, consulting coaches teach the case presentation, and nobody gives a cross-role build method for the round they share. The mechanics are the same. What differs is only where you enter the story.

## What the "present your work" round actually is

The present-your-work round is a live session where a panel watches you walk through selected projects and interrupts to probe your decisions. It exists in three common formats: the design portfolio review, the analyst or PM case presentation, and the consulting written case. They share a spine and diverge only at the entry point.

Design portfolio reviews commonly run 30 to 60 minutes. A standard design-review shape is a 45-minute to 90-minute session with two or three interviewers plus an optional engineering or product person, two to three case studies, and 15 to 20 minutes reserved for questions. Consulting written cases work differently: you get a handout of 20 to 40 pages, one to two hours to analyze it, and you produce three to five slides.

The volume behind this matters for how hard you have to work. In Refolk's index of professional profiles, there are 16,758 US Product/UX Designers and 11,033 US Management/Strategy Consultants, so you are rarely the only person the panel will watch present that month. Selection and defensibility, not polish, are what separate you.

**16,758 - US Product/UX Designers in Refolk's index**

A deep pool means the panel is calibrated; a role-mapped, defensible project beats a prettier off-target one.

## The single slide spine that works across roles

Every version of this round is built on the same backbone: context, process, decisions and tradeoffs, results, and takeaways. The divergence is only where you enter. Design tells the story chronologically from problem to outcome; consulting and exec-heavy panels state the answer first and hold methodology in reserve.

Design sources converge on a sequence of title slide, agenda, a brief introduction, then per project the brief, the design process, the final outcome, and takeaways plus next steps, closing on a thank-you slide. The introduction should take no more than five minutes and you can usually get through it in two to three. The consulting cut inverts the order using the Pyramid Principle, created by Barbara Minto at McKinsey in the 1960s: your opening slide is a clear executive summary delivering the key takeaways and recommendations, followed by findings, business impact, recommendations, and next steps.

#### The shared spine, entry point aside

1. **Context** - The problem, framed so it is well defined before you touch a solution
2. **Process** - How you approached it, compressed to what a decision hung on
3. **Decisions** - The tradeoffs and the constraint you can defend
4. **Results** - The metric next to each claim, and what shipped
5. **Takeaways** - What you learned and what you would do next

*Every present-your-work deck runs this backbone; only where you start it changes by panel.*

The reason one spine holds across roles is that the divergence is genuinely only the entry point. Executives interrupt, and if you build to a conclusion every question derails you; if you have already stated your answer, questions become productive exploration instead. So the same content, resequenced, serves a design panel and a strategy panel.

> **Rule:** Match the entry point to the panel
>
> For a design or research panel, tell the story chronologically from problem to outcome. For a business, PM, or exec-heavy panel, put the recommendation on slide one. The spine underneath is identical.

## Choosing projects against the role, not the prettiest work

Pick projects for defensibility and role-fit, never for prettiness. Each project you present must carry a one-line "this shows the skill you are hiring for," or it does not belong in the deck. This is the highest-leverage decision in the whole job.

Select two to three of your most relevant projects, ideally ones that align with the company's specializations and the job requirements. Note the tension worth resolving early: some coaches argue you should usually present one main case study rather than your entire portfolio, because interviewers prefer depth over quantity. If your slot is short, one deep case beats three shallow ones. The rules that survive across roles:

- **Show finished, shipped work.** Interviewers focus on designs that resulted in a finished product. An abandoned concept, however beautiful, gives them nothing to probe.
- **Pick for talk-shop value.** Choose projects that let you talk about the challenges, tradeoffs, and ultimate impact, not ones that only look good.
- **Map the signal to your role.** If you are a PM, point out tradeoffs, not just screenshots. If you are a data analyst, show the dashboard then explain the metric definitions. If you are in sales, include quota, deal size, and cycle length. If you are going for a UX research role, present a project where you owned the research.

#### Which projects earn a slot

Horizontal axis runs from Off-target for this role to Maps to the screened skill. Vertical axis runs from Not shipped or hard to defend to Shipped and defensible.

| Quadrant | What it means |
| --- | --- |
| Cut it | Off-target and undefendable; delete without regret |
| Bench it | Shipped but off-target; hold for a different role |
| Risky | On-target but unshipped or thin; only if you can defend every gap |
| Lead with it | On-target, shipped, defensible; this is your main case |

*Only the top-right quadrant belongs in the deck; polish without relevance is a trap.*

The deeper the pool you compete in, the more this matters. With 16,758 US designers against 4,107 in the UK in Refolk's index, a 4.08x deeper US pool, you are differentiated by project choice, not by adding one more polished screen.

If you are unsure how a real hiring panel maps projects to a role, it helps to see how people who won that exact role positioned their own work. [Refolk](/candidates) writes a job seeker's resume from their own history and scores how well they fit a posting, which surfaces the projects worth leading with before you build a single slide.

Ask me this: `Data analysts who built customer-facing dashboards and defined the core metrics themselves.` - [run the search](https://www.refolk.ai/start?q=Data%20analysts%20who%20built%20customer-facing%20dashboards%20and%20defined%20the%20core%20metrics%20themselves.).

*Returns profiles of analysts whose shipped, metric-owning work is the kind a case-presentation panel scores highest.*

## Time and slide budgets by slot length

Match your slide count and project count to the slot, and always reserve time for questions. Aim for 7 to 10 content slides at 30 minutes and 15 to 20 at 60 minutes, excluding cover, agenda, and divider pages. Below is the budget assembled from public sources.

| Slot length | Content slides | Q&A reserve | Projects |
|---|---|---|---|
| 30 min | 7 to 10 | 10 min | 1 to 2 |
| 45 min | ~12 | 15 min | 2 to 3 |
| 60 min | 15 to 20 | 15 to 20 min | 2 to 3 |

The Q&A reserve is not optional padding. UX research reviews advise leaving 10 to 15 minutes for panel questions, and standard design reviews reserve 15 to 20 minutes. If your rehearsed run leaves no buffer, you have too many slides or too many projects.

Here is the same discipline applied to the two markets you might be competing in, because the pool size shapes how ruthless your selection has to be.

| Role | Market | Count in Refolk's index | Share of the two-market pool |
|---|---|---|---|
| Product/UX Designer | United States | 16,758 | 80.3% |
| Product/UX Designer | United Kingdom | 4,107 | 19.7% |
| Derived multiple | US vs UK | 4.08x larger US pool | - |

Counts come from Refolk's index; shares and the multiple are derived from those counts.

## Build the deck and rehearse it, step by step

This is the procedure, in order, with how long each stage takes and what "done" looks like. Run it top to bottom. The one place sources genuinely disagree is step three: design tells the story chronologically, while consulting states the answer first per the Pyramid Principle. Pick the entry point that fits your panel and keep the spine underneath identical.

#### From your projects to a rehearsed deck

1. **Confirm the brief** - Get the exact time slot, panel size and roles, format (live, deck, or site), and whether they named projects. Blind confirms panels vary from a solo reviewer to a 6-person panel including a CPO. Done when you know minutes, panel, and format in writing.
2. **Select projects against the role** - Map each candidate project to the skills the role screens for and drop anything not shipped or not defensible. Choose 1 to 3. Done when each project has a one-line "this shows X skill" tied to the posting.
3. **Draft the spine** - Lay out title, agenda, a 2-to-3-minute intro, then per project: context, process, decisions and tradeoffs, results, takeaways, and Q&A. For exec panels, lead with the recommendation. Done when you have an outline with a stated entry point.
4. **Build slides, one idea each** - Give each slide a single idea and use as many as you need so nothing oversaturates. Strip body text to a headline and put the metric next to every claim. Done when no slide holds a paragraph.
5. **Insert tradeoff and impact evidence** - Pre-load an answer to the "hard constraint you can defend" question for every project, and clean the narration so personal decisions read as "I" not "we". Done when each project has one defensible tradeoff slide.
6. **Rehearse to time in three cuts** - Practice a 90-second, a 3-minute, and a 6-minute version of each project with a friend, and simulate an interruption at minute two. Done when the full deck fits the slot with the Q&A buffer intact.
7. **Prepare fallbacks** - Save the deck as PowerPoint and PDF across three locations: emailed to yourself and the recruiter, on a USB drive, and in cloud storage, plus a printed handout. Done when a corrupt file or failed share costs you nothing.
8. **Run a tech dry-run** - Test the actual call software and practice opening the deck the instant you share your screen. Done when screen-share is verified end to end and there is no folder-hunting in the flow.

### Why one idea per slide

The one-idea-per-slide rule is a cognitive-load defense, not an aesthetic preference. Each slide should pertain to one idea; use as many slides as you need so none gets oversaturated. When a slide is dense with text and you speak over it, the split-attention effect kicks in: the audience cannot process both streams, so they process neither well. That is why a wall of text makes the panel disengage even when your spoken content is strong.

> A website is asynchronous; a presentation is not. Reuse the site and the panel tunes out during your best moment.

### Why three rehearsal cuts

Rehearsing three lengths is interruption insurance, not perfectionism. Before the interview, rehearse each project in a 90-second, a 3-minute, and a 6-minute version. Because most panels interrupt around minute two if they want specifics, a candidate who only rehearsed the six-minute version collapses when cut short. The shorter cuts let you compress on demand without dropping the tradeoff and the impact.

## The tradeoff question and the ownership tell

Panels interrupt to test whether you actually did the work, and they do it two ways: by probing a tradeoff and by listening to your pronouns. Prepare for both explicitly, because a polished process story with no tension and vague "we did it" narration is exactly what fails.

Interviewers will jump in and ask about the tradeoffs you made, the research you conducted, and the launch process. It shows immediately if you have BS-ed parts of the process or do not know your own work. HubSpot lists the exact probes: what hard design choices or tradeoffs you had to make, a hard constraint that led to a compromised solution that you can defend, and a tension you had to navigate. The first thing many interviewers check is whether the problem you set out to solve is well defined at all.

The ownership tell is pronoun-level. Interviewers explicitly weigh the moments when you say work "we did" versus "I did." Pronoun discipline is the cheapest credibility signal you have: a candidate who narrates specific personal decisions clears the "did you actually do this" bar that generic process-storytellers fail.

**Tradeoff slide skeleton, one per project**

```
Constraint: [the real limit - time, data, platform, headcount, budget]
The tension: [what pulled against what - speed vs accuracy, scope vs deadline]
My decision: [the specific call I made, in first person]
What I cut: [the compromise I would defend, and why it was the right one]
Result: [the metric that shows it worked, next to the claim]
```

*Fill this in for every project before you rehearse; it is the answer to the question the panel interrupts with.*

Do not skip the "what I cut" line. A story with zero tension reads as a false positive to an experienced panel. They want the defensible compromise, not a flawless narrative.

## How this round goes wrong

Most present-your-work rounds are lost on avoidable mistakes, not on the quality of the work itself. Each failure below has a symptom that feels safe from the inside and a check you can run before the session.

- **Presenting the live site or a Medium article.** Feels efficient, but the panel silently reads ahead and stops listening. When you scroll through an article, interviewers are distracted trying to read ahead and you cannot get their attention. Check: can you control exactly what is on screen at each sentence? If not, build a deck.
- **Recycling the website as the deck.** A website is an asynchronous artifact built for self-paced reading, not a presentation. Check: does each screen carry one idea you are speaking to, or a page of detail you are competing with?
- **"We" everywhere.** Reads as team credit and makes the interviewer suspect you did not own the work. Check: count "I" versus "we" in a recording and name your specific decisions.
- **No defensible tradeoff.** You narrate the process but cannot name what you cut. Check: for each project, state one constraint and the compromise you would defend.
- **Wall-of-text slides.** Feels thorough; triggers split-attention and reads as amateur. If a slide has a 5,000-word essay, it tells the panel you do not understand the intrinsic meaning of design. Check: if a slide holds a paragraph, cut it to a headline plus one visual.
- **Overrunning the slot.** Deep-diving three or four projects in 45 minutes is impossible. Check: time each cut, and if it does not fit with a Q&A buffer, drop a project.
- **Prettiest over most-relevant.** Impressive but off-target work the panel cannot map to the role. Check: every project must carry a "this shows the skill you are hiring for" line.
- **Story-order deck for an exec panel.** Your conclusion sits on slide twelve and time-poor interrupters never reach it. Check: for business and PM panels, put the recommendation on slide one.

> **Watch out:** The folder hunt ends it before you start
>
> The moment a candidate starts hunting through folders on their computer, the interviewer knows they are not prepared. Have the exact file open and ready to share before the call, not somewhere on your desktop.

One claim worth flagging as unsettled: some coaches recommend matching the company's brand fonts and colors, while others warn it reads as pandering. The idea that copying the brand backfires is not established publicly with hard evidence. If you want to test it locally, ask a mentor who has sat on that company's panels rather than guessing.

## Logistics and fallbacks that save the session

Carry the deck redundantly and dry-run the technology, because a corrupt file or a failed screen-share can end a strong candidacy on logistics alone. The standard here is the 3-2-1 rule: three copies, two storage types, one offsite.

Bring your presentation in both PowerPoint and PDF. Save it across multiple locations: a USB drive, cloud storage, and your own device. Even if you are presenting on your own machine, email a copy to yourself and to the recruiter so they can pass it to the interviewer if your setup fails. Keep any emailed PDF under 15MB so it is not rejected by an inbox filter.

| Format or copy | Where it lives | What it protects against |
|---|---|---|
| PowerPoint | Your device plus cloud | Editing on the day, live animation |
| PDF | Emailed to self and recruiter | File corruption, missing fonts |
| Printed handout | In your bag | Total tech failure, in-person rooms |

On the deck-versus-site question for logistics: present directly from your case study pages only if the company explicitly requests it or you need an offline backup. For a live, interrupted panel, the controlled deck wins every time.

## Keep the deck current between loops

A present-your-work deck is not a one-time artifact; it is a reusable asset you re-cut per role. After each round, do three things while the session is fresh. Note which tradeoff question the panel actually asked, because the next panel for a similar role will likely ask a variant. Re-map your project set against the new posting, since the "this shows the skill" line changes when the role changes. And re-time your cuts, because a project you have told four times compresses differently than one you rehearsed cold.

#### Before you call the deck done

- [ ] Every project carries a one-line "this shows the skill you are hiring for" tied to the posting.
- [ ] The entry point matches the panel: story-first for design, answer-first for exec and PM panels.
- [ ] No slide holds a paragraph; each has one idea, a headline, and the metric next to the claim.
- [ ] Every project has a tradeoff slide naming the constraint and the compromise you would defend.
- [ ] Narration says "I" for your own decisions, not a blanket "we".
- [ ] You have rehearsed 90-second, 3-minute, and 6-minute cuts and simulated an interruption at minute two.
- [ ] The full run fits the slot with the Q&A buffer intact.
- [ ] Deck exists as PowerPoint and PDF across three locations, plus a printed handout, PDF under 15MB.
- [ ] Screen-share is tested on the actual call software and the file opens the instant you share.

Treat the spine as fixed and the cuts as disposable. The panel changes, the projects you lead with change, and the entry point changes, but context, process, decisions, results, and takeaways carry every time.

## Frequently asked questions

### How many projects should I present in a portfolio review?

Select 1 to 3 of your most relevant projects, and let the slot decide the exact number. A 30-minute round supports one deep case study or two shallow ones; 45 to 60 minutes supports two to three. Depth beats quantity, so one main case presented thoroughly usually outscores four rushed walkthroughs. Trying to deep-dive three or four projects in 45 minutes is the most common overrun.

### How do I present a case study in an interview without reading off my portfolio website?

Build a deck, do not present the live site. A website is asynchronous: people listening to your voice cannot read a detail-rich page at the same time, so the panel silently reads ahead and stops listening during your strongest moments. Convert your case into slides where you control exactly what is on screen at each sentence, one idea per slide, with the metric next to each claim.

### What questions do interviewers interrupt with during a presentation round?

Panels probe tradeoffs and ownership. HubSpot names the exact form: what hard design choices or tradeoffs you made, a hard constraint that led to a compromised solution you can defend, and a tension you had to navigate. They also weigh 'we did' versus 'I did' to test whether you owned the work. Most panels interrupt around minute two, so prepare to name a specific decision fast.

### How long should the intro to my presentation be?

Cap the intro at five minutes, and you can usually do it in two to three. The panel is there for the work, not your biography. Spend the reclaimed time on decisions, tradeoffs, and results, which is what actually gets scored. A long intro also pushes your conclusion later, which is dangerous with panels that interrupt early.

### Should I put my recommendation first or tell the story chronologically?

It depends on the panel. Design reviews reward a chronological problem-to-outcome story. Business, PM, and consulting panels reward the Pyramid Principle: state the answer first, then hold methodology in reserve. Time-poor executives interrupt, and if your conclusion sits on slide twelve they may never reach it. When in doubt about an exec-heavy panel, lead with the recommendation.

### What backups should I bring to a presentation interview?

Follow a 3-2-1 approach: three copies across two storage types with one offsite. Bring the deck as both PowerPoint and PDF, email a copy to yourself and the recruiter, carry a USB drive, and keep a cloud copy plus a printed handout. Keep any emailed PDF under 15MB so it is not rejected by an inbox. This means a corrupt file or a failed screen-share costs you nothing.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/present-your-work-round-deck*