Kickoff
We learned about their product vision, multiple user segments, and project milestones.
Understand the traditional process
We made a deep dive into the claims submission process and identified ways to optimize workflow.
Defined key information
We defined key information in the process like statuses, state changes, required/optional form fields, and intricate legal logic to move us in the right direction.
Collaborate every step of the way
We brought in the client every step of the way to make sure we captured the happy path as well as edge cases. Adhering to an approved claim form, we developed a web application that is functional and easy to navigate and covers a wide-range of claim filing scenarios.
Release planning
We collaborated with our client to build a backlog and plan the the first release of the software together.
System architecture
We defined structures and schemas that would support the complex workflows and storage needs of the submission process.
Style and design foundations
We explored and refined an interface style that represented all parties equally.
Build and conquer
We designed, coded, and thoroughly tested many different permutations of the workflows. The client was also testing the interface and providing feedback that we could add to our backlog and sprints.
Getting buy-in from stakeholders
We provided a demo site for our client to present the interface to their stakeholders for feedback.
Prepare for launch
We finalized all of the small details and prepared a launch in time for the initial claims filing date set by the client.
Refinements and future enhancements
Once the app was complete and in the hands of real users, we continued to work with our client to enhance the experience where needed. Despite how it may seem, software is never done.
