Thoughts #webapp #UX #SaaS
Design a knowledge management system from 0 to 1
Thoughts is a collaborative knowledge management system which enables individuals in an organization to collectively create, edit, share, access internal documentations across company boundaries to achieve its business objectives.
Contribution
UX design & product strategy
Company
Teambition
Website
thoughts.teambition.com
From the very beginning, I took on the role of the main UX designer for this product, guiding it from the conceptual stage to its launch. Throughout this journey, I led the feature ideation, facilitated design iterations, and fostered collaboration across multiple teams, including design, development, marketing, sales, and customer success.
Project Summary
During my tenure at the company, our primary offering was Teambition, a cloud-based project management and collaboration platform. As part of our expansion plans, we identified a promising business opportunity in the form of a collaborative knowledge management system that would address the existing functional gaps in our main product while entering a relatively untapped market.
Target Users
Our early-stage business strategy focused on implementing an upselling approach to promote the purchase of our primary product, Teambition, while introducing and highlighting the benefits of our collaborative knowledge management platform. As a result, our strategy aimed to target the same user base as Teambition, which consisted of small to medium-sized business professional in four major industries, including tech companies, advertisement agencies, law firms, and construction companies.
Young professionals from small to medium-sized companies who collaboratively engage in writing, reading, and sharing internal team documentation.
Competitors
User Goal
Our user goal is to provide features that are specifically designed for collaborative knowledge management scenarios for small to medium-business users.
Business Goal
Our business goal is to upsell our services to our existing customer base from our main product Teambition, to increase revenue.
Core Loop
The core loop of an editor role consist with three major steps: create/edit a document, organize documents to make them easier to be looked up, and share documents to people in need.
Feature Map
Based on the editor’s core loop on our product, their feature requests comprise from their needs for editing, organizing and sharing documents. This feature map explains what to build to make the MVP work.
Key Design
While numerous design details were considered, I will highlight the pivotal ones that resonated most with our target customers.
Feature overview
Edit
The available toolbar options changes dynamically based on the selection of the content, ensuring users always have the most handy option in front, and only shows up when users need it.
Content-aware
Formatting Toolbar
Share
Permission control allows the administrators implement confidential protocols as well as giving team members the flexibility to access the document.
Document-sharing with
Permission Control
Role control
grant different permissions by assigning roles.
Permission hierarchy inherit
members automatically obtain relevant permissions through the role they have in the parent document without extra permission request to administrators.
Public link and password
invite members outside of the organization to view or edit the document and comply with local laws where document-sharing service could not provide direct link of viewing the document.
Organize
Nested-page navigation helps the users to organized the documentations and makes it easier for others to look up them.
Organize Documentations with
Nested-page Navigation
Drag & Drop
Organize the document tree by drag and drop.
Collapsable Panel
Users can hide the navigation and focus on the writing.
Create Child-document with One Click
A shortcut to create a child-document, and member will inherit permissions without further configurations.
Synchronized Sorting
All the members will see the same sorting to ensure a consistent reading experience across the organization.
Results
After six months of dedicated effort, the product was successfully rolled out internally for testing purposes. We were on the verge of meeting our success metrics, as the product effectively served as a reliable platform for hosting our team's knowledge base. The only missing element was the ability to insert tables, which we swiftly designed and implemented.
With this crucial feature in place, the product had reached a stage where it was prepared for the public, marking an important milestone in its development.
Overview
Discover
Define
Design
Thoughts
Bring a knowledge management system to life from 0 to 1
Contribution
UX design & product strategy
Company
Teambition
Website
thoughts.teambition.com
Thoughts is a collaborative knowledge management system which enables individuals in an organization to collectively create, edit, share, access internal documentations across company boundaries to achieve its business objectives.
From the very beginning, I took on the role of the main UX designer for this product, guiding it from the conceptual stage to its launch. Throughout this journey, I led the feature ideation, facilitated design iterations, and fostered collaboration across multiple teams, including design, development, marketing, sales, and customer success.
Project Summary
During my tenure at the company, our primary offering was Teambition, a cloud-based project management and collaboration platform. As part of our expansion plans, we identified a promising business opportunity in the form of a collaborative knowledge management system that would address the existing functional gaps in our main product while entering a relatively untapped market.
Target Users
Our early-stage business strategy focused on implementing an upselling approach to promote the purchase of our primary product, Teambition, while introducing and highlighting the benefits of our collaborative knowledge management platform. As a result, our strategy aimed to target the same user base as Teambition, which consisted of small to medium-sized business professional in four major industries, including tech companies, advertisement agencies, law firms, and construction companies.
Young professionals from small to medium-sized companies who collaboratively engage in writing, reading, and sharing internal team documentation.
Competitors
User Goal
Our user goal is to provide features that are specifically designed for collaborative knowledge management scenarios for small to medium-business users.
Business Goal
Our business goal is to upsell our services to our existing customer base from our main product Teambition, to increase revenue.
Core Loop
The core loop of an editor role consist with three major steps: create/edit a document, organize documents to make them easier to be looked up, and share documents to people in need.
Feature Map
Based on the editor’s core loop on our product, their feature requests comprise from their needs for editing, organizing and sharing documents. This feature map explains what to build to make the MVP work.
Key Design
While numerous design details were considered, I will highlight the pivotal ones that resonated most with our target customers.
Feature overview
Edit
The available toolbar options changes dynamically based on the selection of the content, ensuring users always have the most handy option in front, and only shows up when users need it.
Content-aware
Formatting Toolbar
Share
Permission control allows the administrators implement confidential protocols as well as giving team members the flexibility to access the document.
Document-sharing with
Permission Control
Role control
grant different permissions by assigning roles.
Permission hierarchy inherit
members automatically obtain relevant permissions through the role they have in the parent document without extra permission request to administrators.
Public link and password
invite members outside of the organization to view or edit the document and comply with local laws where document-sharing service could not provide direct link of viewing the document.
Organize
Nested-page navigation helps the users to organized the documentations and makes it easier for others to look up them.
Organize Documentations with
Nested-page Navigation
Drag & Drop
Organize the document tree by drag and drop.
Collapsable Panel
Users can hide the navigation and focus on the writing.
Create Child-document with One Click
A shortcut to create a child-document, and member will inherit permissions without further configurations.
Synchronized Sorting
All the members will see the same sorting to ensure a consistent reading experience across the organization.
Results
After six months of dedicated effort, the product was successfully rolled out internally for testing purposes. We were on the verge of meeting our success metrics, as the product effectively served as a reliable platform for hosting our team's knowledge base. The only missing element was the ability to insert tables, which we swiftly designed and implemented.
With this crucial feature in place, the product had reached a stage where it was prepared for the public, marking an important milestone in its development.
Overview
Discover
Define
Design
Thoughts
Bring a knowledge management system to life from 0 to 1
Contribution
UX design & product strategy
Company
Teambition
Website
thoughts.teambition.com
Thoughts is a collaborative knowledge management system which enables individuals in an organization to collectively create, edit, share, access internal documentations across company boundaries to achieve its business objectives.
From the very beginning, I took on the role of the main UX designer for this product, guiding it from the conceptual stage to its launch. Throughout this journey, I led the feature ideation, facilitated design iterations, and fostered collaboration across multiple teams, including design, development, marketing, sales, and customer success.
Project Summary
During my tenure at the company, our primary offering was Teambition, a cloud-based project management and collaboration platform. As part of our expansion plans, we identified a promising business opportunity in the form of a collaborative knowledge management system that would address the existing functional gaps in our main product while entering a relatively untapped market.
Target Users
Our early-stage business strategy focused on implementing an upselling approach to promote the purchase of our primary product, Teambition, while introducing and highlighting the benefits of our collaborative knowledge management platform. As a result, our strategy aimed to target the same user base as Teambition, which consisted of small to medium-sized business professional in four major industries, including tech companies, advertisement agencies, law firms, and construction companies.
Young professionals from small to medium-sized companies who collaboratively engage in writing, reading, and sharing internal team documentation.
Competitors
User Goal
Our user goal is to provide features that are specifically designed for collaborative knowledge management scenarios for small to medium-business users.
Business Goal
Our business goal is to upsell our services to our existing customer base from our main product Teambition, to increase revenue.
Core Loop
The core loop of an editor role consist with three major steps: create/edit a document, organize documents to make them easier to be looked up, and share documents to people in need.
Feature Map
Based on the editor’s core loop on our product, their feature requests comprise from their needs for editing, organizing and sharing documents. This feature map explains what to build to make the MVP work.
Key Design
While numerous design details were considered, I will highlight the pivotal ones that resonated most with our target customers.
Feature overview
Edit
The available toolbar options changes dynamically based on the selection of the content, ensuring users always have the most handy option in front, and only shows up when users need it.
Content-aware
Formatting Toolbar
Share
Permission control allows the administrators implement confidential protocols as well as giving team members the flexibility to access the document.
Document-sharing with
Permission Control
Role control
grant different permissions by assigning roles.
Permission hierarchy inherit
members automatically obtain relevant permissions through the role they have in the parent document without extra permission request to administrators.
Public link and password
invite members outside of the organization to view or edit the document and comply with local laws where document-sharing service could not provide direct link of viewing the document.
Organize
Nested-page navigation helps the users to organized the documentations and makes it easier for others to look up them.
Organize Documentations with
Nested-page Navigation
Drag & Drop
Organize the document tree by drag and drop.
Collapsable Panel
Users can hide the navigation and focus on the writing.
Create Child-document with One Click
A shortcut to create a child-document, and member will inherit permissions without further configurations.
Synchronized Sorting
All the members will see the same sorting to ensure a consistent reading experience across the organization.
Results
After six months of dedicated effort, the product was successfully rolled out internally for testing purposes. We were on the verge of meeting our success metrics, as the product effectively served as a reliable platform for hosting our team's knowledge base. The only missing element was the ability to insert tables, which we swiftly designed and implemented.
With this crucial feature in place, the product had reached a stage where it was prepared for the public, marking an important milestone in its development.