GrandPad

/

2026

Designing Out Defects

Designing Out Defects

Turning six months of product defects into design standards and a bug-focused design review, so whole categories of bugs get caught before code.

A checkers game between Patricia and Franklin shown on both devices: Patricia's GrandPad tablet reads 'Waiting for Franklin…' while Franklin's phone reads 'It's your turn!'

Client

GrandPad

Year

2026

My role

Led the analysis, standards, and review process

The problem

Our platform spans seven products across tablet, mobile, and web, and defects kept surfacing late in QA or after release. Fixing them one at a time worked, but the same kinds of problems kept coming back. I wanted to know how many of them started in the design, and whether we could catch them there instead.

What I did

I reviewed every defect logged across the platform over six months and grouped them into recurring patterns. Many traced back to states the designs never defined: empty or missing data, hidden fields that still ran their logic, screens that stayed stale until a refresh, interruptions like a call arriving mid-task, long or translated text, and multi-step flows with no defined exit paths.

I turned those patterns into design standards, so every design now accounts for those states before handoff, and introduced a bug-focused design review where the team checks new work against them. I shared the findings with engineering as well, since many of the same patterns pointed to gaps in testing.

What changed

The design team adopted the standards and the review as part of how we work, and the analysis opened a new working conversation with engineering about preventing defects instead of only fixing them. It's still early, and the next step is tracking whether these categories of bugs decline.

Outcome

New design standards and a bug-focused review, adopted by the whole design team.