PYGMALIONLoading the portfolio
The Thinker · Auguste RodinA study in perspective

02 / Shimo Forms

Connecting form creation, collection, and analysis.

Two perspectives. One continuous workflow.

Explore the design
DisciplineUX & interaction design
FocusWorkflows, states & components
PRODUCT DESIGN / CASE STUDYScroll to change perspective

01 — Understanding the task

One form, two user journeys.

A form connects the person asking with the person answering.

Creators need to build, design, publish, and review responses. Respondents need to access, understand, complete, and submit a form. I mapped these journeys separately, then examined how they connect at publishing and submission.

My role: UX design. I led journey mapping, core workflow redesign, settings architecture, and question components, working with product to define the goals.

THE TWO SIDES OF A FORMFIG. 01

Creator

Organize the questions
  1. Create
  2. Design
  3. Publish
  4. Review responses
Questions go outAnswers come back

Respondent

Provide the answers
  1. Access
  2. Understand
  3. Complete
  4. Submit
Distinguish each group’s tasks before defining the entry points. Journey redrawn from the original design.

02 — Making the rules visible

Know where you are. Know what is live.

Keep the workflow and publishing state visible.

I organized design, collection, and analysis into clear stages, giving question editing and the overall workflow distinct places. Collection status and unpublished-change indicators help creators distinguish current edits from the version respondents can see.

FORM EDITOR / ORIGINAL DESIGNFIG. 02
The main workflow stays above the editor. Questions and question types each have their own space.

A CRITICAL DISTINCTION

Editing does not mean published.

The decision helps creators understand whether a change they are making already affects respondents.

Collecting status in the original designThe collection state stays visible
AA persistent stage navigationBAn explicit unpublished-changes message

03 — Building a shared structure

Different settings. A familiar structure.

SETTINGS / ORIGINAL DESIGNFIG. 03

A place for every setting.

Settings use navigation on the left and content on the right. Question cards and controls for ratings, cascading selections, and dates share interaction patterns, helping people carry their understanding across tasks.

One navigation model, across different tasks.

Consistency, down to the question.

Keep controls and feedback consistent while accommodating different question types.

Exported directly from Figma. Hover or keyboard focus to pause; select any study to see the original.

04 — Connecting the next step

Submission is a step, not the end.

Information becomes useful when it can move forward.

I developed proposals connecting form responses to spreadsheet analysis and onward paths after submission, positioning forms within a broader work process.

PROPOSED FLOW / ILLUSTRATIONFIG. 04
  1. Form responses

    Gather structured answers

  2. Spreadsheet analysis

    Organize and understand

  3. Onward work

    Continue across products

A proposal for the relationship between products, not a screenshot of a shipped integration.

05 — Deliverables & reflection

Design the handoff, too.

People need to complete an action and understand who will use the result and what happens next.

The redesign brought together both user journeys, core workflows, publishing states, settings architecture, and question components, with supporting proposals for analysis and cross-product transitions.

DESIGN DELIVERABLES

  • Dual-role journey map
  • Core workflow & publishing states
  • Settings architecture & question components
  • Analysis & cross-product proposals

Presented as design work and a case review.

Continue exploring

Project Sheet

From individual answers to connected tasks.

Back to selected work