Design Work Breakdowns
AKA: Case Studies , Deep Dives
I document because production moves fast and lessons get lost.
Future-me needs to remember why we made these choices.
Future teams need to understand what worked.
And you need to see how I think.
How I solve design problems, iterate on systems, and ship games.
These aren't polished portfolio pieces—they're honest breakdowns that show mechanical analysis, iterative problem-solving, and the thinking behind shipped work.
The mess, the pivots, and what I learned.
Filter : Category
From 50 Steps to 5: Improving Scene Import Workflow
Life is Strange: Reunion | Designer Advocacy in Pipeline Development
The Challenge: Script import required 50+ manual steps per scene—creating hotspots, copying tags character-by-character, configuring data layers. Typos broke interactions. Missed steps prevented scenes from loading. Designers couldn't reach playable state fast enough to catch design issues when they were cheapest to fix.
My Role: Represented Design in D9Sequencer development. Documented pain points from production experience, provided weekly testing feedback, then validated the improved workflow by importing all 40 game scenes.
The Solution: Translated designer pain into feature requests—automated hotspot creation, grid placement, non-destructive test imports. Time saved shifted upstream to logic validation, ensuring cleaner handoffs to downstream teams.
Impact: 50+ steps became 5. One designer imported all 40 scenes—scope that would have been impractical before. Pipeline thinking isn't separate from design work. Sometimes improving the team's workflow is the most impactful design contribution you can make.