Continuous communication

Listen carefully

separation of personnel

Record and share all contact information within and outside the project team, clearly communicate responsibilities, and determine the overall scope of the project

Agree on a meeting schedule, ensure that the entire project team meets at least once a week, and invite customers to participate in some meetings

All meetings should have a clear agenda and result in concrete decisions and new courses of action

Keep team members informed of the latest progress of the project through frequent emails, in a simple and consistent format

When evaluating the pros and cons of an issue and opinion, be sure to separate the person from the opinion he or she proposes.

Discuss team collaboration status

Determine expectations and monitor completion

Clarify personal development goals and adjust work plans accordingly

Identify the personality types of team members and customers

Before the project is implemented, hold a brief, relaxed meeting to discuss each other’s personalities and working style preferences.

Understand your own nature while maintaining a good attitude when dealing with members of different personality types

Each team member should clearly record their 1-2 main development goals in the project

Openly discuss and coordinate personal development goals among members

Develop procedures for handling disagreements and giving and receiving feedback

Conduct regular feedback sessions to allow time for improvements

Make the most of expertise

Everyone performs their duties

real time feedback

First brainstorm and discuss in depth the key points to be solved in the project

Balance the workload according to the time required for each sub-task

Identify and leverage each team member’s expertise

Hold at least 1-2 phase reporting meetings with the project team (and client)

Provide and update personal and project progress information daily

Identify personalized motivators

Positively influence team members

celebrate achievements

Identify and discuss the primary and secondary factors that motivate each member

Recognize and celebrate every team achievement

Have a grand party after the project is completed

Identify key issues

Create a question tree

formulate basic assumptions

Identify key issues affecting the project through discussions with clients

Clarify the key issues, project scope and rough plan to solve the problems in the authorization letter

Define the project’s timeframe, geographic scope, and functional areas

To avoid the common problem of “scope changes”

Form an overall hypothesis as a potential solution to an existing problem

Supporting hypotheses must be formulated to validate the overall hypothesis

Revisit and revise hypotheses as you collect data

Build an overall flow chart

Develop a content plan to test hypotheses

Design story threads

Maintain objectivity when testing hypotheses

Use the framework model as a starting point to think about the issues to be analyzed

Detailed list of types of analytical questions the team may undertake and associated data requirements

If the hypothesis is modified, the issue tree and content plan will need to be revised

Present necessary data through "Sketch"

Conduct targeted interviews

Collect third party data

Create sketches to present necessary data related to the overall case

Use customer information, prepare an interview outline in advance, organize the interview records in written form within 24 hours, and share them with the team

Indicate the source of the citation on each diagram you draw.

clarify "so what"

Clarify implications for project stakeholders

Document core insights across all charts

Organize your analysis and determine what is most important by asking "so what"

Fully assess the impact of recommendations on client operations

Get feedback and ensure buy-in

Provide specific suggestions for improvement

tell a good story

Tell a story that briefly introduces the circumstances and complexity of the project

Share stories with clients and teams ahead of time to gain buy-in

The story should be concise, focusing on the essential issues and specific suggestions for improvement.

Learn to have fun with it