Face to face / Online public schedule & onsite training. Restaurant lunch included at STL venues.
From £470 List price £650
Who is this course for? This course is tailor-made for professionals with a technical background who are looking to enhance their communication skills. Whether you’re an engineer, IT specialist, or in a scientific field, this course will equip you with the tools to effectively convey complex ideas in a clear, non-technical manner.

The Art of Simplifying Technical Communication
Understanding the barriers to effective communication in technical fields.
Strategies for breaking down complex ideas into simple, digestible content.
Personal Communication Profiling
Leveraging profiling tools to discover your unique communication style.
Tailoring your approach to suit diverse audiences and situations.
Emotional Intelligence in Communication
Harnessing emotional intelligence to foster stakeholder engagement.
Techniques for empathetic listening and response.
Mediums of Effective Communication
Selecting the appropriate channels for delivering your message.
Best practices for digital, verbal, and written communication.
Transparent Communication for Trust Building
Principles of open communication to build trust and rapport.
Case studies on transparency in corporate settings.
Negotiation and Conflict Resolution
Navigating negotiations to find mutually beneficial solutions.
Resolving conflicts through constructive communication techniques.
Stakeholder Engagement Strategies
Crafting communication plans that align with stakeholder interests.
Methods for maintaining long-term engagement and support.
Win/Win Solutions through Effective Communication
Frameworks for creating outcomes that benefit all parties involved.
Real-world examples of win/win success stories in technical environments.
Arguably, the most experienced and highest motivated trainers.
Training is held in our modern, comfortable, air-conditioned suites.
A hot lunch is provided at local restaurants near our venues:
Courses start at 9:30am.
Please aim to be with us for 9:15am.
Browse the sample menus and view joining information (how to get to our venues).
Available throughout the day:
Regular breaks throughout the day.
Contains unit objectives, exercises and space to write notes
Your questions answered on our support forum.
|
|
RiverStone International
Joseph Stone,
Analyst Programmer
Tony was a fantastic trainer in technical communication, the course covered many topics which I have found interesting and useful. I think that I will be thinking about it in my professional communication from this point.
Communication Skills Training for Technical People
| Next date | Location | Price |
|---|---|---|
| Fri 15 May | Bloomsbury | £470 |
| Fri 12 Jun | Online | £495 |
| Tue 16 Jun | Limehouse | £495 |
| Mon 13 Jul | Online | £495 |
| Wed 15 Jul | Bloomsbury | £495 |
| Wed 12 Aug | Online | £495 |
And 25 more dates...
Loading content...

Excellent
Duracell UK
Graham L
Presentation Skills
"Extremely helpful course. Well paced, never felt bored. No topic felt redundant. Andrew was extremely friendly and engaging. Good level of interaction between presenter and us. I definitely feel more confident after today. Would recommend it to anyone."
Tutorials and discussions on MS Office
MS Office tips to save you time
MS Office shortcut keys for all versions
Handy info on industry trends
Latest news & offers
Loading content...
Below are some extracts from our Communication Skills Training for Technical People manual.
1. Jargon and Technical Terminology
• Overuse of specialised terms can confuse non technical audiences.
• Example: “We need to refactor the monolithic architecture into microservices.”
2. Over Complexity
• Presenting too much detail at once can overwhelm the audience.
• Example: Explaining every component of a machine learning model.
3. Lack of Audience Awareness
• Not tailoring communication to the knowledge level of the listener leads to misunderstandings.
• Example: Using deep technical explanations with senior management.
4. Ambiguity and Vagueness
• Unclear language can lead to misinterpretation.
• Example: Saying “It should be fine.”
1. Use Plain Language
• Replace complex terms with simpler alternatives.
• Example: Instead of “latency issues,” say “delays in system response.”
2. Break Down Complex Ideas into Steps
• Present information in a logical sequence.
• Example: Steps for explaining an AI model.
3. Define Key Terms Upfront
• Introduce unfamiliar terms before using them.
• Example: “An API is a way for different systems to talk to each other.”
4. Use Analogies and Metaphors
• Relate technical concepts to everyday experiences.
• Example: “A firewall is like a security guard checking access.”
5. Focus on the Why and Impact
• Explain why something matters rather than just how it works.
6. Use Visual Aids
• Support explanations with images or diagrams.
7. Tailor Communication to the Audience
• Adjust complexity based on who is listening.
8. Use Active Voice and Concise Sentences
• Avoid unnecessary words and passive constructions.
Verbal Communication Best Practices
• Speak clearly and avoid excessive jargon.
• Use active listening.
• Confirm key decisions in writing afterward.
Written Communication Best Practices
• Use clear subject lines.
• Keep emails concise.
• Always proofread.
Digital Communication Best Practices
• Use group chats for quick discussions.
• Set clear boundaries for response expectations.
• Avoid sending important messages late at night.
Visual Communication Best Practices
• Keep diagrams simple.
• Label key components.
• Use consistent colours and formats.
Clarity
• Ensure your message is clear, structured, and easy to understand.
• Example replacement for vague messaging.
Honesty
• Avoid withholding important information or giving misleading details.
Consistency
• Delivering the same message across teams avoids misunderstandings.
Accountability
• Taking responsibility when things go wrong builds credibility.
1. Conflict Over Deadlines
• Example: A project manager pushes for an earlier delivery date while the technical team argues the timeline is unrealistic.
2. Technical vs Business Priorities
• Example: Teams disagree between quality and speed to market.
3. Disagreements Over Technical Solutions
• Example: Two developers propose different methods and cannot agree.
4. Communication Breakdowns with Non Technical Stakeholders
• Example: Difficulty explaining technical issues to non technical management.
• Make sure you have your facts straight before you begin.
• Prepare what you are going to say and why you are saying it.
• Gather solid examples of the behaviour you are addressing.
• Challenge your assumptions.
• Ask for advice or a different perspective.
• Process your emotions and handle the situation calmly.
• Ask questions, probe and listen.
• Use feedback techniques.
Call for assistance
We will call you back