Paul Manship

Wherever you are positioned in your Data or Tech role, you will undoubtedly recognise a situation when delivering projects, where someone just doesn’t get “it”. You might be attempting to articulate technical issues to non-technical stakeholders or are getting vague or ambiguous requirements from your business stakeholders. Is it a case of merely accepting that, sometimes, things just get lost in translation? It doesn’t have to be. As a Business Analyst with a tech and data focus, I’ve been accountable for many a scenario where miscommunications could have led to project catastrophes. Through this talk I want to share learning from my own experiences, good and bad, which will equip you with a toolbox of techniques that you can implement in your day to day to help avoid communication calamities. We will discuss the fundamentals of effective communication and my top tips for maintaining engagement and commitment. Covering some of my do’s and don’ts when approaching complex concepts of code and data with a non-technical audience. From the session you should: - Have a toolbox of techniques you can employ in day-to-day communications - Be more comfortable articulating data and tech to non-tech audiences and get better outcomes from these exchanges - Be aware of the support network and specialisms you can employ in managing communication with stakeholders.