- ✓Communication skills are consistently ranked by employers as among the most important competencies for digital professionals, often valued more highly than specific technical knowledge.
- ✓Professional written communication in a digital context includes the ability to write clear technical documentation, persuasive reports, concise emails and structured presentations for a range of audiences.
- ✓Transferable skills such as critical thinking, problem solving, collaboration and time management are genuinely transferable: they apply across roles, organisations and sectors throughout your career.
- ✓The ability to translate technical concepts into plain language that non-technical stakeholders can understand is a highly valued skill that differentiates effective digital professionals from purely technical ones.
- ✓Developing your communication skills is an active process that requires practice, feedback and a willingness to put yourself in situations that feel uncomfortable at first but build lasting confidence over time.
Listen to the full episode inside the course. Enrol to access all 80 episodes, plus assignments, tutor support and Student Finance funding.
Start learning →Alex: Hello again, and welcome to today's lesson of HTQ Digital Technologies: The Study Podcast. I'm Alex, and today Sam and I are talking about something that surprises a lot of people coming into a technical qualification: communication and transferable skills. Sam, why is this in a digital technology qualification?
Sam: Because it's one of the most important things that distinguishes effective digital professionals from merely technically competent ones. Employers consistently tell us that the graduates they find hardest to work with aren't necessarily the ones with the weakest technical skills. They're the ones who can't explain what they're doing, can't write clearly, can't present their work confidently or collaborate effectively with non-technical colleagues.
Alex: Let's break that down a bit. When we talk about communication skills for digital professionals, what does that actually include?
Sam: It's quite broad. There's written communication: being able to write a clear technical document, a business case, a project update, an email that conveys the right information without ambiguity. There's verbal communication: presenting to a room, explaining a technical concept to a non-technical audience, contributing effectively to meetings. There's visual communication: being able to present data clearly, design a diagram that actually helps people understand a system. And then there's listening, which people often forget to mention.
Alex: Listening as a communication skill. Can you expand on that?
Sam: Active listening, really understanding what someone is saying rather than just waiting for your turn to speak, is what enables you to give genuinely helpful technical advice, understand the real requirements behind a request and pick up on concerns that haven't been explicitly stated. Some of the most catastrophic project failures in digital technology happened because the technical team heard what the client said without really understanding what they meant.
Alex: And what about the term transferable skills? That sometimes sounds like a euphemism for soft skills, which can feel a bit vague.
Sam: I know what you mean, but I think the word transferable is the important one. These are skills that genuinely move with you across jobs, organisations and even careers. Critical thinking, the ability to break down a complex problem and reason through it systematically, is valuable whether you're debugging code, designing a data architecture or running a project. Problem solving, time management, collaboration, adaptability: these compound in value over a career in a way that narrow technical skills often don't.
Alex: Let's talk about the specific skill of translating technical ideas for a non-technical audience. This is something I know a lot of people struggle with.
Sam: It's a real craft, honestly. The instinct of technically-minded people is often to explain how something works rather than what it does and why it matters. But your stakeholders, whether they're senior managers, clients or users, typically need the second kind of explanation, not the first. A useful exercise is to explain a technical concept you're working with to someone outside technology and see where they look confused. That tells you where your explanation is dependent on knowledge that not everyone has.
Alex: That's a practical challenge. Have you got any other practical advice for developing these skills?
Sam: Yes. Write regularly. Even keeping a learning journal through this qualification builds writing fluency. Present where you can: volunteering to present at team meetings, study groups or professional events builds confidence more effectively than any other method. And seek feedback on your communication specifically, not just on your technical work. Most people get plenty of feedback on whether their code works and very little on whether their documentation is clear.
Alex: All really applicable advice. Thank you, Sam. These skills will serve learners throughout the whole qualification and well beyond it.