01 Overview
Bringing structure to complex workflows
My work on Conservation focused on helping Sola employees and insurance agents navigate information-heavy tasks. The interface needed to accommodate detailed reports, validation results, simulation settings, and supporting records.
I developed a component library alongside screen designs for these workflows. This connected decisions about individual controls such as buttons, menus, and table columns to the larger experience of completing a task.
The design challenge was to organize dense information into clear levels: what users needed to understand immediately, what required closer inspection, and which actions should be available next.
02 Requirements & Workflow Discovery
Translating team requirements into interface decisions
Team-provided requirements and workflow diagrams helped me understand the information each task depended on, the decisions users needed to make, and the different paths a process could take.
Three needs shaped the interface:
Make validation results actionable
A report could contain multiple checks, with failures affecting different rows and falling into different error categories. Users needed to see what failed, inspect the details, and rerun checks after a correction. This informed the relationship between summary statuses and detailed validation views.
Support different simulation setups
The simulation requirements included creating a new portfolio and working with an existing portfolio through automatic or manual additions. The configuration interface needed to accommodate these choices while keeping the setup understandable.
Help users return to previous work
Simulation titles, parameters, saved results, and report statuses were important parts of the workflows. The interface needed to support both starting a task and returning to information later.

03 Component Library
Creating consistency across the product
I developed a reusable component library to support Conservation’s different screens. The library covered common actions, navigation, inputs, and data presentation within a shared dark interface.
Buttons, menus, search fields, switches, and segmented controls provided repeatable ways to interact with the product. Their variations helped distinguish different actions and interaction states.
Table columns and chart components supported the information-heavy layouts. Reusable structures gave the screens a consistent foundation while accommodating different types of content.
Developing the library alongside the screens helped connect component decisions to practical needs. Each element needed to work within a larger task, whether that meant finding a report, changing a setting, or reviewing a result.

04 Reporting & Validation
Moving from an overview to the details that need attention
The reporting workflow involved generating reports, checking their contents, resolving errors, and preparing them for submission. My screen designs organized this process through an overview of report activity and more focused validation views.
The reporting page brought together summary metrics, validation statuses, and a report table. This gave users a starting point for reviewing the current reporting period and identifying items that needed attention.
Making errors easier to investigate
The detailed validation view separated the overall result from the individual failures. Users could inspect checks, review error categories, and compare expected information with the values in the report.
Rerun actions supported the next step after a correction. I wanted the interface to make the relationship between identifying an issue, investigating it, and checking the updated information clear.




05 Simulations
Connecting setup, review, and results
The simulation workflow needed to accommodate several ways of configuring a portfolio while providing a clear route to reviewing the output.
Start or revisit a simulation
The dashboard organized previous simulations through recent items and collections. Cards surfaced identifying information and provided an entry point into saved work.
Configure the scenario
The setup screens grouped simulation information, portfolio options, and configuration inputs within a panel beside the map. This kept the controls and geographic context visible together.
Review the output
The results screens introduced summary metrics before offering more detailed views, including percentile charts and state comparisons. This created a progression from an initial overview to closer analysis.




06 Supporting Screens
Extending the interface across related tasks
Additional screens explored claims, losses, and document review. These brought the same visual approach into layouts with different information needs.
The claims and loss screens combined summary information with detailed records, while the document viewer brought a report into a dedicated review environment.
Together, these designs show how the component library could support a range of internal tasks through consistent navigation, controls, and information hierarchy.


07 Reflection
Connecting the system to the screens
The work brought together a documented component library and a connected set of interface designs for Conservation. Building both helped me consider consistency at two levels: how individual elements behave and how a complete workflow is organized.
The reporting and simulation work reinforced the importance of understanding a process before refining its presentation. Requirements about failed checks, configuration options, and saved results directly affected what needed to appear on each screen.
What I would evaluate next
My next step would be to evaluate the designs with employees and agents using representative tasks: finding a failed validation, understanding the error, configuring a simulation, and returning to a previous result.
I would use those sessions to assess whether the labels, information hierarchy, and next actions were clear, then refine the components and screens together.

