Shipped Work

What it is. Shipped work is design that actually made it into production where real users touch it every day. It carries battle scars from engineering handoffs, last minute scope cuts, browser quirks on Android 9, and the inevitable post launch bugs that surface at 2 a.m. The case study template article drives this home on repeat. Hiring managers scan your portfolio for thirty seconds hunting for evidence you shipped something that moved a number. Shipped work supplies exactly that with live screenshots from the production site, Amplitude dashboards showing the conversion lift, GitHub PR links, and specific metrics pulled from the week after launch. It respects every constraint you listed because those constraints shaped the final product. It includes the decision log that proves you made trade offs under pressure instead of endlessly iterating in the studio. The voxel image in the article says it plain. The right side shows the real device with the shipped interface. The left shows the Figma comp with perfect drop shadows. Shipped wins every single time because it proves your decisions faced reality. Tools like LaunchDarkly for feature flags, Hotjar for session recordings, and Core Web Vitals reports become part of your evidence. Without shipped work your portfolio reads like a school project. With it the portfolio becomes a rap sheet of bets that paid off.

What it isnt. Shipped work is not the 47 screen flow you designed in Figma for a fake fintech startup that never saw code. It is not the speculative redesign of the Slack sidebar you posted to Dribbble in 2021 with zero users and zero data. It is not the mood board, the divergent ideation grid, the personal design philosophy essay, or the beautiful but unbuilt comp reel the article correctly labels as bloat. Those artifacts belong in your private folder or your workshop notes. They do not belong in the case study a hiring manager at Linear or Vercel opens while drinking coffee and closing tabs. If your portfolio case study ends with a polished artboard instead of a production link it fails the shipped test. If it opens with your journey instead of the outcome it already lost. If it pads with ten vague metrics instead of three specific ones pulled from production it reads as desperate. Hiring managers smell unshipped work instantly and move on.

Concrete example. Sarah Kim led the checkout redesign for Stripe in Q3 2022. Her one line outcome read Redesigned enterprise checkout flow which lifted conversion 34 percent and cut procurement team friction in half within the first quarter post launch. The problem paragraph nailed the exact constraint. Enterprise buyers abandoned at 67 percent because the flow assumed a single user with a credit card when in reality three departments needed to approve net 60 invoices without leaving the page. Constraints listed seven bullets. Team of three, seven week timeline from kickoff to ship, existing design system locked with no overrides allowed, SAP integration required on day one, WCAG AA mandatory, no backend changes permitted, and must work on mobile for field sales teams.

Process section showed exactly three artifacts. A journey map built in FigJam that isolated the exact screenshot sharing pain point. A Maze usability test with 41 enterprise users that delivered the quote we will never use this. And the actual shipped checkout live at stripe.com with the new public quote link that required zero account creation. The decision log listed five entries. One read Decision rebuilt quote sharing as read only public link. Alternative was native in app collaboration with account creation. Reason was procurement teams sit on completely separate systems and would never wait. Result was 74 percent of quotes opened within 24 hours versus 9 percent before. Outcomes included the conversion lift, support tickets dropping from 186 to 41 weekly, task completion rate climbing to 89 percent, and a Core Web Vitals improvement that moved Stripe from 67 to 94 on mobile. Role statement was direct. I owned all interaction design, ran every test, paired daily with the checkout engineer, and pushed the final CSS tweaks myself. Reflection admitted she under scoped the mobile keyboard behavior by three weeks and would split it into its own spike next time. The full case study followed the exact eight section template, stayed at 1720 words, and got her three staff level interviews at companies that actually ship.

A second concrete example comes from a mid level designer at Dropbox in 2021. His original portfolio showed six gorgeous concepts for the sharing modal with beautiful micro animations. Zero production links. Zero metrics. He received nice feedback and zero callbacks. After the rewrite he focused only on the single shipped version that launched in May 2021. It used a command bar instead of nested modals, produced a 22 percent lift in completed shares, cut support volume by 60 percent according to Zendesk data, and included the actual dropbox.com production screenshot on a real Windows machine. His callback rate tripled. The difference was shipped work.

When to use. Use shipped work as the structural spine of every portfolio case study regardless of seniority. The article table shows junior work stays at 800 words while staff work reaches 2500 but the shipped core never changes. Lead with it in interviews when they say walk me through your best project. Open the live URL and let them click the actual thing. Reference it during performance reviews because shipped work with numbers is how designers prove they deserve the raise or the promotion. Put it above the fold on your portfolio site so the 30 second scan delivers impact before the hiring manager finishes their coffee. Teach it to every junior designer you mentor because portfolios full of unshipped comps create designers who fail at real jobs.

When not to use. Never pad a case study with speculative concepts and call them shipped. Do not claim personal side projects as shipped work unless you actually deployed them to a real domain, drove real traffic, and can show analytics from Plausible or Google Analytics. Skip the shipped framing when presenting early exploration to clients because they understand the difference between pitch material and production. If the project sits behind a strict NDA then name the industry not the company and replace exact numbers with ranges but still show the live patterns if you can. Never invent metrics. The article FAQ warns that hiring managers have friends at every company and fabricated shipped work ends careers.

Shipped work turns your portfolio from a scrapbook of pretty ideas into a rap sheet of things that actually worked.