GullyHR designs and facilitates the programme. We run a needs discussion with you and the managers concerned, collect the workplace situations your people are struggling with, write them into the practice material, facilitate the sessions, and hand back each participant's action plan with a briefing for their manager. You name the conversations that are going wrong, supply the situations we may use, nominate participants, release them for the whole session and follow through in one-to-ones. This is a training engagement with design and reinforcement around it, not a course delivered to whoever was free that day.
A spoken instruction lands once when it is structured before it is said.
Verbal communication: the point first, then the reason, then what the listener has to do about it. Participants practise on their own instructions, status updates and shift or project handovers until the structure stops needing thought.
Listening is work, not the pause before you speak.
Active listening: holding attention, playing back what was said to check it, and picking up what was implied but not stated. Practised on complaint calls, customer briefs and escalations, where mishearing the first time costs the most.
The right question reaches the real problem faster than any explanation.
Open, closed, probing and clarifying questions, and when each one is appropriate. Participants work situations where the first answer is not the real one: a delay report, a vague customer requirement, a junior who is stuck and saying nothing.
You are clear only when the other person can repeat it back.
Clear communication: cutting jargon and hedging, naming the action, the owner and the date, and closing an exchange with a confirmed next step. Applied to spoken updates, short written messages and meeting summaries.
People can raise a problem, or say no, without it turning into a fight.
Assertiveness: the difference between passive, aggressive and assertive responses, and how to push back on an unrealistic ask or report bad news early. Participants rehearse the wording until it sounds like them rather than like a script.
A request should survive the journey to another department.
Cross-functional communication: why sales, operations, finance and engineering hear the same sentence differently, how to state a request in the other function's terms, and how to raise a dependency so a handover does not fail quietly.
Reporting upward means getting to the ask before the detail.
Communication with senior management: the request or recommendation first, the supporting detail held in reserve, and bad news delivered together with what is already being done about it. Practised with the time pressure a real review carries.