Conversation Feature as a common Library
Conversation is a common feature that we published on Storybook for ~30 module teams in the Ocean Network Express (ONE) Chorus to use.
timeline
12 - 03/2025
role
UI/UX Design
platform
Internal Portal
category
Common Service
context
During the growing process, we as a Common Service team received a lot of the requirements for an internal Conversation chatting feature from other module teams. Which is why we started to build a common library for this.
challenges
Since this is a common feature, I had to work closely with the Proxy Product Owner (PPO) and the Technical Architect (TA) to breakdown the requirement.
We also need to carefully list down the in-scope & out-of-scope in technical part. For the out of scope, our team set a customized slot for each module team to integrate functions, based on their business rule.
result & IMPACT
After a few sync up with the Design System team (OTSV), high level POs, PPO and TA, we finally came up with the implementation timeline in 2 months (including Tet national holiday).
The estimated Implementation Timeline
By creating the details design guideline, also publishing the feature on our Common Service's Library, all module teams can use & integrate the component without much effort. Still, keeping the interface & flow consistence across the portal.
Let's dive in the process
approach
Collect use cases from module teams
We collected the requirement tickets with detail use cases, technical expectation, and draft designs from all the teams.
Draft & Finalize the scopes
Then, with the support from Design System team, we finalized the scope with the high level POs.
At this stage, I had a few meetings with the Proxy PO and the Technical Architects to deep dive in the technical parts. So that we can breakdown into user stories with acceptance criteria.
Design & Document
This is the final design guideline for the Conversation features. This will be continuously updated due to future business request from other module teams.
Part of the design guideline
design
Here are a peak of the main features included in the Conversation.
Allow 3 view modes
We support 3 different view modes for each module team to use based on the business rule.
Config on Storybook
Quote a message
Edit message
and others functions…
lesson learned
This is the first time I built a whole detail design guideline for mass usage among ~30 product teams. Thanks to this, I had the opportunity to explore on how to document efficiently in order to hand over to designers, product owners, and developers.
End of story
