Stakeholder Flashcards

1
Q

What are Stakeholders?

A

The people that have invested time, interest, and resources into the projects that you’ll be working on as a data analyst

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What should you do at the beginning of each project?

A

Take time at the beginning of every project to identify your stakeholders and their goals. Then see who else is on your team and what their roles are.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are three common stakeholder groups?

A
  • Executive Team
  • Customer-Facing Team
  • Data Science Team
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What does the Executive team do in the project?

A
  • The executive team provides strategic and operational leadership to the company.
  • They set goals, develop strategy, and make sure that strategy is executed effectively.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What roles might be represented in the Executive Team?

A
  • Chief Marketing Officer
  • Vice Presidents
  • Senior-level professionals
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the Executive Team interested in where the project is concerned?

A
  • They think about decisions at a very high level and they are looking for the headline news about your project first
  • They are less interested in the details.
  • Time is very limited with them, so make the most of it by leading your presentations with the answers to their questions.
  • You can keep the more detailed information handy in your presentation appendix or your project documentation for them to dig into when they have more time.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Who is often a good liason between you and the Executive Team?

A

The Project Manager

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Who makes up the Customer-Facing Team?

A

Anyone in an organization who has some level of interaction with customers and potential customers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What does the customer-facing team do?

A
  • Typically they compile information, set expectations, and communicate customer feedback to other parts of the internal organization.
  • These stakeholders have their own objectives and may come to you with specific asks. It is important to let the data tell the story and not be swayed by asks from your stakeholders to find certain patterns that might not exist.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Who is a Data Science Team made up of?

A

Data analysts, data scientists and data engineers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Data Analysts role in the Data Science Team

A
  • There’s a good chance you’ll find yourself teaming up with the Data Science Team during the project
  • A big part of your job will be collaborating with other data team members to find new angles of the data to explore.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What do Data Scientists do?

A
  • Say you look into the data on employee productivity, while another analyst looks at hiring data.
  • You then share those findings with the data scientist on your team, who uses them to predict how new processes could boost employee productivity and engagement.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Roles within a Data Science team

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Feel empowered to say “no”

A
  • Let’s say you are approached by a marketing director who has a “high-priority” project and needs data to back up their hypothesis. They ask you to produce the analysis and charts for a presentation by tomorrow morning.
  • Maybe you realize their hypothesis isn’t fully formed and you have helpful ideas about a better way to approach the analysis. Or maybe you realize it will take more time and effort to perform the analysis than estimated. Whatever the case may be, don’t be afraid to push back when you need to.
  • Stakeholders don’t always realize the time and effort that goes into collecting and analyzing data. They also might not know what they actually need.
  • You can help stakeholders by asking about their goals and determining whether you can deliver what they need. If you can’t, have the confidence to say “no,” and provide a respectful explanation.
  • If there’s an option that would be more helpful, point the stakeholder toward those resources.
  • If you find that you need to prioritize other projects first, discuss what you can prioritize and when.
  • When your stakeholders understand what needs to be done and what can be accomplished in a given timeline, they will usually be comfortable resetting their expectations. You should feel empowered to say no– just remember to give context so others understand why.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Make a list of potential roadblocks

A
  • Before you start a project, make a list of potential roadblocks.
  • When you discuss project expectations and timelines with your stakeholders, give yourself some extra time for problem-solving at each stage of the process.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Know your project

A
  • Keep track of your discussions about the project over email or reports, and be ready to answer questions about how certain aspects are important for your organization.
  • Get to know how your project connects to the rest of the company and get involved in providing the most insight possible.
  • If you have a good understanding about why you are doing an analysis, it can help you connect your work with other goals and be more effective at solving larger problems.
17
Q

Start with Words and Visuals

A
  • It is common for data analysts and stakeholders to interpret things in different ways while assuming the other is on the same page. This illusion of agreement has been historically identified as a cause of projects going back-and-forth a number of times before a direction is finally nailed down.
  • To help avoid this, start with a description and a quick visual of what you are trying to convey.
  • Stakeholders have many points of view and may prefer to absorb information in words or pictures.
  • Work with them to make changes and improvements from there. The faster everyone agrees, the faster you can perform the first analysis to test the usefulness of the project, measure the feedback, learn from the data, and implement changes.
18
Q

Communicate often

A
  • Your stakeholders will want regular updates on your projects.
  • Share notes about project milestones, setbacks, and changes. Then use your notes to create a shareable report.
  • Another great resource to use is a change-log, which is a tool that will be explored further throughout the program. For now, just know that a change-log is a file containing a chronologically ordered list of modifications made to a project. Depending on the way you set it up, stakeholders can even pop in and view updates whenever they want.
19
Q

What questions should you ask yourself before each task to ensure that you’re able to stay focused on your objective while still balancing stakeholder needs?

A
  1. Who are your primary and secondary stakeholders?
  2. Who is managing the data?
  3. Where can you go for help?
20
Q

What should you do when balancing everyone’s needs is a little chaotic?

A
  • Look past the clutter and stay focused on the objective.
  • It’s important to concentrate on what matters and not get distracted.