Programme managers are very much like translators and that is one of the least talked-about parts of programme management. Strategy into delivery. Vision into tasks. Leadership intent into team priorities. It’s not just about structure and governance. It’s about understanding what different people need to hear and helping them hear it in a way that makes sense to them. Sometimes that means explaining technical constraints in plain English. Sometimes it means giving leadership a reality check – tactfully. Sometimes it’s just noticing when two teams are saying the same thing in completely different ways.
Programme managers live in the in-between. They join the dots. They close the gaps. And they help organisations move forward by making sure everyone’s actually on the same page – not just pretending to be.
It’s not glamorous work. But it’s essential.
The comparison to translation work is more apt than most people realise. Professional translators don’t just convert words from one language to another – they translate meaning, context, and cultural nuance. They understand that direct word-for-word conversion often misses the point entirely. The same sentence can convey completely different messages depending on the audience, the setting, and the relationship between speaker and listener.
Programme managers operate in a similar landscape, but instead of navigating different languages, they’re navigating different professional dialects, organisational cultures, and cognitive frameworks. The CFO’s concern about “return on investment” and the developer’s worry about “technical debt” might be describing the same underlying issue, but they’re using completely different conceptual vocabularies to frame it.
This translation challenge becomes particularly acute in organisations where different functions have evolved their own ways of thinking and communicating. Sales teams speak in terms of opportunities and pipeline. Engineering teams discuss architecture and scalability. Marketing focuses on messaging and positioning. Finance talks about costs and margins. Each group has developed sophisticated ways of understanding their domain, but these specialised languages can become barriers when cross-functional collaboration is required.
The programme manager’s role in this context becomes that of a multilingual facilitator, someone who can understand the underlying concerns of each group whilst helping them communicate effectively with others. This requires more than just vocabulary translation – it demands understanding the mental models, priorities, and anxieties that shape how different groups perceive problems and solutions.
Consider a typical scenario where a technical team identifies a performance issue that requires significant architectural changes. The engineers might frame this as “refactoring to address scalability constraints,” whilst the business stakeholders hear “expensive delays with no visible customer benefit.” The programme manager’s translation work involves helping both sides understand that they’re actually discussing the same thing: how to ensure the product can handle future growth without compromising user experience.
This translation often involves what linguists call “cultural mediation” – helping each side understand not just what the other is saying, but why they’re saying it that way. The engineering team’s focus on technical elegance isn’t academic perfectionism; it’s professional responsibility for long-term system health. The business team’s concern about delivery timelines isn’t impatience; it’s accountability for market commitments and revenue targets.
The most effective programme managers develop a kind of contextual intelligence that allows them to adjust their communication style based on their audience’s needs, priorities, and cognitive preferences. When speaking with senior executives, they might emphasise strategic implications and business outcomes. When working with technical teams, they might focus on implementation challenges and resource requirements. When coordinating with operations, they might highlight process impacts and support implications.
This adaptation isn’t about manipulation or telling people what they want to hear. It’s about ensuring that important information gets communicated in ways that allow different audiences to understand and act upon it effectively. The same project update might need to be presented as a risk mitigation strategy to the board, a technical challenge to the engineering team, and a service delivery consideration to the operations group.
The translation work becomes particularly challenging when dealing with what organisational psychologists call “fundamental attribution errors” – the tendency for different groups to explain the same events in completely different ways. When a deadline is missed, sales might attribute it to engineering inefficiency, engineering might blame unrealistic requirements, and leadership might question project management effectiveness. The programme manager’s role is to help everyone see beyond these initial attributions to understand the systemic factors that contributed to the outcome.
Sometimes the most valuable translation work involves helping people recognise when they’re actually in violent agreement – saying the same thing using different terminology. I’ve watched teams spend hours debating approaches only to discover they were advocating for identical solutions described in different professional vocabularies. The programme manager who can spot these false disagreements and help teams recognise their alignment can save enormous amounts of time and relationship capital.
The emotional translation aspect of this work is equally important but often overlooked. Different organisational groups don’t just use different languages; they express concerns, excitement, and frustration in different ways. Technical teams might express anxiety about system reliability through detailed discussions of potential failure modes. Business teams might communicate the same anxiety through questions about competitive positioning and market timing. Understanding these emotional subtexts allows programme managers to address underlying concerns rather than just surface symptoms.
This emotional intelligence becomes crucial when delivering difficult messages or managing conflicting priorities. The same budget constraint might need to be communicated as a “strategic prioritisation opportunity” to senior leadership, a “resource allocation challenge” to project teams, and a “scope refinement requirement” to stakeholders. The facts remain the same, but the framing helps each audience understand how the constraint affects their specific concerns and responsibilities.
The programme manager’s position “in the in-between” creates unique visibility into organisational dynamics that others might miss. They see how information flows – or fails to flow – between different groups. They notice when strategic decisions aren’t translating into operational changes, when team priorities aren’t aligning with stated objectives, and when communication breakdowns are creating unnecessary friction.
This systems-level perspective allows programme managers to identify and address communication gaps before they become programme risks. They might notice that the design team’s assumptions about user behaviour don’t match the customer service team’s experience with actual users. They might spot that the marketing team’s messaging commitments aren’t technically feasible given current development constraints. They might observe that leadership’s vision for rapid scaling conflicts with the operations team’s capacity planning.
The translation work also involves helping organisations develop better communication habits over time. This might mean establishing common vocabularies for frequently discussed concepts, creating forums where different groups can share their perspectives directly, or implementing feedback mechanisms that help teams understand how their decisions impact other parts of the organisation.
One of the most challenging aspects of this translation role is managing situations where the translation reveals fundamental misalignments rather than simple communication gaps. Sometimes the programme manager discovers that different groups aren’t just using different words for the same concepts – they’re actually pursuing incompatible objectives or operating under contradictory assumptions about success.
When these deeper conflicts surface, the programme manager’s role shifts from translation to facilitation of difficult conversations. This might involve helping leadership teams recognise that their strategic priorities are in tension, supporting technical and business teams in finding acceptable compromises, or escalating decisions that require organisational clarity and alignment.
The skills required for effective translation work extend beyond traditional project management competencies. Programme managers need to develop cultural sensitivity to understand how different professional backgrounds shape communication preferences. They need emotional intelligence to recognise the feelings and concerns underlying different groups’ positions. They need systems thinking to understand how communication patterns affect organisational performance.
Perhaps most importantly, they need the intellectual humility to recognise when they don’t fully understand something and the curiosity to keep asking questions until clarity emerges. The best translators are those who remain genuinely interested in understanding different perspectives rather than rushing to premature synthesis.
The impact of effective translation work extends far beyond individual programme success. When programme managers help organisations communicate more effectively, they’re building capability that benefits future initiatives. Teams learn to anticipate translation needs, stakeholders develop appreciation for different perspectives, and the organisation becomes more resilient in the face of complexity and change.
This capability becomes particularly valuable during periods of rapid growth or transformation when new roles, processes, and priorities are constantly emerging. Organisations with strong translation capabilities can adapt more quickly because they can maintain effective communication even as their structures and strategies evolve.
The work is indeed unglamorous, but its absence creates visible problems quickly. Programmes drift when strategy doesn’t translate into clear action. Teams become frustrated when their concerns aren’t understood by other groups. Stakeholders lose confidence when they can’t see how their priorities are being addressed. Good translation work prevents these breakdowns before they occur.
Key Takeaways
Programme managers function as organisational translators, converting strategy into delivery, vision into tasks, and leadership intent into team priorities. This translation work goes far beyond vocabulary conversion – it requires understanding the mental models, priorities, and cultural contexts that shape how different groups perceive problems and solutions.
Effective translation involves contextual intelligence, adjusting communication style based on audience needs whilst ensuring important information gets communicated in ways that enable understanding and action. The same project update might need different framing for executives, technical teams, and operations groups, not to manipulate but to ensure effective comprehension.
The emotional dimension of translation work proves equally important, as different organisational groups express concerns, excitement, and frustration in distinct ways. Programme managers must recognise these emotional subtexts to address underlying concerns rather than just surface symptoms, particularly when delivering difficult messages or managing conflicting priorities.
The programme manager’s position “in the in-between” creates unique visibility into communication patterns and organisational dynamics that others might miss. This systems-level perspective allows them to identify and address communication gaps before they become programme risks, whilst helping organisations develop better communication habits over time. When translation work reveals fundamental misalignments rather than simple communication gaps, programme managers must shift from translation to facilitation of difficult conversations. The goal isn’t just individual programme success but building organisational capability that benefits future initiatives by improving how teams understand and communicate with each other across functional boundaries.