An early read on technical limits, APIs and data the design depends on.
Curious what testing looks like? See a sample bug report and the severity scale
A 15-minute call inside your core hours to agree the week's goals.
Loom walkthroughs and annotated files, so nobody waits for a meeting.
Clickable progress every week. You comment, I adjust.
Built screens checked against the approved design before they ship.
Full overlap with European working hours, and about 3 to 4 hours with US Eastern mornings. Calls go inside your core hours.
A written update at the end of each working day: what moved, what is blocked, what I need. Decisions go in the decision log, so nobody has to have been in the room.
Slack or Teams, Jira or Linear, Notion or Confluence, Figma and GitHub. Your files, your tracker, your channels.
Leading design is mostly habits: how feedback is given, how decisions are recorded and how the team stays aligned. These are the ones I bring to every team.
A weekly 30-minute critique. The presenter states the stage and the question, people comment in the file first, and feedback is tied to the goal, not to taste. Actions are written down before we leave.
Every product decision gets a short record: options, what we chose, why, the cost we accepted and when we would revisit it. New people catch up by reading, not by asking.
At each phase gate, a pre-read goes out a day ahead, then a review with product, engineering and the founders. Decisions and open questions are written up the same day.
I join sprint planning, size design work in your tracker, pair on tricky states and review UI pull requests against the design before merge.