01Overview
Overview
Trust administrators manage financial responsibilities for beneficiaries, often across pooled trusts and other complicated account structures. A large part of that work involves disbursements. The process has to be accurate because administrators are working with real people's money. But accuracy does not mean the workflow should require unnecessary repetition.
Create Draft Disbursements focused on making it easier for trust administrators to prepare disbursement information while maintaining control over the final financial action.
02Understanding the Workflow
Creating information vs. executing a transaction
Before designing the feature, I worked with product partners and trust administrators to understand how disbursements were actually being handled. The important distinction was between creating information and executing a financial transaction.
Administrators often knew that a payment or disbursement needed to be prepared before every final detail was ready for submission. The product needed a way to preserve that work without forcing someone to either finish everything immediately or start over later.
03The Opportunity
What does "draft" mean in a financial product?
Draft functionality sounds simple until it enters a financial product. What does "draft" mean? Which fields are required? Which information can be incomplete? Who is allowed to edit it? When does it become a real transaction? What happens when someone returns later? How do we make sure a draft cannot accidentally be mistaken for a submitted disbursement? Those questions shaped the experience.
04Designing the Draft Workflow
Making financial state unambiguous
The workflow allowed administrators to create a disbursement and save progress before completing the final action. The interface had to clearly distinguish between in-progress information, required financial information, saved drafts, and completed or submitted actions.
Visual hierarchy and language became extremely important because the system could not leave the financial state ambiguous.
05Designing for Pooled Trust Administration
One workflow, repeated across many accounts
Pooled trusts add another layer of complexity because administrators may be responsible for many beneficiary accounts. The feature therefore could not be designed as though someone were managing a single personal account. Efficiency matters differently when the same workflow may be repeated across many people during a workday.
We looked for opportunities to reduce unnecessary re-entry while preserving the controls administrators needed to verify each disbursement.
06Research & Collaboration
Where the friction actually lived
I worked with administrators and product stakeholders throughout the project. Those conversations were particularly useful because the people using the product understood where operational friction lived in ways that were difficult to see from the interface alone.
A workflow might appear reasonable when viewed once in a prototype. Repeating that workflow dozens of times can reveal entirely different problems. That understanding influenced field organization, workflow order, terminology, and draft behavior.
07Balancing Speed With Safety
Useful friction vs. repetitive friction
One of the biggest UX challenges in financial products is that "faster" is not always automatically better. Removing a step can save time. It can also remove an important opportunity to verify information. The goal was not to eliminate friction indiscriminately. It was to separate useful friction from repetitive friction.
Useful friction protects someone from making an expensive mistake. Repetitive friction makes them type or navigate through something again without improving the quality of the decision.
08What I Learned
Not every step should be cut
Create Draft Disbursements changed how I think about efficiency. Good enterprise design is not about turning every five-step process into a three-step process. Sometimes all five steps matter.
The better question is: does every action the user takes contribute to completing or verifying the work? When the answer is no, that is where the design opportunity usually lives.