Lesson Outcomes
By the end of this lesson, you will be able to:
- Explain why you should consult stakeholders and role-players when defining a problem.
- Identify people and groups who should participate in the problem-solving process.
- Explain the value of involving stakeholders early.
- Prepare for an effective stakeholder problem-solving meeting.
- Recognise how stakeholder input can improve your understanding of a problem.
Lesson Overview
Workplace problems rarely affect only one person. A problem may involve employees, supervisors, customers, suppliers, managers or other groups.
When you try to solve a problem without speaking to the people affected by it, you may miss important information, misunderstand the causes or create a solution that people will not support.
For this reason, stakeholder consultation forms an important part of the problem-solving process. The Learner Guide explains that preliminary problem assessment helps determine who needs to be involved, what information they can provide and how the organisation should respond to the problem.
Main Lesson Content
Who Are Stakeholders and Role-Players?
A stakeholder is a person or group that is affected by a problem or may influence its outcome.
A role-player is someone who has a role in understanding, managing or resolving the problem.
For example, a problem with customer complaints could involve:
| Person or group | Possible connection to the problem |
|---|---|
| Customers | Experience the effects of the problem |
| Frontline employees | Deal with the problem directly |
| Supervisors | Manage the affected work area |
| Managers | Make decisions and allocate resources |
| Support departments | May control systems, equipment or processes |
| Suppliers | May influence availability or quality of resources |
The exact stakeholders will depend on the problem.
Why Should You Consult Stakeholders?
1. To understand the problem properly
Different people experience the same problem differently.
A manager may see:
“Our customer response time is too slow.”
A customer-service employee may explain:
“We lose time because the system takes several minutes to load each customer record.”
The employee’s experience adds information that the manager may not have known.
Consultation therefore helps you build a fuller understanding of the problem.
2. To identify who needs to be involved
Problem-solving may require action from different people or departments.
Early analysis helps you determine:
- Who is directly affected?
- Who has useful information?
- Who needs to take action?
- Who has authority over the relevant resources?
- Who will experience the consequences of the solution?
The Learner Guide explains that preliminary assessment helps identify the individuals and groups who should participate directly in managing the problem.
3. To understand different perceptions of the problem
Not everyone sees a problem in the same way.
One group may think:
“The new procedure is inefficient.”
Another may think:
“The procedure is fine; employees simply need better training.”
Another may say:
“The real issue is that the procedure is applied differently across departments.”
Listening to these perspectives can help you challenge assumptions and investigate the problem more accurately.
The Learner Guide emphasises the need to obtain enough information to understand both the causes and perceptions of a problem.
4. To build commitment to the solution
People are more likely to support a solution when they have had an opportunity to contribute to the process.
Stakeholders can help shape:
- the understanding of the problem,
- the priorities,
- the proposed actions,
- the implementation process,
- and the expected outcomes.
Early involvement can therefore create greater commitment when you later implement the solution.
5. To identify concerns before implementation
Stakeholders may identify risks that the problem-solving team has not considered.
For example, a proposed change may:
- require additional resources,
- affect another department,
- create extra work,
- interfere with an existing process,
- or have unintended consequences.
Consulting people early allows the team to consider these concerns before implementation.
When Should You Consult Stakeholders?
As early as practical.
Do not wait until you have already designed the solution.
The Learner Guide specifically recommends involving stakeholders from the earliest possible opportunity rather than waiting until the plan is complete and implementation is about to begin.
A useful way to think about this is:
Stakeholder involvement should therefore continue through the different stages of problem-solving where appropriate.
How Do You Decide Which Stakeholders to Include?
An initial stakeholder analysis may produce a long list of people or groups.
Not everyone on that list will necessarily need to participate in every discussion.
The Learner Guide explains that practical constraints may require the list to focus on essential stakeholders. In other situations, wider involvement may be necessary to obtain enough information about the causes and perceptions of the problem.
Ask:
- Who is directly affected?
- Who has relevant information?
- Who has a role in the process?
- Who can influence the outcome?
- Who will need to support the solution?
- Who has authority to make relevant decisions?
The final stakeholder group should suit the problem.
Stakeholder Consultation Is Not About Blame
When people become frustrated by a workplace problem, they often look for someone to blame.
Effective problem-solving requires a different approach.
Instead of asking:
“Who caused this?”
ask:
“What is happening, who is affected, and what information can help us understand why?”
This keeps the focus on solving the problem rather than attacking individuals.
The Learner Guide makes a similar point when it advises managers to address issues rather than people while defining a problem.
Conducting a Stakeholder Problem-Solving Meeting
Stakeholder meetings work best when participants understand why they are there and what the meeting should achieve.
Step 1: Explain the purpose
Tell participants that the meeting aims to understand and work through a problem.
For example:
“The purpose of this meeting is to understand why customer complaints have increased and identify the information we need to define the problem accurately.”
Step 2: Set ground rules
Agree on how the group will work together.
Ground rules may cover:
- listening to others,
- allowing people to contribute,
- staying focused,
- respecting different views,
- and avoiding personal attacks.
The Learner Guide recommends establishing agreed norms before beginning the problem-solving discussion.
Step 3: Acknowledge existing actions
Stakeholders may already have tried to address the problem.
Do not ignore this work.
Ask:
- What have you already tried?
- What worked?
- What did not work?
- What did you learn?
The existing actions and solutions can provide a useful starting point for improving the response.
Step 4: Gather perspectives
Allow participants to explain what they see, experience and understand.
Look for:
- facts,
- perceptions,
- different experiences,
- possible causes,
- and information that requires further investigation.
Step 5: Agree on next steps
The meeting should help the team determine what needs further investigation and who needs to be involved next.
Benefits of Early Stakeholder Involvement
When you involve stakeholders early, you can:
Understand the problem better
Different perspectives reveal information you may otherwise miss.
Develop realistic processes and timelines
Stakeholders can help identify what can actually be done.
Address priorities and concerns
People can raise issues before implementation creates problems.
Build trust
People are more likely to trust a process when they feel heard.
Improve working relationships
Collaboration can strengthen relationships between teams and departments.
The Learner Guide specifically identifies mutually agreed processes and timelines, incorporation of stakeholder priorities, mutual trust and positive working relationships as benefits of early involvement.
Example: A Workplace Problem
Situation
A department has experienced repeated delays in processing customer requests.
Manager’s initial view
“The administration team is too slow.”
Stakeholder consultation reveals:
- Employees receive incomplete information from sales.
- The current system requires duplicate data entry.
- Customers sometimes submit incorrect information.
- Supervisors approve requests only at certain times of the day.
The problem now looks very different.
Without stakeholder consultation, the manager might have blamed the administration team and introduced the wrong solution.
With consultation, the team can investigate the actual causes.
Practical Application
The Learner Workbook asks learners to identify questions they can use to define a problem and explain the rationale for consulting stakeholders and role-players.
When you encounter a workplace problem, ask yourself:
Who is affected?
Who understands what is happening?
Who has information I need?
Who will need to support the solution?
These questions help you identify the right people to involve.
Key Notes / Lesson Summary
- Stakeholders and role-players can provide information that improves your understanding of a problem.
- Different people may experience and interpret the same problem differently.
- Consult stakeholders as early as practical.
- Involve the people who are affected, informed, responsible or able to influence the outcome.
- Do not focus on blame; focus on understanding the problem.
- Use meetings to establish the purpose, set ground rules, hear different perspectives and agree on next steps.
- Early involvement can improve commitment, trust, communication and the quality of the eventual solution.