Values Collection Campaign Builder
Intro
In the world of insurance, ensuring accurate and up-to-date information is crucial for securing optimal coverage. This initiative focused on enabling insurance brokers to create Values Collection Campaigns—a streamlined process for gathering critical Schedule of Values (SOV) data. Brokers managing client locations worldwide can now assign campaigns to gather accurate information from key stakeholders. By simplifying the collection of up-to-date values, this solution ensures data integrity, enhances collaboration, and ultimately drives better outcomes for all parties involved.
As the lead UX designer for this initiative, I worked closely with my product manager and a team of engineers to bring the project to life. I spearheaded the entire design process, from research to final design, ensuring that the user experience addressed the needs of insurance brokers collecting Schedule of Values (SOV) data. Collaborating with actual users throughout the process, I gathered regular feedback on my design proposals to refine and optimize the solution. This user-centric approach ensured that the designs were not only functional, but also intuitive and effective in meeting the unique challenges of the insurance industry.
Business Goals
The primary business goal for this initiative was to replace our reliance on Origami, a white-labeled values collection tool that costs the company several million dollars annually. By creating our own in-house values collection workflow, we aimed to seamlessly transition users without disrupting their existing workflows or creating a jarring experience for those already familiar with Origami. Additionally, it was critical to design a solution that integrated smoothly into the context of our current application, ensuring a cohesive experience for users and aligning with the broader product ecosystem. This approach not only reduces long-term costs but also gives us greater control over the user experience and future enhancements.
Getting Started
The project kicked off with initial meetings with leadership to discuss the core requirements and establish a clear vision for the initiative. To better understand the landscape, I researched how competitors like AON and Origami approached values collection, analyzing their workflows and identifying opportunities for improvement. With these insights in hand, I began designing basic user flows and low-fidelity mockups in FigJam. This collaborative process allowed me to gather regular feedback from stakeholders, ensuring alignment with both business objectives and user needs as the foundation for the project took shape.
After two weeks of iteration, we finalized a proof of concept and determined where the workflow would integrate within the existing application. With the foundational direction set, I began designing high-fidelity mockups to create a realistic representation of the final product. Leveraging internal design system components allowed me to work efficiently and maintain consistency with the broader application. I shared my progress every few days, fostering regular feedback and open communication. This approach enabled internal brokers to suggest key features that would enhance the user experience, ensuring the solution met their needs. By sharing designs frequently, I kept everyone aligned and provided visibility into how the vision was being brought to life in real time.
Defining the Right Home for the Workflow
One of the key decisions we faced was determining where the values collection workflow would live within the existing application. Given the size, complexity, and importance of the workflow, we quickly realized it could not be effectively integrated into any of the current pages without compromising usability or clarity. After careful consideration, we decided that the workflow warranted its own dedicated page within the application. This approach provided the necessary space to accommodate the table, value selection process, and supporting features, while ensuring a clean, focused experience for users navigating this critical task. By giving the workflow its own space, we were able to design a solution that felt intentional, organized, and aligned with the scale of the functionality it delivered.
Testing Different Versions
I created low-fidelity user flows to map out the basic page structure and guide the user experience from start to finish. These early drafts allowed me to focus on core functionality and navigation while keeping the design flexible for iteration. By visualizing the entire workflow, I was able to quickly test ideas, gather feedback, and refine the experience to ensure it met user needs before moving into high-fidelity designs.
Early in the design process, we considered allowing users to select locations directly from the full SOV table. However, after consulting with our engineering team, we learned that this approach would place a heavy load on the backend, making it inefficient to implement. To address this challenge, we introduced a pre-filtering step that allows users to narrow down locations based on specific criteria before displaying them in a table. This approach significantly reduced backend strain while still providing users with an intuitive and efficient way to browse and select locations. By balancing performance constraints with user needs, we were able to streamline the workflow without compromising usability.
Campaigns Page
The requirements for this page focused on providing users with a centralized dashboard to manage campaigns effectively. It needed to display key details such as campaign name, Total Insured Value (TIV), assignee, date, and status in a clear and organized table format. Each campaign entry required an action menu for additional options, enabling quick updates or edits. Status indicators, such as "In Progress," "Needs Review," and "Complete," were specified to provide visual clarity on the progress of each campaign. Additionally, the page required a "Create Campaign" button for adding new campaigns, along with filtering and download options to support data management. Pagination was also included to handle large datasets, ensuring scalability as more campaigns are added over time.
Creating a Campaign
The campaign creation process was designed to be broken into five clear steps—Details, Values, Locations, Assignees, and Review—to guide users through each stage efficiently. The Details step prompts users to name the campaign and optionally set a threshold value. This threshold acts as a safeguard, requiring assignees to provide an explanation if their entered values meet or exceed the specified limit. This feature helps prevent errors that could impact data accuracy and ensures the information collected supports optimal coverage recommendations.
The Values step was designed to streamline the process of narrowing down location data while improving performance. In this step, users are required to select countries, business unit types, and occupancy types to filter and refine the list of locations that will appear in the next step. This approach significantly reduces backend strain by avoiding the need to load the entire locations table upfront. Additionally, users specify the values they want to request during this step. Since insurance brokers typically have a clear understanding of the data they need before creating a campaign, this step ensures the process is both efficient and aligned with their expectations.
The Locations step presents users with a filtered table of locations based on the criteria selected in the previous Values step. This pre-filtering ensures that only relevant locations are displayed, improving usability and performance. Users can select specific locations by checking the boxes in each row, allowing for flexible selection across multiple entries. To further streamline the process, a search bar is provided above the table, enabling users to quickly find a specific location without manually scanning through the entire list. This step balances simplicity and efficiency, making it easy for users to finalize their location selections.
The Assignees step is focused on assigning responsibility for updating the requested values. In this step, users are presented with a list of eligible assignees who have the authority to provide the necessary data. Users are required to select a single assignee from the list, ensuring clear ownership and accountability for completing the campaign. This step simplifies the assignment process and helps avoid confusion by making it clear who is responsible for submitting the requested values.
The final step in the campaign management system allows users to review all campaign details, such as values, locations, and assignees, ensuring accuracy before sending it out. Once confirmed, the campaign is added to the campaigns table with the status "In Progress."
Fulfilling The Request
When the assignee logs into the application, they will be greeted with a prominent banner notifying them that values have been requested. This alert is also available in the notifications feed in the top right corner, and they will receive an email about the request. By clicking on the alert, a modal opens, allowing the assignee to input the requested values for each location. The current value will also be displayed as a point of reference. A banner at the top of the modal shows the specified value threshold, alerting the assignee that if the threshold is exceeded, they will be required to provide an explanation for the change.
Confirming the Values
The campaign creator reviews and approves the values collection inputs when the campaign’s status is marked as "Pending Review" in the table. To begin the review process, the user selects "Review Values" from the action menu on the campaign’s table row. They can then review the value inputs location by location, along with any comments that were added if the value threshold was met. From this modal, the user can either approve the inputs or request edits. If edits are requested, the user selects the values that need to be adjusted and must provide a note explaining the reason for the edit request.
Handling Edits Requests
When assignees fulfill edit requests, the flow is similar to the original values collection process. Upon receiving the edit request, the assignee is notified and can access a modal where they will see both the current value and the previously inputted value for reference. Additionally, the modal includes the note from the campaign creator explaining the reason for the edit request. The assignee can then make the necessary adjustments to the values and submit the updated inputs for review.
Delivery
After two weeks of iteration, we finalized a proof of concept and determined where the workflow would integrate within the existing application. With the foundational direction set, I began designing high-fidelity mockups to create a realistic representation of the final product. Leveraging internal design system components allowed me to work efficiently and maintain consistency with the broader application. I shared my progress every few days, fostering regular feedback and open communication. This approach enabled internal brokers to suggest key features that would enhance the user experience, ensuring the solution met their needs. By sharing designs frequently, I kept everyone aligned and provided visibility into how the vision was being brought to life in real time.
Conclusion
I’m incredibly proud of the work I contributed to this initiative and grateful for the collaborative efforts of the engineering team, product managers, and brokers who worked closely with me throughout the process. Their feedback and support were invaluable in shaping a solution that aligns with user needs and business goals. While this feature has not yet been built, it is currently slated for development in Q1 of 2025. I’m excited to see this work come to life and confident it will deliver significant value to the organization and its users.