Savelev Nikita
E-mailLinkedInTelegramDownload CV
Savelev Nikita
E-mailLinkedInTelegramDownload CV

Design review before release

Designers didn’t see builds before release, and tasks often shipped looking off. I found the people who could change that, and design review became a step in the team’s workflow.

My role

Design Lead

I suggested the review, found the people to set it up with and agreed how it would work.

Result

The app shipped cleaner: layout problems and unfinished details were caught before users saw them.

Tasks shipped without a design check. In my last team at X5 we worked on the catalog in several apps at once. Designers didn’t get builds before release, and tasks often shipped looking off or not quite finished.

I suggested a design review, but at first it didn’t get support.

How I set it up

  1. Find support

    I asked our new design director to help me find the person who handled builds.

  2. Get builds

    That person and I agreed that designers would get builds in TestFlight before release.

  3. Add a status

    With the person who set up sprint tasks, I added a Design review status. A task couldn’t move on without it.

  4. Review in two days

    Designers checked builds alongside QA, so releases didn’t wait. If they found a problem, the task went back to QA.

What changed. Every task designers worked on got a design check before it reached users. Problems that used to slip into the app were fixed before release, and what we shipped was cleaner.

Next case

In Store — a space for the physical store

I suggested giving the physical store its own space in the Perekrestok app, then designed the MVP when it became a priority.