Presenting your experience clearly is a practical workplace communication skill. You may need to explain a completed task in an interview, describe a project during a review or show a colleague why you can take responsibility for new work. The aim is to make your contribution understandable without exaggerating it.
This checklist helps you prepare a spoken example using work you have actually done. It suits people practising workplace communication in Australia across different industries. Adapt it to the conversation rather than treating it as a script that every employer expects.
Check the purpose before choosing your example
- Identify who will listen and what they need to understand.
- Read the question or discussion agenda carefully.
- Select one capability to demonstrate, such as organising work or resolving a problem.
- Check whether the conversation calls for a brief overview or a detailed explanation.
A useful example answers the question in front of you. A technically impressive project may be a poor fit if the listener is asking about teamwork. Choose evidence that shows the relevant behaviour, even if it comes from a smaller task.
For an internal conversation, consider what the listener already knows. You might need to explain your decision and result rather than retell the entire project. For someone outside the organisation, prepare a plain-language description of the work first.
Separate context, responsibility and action
- State the situation in a sentence or two.
- Explain the task you were responsible for.
- Describe the actions you personally took.
- Explain the outcome and any limits on what you can demonstrate.
The Australian Public Service Commission’s interview preparation guidance includes using STAR examples to demonstrate skills and experience. STAR provides a situation, task, action and result structure. It is a useful preparation tool, rather than a universal requirement for every workplace conversation.
Give actions enough space. Saying that you were involved in an improvement does not explain what you did. Describe how you gathered information, selected an approach, checked the work or communicated a change. Avoid giving background details so much time that your contribution disappears.
Check the evidence behind the result
- Use figures only when you can support them.
- Distinguish a measured outcome from an impression.
- Acknowledge other people’s contributions.
- Explain what remained unfinished or uncertain.
If you do not have a reliable percentage or dollar result, do not create one. A clear qualitative outcome can still be useful: the team adopted the revised handover, the document was completed by the agreed date or a recurring question was addressed in the instructions.
Choose language that matches the evidence. Helping a group deliver a project is different from leading the whole project. You can communicate your value clearly while recognising shared work. An accurate description also makes follow-up questions easier to answer.
Remove detail the listener cannot use
Read your notes and mark abbreviations, internal job titles and specialised terms. Keep technical language where the audience needs it, but explain unfamiliar terms briefly. The listener should not have to decode your organisation before understanding the example.
Protect confidential information. Replace unnecessary client identifiers and sensitive project details with a general description that still explains your role. Check your workplace’s requirements before using documents or records as supporting material. You do not need to expose private information to demonstrate a communication skill.
- Keep only the background needed to understand the action.
- Replace vague claims such as excellent communicator with observable behaviour.
- Remove repeated explanations of the same point.
- Retain any limitation needed to keep the example accurate.
Practise aloud and ask a specific feedback question
Speak the example rather than silently reading it. Notice where a sentence becomes hard to finish or where you lose track of the point. Shorten the wording there. Written notes can be more detailed than the explanation you need to give aloud.
If a trusted person is willing to listen, ask whether they understood your responsibility and the result. A focused feedback question is more useful than asking whether you sounded impressive. If you record a practice conversation involving anyone else, agree on that first and handle the recording appropriately.
Prepare a shorter version and a fuller version. The short version establishes the example; the fuller version gives supporting detail when requested. This lets you respond to the time available without rushing every sentence.
Check that you can respond, not just recite
Practise answering a follow-up question about why you chose an action, what you would change or how you dealt with a constraint. If the question exposes a gap, revisit your actual experience rather than adding an invented detail to make the story smoother.
During the conversation, listen to the whole question and clarify its focus if necessary. Pause when you need to think. A clear, accurate explanation with room for questions usually serves the discussion better than a polished speech that ignores what the other person asked.