Communication and Storytelling specialists for teams that need to be understood

Start with the audience, not the format

Most briefs arrive as a format request: a deck, a video script, a town hall. The format is the last decision, not the first. A specialist who is told to build a deck before the audience is named will build something that looks finished and answers a question nobody asked.

Before anything is drafted, the specialist needs to know who receives the material, what they already believe, and what they will do after reading or watching. A message for a sales team and a message for a board can share every fact and still need different structures, different openings, and different levels of detail. Naming the audience early saves a rewrite later, and it gives the specialist a test to apply when a draft starts to drift.

The brief should also name who decides, what must be true before a shortlist, and what would make you stop. Those three answers keep the engagement honest. Without them the work expands to fill the review cycle, and the specialist ends up guessing at the decision the material was meant to support. A short written brief with the audience, the decision, and the format is usually enough to begin.

What to confirm before you hire

Name the outcome, the owner, and the decision this hire must change before the first conversation. The note should stay specific to the role, the tools, and the decision the company needs. A brief that lists skills without naming the decision produces a shortlist of capable people who are not sure what success looks like.

Confirm the format and the deadline next. A deck for a board meeting and a script for a product video draw on different strengths, and a specialist who is strong in one may be weaker in the other.

Ask what already exists. Current decks, past messages, and documents that failed are useful evidence. The specialist needs to see what the team tried before, because the reason it did not land is often the most useful input in the brief and shapes the first draft more than any style preference.

Finally, agree what handover looks like and who owns it. If the team expects templates and tone notes, say so at the start so the specialist builds them alongside the work rather than assembling them at the end. Handover planned early is more useful than a folder delivered after the engagement closes.

What the specialist can and cannot decide

The specialist can shape the message, choose the structure, and write the words. They can test whether a draft is clear to a reader who was not in the room. They can point out where a claim is unsupported or where two sections contradict each other, and they can propose a version that resolves the conflict.

They cannot decide regulatory approval, legal wording, or whether a product claim is accurate. In finance, healthcare, and other regulated sectors, the specialist keeps language within approved wording, but compliance review stays with your team. They also cannot decide company strategy or which audience matters most; that belongs to the people who own the business decision.

They cannot guarantee that a message will persuade, that a launch will succeed, or that a board will approve a plan. Communication improves clarity and structure, and the outcome still depends on the audience, the decision, and how the work is used. A specialist who promises results beyond the material is overstating what the work can do. Being clear about this boundary protects both sides.

Choosing the right level of seniority

Not every engagement needs the most senior specialist available. A single deck, a script, or a round of editing can be handled well by a specialist with solid craft and a clear brief. The work is bounded, the review is short, and the cost should reflect that.

Seniority matters more when the message is contested. If leaders disagree about what to say, if a restructure needs careful explanation, or if a launch narrative must hold across sales, support, and customers, experience with those situations changes the quality of the work. A senior specialist can run the session where the message is agreed, not only write the draft afterwards.

Match the level to the decision, not to the job title. A part-time engagement with a senior specialist may serve a change program better than a dedicated junior writer, and an hourly engagement with a strong editor may be enough for a document that only needs tightening.

Ask the specialist what they would need to see before quoting a timeline. A considered answer tells you more about fit than a list of past clients, and it shows whether they have done this kind of work before.

How to run the engagement well

Agree the review process at the start. Name who approves the message and who reviews the wording, and keep those two roles separate where possible.

Keep the specialist close to the source. If the message depends on a product decision or a policy change, give them access to the people who made it. Second-hand summaries lose the detail that makes a narrative credible, and the specialist ends up writing around a gap instead of filling it with something true.

Set review windows and hold them. A specialist working part-time or hourly needs to know when feedback will arrive so the schedule holds. When reviews slip, the work compresses at the end, and the final draft is weaker for reasons that have nothing to do with the specialist.

Review for the reader, not the room. The most common failure is a draft that satisfies everyone in the meeting and confuses the audience outside it. Test the material with someone who matches the audience, and treat their confusion as useful evidence rather than a problem to explain away.

Keeping the work useful after handover

Handover is part of the engagement, not an afterthought. Decide at the start what your team keeps: templates, tone notes, examples, or a short guide to the message structure.

Document the decisions, not only the deliverables. A note that explains why the audience was named, why the structure runs in a particular order, and what was rejected is more valuable than a folder of finished files. It lets the next person pick up the work without repeating the same debates.

Keep the examples that worked. A deck that landed, a mail that got a reply, a town hall script that held the room are all useful references. Store them where the team can find them, and label what made them work so the pattern can be repeated rather than guessed at.

Plan a short review after the engagement ends. Ask what the team reused, what they changed, and what they could not apply. That conversation is the cheapest way to learn whether the handover was real, and it tells you what to ask for the next time you brief a specialist.

Conclusion

A useful engagement leaves a brief the team can run, a short list of decisions, and a clear point where the work should stop. Keep the next step small enough that a hiring manager can approve it without inventing a larger programme, and measure the result by what the team can now do without help.