AI-Powered Forms for Medicine, Taxes, & More

Google Cloud Virtual Hackathon (2022)
Building a serverless web application that fills out forms through AI-powered speech recognition.
User Icon
Role: UX, UI, Branding
Window Icon
Product: Web Application
Mockups

What is inForm?

AI-powered assistant converting your speech to forms using Google Cloud Run & Functions

inForm Prototype

Software

Figma Icon

Figma

Maze Icon

Maze

Scope & Team

Calendar Icon

3 Weeks

Three (3)

Developers

Two (2)

Designers

Challenge

Build a creative, enjoyable, and valuable solution for optimizing a resource-intensive business. Use Cloud Run, Cloud Functions, and Workflows.

Outcome

We built a serverless web application, reimagining the workflow of multi-input forms.

Mockups

the challenge

Google Cloud Virtual Hackathon

Teaming up with 3 developers (Santiago Uriarte, Brandon Huynh, Daniel Vu) and 1 designer (Tiffany Trinh), we joined the Google Cloud Easy as Pie Serverless Hackathon, aiming to foster skill growth and collaborative innovation together.

Objective: Build and deploy serverless apps with Cloud Run, Cloud Functions, and Workflows.

discovery

Brainstorming Business Issues

Prompt: "What’s your most sticky, time-consuming, budget-draining business function? Imagine that hot mess transformed into a sleek, simple process."

Our team brainstormed together to decide which business problem we wanted to tackle. We decided to address the pain points of forms using speech-to-text to:

  • Help increase workflow efficiency

  • Address the documentation needs of customers

  • Create a scalable SaaS product applicable to several industries

Let’s get to research!

surveys

Asking the Core Questions

We surveyed 30 participants about their recent experiences with forms and speech-to-text. Our research goals were to identify pain points with forms. We were also curious about the value of speech-to-text and applicable markets.

  • What is the current experience like with forms?

  • How often do users use speech-to-text?

  • Where do users typically use forms?

Insights

60%

say filling out forms are tedious

67%

rarely or never use speech recognition

53%

say speech recognition is convenient

Common Pain Points

Rotate Icon

Repetitive

Pencil Icon

Writing Burdens

Hourglass Icon

Time-Consuming

Common Use Cases

Government Icon

Government

Medicine Icon

Healthcare

Backpack Icon

Education

An opportunity to expand speech recognition usage

Although 67% of participants rarely or never use speech-to-text, 53% found it convenient. This reveals an opportunity to expand speech recognition usage.

the mvp

Defining the MVP

Due to time constraints, we needed to focus on high-priority features. We crossed out lower priority features, making our main features of the app to be:

  • Logging in as an existing user

  • Creating a SMART form

  • Accessing the transcribed form

  • Creating a template

  • Editing a form

  • Downloading a completed form

User Flow

inForm user flow

User FlowAfter logging in, the user can select a template to create a SMART form. The app then uses AI to transcribe the users' speech in real-time. Once the form has processed, users can view, edit, and download the transcribed form.

wireframes

Collaborative Ideation

Using Figma, we created low-fidelity wireframes to depict potential designs for the app. We aimed the designs to be:

Learnable

Familiar and learnable since this was not an ordinary transcription app.

Responsive

Optimized for mobile device to allow for flexible usage wherever, whenever.

Simple

Simple for ease of use and navigation when performing the MVP tasks.

usability testing

Putting the Prototype to the Test

Using Maze, we conducted 4 remote, moderated and 10 remote, unmoderated usability tests. Our goals were to assess user navigation and ease.

Tasks

Select a Template

Create a SMART Form

View SMART Form

Usability Metrics

Wand Icon

Success Rate

Warning Icon

Misclick Rate

Hourglass Icon

Duration

Quotes

Win #1

"Nothing really confused me, it was pretty straightforward."

Pain Point #1

"I thought it was a list, but I wasn’t sure if I had to click anywhere else before...it seemed like an unclickable list."

Win #2

"Anything where you purchase at a counter...or anything if they want to take note what the customer or buyer needs, this would be useful."

Pain Point #2

"...The way it was laid out and when it gave me the time accessed and when the file was opened, it kind of confused me because I wasn’t sure if this was a template or a file that I made."

Based on feedback, we realized that users needed more context and clarification. Refinements done to address these main concerns are as shown:

Iterations 1

Templates ScreenCards replaced list items to better differentiate between templates and forms.

Iterations 2

Forms ScreenDesign improvements when creating a new form on the "Forms" screen.

branding

inForm

Intended to be a scalable SaaS product, the branding is modern, clean, and professional.

inForm UI Kit
Mockups

outcomes

Impacts & Reflections

I enjoyed building a demo product with this team. This experience taught me how to work with others in an agile environment. A few thoughts:

Increased Usability by 10%

The app usability improved by 10% based on task success & duration, test exits, and misclicks.

If I had more time:

  • I would have explored an onboarding flow to guide users on what the app is about and its main features.

  • Explored motion design and animation for the audio waves to increase accessibility.

What I learned:

  • Attending weekly stand-ups and reviews helped us identify roadblocks, expectations, and new learnings.

  • Bouncing off ideas with one another during brainstorming sessions helped spur creative solutions.

other work