The first-ever intranet in Meyer – What should be our MVP?
Meyer is one of the largest cookware manufacturer in the world with office located over thirteen countries. While the company was expanding very quickly, staff were disconnected with others and the company. Therefore, this project was to create the first intranet that re-connect everyone in the company. The case study talked about how we use research to define our most important functionality.
📁 Project
Meyer Connect (2018)
💪 My role
Leading role in UX & UI team + Directly communicate with development team
👥 Target audiences
Meyer Staff Globally (Evereyone from the admin team to R & D to marketing team)
📍Market
Global
—
How might we…
How might we find out the common pain points from staff in communication?
How might we help users to know better about this company?
How might we better engage our colleagues and HR?
How might we identify the most efficient function for our Day 1 launch?
—
Research & discovery
Research #1 – Let’s chat with our colleagues
The team interviewed 86 staff in Hong Kong, Macau and Thailand office. Each deaprtment would assign two staff for interview, a general and a managerial staff. Each interview lasted around an hour, we asked them about their daily routine, communication method and feedback about the company.
Document for the team to collect information from HR team
Research #2 – Really learn about the company
When it came to intranet, it required every effort from every team, especially the human resource team. In order to collect information and resources, we communicated with HR team over the world, to learn the information they had and their difficulties.
Research #3 – Data analysis
The team recorded data in typeform and later moved all the data into airtable. We combed and grouped information in different ways, trying to identify unique points or patterns that could lead to new opportunities.
how our airtable look like
—
How shall we better engage our colleague and HR?
—
How we use research findings to inform our design?
Problem #1
We don't know the basic information about the co-workers.
MVP #1 – Global staff directory
a global directory with job & contact information
With (optional) profile picture so that it help staffs to recognise each other
Staff Directory Design
How shall we better engage our colleagues offline?
Profile picture shooting session (Pre-launching Event) with our colleague in Thailand. Yes! We travelled to our Thailand office to meet and greet with them!
🥴 Some colleagues were reluctant to show their picture as a lot of them do not have a proper professional profile picture.
📸 Therefore, we launched a pre-launching event that we helped our colleague to take professional profile picture. We have taken pictures over 150 staff in Hong Kong, Macau and Thailand!
—
Problem #2
Staff are unclear with the administrative policies and procedures
MVP #2 – Resources directory
A resources session that gathered all of the useful information
From HR info to useful document to internal system link to different office addresses
Resource page about HR procedure
Resource page about all internal system
Resource page about company info
—
Problem #3
There is not enough channel for staff to learn and share the company knowledge.
MVP #3 – Meyer Wiki
A wikipedia with our experienced staff that can share
When we launched, our team connect with different team to encourage each team to write about their department and some cookware knowledge
wiki landing page
editing page
the navigation
—
Communicating with development team with no Digital Analysts
Our Trello board
One of the biggest challenge for this project is to communicate with development team which locate in Thailand. Usually there will be a digital analyst who translate design into development language/story. There is no such role in this project, therefore, I learnt how to manage the communication with the team. In order to enhance our communication, we set up regular meeting, clear documents and a trello board. Therefore, whenever there is any one unclear about the project progress or design detail, there were always a document or a trello card for everyone to refer to.
Our product requirement documentation
