The gap between what was built and what was designed

Every sprint, the same rework problem. I reframed it as a scoped product concept.

Year2026
IndustryDeveloper tools
Duration2 weeks to scope

Problem

Work kept drifting from the design and the specs, and nobody noticed until testing. A table shipped without the sorting and filtering a customer had asked for. Colours and icons appeared that weren't in the design system.

2–3

tickets came back every sprint

5–8 h

lost per sprint to catching, explaining, redoing and re-testing

~1 year

of watching the same problem repeat

2 weeks

to scope the concept that could fix it

I was the designer, but I also filled the product manager gap: writing user stories, holding customer requests and shaping the build. I often tested key flows myself because I had the full context. That double role made the gap impossible to ignore.

Pretty much every sprint, a few tickets came back because what got built didn't match what was specced - and it usually surfaced in testing, after the work was already 'done'.
Sacha M.
QA at Nolea

Solution

Better handoff docs, more QA and extra sync meetings were all tried. None of them stuck, because they asked people to be more careful, while the mismatches came from deadline pressure.

Before merge

A mismatch is a comment

On a pull request it is cheap to raise, cheap to fix and nobody has to re-test.

After merge

A mismatch is a ticket

It costs a loop of reporting, explaining, redoing and re-testing, every single sprint.

The shift: stop trying to make people more careful and change when mismatches get caught. One automatic check right before merge compares what was built against what was intended.

MVP

The goal was to test whether a merge-time check changes how the team works. When a pull request opens, it is linked to its Jira ticket and checked for three things.

1

Elements

Is a required UI element present or missing?

2

Flow

Is each step of the flow there?

3

Layout

Does the layout roughly match the design?

Aligned → allow Partially aligned → warn Not aligned → block

Left out on purpose: AI judgement of code against design, and pixel-perfect comparison. I wanted to learn first whether a simple gate changes behaviour at all.

Design

A check only helps if people trust it and act on it. The report lives on the pull request and reads in seconds, with a compact status in the merge box and a detailed comment with the findings.

Principle 1

Hierarchy

Status first, then the most severe finding, then the next action.

Principle 2

Trust

Findings are specific and tied to the user story, so engineers act on them instead of dismissing them.

Principle 3

Actionability

The next step is clear in every state.

Atlas alignment report on a pull request: a not aligned status and a high severity finding

Overrides: a blocked merge can be overridden with a short reason. That avoids resentment and workarounds, and the logged reasons show where the rules are too strict or missing context. It is how the system would learn.

Validation

Atlas was never built. It came from a problem the team lived with for months and was scoped into a product plan. The core bet: catching a mismatch before merge is cheaper than after.

Fewer tickets back each sprint Fewer clarification meetings Less redo and re-test time A steady stream of overrides

That last signal would mean the rules are wrong, so it counts as a metric too.

What it catches

Clear misses

A missing element or a missing step in the flow.

What it misses

Subtle problems

A table can contain every required feature and still be built wrong. I accepted that, to test the gate before investing in something smarter.

Let's work together!

Kristina Sarieva · Product Designer Bulgaria · Open to remote