Vyond - Seamless Collaboration with User Groups

Vyond is a California-based animated video creation platform

As company account grows, collaboration will slow down and content complexity will increase. User Group is an enterprise-only feature that aims to facilitate collaboration among team members. Its self-defining feature can improve efficiency on workflow and support multi-layered content structure in large accounts.

Use Group gives contributors a clear messages about the relationship between content and organization.

As company account grows, collaboration will slow down and content complexity will increase. User Group is an enterprise-only feature that aims to facilitate collaboration among team members. Its self-defining feature can improve efficiency on workflow and support multi-layered content structure in large accounts.

Use Group gives contributors a clear messages about the relationship between content and organization.

As company account grows, collaboration will slow down and content complexity will increase. User Group is an enterprise-only feature that aims to facilitate collaboration among team members. Its self-defining feature can improve efficiency on workflow and support multi-layered content structure in large accounts.

Use Group gives contributors a clear messages about the relationship between content and organization.

I served as the lead UX designer tasked with a new feature development from end to end, which including stages of discovery, inception, validation and eventually implementation.
I served as the lead UX designer tasked with a new feature development from end to end, which including stages of discovery, inception, validation and eventually implementation.

Role

Lead UX Designer

Duty

UX Design

User Research

Tool

Google Slides

Adobe XD

Lucidspark

Team

Lead UX Designer (me)

UI Designer

UX Designer from another team

Product Manager

Engineers*4

Project Goals

This project aims to improve workflow efficiency and support multi-layered content structure in large accounts, eventually extend market penetration. The success metric of this project is measured by the adoption rate of group feature and customer satisfaction score.

This project aims to improve workflow efficiency and support multi-layered content structure in large accounts, eventually extend market penetration. The success metric of this project is measured by the adoption rate of group feature and customer satisfaction score.

🎯 Improve collaboration efficiency

🎯 Improve collaboration efficiency

🎯 Support multi-layered content structure

🎯 Support multi-layered content structure

🎯 Support multi-layered content structure

Back

Back

Discovery

Inception

Validation

Implementation

Benchmarking

I did benchmarking products with large user account including Lucidchart, Google Suite, Jira, MS 365 and Slack to understand what's the potential risk and opportunity for the user group feature.

I did benchmarking products with large user account including Lucidchart, Google Suite, Jira, MS 365 and Slack to understand what's the potential risk and opportunity for the user group feature.

I did benchmarking products with large user account including Lucidchart, Google Suite, Jira, MS 365 and Slack to understand what's the potential risk and opportunity for the user group feature.

1st User Interview: Animators*2 & Information Security Manager

In discovery stage, my objectives is to understand user's workflow, and the potential threats on assets sharing. I conducted interviews with internal user (animators) and information security manager and ask details regarding the workflow, pain points, needs and their concerns.

“

Single sharing is easy, because you don't have to change the sharing setting and the link. But it is not the case for sharing to multiple people.

Animator J

“

Single sharing is easy, because you don't have to change the sharing setting and the link. But it is not the case for sharing to multiple people.

Animator J

“

I need to type in their email one by one when sharing Vyond video to multiple people. It is time-consuming and sometimes causing mistakes.

Animator P

“

I need to type in their email one by one when sharing Vyond video to multiple people. It is time-consuming and sometimes causing mistakes.

Animator P

“

If there is a group feature, I prefer assigning managers to manage groups, but not everyone.

Information Security Manager

“

If there is a group feature, I prefer assigning managers to manage groups, but not everyone.

Information Security Manager

“

Usually I share my video on slack or just Vyond link to others for reviewing.

Animator J & P

“

Usually I share my video on slack or just Vyond link to others for reviewing.

Animator J & P

“

Sometimes I don't share the original Vyond video because I don't want others to edit it accidentally.

Animator J & P

“

Sometimes I don't share the original Vyond video because I don't want others to edit it accidentally.

Animator J & P

“

Customized settings for each group like G suite is convenient.

Information Security Manager

“

Customized settings for each group like G suite is convenient.

Information Security Manager

Insights can be summarized as:

  1. It is common to share video to multiple group of people by video link or downloading it from the platform
  2. Current sharing feature is time-consuming and causing mistakes

  3. A "Manager" role should be included in user group feature for customized privileges

2nd User Interview: Current enterprise users, Sales Team

The insights of 2nd user interview have been conducted as the following:

“

In production, they work individually or with others. Sometimes they need to share with other teams in different subscriptions

User A

“

In production, they work individually or with others. Sometimes they need to share with other teams in different subscriptions

User A

“

Sometimes reviewers are not Vyond users. So they tend to share video manually.

Sales Team Member C

“

Sometimes reviewers are not Vyond users. So they tend to share video manually.

Sales Team Member C

“

It's a bit messy as we try to store everything in one centralized place for the account.

User F

“

It's a bit messy as we try to store everything in one centralized place for the account.

User F

Insights can be summarized as:

  1. Different level of access is vital to various users or even non-Vyond users
  2. Sharing feature should consider the ability to manipulate assets within account
Mental models (Admins & Members)

The mental models show how admins and members assiocate with the platform by their needs and major tasks.


Blue block: goal / Red blocks: actions / Yellow blocks: opportunities of user group feature

User journey

I analyzed the user journeys of different roles (account owner, admin, and team member) and categorized them based on the activities they perform. The key activities where the group feature becomes relevant are onboarding new members and sharing videos or assets on the platform.

1st Prototype testing

This prototype testing is conducted via usertesting.com and aimed for understanding the common use case and pain point of creating user group and sharing content to multiple users. And investigate what/how much value group feature can bring to users. Interview guide will also be provided for asking measurable question during the interview.

This prototype testing is conducted via usertesting.com and aimed for understanding the common use case and pain point of creating user group and sharing content to multiple users. And investigate what/how much value group feature can bring to users. Interview guide will also be provided for asking measurable question during the interview.

Solution Plan -> Solution Pitch

  • 🛠️Technical Investigation Meeting

  • 🤜🤛Product Team Sync Up

  • 📅Weekly Design Team Meeting

At this stage, I outlined several potential solutions in a solution plan. The plan broke down each key journey, evaluating the solutions based on design effort, impact areas, and the workflow adjustments required at the enterprise level. Technical investigation meetings, team weekly sync up etc. were also held to assess feasibility and keep everyone posted. Finally, I consolidated the findings into a pitch deck and reviewed the possible solutions with the team.

At this stage, I outlined several potential solutions in a solution plan. The plan broke down each key journey, evaluating the solutions based on design effort, impact areas, and the workflow adjustments required at the enterprise level. Technical investigation meetings, team weekly sync up etc. were also held to assess feasibility and keep everyone posted. Finally, I consolidated the findings into a pitch deck and reviewed the possible solutions with the team.

2nd Prototype testing

This prototype testing is conducted via usertesting.com and aimed for understanding the common use case and pain point of creating user group and sharing content to multiple users. And investigate what/how much value group feature can bring to users. Interview guide will also be provided for asking measurable question during the interview.

This prototype testing is conducted via usertesting.com and aimed for understanding the common use case and pain point of creating user group and sharing content to multiple users. And investigate what/how much value group feature can bring to users. Interview guide will also be provided for asking measurable question during the interview.

Testing prototype and interview guide for Admin role to test the create group action.

Testing prototype and interview guide for Member role to test the sharing via group feature.

Revised User journey

After the pitch and the second round of user testing, the revised user journey demonstrated improvements in the workflow by reducing the number of steps significantly. It also highlighted potential risks that I need to consider as the group feature continues to develop.

After the pitch and the second round of user testing, the revised user journey demonstrated improvements in the workflow by reducing the number of steps significantly. It also highlighted potential risks that I need to consider as the group feature continues to develop.

Functional Specification (Documentation)

During the implementation stage, I created a "Functional Specification" document that captured the story and scope, use cases, design patterns, interactions, error handling, and other essential details. This document served as a reference for developers to ensure the design requirements were accurately implemented. It also provided a foundation for the QA team to create test cases and validate the feature’s feasibility in the staging environment.

Feature Demo

This feature demo showcase how group feature can be utilized among enterprise accounts.

How was it?

0
0
Enterprise user agrees that group feature making sharing more convenient
0.0
0.0
Adoption rate of group feature

After feature release 1 month where a group at least have 5+ users

Adoption rate of group feature

After feature release 1 month where a group at least have 5+ users

Adoption rate of group feature

After feature release 1 month where a group at least have 5+ users

0.00
0.00
Customer satisfaction score

Create a free website with Framer, the website builder loved by startups, designers and agencies.