Ossai.

Back.

Craft

Experience

About

Contact

Ossai.

Back.

Craft

Experience

About

Contact

Ossai.

Back.

Craft

Experience

About

Contact

Orbit

2023

An Automated experience for programs.

My TEAM MEMBERS?

Anthony (Software engineer)

Tomisin (Product manager and designer)

Basile (Software engineer)

Me (Product Designer)

mY Role and summary

Following the implementation of programs in Orbit, we looked for new ways users managed their communities through the program pipeline. I played a significant role on the team in creating an automation system that helped with the interaction experience between the community managers and their users, from checking in on inactive members to congratulating members to switching statuses, thereby triggering connected Webhooks and emails. This further created new usage path ways for programs

Following the implementation of programs in Orbit, we looked for new ways users managed their communities through the program pipeline. I played a significant role on the team in creating an automation system that helped with the interaction experience between the community managers and their users, from checking in on inactive members to congratulating members to switching statuses, thereby triggering connected Webhooks and emails. This further created new usage path ways for programs

Challenge, purpose and definition.

A hassle in THE CURRENT process

On following the release of programs, we set out to get feedback from our users on how they felt there. We got really interesting insights into what they thought of the feature

On following the release of programs, we set out to get feedback from our users on how they felt there. We got really interesting insights into what they thought of the feature

Key feedback and requests

  • Being able to take different actions on the transition between different states, like New to Onboarding or rejected and more.

  • These actions can range from ending emails to webhooks.

  • Some said they explicitly wanted to automate their processes.

It’s settled then, we create an automative feature

It’s settled then, we create an automative feature

Why? The users constantly requested and it was already in the road map.

Why? The users constantly requested and it was already in the road map.

user expectation

So what do we want to achieve with this automation?

So what do we want to achieve with this automation?

  • Users want to take certain automated actions when their members transition from one status to another. These actions include Webhooks and Sending emails

  • Users want to be able to send automated emails when a member isn’t progressing in their program. For example, If a member does not complete onboarding after xxx period.

What are other people doing? -We are not reinventing the WHEEL

What are other people doing? -We are not reinventing the WHEEL

We started by looking at what people in the industry have done, but remember, we wanted to keep it as simple and as uncomplicated as possible. We looked at:

  • Hub spot

  • Common Room

  • Hello Monday.

How did we design this

First we mapped out the process

We started by asking a lot of questions on how this would go, and we created a strong formula /rule of how automation was executed.

  • Do we want to allow users to set multiple actions?

  • Do we want to allow users to set multiple triggers?

  • Do we want people to have specific criteria attached to these triggers?

  • Can users stop automation?

When a user doesn’t do or does an action, then give a consequence

Users should be able to set a trigger action

When triggered, take the action specified.

Once again, we wanted to get this process right, and we created a flow that reflected the question and answered with the following factors: time to execution and vision for the business and future of the tool.

Once again, we wanted to get this process right, and we created a flow that reflected the question and answered with the following factors: time to execution and vision for the business and future of the tool.

ITERATIONS AND TRIALS

We started with wireframes and iteration, which did not give the right experience and the right balance between cognitive overload, progressive guidance and seamless fluidity.

We started with wireframes and iteration, which did not give the right experience and the right balance between cognitive overload, progressive guidance and seamless fluidity.

We settled on this design

Here's the prototype

We settled on this design as it conveyed the right experience we wanted to give to our users. It was also a blend and start of a new design language with the old design system. In turn, we update this as we went through this process,

Some of the components

Impact and learning

Impact

By focusing on simplicity and user needs, we successfully implemented a feature that significantly improved workflow efficiency and user satisfaction.

  • Automation significantly reduced the time and effort required for manual tasks, leading to enhanced productivity.

  • Improved User Experience: The automation feature provided users with the tools to manage their workflows more effectively and focus on higher-value tasks.

What did I learn from this?

I learnt that automation can be a double-edged sword, it can be a burden and a tool for optimising workflow depending on how natural and seamlessly it integrates while simultaneously skipping processes.

Previous case study

An Onboarding experience for a new direction.

Next case study

Community Search