top of page

              At a Glance


In 2016,  I was tasked with designing a Content Management System for Xinkaishi which is a mobile app for pregnant women. As a SaaS Product,Mykaishi is a collaboration application includes web-based publishing, format management, content editing, member management and Order Management.

Mykaishi serves three primary user groups:

       My Role

UX Design Solution for SaaS

​Interface Design


 Web Application

Monica and her product team is the champions of the product. These decision-makers use the product to track user’s behaviour. She needs a platform to help her manager the content operation team.

Lily is a content operation specialist. She needs to identify user Needs, manage contents and users in the community. She needs a platform to help her manage her accounts in the community and push notifications for different level users.

As a Product Specialist, Jack manages the orders in Mykaishi‘s online store.  He needs to monitor all aspects of a product lifecycle, including long- and short-term development and marketing. Stays abreast of trends in the marketplace to ensure the product's competitive position.

Stage One: Discovery & Conceptin

Before the actual legwork started, the PM gathered for a brainstorming/sketching session.

We sketched out ideas on the whiteboard. These mostly involved user flow charts, drawing out the pace of the experience screen by screen. The user flows formed the foundation that would eventually grow into the perfect solution for Mykaishi.

Stage Two: Mid-Fidelity Flows


Immediately following the whiteboard session, I used Sketch to create mid-fidelity versions of the white board sketches. These mid-fi flows become the key to the intermediary stage of internal testing before hi-fi prototyping and testing with users.

Stage Three: Hi-fi Prototyping

Building on the mid-fidelity user flows and internal feedback, We were ready to create a functioning version of their design.


Since the goal of creating a prototype is to test our design decisions, the first step was outlining desired insights in a usability testing plan.


Usability testing revealed the design worked well as a system:

• Users found the layout easy to use and understand when creating post

• Users mentioned the default dashboard was useful and matched their needs.

• While most users found the default widgets useful, some mentioned how they’d prefer different widgets due to personal preferences. For example, some users didn’t find the “Flag Post/Unflag Post” .Others wanted the ability to save their customizations to the templates.

• Users did experience some difficulty in review/edit their post before publish


To improve findability of newly-created post, we decided to increase negative space around the “View My Thread” label which is sort by date.

Stage Four: Development and Live Launch


Following the Agile process, development sprints immediately followed the design sprints.


Thanks to efficient hi-fi prototyping and close collaboration, we launched  Mykaishi on April 9, 2016 on schedule and within scope.

The initial results are promising:

• 800 + posts were created by Mykaishi, 200+ comments were created  in 4 weeks after launch.

• Increased Activation Rate by 55% in the community,Increased app signups by 67%

• Less reported stress among the product team

“I was blown away by the numbers,It was great to see that something I worked on was this popular with users.”

bottom of page