Bringing Design Into Code Review for Keep Me Safe
How our designers and engineers review safety features together before each release.
Process
Why design belongs in the review
A safety feature fails when a person cannot understand it under stress. Code can be correct and still leave someone unsure which button to press during an alert.
For that reason, a design reviewer now reads each change alongside the engineer, with the same weight given to wording, timing, and layout.
What reviewers check
Each pull request that touches an alert or check-in screen is reviewed against a short checklist that the whole team wrote together.
- Labels state the action in plain words
- Timers show remaining time without flashing
- Error states offer a next step
Workflow
From sketch to release
Week 1
Shared sketch
Designers and engineers mark up the flow together before any code is written.
Week 2
Paired review
The design reviewer and the code reviewer sign off on the same pull request.
Week 3
Field check
Testers in volunteer households use the build and report anything confusing.
Notes
Open questions
The safety lead decides on wording that affects emergency actions. Designers propose and engineers verify that the text fits the interface.
Paired review adds about one day to safety changes. We accept that cost because it has reduced confusing alerts reported after release.