Is the gap between the way your technical teams communicate so vastly different from what your leadership needs to hear that you often rewrite their papers yourself – or edit them so much you may as well have?
This is because you naturally understand that you must not sacrifice technical accuracy and incur the wrath of your team (who will accuse you of ‘dumbing down' their work), but that you also must provide a clear sense of perspective and clarity about the context of the work for those who need to make the decisions.
While it is valid to think that in sitting between these two worlds you are well placed to translate for them, there are some practical things you can do to help your technical team communicate to non-technical audiences.
Here are three to get you started:
Appreciate that “writing” is not the same thing as “communicating” to an audience
Writing is a tool both for the writer to complete their own problem solving and sense-making as well as a tool for conveying ideas to another person.
It is vital that a writer learns to discern when they are communicating to themselves and when they are communicating for another person.
Understand what their audience really needs from them
Have a clear picture of the people they are communicating to: their interest (or lack of) in the writer's pet topic, existing biases, and purpose for wanting to hear from the writer in this particular instance.
Flip their early drafts on their head
When pouring out the first draft or two, writers so often describe their own problem solving journey: “we did this, found this and then did this and … and … etc.”
However, once a writer is more familiar with not just the journey itself, but what this journey told us, they can flip early drafts upside down and communicate the conclusion up front to address our audience's key concern.
Writers are ready to flip their writing to focus on their audience only when they can explain their key points to another person while ‘standing on our head' – not that I suggest you try it: explaining the main points to someone who is not a technical expert in less than a minute will do.
If you would like some more ideas that will help your technical team turn their communication on its head, take a look at Clarity Hub or read my books.
We teach individuals and groups how to communicate so that their good ideas get the traction they deserve.
Keywords: #design your strategy #develop your storyline
PRESENTED BY DAVINA STANLEY
I love what I do.
I help senior leaders and their teams prepare high-quality papers and presentations in a fraction of the time.
This involves 'nailing' the message that will quickly engage decision makers in the required outcome.
I leverage 25+ years' experience including
- learning structured thinking techniques at McKinsey in Hong Kong in the mid 1990s before coaching and training their teams globally as a freelancer for a further 15 years
- being approved to teach the Pyramid Principle by Barbara Minto in 2009
- helping CEOs, C-suite leaders and their reports deeply understand their stakeholder needs and communicate accordingly
- seeing leaders cut the number of times they review major papers by ~30% and teams cut the amount of time they take to prepare major papers by ~20%*
- watching senior meetings focus on substantive discussions and better decisions rather than trying to clarify the issue
My approach helps anyone who needs to engage senior leaders and Boards.
Recent clients include 7Eleven, KPMG, Mercer, Meta, Woolworths.
Learn more at www.clarityfirstprogram.com
(*) Numbers are based on 2023 client benchmarking results.
