← All case studies
Patreon — Video Production Team
Patreon: Video Production Workflow
They loved Notion — but their system wasn't built to scale.
My role
What I was responsible for on this engagement.
UX Researcher and Information Designer — Discovery & Design Sprint Lead. I ran discovery as a short, focused sprint against a single team of five people shipping content on a weekly cycle. We worked as a team of seven: alongside me, 2 information designers, 2 developers, 1 engineer and 1 project manager.
The client
Who they are, and the scale of what they were managing.
Patreon's video production team is a five-person operation creating content for multiple shows and platforms. Every week they produce episodes of Digital Spaghetti — a flagship YouTube series featuring creator interviews — plus a Patreon-exclusive full-length cut, vertical shorts for social platforms, recurring series like Cut by Cut and Shot by Shot, and content for the CEO's Instagram. All of it was managed through a single, sprawling Notion workspace. The team also moves about 50 pieces of camera equipment between San Francisco, Los Angeles and New York.
Client
Patreon — Video Production Team
Industry
B2B: Creator Economy / Media & Entertainment
Role
UX Researcher and Information Designer (Discovery & Design Sprint Lead)
Timeline
[NEEDS INPUT: timeline]
Methods
Workspace audit, Semi-structured interviews, Contextual inquiry, Workflow mapping, Iterative concept testing
How I researched it
Five methods, and what each one actually surfaced.
🔍
Workspace audit — Before any interview I went through the live workspace — the franchise → project → task → subtask nesting, the status fields, the episode template. Finding finished work still sitting at "Not Started" gave me specific, evidence-based questions instead of generic ones.
🔍
Semi-structured interviews — Five 1:1s of 30–45 minutes, covering every role on the team. I asked people to walk me through the last episode they shipped — chasing behaviour and decisions, never "what would you like us to build?"
🔍
Contextual inquiry — I asked each person to share their screen and do the work in front of me. This is where the truth lived: people described one process and then clicked through a different one. Observation caught what the interviews missed.
🔍
Workflow mapping in FigJam — Current and future state side by side, using a colour system for working steps, changes, evidence, handoffs and triggers. The rule was simple — nothing green ships without a grey behind it.
🔍
Iterative concept testing — Two rounds of wireframe review with six participants. Round one surfaced confusion about where Shorts belonged; round two split editing status from publication status. Testing early kept the build honest.
The discovery sprint
What it involved, and what came out of it.
I ran discovery as a short, focused sprint against one five-person team on a weekly shipping cycle. It produced current- and future-state workflow maps in FigJam, a workspace audit health report, and two rounds of concept testing with six participants that fed straight into the build. From there we designed a redesigned production pipeline, automated episode setup and deadline templating, streamlined V0 → V1 → V2 → Lock review cycles, personal "My Work" dashboards, a shorts publishing pipeline, an editor resourcing dashboard, an equipment tracker and a calendar sync.
Key finding and impact
The problem in one line, and the measured result after rollout.
💡
Key finding — The workflow had become so deeply nested and manual that the team stopped trusting it, and stopped using it.
📈
Impact — 87% less setup time (15 min → 2 min). 30+ tasks auto-generated per project. Status updates 3× (30% → 90%). 100% adoption across the team.
Let's work together
The fastest way to reach me is LinkedIn.
Connect on LinkedIn ↗
© 2026 Hasty Haghkhah
Designed in Figma
← All case studies
Patreon — Video Production Team
Patreon: Video Production Workflow
They loved Notion — but their system wasn't built to scale.
My role
What I was responsible for on this engagement.
UX Researcher and Information Designer — Discovery & Design Sprint Lead. I ran discovery as a short, focused sprint against a single team of five people shipping content on a weekly cycle. We worked as a team of seven: alongside me, 2 information designers, 2 developers, 1 engineer and 1 project manager.
The client
Who they are, and the scale of what they were managing.
Patreon's video production team is a five-person operation creating content for multiple shows and platforms. Every week they produce episodes of Digital Spaghetti — a flagship YouTube series featuring creator interviews — plus a Patreon-exclusive full-length cut, vertical shorts for social platforms, recurring series like Cut by Cut and Shot by Shot, and content for the CEO's Instagram. All of it was managed through a single, sprawling Notion workspace. The team also moves about 50 pieces of camera equipment between San Francisco, Los Angeles and New York.
Client
Patreon — Video Production Team
Industry
B2B: Creator Economy / Media & Entertainment
Role
UX Researcher and Information Designer (Discovery & Design Sprint Lead)
Timeline
2025
Methods
Workspace audit, Semi-structured interviews, Contextual inquiry, Workflow mapping, Iterative concept testing
How I researched it
Five methods, and what each one actually surfaced.
🔍
Workspace audit — Before any interview I went through the live workspace — the franchise → project → task → subtask nesting, the status fields, the episode template. Finding finished work still sitting at "Not Started" gave me specific, evidence-based questions instead of generic ones.
🔍
Semi-structured interviews — Five 1:1s of 30–45 minutes, covering every role on the team. I asked people to walk me through the last episode they shipped — chasing behaviour and decisions, never "what would you like us to build?"
🔍
Contextual inquiry — I asked each person to share their screen and do the work in front of me. This is where the truth lived: people described one process and then clicked through a different one. Observation caught what the interviews missed.
🔍
Workflow mapping in FigJam — Current and future state side by side, using a colour system for working steps, changes, evidence, handoffs and triggers. The rule was simple — nothing green ships without a grey behind it.
🔍
Iterative concept testing — Two rounds of wireframe review with six participants. Round one surfaced confusion about where Shorts belonged; round two split editing status from publication status. Testing early kept the build honest.
The discovery sprint
What it involved, and what came out of it.
I ran discovery as a short, focused sprint against one five-person team on a weekly shipping cycle. It produced current- and future-state workflow maps in FigJam, a workspace audit health report, and two rounds of concept testing with six participants that fed straight into the build. From there we designed a redesigned production pipeline, automated episode setup and deadline templating, streamlined V0 → V1 → V2 → Lock review cycles, personal "My Work" dashboards, a shorts publishing pipeline, an editor resourcing dashboard, an equipment tracker and a calendar sync.
Key finding and impact
The problem in one line, and the measured result after rollout.
💡
Key finding — The workflow had become so deeply nested and manual that the team stopped trusting it, and stopped using it.
📈
Impact — 87% less setup time (15 min → 2 min). 30+ tasks auto-generated per project. Status updates 3× (30% → 90%). 100% adoption across the team.
Let's work together
The fastest way to reach me is LinkedIn.
Connect on LinkedIn ↗
Site
Work
About
© 2026 Hasty Haghkhah
Designed in Figma