Translating Complex Questionnaire Logic into Intuitive UI

Background

Each screening type had a different target user and questionnaire structure.

KBSMC runs three types of health screenings: preventive, comprehensive, and corporate. Preventive checkups are largely legally mandated, covering general adults and employees with a basic questionnaire. Comprehensive checkups exist to catch disease early, which means a much deeper, more detailed questionnaire for each individual. Corporate checkups are company-paid and built around employees, with the questionnaire itself changing shape depending on the contract. Three different audiences, three different questionnaire structures, and my job was to fold them all into one coherent system.

Three screening types, three different questionnaire structures — one system had to hold all of them.

Finding the Flow

A flow designed to reduce fatigue, one question at a time.

The questionnaire was built from seven question categories and four levels of conditional logic; branch it all out and you get 100+ possible paths. Show users that complexity directly, and they're liable to give up before finishing. I redesigned the flow to feel like a simple conversation instead, showing just one category's questions per screen.

100+ possible paths, experienced as a single, calm conversation.

IA & Design Pattern

A visual hierarchy you can actually follow.

I gave the sub-questions in each category a hierarchy and structured them as a tree: a top-level question, sub-questions beneath it, and follow-up questions beneath those, capped at four levels deep to keep the questionnaire from getting too complex. To make that hierarchy recognizable at a glance, I used a different button design for each level.

Question hierarchy as a tree, capped at four levels deep.

A different component design at each depth, so the hierarchy reads at a glance.

Admin

The admin screen is organized around edit permissions.

I split the admin's information into two groups: what PMs and developers can freely edit (question text, branching logic, answer options, warnings), and what stays locked because it's synced from the hospital's back-office (clinical codes, exam records). That distinction is clear on screen, so admin users always know what they can and can't touch while building a questionnaire.

The permission boundary — what the back-office owns, and what operators can edit.

Final Delivery

Designing a Real-Time Validation Admin

I designed a backend admin to manage the user-facing questionnaire, with a focus on operational efficiency and developer velocity.

SaaS

By integrating a live mobile preview on the right, PMs can instantly validate how changes apply to the end-user interface.

Mobile

Impact

Stronger business results, and a smoother process to get there.

This project secured a key enterprise partnership, streamlined the cross-functional development cycle, and delivered measurable business results.

Takeaway

I learned how to solve complexity through design.

Being involved end-to-end, from product design through design QA, gave me especially valuable experience in the two areas below.