Part 1: UX Research

What is MessageWatcher?

Message Watcher offers a monitoring solution for electronic communication in the business. They take all employee’s electronic communication on Mail, Facebook, Twitter, Linkedin, Bloomberg, and specific website, and then run it from their automated engine. Employee’s communication is elevating and flagged. This policy tool allows the organization to define bad keywords to be used in this reporting and the message is sent to admin. The organization will recover valuable time, money and security manage their employees.

Current Information Architecture

I spent two days to go through and figured out the content in an entire portal website. Besides, I captured all about the screenshots as a convenient way to share my research things with teammates.

Write down the problem

The active way to approach the Main User Pain Points is to write down all UX problems that I assume need to improve. Of course, you can do it in mind so far, but you need to remember the thinking is the fastest way and easy to away, so your brain can't capture on a long moment later. So, the writing is the best way to keep the ideas and put them out of the box. Our problems thus far are as follows:

Competitive Research

To be honest, I did not too much time for the competitive analysis research. Anyway, I tried all my best by conducting user testing sessions on these products to get insights and understand the market:

  • Going further through to the similar products as Global Relay, Proof Point, Smarsh, Mimecast and Actiance. To see what is competitors offering? What is the different thing with our product. 

  • Researching on the similar features as Gmail, Inbox and Outlook. To see how can they handle the message list with the huge item and how to quick action on the each message. 

  • Researching on the products focus about the Dashboard like Google Analytic.

  • Moreover, we also have a look at design shots in Dribbble to collect more creative side.

Google Design Sprint (2 Days)

After that, we used two full working days to run the Google Design Sprint to create new information architecture. Addition we tried to find find the common ideas.

1. List Print Questions:

To be making sure each team member understands about insight the project, we put questions relate to discussing the product vision, goal and outcome from the client and team members as well.

1. What is our target user? — Compliance, Officers, Technicals, Legals

2. What do we offer? — Large employee base, get more revenue, understand value and offerings

3. How could this fail? — 3rd party changes APIs, too high maintenance, misunderstanding about what is being built

4. What is the next 5 year goal? — Planning the services like Slack and Instagram

5. Why do they want our websites archived? — The cheapest

After discussing, we chose three core things as the target that we need them in this MVP (Minimize visible project), it's included:

  • Having an area somewhere on the website to track all the metric data.

  • Changing the experience and user’s behavior to review the message list and action on that.

  • Improving the advanced search behavior. 

2. Stakeholder Interview

We had an opportunity to hear their troubles when they run on the website to draw ideas need to resolve.

3. Mind Map:

Based on the information that we collected, we brought all the first ideas in mind on the paper. On the mind map, we don't need about a gorgeous or unique map, anything for arrows and basic shapes are enough.

3. Sorting Card

Sort Card or How Might We method is an essential method, to take the insight and come up with positive solving the challenge. We avoid using words as personal in this step.


"How" guides team members believe the answer is out there.
"Might" lets team members know their HMW statement might or might not work, and either possibility is okay
"We" reminds team members that the Design Sprint is about teamwork and building on each others' ideas


- Google Design Sprint Book

During review, we gathered ideas and capture all day from beginning like How might we notes, sprint questions, mind map flow to figure out and think some more the new ideas from stakeholder. Try hard to think about the solutions as personal

6. Crazy 8s:

Crazy 8s is the paper with the eight pies. In one minute per each pie, we have a quick sketch on any elements we want to present. Why the time is so rush? The human will be forcing their brain to push new creativity when the time to squeeze you into a specific limit. I did some sprint designs I felt the productive core of Crazy 8s was very high to catch an idea.

7. Solution Sketches:

Whilst we had enough the information, mind map ideas and sketches around, then we based on that and made the personal storyboard that we want to represent. We also picked for each yourself one or two main ideas to give the concentrate on that solution. Moreover, two or three peoples can work the same segment together to make the comparison and various options to support the different ideas.

  • Focus on solving all metric data on the dashboard

  • Focus on the main menu navigation

  • Focus on how to view the message list and details

  • Focus how to work well on advanced search and filter

8. Vote on Solutions Sketches:

Day 2, we continued with Google Design Sprint and caught up anything on the first day, looked around at sketch solutions have been stuck on the wall. We had small dot stickers in hand and can vote for any components that this is an awesome idea need to turn up.

3. Mind Map:

Based on the information that we collected, we brought all the first ideas in mind on the paper. On the mind map, we don't need about a gorgeous or unique map, anything for arrows and basic shapes are enough.

Team Size

Client, Head of Product, CTO, Product Manager and Product Designer (me).