Merilin Ekzarkova

Work

Built a portal and tracker for partner feedback and QA

Head of Product and Design · a health app · 2026 · partner:

Sketch of a feedback portal: a form to submit an issue, and a log of how often each change was requested New issue Type screenshot Submit Request logwhat, how often, when Wordingasked 3×Layoutasked 1×Wordingasked 2×
Sketch with made-up numbers, not the real screen.

Problem

Partner feedback arrived as slide decks. Each slide was a screenshot and a note.

Each deck was reviewed in a meeting, with the whole team going through it slide by slide to decide what to do.about an hour, every time

There was no single log of requests, so it was hard to see whether something had been asked before or what had been decided.this again?

Solution

A portal. The partner submits each issue online and picks its type. Feedback now arrives one item at a time, in the same shape, with the screenshot attached.

A tracker. Every request is logged: what was asked, how often and when.

An AI agent runs each round. It sorts the submissions, checks whether a request has come in before, and drafts the tickets for the developers and the replies to the partner. I read, edit, then send.

What changed

← All work