6
STEPS TO LAUNCH MUSHIN

STEPS TO LAUNCH MUSHIN - · PDF filePrepare a brief with your personal Mushin project manager to help you: ... • Set the short, middle and long term objectives with ... onboarding

Embed Size (px)

Citation preview

Page 1: STEPS TO LAUNCH MUSHIN - · PDF filePrepare a brief with your personal Mushin project manager to help you: ... • Set the short, middle and long term objectives with ... onboarding

STEPS TO LAUNCH MUSHIN

Page 2: STEPS TO LAUNCH MUSHIN - · PDF filePrepare a brief with your personal Mushin project manager to help you: ... • Set the short, middle and long term objectives with ... onboarding

Mushin and you in 3 key steps

Our User Support experts are here to help during office onboarding, ensuring your team is ready for a new digital and collaborative adventure. This document covers the Mushin integration process that has proved successful with our current clients.

On site or remotely, we'll work hand in hand to ensure your collaboration projects is a success.

Setting up Mushin can be resumed in 3 easy steps:

1. Project preparation

2. Training

3. Tracking

D-30

Objective definition

D-20

Mushin account creation

D-15

Launch

D-Day

Training

Page 3: STEPS TO LAUNCH MUSHIN - · PDF filePrepare a brief with your personal Mushin project manager to help you: ... • Set the short, middle and long term objectives with ... onboarding

Project preparation 'Mushin & you'

Following discussions with our sales team and in review of our offer, give us the green light to start your Mushin account.

- The decision maker- Project team members- Mushin User Support team

2. Creating your Mushin account

Mushin makes your life easier... when you know how to organise your workspace. During this step, our team will work alongside you to help structure and simplify your current processes.

This step includes a meeting with our team to ensure we fully understand your present operational methods. We will then recommend relevant topics and folders’ structures for your business, identifying and inviting team members.

Key players:

1. Structuring your Mushin account

Prepare a brief with your personal Mushin project manager to help you:

• Identify key team members: project manager1, contributors and viewers• Set the short, middle and long term objectives with our application• Define KPIs to track the project progress

This is a critical step that will ensure base line standardization and inclusion of the right team members, improving communications, increasing the chance of successful Mushin integration on a company level and within your team.

Key players:- The decision maker

(1 See our last section about «What makes a good project manager?»)

D-30 D-20

Page 4: STEPS TO LAUNCH MUSHIN - · PDF filePrepare a brief with your personal Mushin project manager to help you: ... • Set the short, middle and long term objectives with ... onboarding

Starting working with Mushin

To ensure successful Mushin implementation, we advise organizing a Steering Committee to discuss, debrief and improve user functionality.

3. Mushin launch

This step allows you to validate the project structure set out by your Mushin representative. We will also use this opportunity to organize team training.

At this stage, we will program team monitoring (project management, training, onboarding tips for partners).For the first 4 months, we offer a complete aftercare package to ensure all users are fully trained. Support can be extend if necessary.

Our priority: to allow you to reach the goals set out in the initial brief and notice positive results quickly.

Key players:

- The decision maker- Project team members- Mushin User Support team

Key players:- The decision maker- Project team members- Mushin User Support team- Users

4. Users training

Each account is set up before training begins to allow users to explore their new workspace.

We recommend two-hour sessions to:

• Briefly introduce Mushin• Demonstrate primary and fixed functionality• Familiarize users: we pay particular attention to team apptraining to maximize user confidence• Introduce the objectives and related timelines to thewhole team• Answer all questions

D-DayD-15

Page 5: STEPS TO LAUNCH MUSHIN - · PDF filePrepare a brief with your personal Mushin project manager to help you: ... • Set the short, middle and long term objectives with ... onboarding

Quality feedback and permanent support

Mushin is committed to offering a high-quality, personalized service. We will regularly follow user activity to offer detailed reporting: creation volume, emerging practices, key team drivers.

The Mushin promise? To offer daily coaching during your digital transition and internal communication.

You’re in good hands!

Bernard SorianoCEO/Co-founder

of [email protected]

Adeline BrenneCTO/Co-founder of

[email protected]

Marine BouletCustomer Relationship

[email protected]

Axelle SeifertUser Communication

[email protected]

Page 6: STEPS TO LAUNCH MUSHIN - · PDF filePrepare a brief with your personal Mushin project manager to help you: ... • Set the short, middle and long term objectives with ... onboarding

Appendix - What makes a good project manager?

SKILLS* Ideally someone who has some experience in digital project management* With an overview of departments within the business* Able to unite a team towards a common goal* Capable of driving a project: organizing communication & feedback* Capable of defining SMART objectives: specific, mesurable, ambicious, reachable in time* Capable of generating enthusiasm and identifying potential roadblocks

Personality* Enthusiastic and welcomes change* Committed to the business (company spririt, seeks solutions) * Dynamic and positive, ready to solve problems to see the project to completion* Available and ready to allocate some time to the project* Well established within the team and the company: his role must be appreciated and

legitimate

Profile* Ideally a manager...* ...But not necessarily. They could be a motivated team member* Rarely a technician or IT* Project Manager profile* Good knowledge of internal processes to avoid technical setbacks