Lead With the Recommendation, Not the Background
The analysis is sound and the proposal still dies in the review. Practice in structuring a case, putting the ask first, and holding up when the person who signs starts asking questions.
The Proposal That Died in the Review
Weeks of analysis, a deck nobody finished reading, and the machine is still not approved. The team opened with methodology, reached the recommendation as the meeting was ending, and answered the first hard question by promising to check and come back. The idea was probably right. It lost to a competing request from someone who led with the ask, the cost and the risk. This session works the gap between having the better answer and getting a decision on it.
What the Session Works On
The Ask, First
What you want decided, what it costs, and what happens if it is not done. Everything else is support. Participants rewrite their own real proposal into that order and feel how much shorter it becomes.
Structuring So It Cannot Be Argued Sideways
Separating your points so they neither overlap nor leave a gap — the MECE discipline, applied to a recommendation your team is genuinely making rather than to a textbook example.
Pitching to the Person Who Signs
A promoter, a finance head and a plant head each want a different opening sentence. Reading the audience and re-cutting the same content for each of them.
Visuals That Carry Weight
One chart that makes the case beats a deck that buries it. Also when a single sheet of paper, or a walk down to the machine, will do more than any slide.
The Questions That Decide It
Preparing for the objection you are dreading, saying “I don’t know” without losing the room, and handling the senior person who interrupts before you have properly started.
Delivery Under Real Conditions
Pace, pauses, and what to do with your hands — practised in the languages your meetings actually run in, including the mix of English and the local language most rooms use.
Pitch, Feedback, Pitch Again
Every participant presents a real proposal, takes structured feedback from peers and the facilitator, and presents it again. The rebuild is the part that teaches.
What Participants Are Equipped to Do
Get to a Decision in the Meeting
Proposals arrive short and in decision order, so a review ends in an approval, a rejection or a named next step instead of a request for more information.
Carry Technical Content to a Non-Technical Room
Engineers, quality staff and accountants get a structure that moves their work intact to people who do not share their background.
Stay Steady When Interrupted
Practice being cut off, doubted and asked for a figure they do not have, so that the real review is not the first time it happens.
Send Good Ideas Upward
When a proposal is easier to make, more people make one, and fewer usable suggestions stop at the supervisor’s desk.
How GullyHR Runs It
Real Proposals in the Room
Participants bring something they actually want approved — a machine, a process change, a hire, a price revision. Nobody presents about a fictional company.
The Facilitator Plays the Hard Audience
Including the promoter who interrupts, the peer with a competing request for the same money, and the finance head who wants the payback before the vision.
Recorded Only If the Group Agrees
Playback helps and it is never the default. The room decides, and anyone can decline without having to explain why.
Your Rebuilt Proposal, in Hand
Their own proposal, rebuilt, plus a one-page structure for the next one and a self-review sheet to use before the real meeting.
Have Your Team Present Something They Want Approved
Bring live proposals and we will build the practice rounds, and the hard questions, around them.
Questions We Get Asked
Scoped per engagement, and it depends mostly on cohort size, because everybody presents, takes feedback and then presents again.
No. Many participants have never presented formally at all. The programme starts with structure, which is where most of the improvement sits, and delivery comes afterwards.
Yes. The material shifts to the client’s decision and the objections they raise, and the practice cases come from deals your team is actually working on.
No. Clear structure gets a weak idea rejected faster, which has its own value, but the programme trains how a case is made, not whether the case is sound. If the analysis underneath is the real problem, structured problem-solving or data-driven thinking is the better place to start.