Rate Sage Leader Form
Overview
As part of this new startup’s acquisition task, I was asked to develop an insurance quote form, email template, and other advertising assets all within their new brand guidelines. These were to be introduced into their new website design that just launched.
As a fresh face on the insurance market, Evan, Rate Sage’s CEO understood how nimble they needed to be with beginning to bring in revenue. Evan and I coordinated this project around my schedule with Minerva’s work and I was able to hand off all final deliverables within the month since this project was briefed.
Timeline
1 month
Teammates
Engineering Department, CEO, Project Management
Tools
Figma, Slack, Zoom, Confluence, GitHub
The Flow
This was the first portal I had ever created from start to finish. Creating an organized user flow was the first step in understanding how we are walking customers through this quoting experience.
Here you can see how I broke up the questions into categories so that people could reasonably expect what’s next and allow us to introduce more personal questions like “What is your address?” without scaring people away.
The Design System
Given the tight timeline, I imported components from ANT library and made custom adjustments to fit our product’s brand identity. This, alongside some developer notes, made exporting these pre-built UI elements a breeze.
Communication
There were three key actions that allowed everyone to hop from step to step and wrap this up with a bow in time. As a core piece of my attitude of a designer, I never want to leave anyone in the dark about what’s next.
Ask Questions
Knowledge is power and lack of it usually leads to blockage on projects. I made sure to reach out to Evan, my main point of contact, when I needed clarification or his opinion on the overall vision. Commenting questions in Figma to address in checkpoint meetings helped define specific topics needing more discussion.
Plan Checkpoints
A predetermined time to discuss features ensured everyone was on the same page and set a respectful cadence of when the next iterations could be delivered.
Labels and Notes
Keeping a clean Figma document with systematic labeling meant easier onboarding in the future and lower maintenance. The engineers were not familiar with using Figma, so I found that creating tool tips along side the wireframes added a layer of static clarity when creating those components.