Steady's mission is to increase the earnings of American workers. As a part of fulfilling that mission, a project was initiated to enable payments to be made to customers that qualify for basic universal income programs.

That project has three parts to it. The first is to manage the members that qualify, the second is to facilitate and manage payments and the third is to provide data to enable a further analysis to understand the target customer and the impact the UBI payments are making.

My involvement was in three parts, however, the main focus --and this case study refers to the second, facilitate and manage payments

The product team desired to deliver the MVP as fast as possible and the team could iterate and improve features of the project based on usage data.

As a result, we decided to proceed with a discovery design sprint. This meant that daily, we coordinated workshops with the client.

As a lead designer, my main task was to coordinate and deliver daily design artifacts [user personas, user flows, and others]. These artifacts were discussed by the rest of the product team. After each meeting, based on the team's feedback I had to revisit and iterate, improving the deliverables daily.

The deliverable flow was Personas-> Information Architecture -> User Flows (& Admin) -> Lo-fi Wireframes for crucial user flow

As mentioned these should be delivered and iterated within a week. In the context of the design discovery sprint. Following this week, more detailed wireframes would be delivered based on the agreed-upon user flows.

Personas were based on actual user needs. Users of the platform were interviewed on how they use the platform, what other software they use, what are the main points of the existing offline processing of payments, and what are the things they consider as unique selling propositions (USPs) of the App.

As mentioned numerous times information architecture is essential, especially for complicated products for example e-commerce, financial or healthcare platforms, etc.

This is crucial to enable the app to scale and breathe as business needs evolve and, sometimes pivot.

User flows are an essential step in a human-centered design approach. The team took care to lean and refine user flows since these would serve as a high-level map for the wireframe screens that needed to be delivered.

User flows were shared and tested with users to make sure the flows respect their priorities and improve the way they work. Putting the users in the center was essential because we found "holes" in producing costs. [image of high-level user flows] [Image of only on user flow complete]

Wireframes were used to align the team on specific interactions, sharing a common vision. Wireframes were also shared with the developers, to assist them in their estimates.

The design system respected the branding and existing Design Guidelines. But special care was taken on table interactions. TABLES were important in this project. Multiple table interactions were designed and intuitive additions were included to assist the users in spotting information fast. Filters, sorting options, and special care for currency tables are few among the considerations for improving a solid table user experience

The impact the project caused was huge. Pareto says that 20% of causes affect 80% of results. The deliverable surpassed expectations minimizing by 85% the time users spent on the payment tasks the solution handled. And not only that feedback was "this is one of the most beautiful tools we have, but is not only easy to use is also so beautiful environment