Study guide · 5.2
Communicate with others to identify and understand issues
Before a problem can be solved, it has to be understood. Working with teammates and with external clients to define an issue clearly, through good questions, active listening and shared records, saves time and avoids fixing the wrong thing.
A study feature written by ExamDragon, not part of the real exam. Each heading is one of Certiport's skills for this objective.
5.2.1Work with internal team members to identify and understand issues
- Describe the issue with facts: what happens, where, since when, how often and who is affected.
- Ask colleagues what they have seen and tried, and check whether others have reported the same issue.
- Use shared tools such as a ticket system, task board or team channel so information is in one place.
- Separate symptoms from causes; agree on what the real problem is before discussing solutions.
- Respect each person's role and expertise, and involve the right people early.
Example: Several staff say 'the network is slow'; the team lead collects times and locations and finds that it happens only on the second floor in the afternoons.
5.2.2Interact appropriately with external clients to identify and understand issues
- Be polite, patient and professional, and use the client's preferred channel and language level.
- Ask open questions first ('What were you trying to do?'), then closed questions to confirm details.
- Listen actively, summarise the issue back to the client and confirm that you have understood.
- Collect only the information needed, and protect any personal or confidential data the client shares.
- Set clear expectations about next steps and timing, and record the details for the team.
Example: A client emails that 'the app is broken'; the support agent asks which device and version, what they tapped and what message appeared, then repeats the issue back for confirmation.
Key terms
- Active listening
- Giving full attention, asking questions and summarising to confirm understanding.
- Open question
- A question that invites a detailed answer rather than yes or no.
- Ticket
- A tracked record of a reported issue and the work done on it.
- Symptom
- What people notice when something is wrong, as opposed to its cause.
- Stakeholder
- Anyone affected by or involved in an issue or project.
Easy to confuse
- Jumping to a solution before the problem is defined often fixes the wrong thing.
- Using technical jargon with clients can confuse them and hide what they really mean.
- Information shared only in private messages is lost to the rest of the team.
After this guide: You can work with colleagues and clients to gather facts and define an issue clearly before trying to solve it.