Ossai.

Back.

Craft

Experience

About

Contact

Ossai.

Back.

Craft

Experience

About

Contact

Ossai.

Back.

Craft

Experience

About

Contact

Ossai.

Back.

Craft

Experience

About

Contact

Orbit

2023

An Onboarding experience for a new direction on Orbit.

My TEAM MEMBERS?

Anthony (Software engineer)

Tomisin (Product manager and designer)

Me (Product Designer)

mY Role and summary

Orbit is a platform that lets people manage communities by getting insight and more. This was my first project after joining the team 😬 and the aim was to redesign a new onboarding that steered Orbit in the new direction of Programs and increased activation(Programs are designed to provide users with a 'subsequent steps' guide regarding the analytics and insights they receive). This design led to a more streamlined onboarding and an increased activation of current users of Orbit

Orbit is a platform that lets people manage communities by getting insight and more. This was my first project after joining the team 😬 and the aim was to redesign a new onboarding that steered Orbit in the new direction of Programs and increased activation(Programs are designed to provide users with a 'subsequent steps' guide regarding the analytics and insights they receive). This design led to a more streamlined onboarding and an increased activation of current users of Orbit

Challenge, purpose and definition.

A NEW VENTURE

Orbit enables organisations and individuals to manage communities (mostly dev communities), by providing analytics from linked integrations such as YouTube, Github, Discord, Reddit, and more. While it presently works as a tool for passive observation, we planned to transition Orbit into a platform for active engagement. This leads to the question, “After deducing key insights from my community, what’s next?”

Orbit enables organisations and individuals to manage communities (mostly dev communities), by providing analytics from linked integrations such as YouTube, Github, Discord, Reddit, and more. While it presently works as a tool for passive observation, we planned to transition Orbit into a platform for active engagement. This leads to the question, “After deducing key insights from my community, what’s next?”

So we created Programs.

What are programs

Through applications, individuals can initiate engagement within their communities via champions, donations, and UGC schemes among others. This positions Orbit as a tool for “action”. It essentially transforms Orbit into an “active” platform. Nevertheless, what are the challenge?

Through applications, individuals can initiate engagement within their communities via champions, donations, and UGC schemes among others. This positions Orbit as a tool for “action”. It essentially transforms Orbit into an “active” platform. Nevertheless, what are the challenge?

The starting point dosen’t fit the new narrative

The starting point dosen’t fit the new narrative

Well, onboarding is heavily focused on connecting users' data to get started, which doesn't fit this new narrative.

Well, onboarding is heavily focused on connecting users' data to get started, which doesn't fit this new narrative.

Also ,Yikes!! Activation is low.

Also ,Yikes!! Activation is low.

While pushing this narrative, we realised that the activation and adoption numbers on orbit have increased for a couple of months. We checked the numbers, and it seems we had lots of users that didn’t add integration at all

While pushing this narrative, we realised that the activation and adoption numbers on orbit have increased for a couple of months. We checked the numbers, and it seems we had lots of users that didn’t add integration at all

New questions arise

  • How do we Introduce programs to this new Audience??

  • How do we Introduce programs to this new Audience??

  • How do we increase activation for Users?

  • How do we increase activation for Users?

What do we do?

So We conducted a design audit

Yes, we see where the users are coming from. So many break points and less fluidity

  • Alright?? I have no integration what’s next?

  • Okay, I have connected an integration and it’s taking time what do I do while i wait?

It appears people get STUCK on getting started

Now, we what? we cook!

We decided to re-do the onboarding and see if this eases the experience

We decided to re-do the onboarding and see if this eases the experience

We decided to re-do the onboarding and see if this eases the experience

With the problem in mind we created the goal of revamping the onboarding process to proactively guide users with setting up their workspace, starting up their first programs, and taking more actionable steps toward their community goals.

With this approach, New Users:

  • Should be able to start a program as part of their onboarding process.

  • Should get a guided experience to setting up their first program

  • Should see an updated in-app first time experience (e.g empty state, CTAs)

  • Do not need to connect data sources as part of starting a program.

  • For users invited to join an existing workspace; They should get a new onboarding experience and walkthrough similar to an existing user.

With the problem in mind we created the goal of revamping the onboarding process to proactively guide users with setting up their workspace, starting up their first programs, and taking more actionable steps toward their community goals.

With this approach, New Users:

  • Should be able to start a program as part of their onboarding process.

  • Should get a guided experience to setting up their first program

  • Should see an updated in-app first time experience (e.g empty state, CTAs)

  • Do not need to connect data sources as part of starting a program.

  • For users invited to join an existing workspace; They should get a new onboarding experience and walkthrough similar to an existing user.

How did we design this

First we mapped out the process

The onboarding process is quite delicate as it involves a lot of integration, and these leave room for possible drop-off points, so while designing this flow, we had to holistically come up with the flow. This included involving every use case of the user type and then including helper experiences (Email and User guide ref triggers) to the different points to make the experience one.

The onboarding process is quite delicate as it involves a lot of integration, and these leave room for possible drop-off points, so while designing this flow, we had to holistically come up with the flow. This included involving every use case of the user type and then including helper experiences (Email and User guide ref triggers) to the different points to make the experience one.

WE worked on a lot of iterations

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

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

We settled on this design

Prototype

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

Some of the components

Done

Impact and learning

Impact

  • We were able to create a new look for the product.

  • The onboarding was streamlined, direct and less ambiguous.

What did I learn from this?

We then realised that the adoption did not stem from the user experience of the application, but it came from the use case of Programs. We learnt from users in the later cause of this change that we needed to focus on using programs to track the impact of events and in communities across teams and community managers rather than just tracking activities and engaging community members.

Next case study

An Automated experience for programs.