Section 1
Design backwards from the artefact
Decide first what the workshop produces. A rewritten positioning paragraph. Six customer stories captured with permission and enough detail to use. A revised first five minutes of the sales call. A one-page change narrative that five managers can repeat. With the artefact fixed, most agenda decisions make themselves, and the generic exercises fall away. Without it, you get a well-run day of activities and a set of flipchart photos that nobody opens. Note also that the moment you start capturing employee and customer stories for external use you are handling consent and rights, which [Navigating Legal and Ethical Issues in Business Storytelling](/blog/navigating-legal-and-ethical-issues-in-business-storytelling) sets out before it becomes a problem.
Section 2
Use real material, not invented scenarios
Practising on a fictional company is safe and it teaches almost nothing that transfers. The difficulty in business storytelling is not technique. It is deciding what to leave out of your own situation when everything in it feels necessary. So bring actual material: a losing proposal, a call recording, the homepage, a deck that did not land. Participants work on things they own, which raises the stakes in the room and means the output is immediately usable. It also surfaces the disagreements about the business that a workshop is a useful place to have.
Section 3
Pre-work does half the job
Ask each participant to arrive with one specific example: a moment where a customer misunderstood the offer, or a question that keeps coming up in the same place in the sales conversation. Collecting these a week ahead also tells the facilitator what the room actually needs. If the workshop concerns an automation shift, [How AI Automation Changes Business Models, Margins, and Speed](/blog/how-ai-automation-changes-business-models-margins-and-speed) is worth reading beforehand.
Section 4
Running the first one
Keep it to half a day and one team. A first workshop that produces a single usable artefact earns the right to a second. A two-day all-company event that produces enthusiasm and nothing else usually ends the programme by exhausting the budget and the goodwill in one attempt. Structure the day so that at least half of it is production rather than instruction. Teach a frame in twenty minutes, then spend two hours with participants writing, testing on each other, and revising. Close with each group reading their output aloud to the room. Reading aloud is the cheapest quality test available, because weak reasoning is much harder to hear than to look at.
Section 5
Whether you should run one at all
You are ready for a storytelling workshop if there is a named artefact, a person who owns it after the day ends, and a scheduled moment in the next month where it gets used with a real audience. You are not ready if the goal is described as alignment, or if the workshop is being run because engagement scores dipped. Those are real problems and this is not the instrument for them. The most common regret is scope. Twenty people, four objectives, one day, and an agenda that assumes every exercise runs to time. Cut the objectives to one and the workshop starts producing something you can point at afterwards.