Tetris Live
Case study focused on UX/UI decisions, system constraints, and execution details.
At a glance
Replace this block with the tightest possible positioning statement for the project.
Overview
What this was, why it mattered, and what success looked like.
Problem
State the core constraint, tension, or failure mode you were fixing. One paragraph max.
Goal
Define what “better” meant in measurable or observable terms. Keep it concrete.
Approach
The decisions you made and why. Focus on tradeoffs, not fluff.
1) Constraints
List the hard constraints. Platform, tech, cadence, stakeholders, timelines, pipelines.
2) Key design moves
Bullet the moves that actually changed the outcome. Avoid vague words like “improved.”
- Reduced cognitive load by restructuring navigation into fewer primary actions.
- Normalized layout rhythm and spacing for scanability and speed.
- Clarified progression and state feedback so players always know what changed.
3) Implementation notes
Keep it “real.” What did you ship, what did you cut, what did you protect.
Outcomes
Results, learnings, and what you would do next if you owned another iteration.
Impact
Add 1 to 3 concrete outcomes. If you have no metrics, describe observable behavior change.
What worked
Name the highest leverage decision. The one that made everything else easier.
Next
If you had 2 more weeks, what would you attack first and why.
Gallery
Replace, reorder, or expand these. Uses your existing work card styles.