When an application asks for a Loom, most candidates record a portfolio tour. Record this instead: one method, run live, on something real.
Target: 5:00. Under four feels thin, over six gets scrubbed. Screen share with your face in the corner — they are hiring a client-facing designer and need to see you talk.
---
0:00–0:25 · Cold open, no throat-clearing
On camera, full screen. No slide.
"Mikel Rosenthal. Twenty-three years making enterprise software legible — Edison at GE Healthcare, FIBER at Blue Cross, Pathfinder at Avant. Rather than walk you through screens, I want to show you how I actually work, because that's the part that transfers to your clients."
Do not list your résumé past those three systems. They have the PDF.
0:25–1:10 · The problem you're solving for them
Share screen. Start Here page, then the deck's "two entry points" slide.
"Agency work starts the same way every time: a pile of material, a client who described a solution rather than a problem, and a date. The first decision is which fork you're on. If the question is a design system, that's a counting exercise — I start with artifacts, with what actually ships. If it's a product, it's a people exercise. Getting that wrong wastes the first two weeks, and I've watched it happen."
1:10–2:40 · Run intake, live
Switch to Claude with the skills loaded. Paste a brief — theirs if you can get one, otherwise a public product page.
"I'm running the intake skill. Watch what it refuses to do."
Let it generate. Do not narrate the wait. Then:
"Two things. The metric says UNRESOLVED — it didn't invent a number, because the rule says never invent a number. And there are three questions back, not thirty. Three, because those are the ones that change the shape of the work."
Scroll to the assumption register.
"Every ambiguity has an owner and a cost of being wrong. That's the artifact that stops month-three relitigation."
2:40–3:40 · The systems-thinking beat
Deck, "mapped six ways" slide.
"Once the problem is agreed, I map it in six directions. Up to the business number. Down to tokens and components. Across to patterns that already exist — most problems have been solved once in the product already. Back to the data, because what the API actually returns is a design input. Forward through every state. Out to the edges."
Then Pathfinder:
"On Pathfinder that meant the system shipped alongside the product rather than ahead of it, and every pattern was proven in a real screen before it entered the library."
3:40–4:25 · Critique — the beat that separates you
"Here's the part I care about most."
Run critique on the output from 1:10.
"It's arguing against my own work before anyone else has to. If the output is encouraging, the skill has failed — that's written into the file. This is the cheapest quality gate I have, and it's why what reaches a client review is the second version, not the first."
4:25–5:00 · Close on the limit, not the capability
Back to camera.
"What I never delegate: the problem statement, talking to users, the final visual call, and anything stated as fact. The tooling compresses the loop — it doesn't decide what the loop is for. Twenty-three years of judgement is the part that doesn't automate.
Give me a brief and an hour and I'll run this on your product instead of mine. Thanks for watching."
---
Rules for the recording
- One take, minor stumbles kept. Over-polish reads as a sales video and undercuts the point. A real pause while something generates is fine.
- Don't apologise for the tool. No "obviously AI isn't a designer" hedging — the close handles it with more authority than a disclaimer.
- Don't read the slides. They're behind you; say the thing the slide can't.
- Show one real failure if the demo misfires. Recovering on camera proves more than a clean run.
- Caption it. They advertise WCAG conformance; an uncaptioned video from an accessibility-forward candidate is a bad first impression.
What to send with it
Subject line: Senior Designer — process walkthrough + the tooling
Three links, nothing else: the Start Here page, the Loom, the résumé PDF. No paragraph explaining them; the page does that.