mh studio Book a free call

● Process

A design process you can see every week.

Five phases, clear deliverables and a weekly rhythm with async updates, so you always know what is happening and why.

Phases

Five phases, one clear path.

01 · Week 1

Discover

We align on the business goal before touching pixels.

What happens

  • ✓Stakeholder interviews
  • ✓User interviews or support-ticket review
  • ✓Benchmark of competing products
  • ✓Success metrics agreed in writing

You receive

Research summaryProblem statementSuccess metrics

Your engineers get

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

Weekly rhythm

How a week with me looks.

Monday kick-off

A 15-minute call inside your core hours to agree the week's goals.

Updates by short video

Loom walkthroughs and annotated files, so nobody waits for a meeting.

Thursday demo

Clickable progress every week. You comment, I adjust.

Design QA

Built screens checked against the approved design before they ship.

Working hours

Time zones

Full overlap with European working hours, and about 3 to 4 hours with US Eastern mornings. Calls go inside your core hours.

Async cadence

Written first

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.

Your tools

I plug into your stack

Slack or Teams, Jira or Linear, Notion or Confluence, Figma and GitHub. Your files, your tracker, your channels.

Design leadership

Beyond screens: the rituals I run.

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.

01

Design critique

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.

02

Decision log

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.

03

Stakeholder reviews

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.

04

Working with engineers

I join sprint planning, size design work in your tracker, pair on tricky states and review UI pull requests against the design before merge.

Template · Critique agenda

30 minutes, five parts

  1. 01
    ContextStage, goal and what is already fixed.
    2 min
  2. 02
    The questionWhat kind of feedback is needed today.
    1 min
  3. 03
    Silent reviewComments go straight into the file.
    5 min
  4. 04
    DiscussionFeedback tied to the goal and the user.
    15 min
  5. 05
    ActionsOwner and next step, logged.
    5 min
Sample decision log entry · Corridor conceptDEC-007

How transfers are confirmed

Options
Tap to send, a confirm screen, or hold to send
Chose
Hold to send
Why
Stops accidental sends without adding another screen.
Cost accepted
A little slower for people who send often.
Revisit if
Repeat senders start dropping off at this step.
Read the Corridor case study

Have a product in mind? Let's talk.

  1. 01 30-minute call
  2. 02 Scope and quote in 48h
  3. 03 First screens in week one
Book a free call → mhdigitalstudio.com