Making complex advice
easier to manage.
Auda is software that helps financial advisers manage client information, documents and casework. I defined how the product should behave and designed the workflows around that work.
- Context
- Financial advice & operations
- My role
- Product direction & workflow design
The current stage, the next adviser action and the remaining work sit together. Stage sign-off stays visible beneath the task list.
Captured 21 October 2026
The thinking behind the workflow.
Explore three product decisions in the real adviser workspace. Select a step to see how the experience supports the work.
The case and its place in the journey remain visible.
Know where the work stands.
The client, current stage and journey sit together at the top of the case. An adviser can understand the context before opening a task.
The task sits in the context of the case and its journey.
Make the work that needs attention obvious.
The task list highlights what needs the adviser next. Here, affordability needs assessing before the case can move from Analysis & research to Recommendation.
Review and progression remain visible in the workflow.
Keep progression an explicit decision.
The sign-off area sits alongside the work. It shows the current stage’s position and gives the adviser an explicit way to continue the journey.
When the work is complex, the experience matters more.
Financial advice connects client information, documents, decisions, compliance requirements and operational administration. Those relationships can be difficult to follow when the work is fragmented.
I defined how the product should behave: what people need to understand, how work should flow and where review belongs in a case journey.
Make the next step clear, while keeping the context that makes it meaningful.
Design around the work people need to do.
I defined functionality, designed operational workflows, specified user interactions and shaped how information is presented.
The focus is on the relationships between information and action. What belongs together? What needs to be visible at the point of a decision? Where should a review happen?
Product direction, grounded in practical implementation.
My contribution includes challenging processes, defining functional requirements, reviewing proposed behaviour and coordinating implementation through AI-assisted development.
Engineering implementation and architectural decisions have involved significant AI assistance. My focus is on connecting the business need, the product behaviour and the user experience.
This case study describes my product contribution. Current product availability and capabilities are confirmed through Auda.
Visit AudaLet’s talk about
working together.
A product to shape, a process to improve or a role in your team. Tell me what you have in mind.
Let’s talk