saas

OVERVIEW

Design a platform for the Saas user.

The goal of this project was to design a high-definition user experience that could break down complex information into simple, digestible user interfaces.

ROLE

Product Designer
Product Strategy, User Research, Interaction, Visual design, Prototyping & Testing, Pitching

2022

Group-3912

BACKGROUND

Like many project in BOOM, divided into teams, I was the only product designer on this project.
I worked closely with the Product Manager on my team and several Frontenders and Backenders Engineers.
I joined BOOM as a product designer two and a half years ago year ago as one of 2 designers in a company of over 30 engineers and 3 product managers. I support design across every aspect of our business and am responsible for leading UX and UI across key parts of the application side of the platform, both client side, internal employees, and content creator.
During these years I have experienced great growth, with some key achievements that I have listed below:

- Implemented a design process. Organize discovery meetings with the product manager in order to investigate the problem by helping us through wireframes and user research.
- Creation of a design kit. This helped maintain design consistency across the many sections of the platform.
- Establishing a design system. This has helped the Engineering and Product teams to understand how and why we choose to implement certain components over others.
- Working with the engineering team. Organizing standup, discovery, demo and spint planning.

Group-3913

PROBLEM STATEMENT

Before this project, platform access was provided only for clients and our content creators. In the first case a user account was created directly from BOOM for clients by giving them access in the platform only for photoshoot order, while for content creators there was a selection process at the end of which an onbording gave access to another platform. 
This project involves the management of the entire Saas platform, for all paid or free subscription customers through the self-sign flow in. The development had to take into consideration:

- Role of users with subscription
- Inviting member users and roles
- Upgrade, downgrade and cancellation of subscription
- Manage of payment and Payment method
- Manage Plan end limits

And next:
Understanding which parts of the client platform they would not see and which they would

GOAL

elenco1

Design clear and intuitive plan management saas platform, including upgrade, downgrade, limits management and cancellation.

elenco2

Manage the monetisation of the saas platform, including the purchase of units

elenco3

Manage roles in the platform for both worksite and production-only customers (orders) and new users

elenco4

Improving retention and acquisition

APPROACH

Study competitors and the established management of saas platforms. Respect the present information architecture, always evaluating the numerous user actions and possibilities. Apply an inclusive and cognitively clear approach to indicate steps, actions and information.

Group-3914

RESEARCH METHOD

word

MOCKUPS

I tested the mockups using a combination of:

- Internal critiques for initial feedback
- Discovery with the engineering team for immediate feedback and feedback on the complexity of the Cta and the many possibilities for the user (upgrade, downgrade, cancellation)
I find that making mockups too simple will not draw the best feedback from users, but also from the engineering team.
On the other hand, mockups too polished do not offer room for sharing ideas and do not encourage users to look for flaws and engineers to go deeper into the discussion. I also ensured that copy was consistent and strong to maintain clear communication for all.

Group-3915-1

PROTOTYPING AND DEVELOPMENT

The project was developed in different steps. The first MVP was the development of a basic dashboard, with all the CTAs conceived, but without yet any real autonomy of management for the user. In each subsequent release, we thought of adding a piece to complete the project in its entirety. To give a measure of all the steps, the image below represents just one of them

proto-saas

LEARNING

In this project, there were many variables handled. From managing roles and permissions (GDPR), to plan constraints, payment and updating billing info. In addition, monetisation of the platform was an important part of all the discovery. The complexity was a lot, but I am very proud of how we worked as a team. We probably could have simplified some modalities, such as the Upgrade modalities, and we probably could have postponed the downgrade development.