The research was ready before the product was
The interviews, personas, and competitor analysis were done before we could change anything, so the design phase started with answers already in hand.
Role
Lead UX Designer
Tools
Figma, Minimals UI, Miro
Timeline
Research 2024–2025, design began August 2026
Status
Wireframes complete, user testing planned for 2027
Responsibilities
Member interviews, personas, competitor analysis, wireframes, interactive prototype
Corporate One is a corporate credit union, so our members are credit unions. One of the products we offer them is CU Corporate RTP, which they use to send immediate payments to the companies that keep their branches running, like payroll, landscaping, and utilities.
The product runs on a platform we contract from a third party, so for years we could sell and support it but couldn’t change how it works. In 2026 we started building our own version inside a larger project called the unified system, which is planned to launch in 2027.
I’m the lead UX designer on the project, and I came into the design phase with two rounds of member interviews, three personas, and a competitor analysis already done. I designed both parts of the product, the send experience and Payments Management, where members approve, cancel, or fix payments that have already been submitted.
When a member sends an immediate payment today, they log into Juniper Payments, a third-party platform with our logo across the top. Real-time payments are new, but the interface they’re built into is much older. Juniper had moved on to a newer system called JuniFunds and wasn’t going to update ours, so our leadership team decided to build our own experience in-house.
Sending one payment takes three separate pages, and there’s no progress indicator, so someone on the first page has no way to know how much is left.
Templates only exist inside the send flow. To create one, a member has to fill out an entire payment and reach the final overview, where the save buttons sit in the same row as the button that sends the money. Creating a template and sending a payment are two different tasks, so we wanted to separate them.
Juniper’s send payment experience
We interviewed seven members in 2024 and six more in 2025. We talked to the people who use the product every day, the executives who decide whether to buy it, and members who went through the sales process and chose not to buy.
Three personas came out of the research: a CFO who wants to move away from mailed checks and the fraud that comes with them, an electronic services staff member who sends the payments and has trouble with templates, and a CEO who evaluated the product and didn’t buy.
The three CU Corporate RTP personas.
The CEO who didn’t buy gave us some of the most useful feedback. She wanted use cases, testimonials from other credit unions, and information on fraud mitigation, and she couldn’t tell which of our products needed a core integration. Most of that can’t be solved with wireframes, but it’s the reason I put support links, training links, and tooltips inside the product.
Fraud came up often, since a real-time payment can’t be reversed. Fraud prevention is sold separately and isn’t part of this build, so that feedback is something our sales team can speak to.
I compared CU Corporate RTP with US Bank, JuniFunds, and Alacriti using demos of each system. I looked at areas like sending a payment, templates, alerts, bulk capabilities, fees, support, and approvals, and for each one I wrote up what we should and shouldn’t do so the product team could make decisions from it.
"Sending Payment" experience comparison from competitor analysis.
US Bank fits a whole payment on one screen, lets users search for account and routing numbers, and has tooltips plus support and training links in the main navigation. Our system has none of those.
JuniFunds, the newer system Juniper moved on to, uses a wizard that shows where you are and what’s left. That visible step list is what I brought into our design.
Templates comparison from the competitor analysis.
Templates were weak almost everywhere. None of the other systems let members create and manage their own templates, and ours was better than most but still not good, so templates were a clear place where we could do better.
I pulled the interview findings and the competitor analysis into a single set of opportunities and took them to the product and development team so we could agree on what was feasible for the first build.
Bulk send, built-in fraud prevention, and fee transparency are outside the scope of the first release, so they’re documented for later. Our team also discussed scheduled payments. I advocated for the feature based on our research, but only a few members mentioned it, and as a nice-to-have, so we couldn’t justify the development resources for the MVP. Bulk approval ended up on that list too, which I cover in Payments Management.
The new product is part of the unified system, which brings the separate applications members reach through Members Only into one place. I’m designing inside the navigation and visual style our senior UX designer created for it, and we chose Minimals UI as our component library after moving off OutSystems, so we start with consistent, documented components.
The new send experience, from the interactive prototype: creating a template, sending from it, and entering a payment manually.
Sending a payment takes three steps: choose a template or enter the payment manually, fill in the details, then review and confirm. The step list stays on screen the whole time. Templates are chosen at the start from a searchable list that shows the amount on each one, and a Create New Template button at the top means members can make a template without sending a payment.
Templates can be viewed and deleted, but not edited. Allowing edits would add another place where routing number validation has to happen on the back end, so leaving it out of this release was a compromise I made. I did push for delete, so a member isn’t stuck with a template that has an error in it.
Choosing a template pre-fills the details step, and the amount stays editable since it’s the thing most likely to change from month to month. The review step shows every detail as read-only text, and the submit button is the most prominent thing on the screen. In the old system, the button that sends money sat in a row next to two template buttons.
The wizard also has to work for other payment types. Wires are next, and they need more information than an immediate payment, so I designed the steps and layout to expand without rebuilding the flow.
Payments Management is where approvers work through the payments waiting on them and submitters fix the ones that were sent back. It took a lot more back and forth with the team than the send experience did.
Our product owner wanted approvers to be able to process payments in bulk, which matched what we heard in research. It took four versions to figure out what that should look like.
I suggested a checkbox on each row, so approving payments would work like sorting email. You check the payments you want, then choose one action. It wasn’t finished when we reviewed it with the team.
Our product owner wanted a queue instead, where each payment could get a different action. That is where the challenge came in, since people would need to add a note to each action, review the details as they went, and submit everything at the end.
The tabs still let approvers go straight to the payments that need them, and the badges cover one of our research opportunities, making it obvious when something needs action.
Both parts are designed and built as an interactive prototype, and wires are the next payment type we’re taking on. None of it has been tested with members yet. User testing is planned for 2027, and I expect some of these decisions to change. The template flow is the one I’ll watch most closely, since it’s the furthest from how members work today.
The interviews, personas, and competitor analysis were done before we could change anything, so the design phase started with answers already in hand.
A credit union that chose not to buy asked questions our current users had already moved past, and that’s why help and training are built into the product.
I’d rather ship templates members can create and delete than hold the whole feature for an edit path.
Once stakeholders could see the wireframes, opportunities for improvements were easier for them to recognize, and they spotted obstacles they hadn’t thought of before. Reviewing bulk processing is how they realized we couldn’t allow editing a payment in bulk mode.
I’m happy to walk through the research, the constraints, and how Payments Management changed with the team’s feedback.
© 2026 Michelle Magruder