muunai case study cover

muunai

muunai is a startup in Munich building an AI documentation tool for doctors. A doctor records a patient conversation, and the app generates a structured medical report for editing and finalization.

I was one of three designers on a two-month engagement. I owned the redesign of the report page, where doctors review what the AI produced, and the patient info page. I also built the component library that the product lacked.

Product Designer
Oct 2024 — Jan 2025
Karin Oberreiter, Özge Belgül
Interaction Design, Design Systems, Prototyping
Walkthrough of the redesigned muunai report page

First-time users could not tell what the controls on the report page did.

My teammates ran task-based sessions with three medical students. Each student reviewed a generated report, edited it, changed its structure, and copied or sent it. Students stood in for doctors, partly because doctors were hard to schedule. None of them had seen the app before, which matched the first-run experience we were redesigning.

  • An icon that misled

    The eye icon looked like a privacy blur but hid empty sections.

  • Unlabeled send options

    One student hovered over every icon in the corner before choosing one.

  • AI without context

    Students were never told the report was AI generated, so Smart Edit options had no clear purpose.

The original report screen, annotated with the three failures: an eye icon read as a privacy blur but hiding empty fields, unlabeled icons in the top corner, and Smart Edit rewrite options with no sign the text was AI written

The redesign needed a clear layout and the parts to build it.

Layout first

I sketched two layouts, one with the report on the right and one with it in the center. The center version matched the founders’ vision for the product, so it became the wireframe. Recording sat on the left, the checklist on the right, and the report in between.

Two layout explorations: a hand sketch with the report on the right, and the centered version that became the wireframe, with recording on the left and the checklist on the right

From toolbar to panel

I explored Smart Edit as a collapsible toolbar above each section, so the options sat beside the text they changed. The founders preferred a dedicated right panel, which now opens from the section header. The checklist moved left to make room.

Smart Edit explored as a collapsible toolbar above a report section, beside the final version where one toolbar option opens the Smart Edit panel on the right

A library to build on

muunai had a palette and typography but no components. I gathered them into a style guide and defined states for icons and buttons. I then built the components the redesign relied on, including section headers, the Smart Edit panel, and form fields.

The muunai style guide: type scale, colour palette, and the icon and button states defined for each
The components built for the redesign: toggles, section headers, the Smart Edit panel, and the report form fields

The report page now follows the order doctors work in.

A doctor reviews the report, edits it, then finalizes it. The layout guides them through those steps from top to bottom.

  • Sections you can scan

    Each section opens with a shaded header. A doctor can find the part they need without reading the whole report.

  • Smart Edit on demand

    Smart Edit opens from the section a doctor wants to change. When closed, the report has the screen to itself.

  • Labels, not icons

    Save and send became labeled actions at the end of the report. They sit where the doctor finishes reading.

The report page before and after: the original screen beside the redesign, which sets recording and the checklist on the left, the report in the center under shaded section headers, and labeled Save and Send actions at the end
The redesigned report page with Smart Edit closed, where the report has the screen to itself, and with Smart Edit open in a panel on the right beside the section it edits