Author: timhjrogers

Assertive, Not Aggressive: The Real Art of Project Leadership

Why Tone, Trust, and Team Dynamics Matter More Than Ever

Project management has always been a delicate balance of delivering results while navigating relationships. But in today’s landscape—where remote teams, shifting priorities, and increased stakeholder scrutiny are the norm—the role of the project manager has evolved beyond schedules and status reports.

Now more than ever, how you lead matters as much as what you deliver.

The Fine Line: Assertiveness vs. Aggression

It’s common to hear project managers say, “I’m just being direct,” or “I have to be tough to get things done.” But there’s a critical distinction between being assertive—which is professional and productive—and being aggressive—which is damaging and demotivating.

Assertiveness is about setting expectations, communicating clearly, and holding people accountable with respect and empathy.
Aggression, on the other hand, uses pressure, fear, or blame to force compliance—often at the cost of morale and long-term outcomes.

Example:
Assertive:* “We agreed the testing would be complete by Friday. Is there a blocker I can help with to keep things on track?”
Aggressive:* “You’ve missed the deadline again—this isn’t acceptable.”

The difference isn’t just tone—it’s the underlying attitude: one builds trust; the other breaks it.

Managing Remote or Dispersed Teams

Remote project management adds further complexity:

Fewer non-verbal cues
Reliance on written tone
Time zone and cultural differences
Less “corridor conversation” to build rapport

This makes intentional communication essential. An assertive email can sound aggressive without context. A poorly timed message can undermine psychological safety. That’s why remote leadership needs clarity, empathy, and consistent follow-through.

Cross-Functional & Matrix Teams: Competing Priorities, Shared Resources

One of the biggest challenges in modern project management is working with matrixed teams—where the people you rely on don’t report to you, have their own departmental goals, and may be pulled in multiple directions.

In these environments:
Team members have dual loyalties: to the project and to their line managers
Departmental KPIs may conflict with project outcomes
Prioritization becomes a moving target, often shifting week to week
Authority is limited—you can influence, but rarely enforce

It’s easy to become frustrated or resort to pressure tactics—but this often backfires. Instead, the project manager must act as a diplomatic broker, not a commander.

What Helps:

Build strong relationships across departments
Acknowledge competing priorities—don’t ignore them
Be transparent about dependencies and risks early
Use clear documentation to track commitments and slippage
Stay professional under pressure, and avoid taking delays personally

And when tensions arise—as they inevitably will—don’t escalate emotionally.

Instead, escalate structurally.

That’s the role of the Project Board or Steering Group:

A well-functioning governance group can:
Resolve conflicts of priority
Reallocate resources
Reaffirm the project’s strategic value
Protect delivery timelines from external drift

Project managers don’t need to win every battle alone. They need to raise the right questions in the right forum, and let the governance structure do its job.

Final Thought

True leadership in project management isn’t about force—it’s about focus, finesse, and follow-through.

The best project managers aren’t the loudest voices in the room. They’re the ones people trust when things go wrong, listen to when things get tough, and rally behind when it’s time to deliver.

Be the leader who gets results and earns respect.

#ProjectManagement #RemoteLeadership #CrossFunctionalTeams #AssertiveCommunication #SteeringGroup #DeliveryLeadership #MatrixManagement #GovernanceMatters

The Culture Game: Traitors in the Team

A team-building experience exploring what strengthens or weakens organizational performance.

It is interesting how we sometimes by our behaviours undermine the things that we collectively are trying to accomplish. The game is meant to be light hearted (not cheating and lying) but instead explore which actions help or hinder, support or frustrate the people, process, performance and progress. A game that examines and discusses these issues openly (with the psychological safety that comes from a game) may be useful to thinking about them an means to adddress them. Not everyone will agree, but sometimes play provides the best learning.

Workshop Objective

To experience how hidden behaviors, misalignment, and lack of communication impact team culture and outcomes.
To surface what enables and what hinders team performance.
To build shared understanding of how to create psychological safety, transparency, and collaborative norms.

STRUCTURE (Under 4 Hours)

00:00–00:15 – Introduction & Setup

Welcome, set ground rules for psychological safety.
Explain theme: Inspired by The Traitors*, this is a fictional scenario to explore real-world teamwork dynamics.
Divide group into 2–4 teams of 4–6 people.
Secretly assign Traitors (1 per team, or 2 across all teams depending on group size). Traitors are given a mission: subtly hinder progress without being obvious.

00:15–01:00 – Task 1: “The Chain of Trust”

Activity: A problem-solving or process design task (e.g. assemble a prototype, design a basic workflow, or complete a team puzzle in a time limit).

Purpose:
Observe how people collaborate, lead, contribute—or undermine.
Watch how communication and trust flow.

Facilitator Notes:
The Traitor’s job is to slow the process subtly (misdirect, delay consensus, overcomplicate).
Debrief: What helped the team succeed or fail? Did they notice any strange behaviors? What could have made communication better?

01:00–01:45 – Task 2: “Cultural Values Auction”

Activity: Teams are given “culture coins” and must bid on organizational values (e.g. transparency, innovation, accountability, flexibility, loyalty). They must choose 5 and justify how these help their team succeed.

Twist: Traitors are told to argue for misaligned values (e.g. promote excessive hierarchy, risk-aversion, or silence).

Purpose:
Forces discussion about what cultural elements matter—and why.
Encourages reflection on misalignment.

Debrief:
Did the group agree easily or struggle?
Were some people more persuasive? Why?
What values actually align with our current or desired team culture?

01:45–02:15 – Round Table Elimination

Activity: Open discussion and then vote: Who do you suspect is a Traitor? Each team or the whole group votes. Traitors reveal themselves.

Debrief:
Were you surprised?
What clues were missed or misinterpreted?
How does this relate to real organizational culture—where dysfunction may go unnoticed?

02:15–03:30 – Group Reflection & Application

Guided questions:

1. What behaviors help us perform well as a team?
2. What hinders performance—even unintentionally?
3. What are the “silent saboteurs” in our real workplace? (e.g. unclear roles, lack of feedback, fear of conflict)
4. How do we deal with difficult team dynamics when they’re not obvious?
5. How can we surface misalignment without blame?

Optional Outputs:
A team charter or list of cultural commitments
Group creation of a “Code of Trust”
Culture radar (what we want more of / less of)

Key Themes You’ll Explore

Psychological safety vs. fear
Trust and betrayal (real or perceived)
Communication styles and groupthink
Values alignment and behavioral norms
Individual vs. collective responsibility

Materials Needed

Envelopes with role cards (Faithful / Traitor)
Task supplies (puzzle pieces, flipcharts, fake coins, printed value cards)
Voting cards or slips
Reflection worksheet / template

Group Size Recommendation

8 to 24 participants
Works best with 2–4 mixed teams
Optional: Have observers or rotating facilitators who report insights

The Invisible Workload: When Your Role Outgrows Your Job Description

Most of us have been there.

You start in a well-defined role, perhaps with a clear job description and a sense of what success looks like. But over time, as things change—staff leave, new initiatives emerge, or informal requests pile up—your responsibilities quietly multiply. You pick up tasks, support others, fill gaps, create systems, patch problems, and… suddenly, you’re the glue holding things together.

Yet, none of this is written down.

You’ve outgrown your job description, and so has your role. There’s no documentation, no handover plan, no SOPs. If you left tomorrow, no one would know half of what you do—or why you do it.

And still, no alarms go off until something breaks.

The Pattern Is Very Common

This is not unique. In fact, it’s a deeply familiar scenario across all sectors—from healthcare and public service to education and tech.

Here’s what typically happens:

1. Role Creep
People take on more because they can or because someone needs to. The job evolves quietly without formal recognition.

2. Invisible Knowledge
Key systems, routines, and contacts live only in someone’s head. When they leave, there’s no blueprint for what they were doing.

3. No Oversight or Standards
Tasks operate without documentation, metrics, or accountability. There’s often little clarity on what’s essential vs. historic.

4. Crisis Triggers Change
Only when someone goes on leave, resigns, or a new person steps in do we realize: We don’t really know what’s happening here.

5. Panic → Process Improvement
This leads to urgent “mapping” of current roles, services, and systems—often starting from scratch and under pressure.

Is It Time to Review What You Actually Do?

Here’s a simple self-checklist. If you answer “yes” to more than a couple of these, it might be time to hit pause and take stock.

Self-Assessment: Spot the Red Flags

Is your current role significantly different from the job description you were hired into?
Are you doing work that no one else knows how to do?
Do you routinely create workarounds or “just-in-case” solutions without documenting them?
Do people say, “We always ask [you] for that,” even though it’s not formally your responsibility?
If you took a week off, would tasks fall through the cracks?
Is there no clear successor or cover plan for your responsibilities?
Have you had to explain your job to your manager or colleagues more than once?
Are you unsure which of your tasks are essential, optional, or outdated?

If this sounds familiar, you’re not alone. It’s a common issue in many high-pressure or under-resourced environments. But it can—and should—be addressed.

What to Do Next: Practical First Steps

You don’t need a full-scale transformation program to start fixing this. Begin with small, structured steps:

1. Capture What You Actually Do

List your daily, weekly, and monthly tasks
Describe the purpose, frequency, and outcomes of each one
Note the systems used, people involved, and risks if not done

2. Create a Simple Task Summary Template

Use a standard format: Task Title, Purpose, Frequency, Inputs, Outputs, Success Criteria, etc.
Keep it high-level—this isn’t a training manual or SOP (yet)

3. Hold a Role Review Conversation

Meet with your manager or team lead to compare your task list with your formal job description
Ask: What should we ditch, delegate, document, or develop?

4. Decide What Needs Further Work

Which tasks need SOPs, workflows, or system support?
Where are the biggest risks or knowledge gaps?

5. Schedule a Routine Check-In

Roles evolve—so should documentation. Set an annual or biannual review to avoid repeat drift.

Final Thought

In many organizations, the greatest risks are hidden in plain sight—in the heads of capable people quietly doing untracked, unrecognised, but vital work. The sooner we surface and share that knowledge, the better.

And if you’re a leader, ask yourself: Do I know what my team actually does—or just what I think they do?

If you’re not sure, it’s time to find out—before someone leaves and takes your continuity with them.

\#WorkplaceWellbeing #ProcessImprovement #TaskMapping #OrganizationalHealth #PublicHealth #Leadership #RoleDrift #KnowledgeTransfer #SuccessionPlanning #InvisibleWorkload

Stakeholder Management: Aligning People, Purpose, and Process

Stakeholder management is more than just managing a list of names. It’s about navigating the subtle interplay of personalities, power, politics, and perception. Whether you’re leading a national programme or a community initiative, your ability to engage stakeholders can make or break the project.

Understanding the Types of Stakeholders

Stakeholders vary in their role, influence, and engagement. It helps to identify and group them:

* Project Participants: The people doing the work—analysts, developers, engineers.
* Project Recipients / Customers: Those who will use or benefit from the deliverables.
* Authority Holders: Regulators, directors, or executives who give approvals or set parameters.
* Advisors / Overseers: Board members, consultants, subject-matter experts.
* Bystanders / Onlookers: Internal or external parties with an interest, influence, or opinion.

Mapping these groups early allows for tailored engagement, expectation management, and alignment.

Mapping Influence and Interest

A key model in stakeholder management is the Power-Interest Grid (also known as Mendelow’s Matrix). It helps you classify stakeholders into four types:

* High Power, High Interest: Manage closely
* High Power, Low Interest: Keep satisfied
* Low Power, High Interest: Keep informed
* Low Power, Low Interest: Monitor with minimal effort

This tool enables you to prioritize communication, manage expectations, and allocate energy effectively.

Applying the RACI Model

The RACI framework helps clarify roles and responsibilities:

* Responsible – Who does the work
* Accountable – Who owns the outcome
* Consulted – Who must be asked or involved
* Informed – Who needs to be kept in the loop

Responsible vs. Accountable

While many people may be responsible, only one should be accountable to avoid blurred ownership. Confusing the two often leads to duplication, delays, or dropped balls.

Factoring in Personality: The DISC Model

Personality differences affect how stakeholders interpret information and respond to change. The DISC model provides a helpful framework:

* Dominant (D) – Fast-paced, results-oriented. Communicate directly, avoid fluff.
* Influential (I) – Sociable, optimistic. Use enthusiasm, stories, and group dynamics.
* Steady (S) – Loyal, calm. Be clear, patient, and empathetic.
* Conscientious (C) – Analytical, detail-driven. Offer logic, structure, and data.

Tailoring your approach to different personalities builds rapport, trust, and engagement.

Communication: Choosing the Right Channel

The *how* and *when* of communication matter as much as the *what*. Consider this spectrum:

Table

Communication Style	Best For
Face-to-Face	Trust-building, conflict resolution, empathy
Video Calls	Collaboration, decision-making, remote teams
Email / Written Docs	Clarity, records, formal approvals
Casual Conversations	Sensing sentiment, informal updates
Reports & Briefings	Governance, assurance, executive-level updates

Match your method to the message, and your formality to the context.

️ The Consequences of Poor Communication

Poor stakeholder management is often rooted in poor communication. The ripple effects include:

* Delays due to misunderstandings or missed expectations
* Cost Overruns from rework or misaligned scope
* Reduced Quality when needs aren’t clearly articulated
* Broken Trust if stakeholders feel excluded or ignored
* Inequity if dominant voices override diverse perspectives
* Governance Failures from unclear approvals or inadequate documentation

Communication isn’t just about speaking—it’s about *connecting* and *aligning*.

The Role of Emotional Intelligence

Projects are human systems. Leaders with high emotional intelligence (EQ) are better equipped to:

* Recognize and regulate stakeholder emotions
* De-escalate tension or resistance
* Foster psychological safety in stakeholder dialogue

It’s not just what you say, but how it *feels* to others.

Final Thoughts

Stakeholder management isn’t just a task—it’s a craft. It requires emotional insight, strategic mapping, flexible communication, and clear governance. You can have the best Gantt chart in the world, but if you ignore people, politics, and personalities, the project will struggle.

---

Possible Models and Tools

1. Salience Model

Classifies stakeholders based on:

* Power (ability to influence)
* Legitimacy (their stake is appropriate)
* Urgency (need for immediate attention)

Helps you prioritise stakeholders as:

* Dominant
* Dangerous
* Dependent
* Definitive

2. Engagement Matrix

Tracks stakeholder attitudes over time:

* Unaware
* Resistant
* Neutral
* Supportive
* Leading

Useful for monitoring change fatigue, enthusiasm, or resistance during long programmes.

3. Stakeholder Onion Diagram

Visualises proximity to the project:

* Core team
* Internal partners
* Indirect stakeholders
* External observers

This helps identify layers of influence and communication needs.

4. Stakeholder Circle

A visual tool showing influence and emotional proximity—who *feels* closest to the project even if they aren’t officially involved.

5. PMBOK Stakeholder Processes

A formal approach includes:

* Identify stakeholders
* Plan stakeholder engagement
* Manage engagement
* Monitor stakeholder engagement

Essential for large or regulated projects with formal controls and documentation.

Building Trust and Feedback Loops

Effective stakeholder management is not one-way:

* Set up feedback channels (surveys, retrospectives, open forums)
* Acknowledge feedback and show how it shaped the project
* Build relationships, not just transactions

Trust builds over time but can be lost in a moment. Transparency, consistency, and empathy are essential.

Striking the Balance Between Informal and Formal Communication in Project Management

In project management, one of the most challenging tasks is balancing informal relationships and formal documentation. Early in a project, much can be achieved through informal methods like face-to-face meetings, one-on-one discussions, and building trust. These approaches foster collaboration and flexibility, enabling quick resolution of issues. However, there comes a time when informal methods are no longer sufficient, and formal documentation is required, especially when risks or critical issues arise. Without proper documentation, relying solely on informal agreements can undermine governance and hinder decision-making, potentially leading to project failure.

The Need for Documentation: Knowing When to Formalize

As a project manager, it’s essential to recognize when informal discussions are no longer enough and formal documentation is necessary. A project that operates without sufficient documentation—where everything is agreed upon with a handshake or informal nod—lacks accountability and transparency. This can create a governance gap that severely impacts the project’s long-term success.

On the other hand, an over-bureaucratic approach, where every decision requires a lengthy memo or formal report, can become stifling and time-consuming. It’s important to find a balance: use formal documentation when necessary, but avoid unnecessary bureaucracy. Knowing when to escalate issues formally and when informal communication is enough is a key part of effective project management.

When to Formalize: Understanding the Tipping Point

Having observed various public inquiries and high-profile cases such as the Post Office Inquiry, COVID Inquiry, and documentaries like *Toxic Town*, I’ve developed a keen sense of when an issue is likely to escalate and require formal documentation. If you anticipate that a particular issue might come under scrutiny in a panel, review board, or even an inquiry, it’s time to formalize the matter.

Written documentation is essential not only for maintaining transparency but also for protecting all parties involved. It ensures that decisions are well-documented, enabling informed decisions at every level. Documenting issues in an impartial, fact-based manner allows those in positions of authority to take action. If an issue remains unresolved, escalation to the project board, oversight group, or relevant external bodies (e.g., HR, compliance teams, or regulatory authorities) is necessary.

Escalation: Knowing When to Raise the Alarm

Escalation becomes critical when an issue threatens the success of the project. It’s important to know when to formally escalate an issue rather than let it remain unaddressed. In these cases, written documentation is essential for transparency and accountability. However, it’s also vital that this escalation is approached objectively, focusing on the facts and risks rather than personal critique.

For example, if a project is at risk due to resource shortages, budget overruns, or regulatory concerns, formal reporting ensures that the issue is documented and that action can be taken. The escalation process should be systematic and objective, free from blame or personal attacks. The goal is to present the issue, outline its impact, and recommend solutions.

Conflict Management Styles and the Role of Organizational Culture

In project management, navigating conflict is often inevitable, especially when opinions differ regarding project risks, budgets, or timelines. Understanding conflict management styles is crucial for addressing disputes effectively without damaging professional relationships.

* Collaborating: This style seeks a win-win solution, with both parties working together to find a mutually beneficial outcome. This is often the preferred style for managing conflict in projects, as it fosters long-term cooperation and problem-solving.

* Compromising: Both parties give up something to reach an agreement. This approach is useful when a quick resolution is needed but may not be the best for addressing root issues in a project.

* Avoiding: Sometimes, avoiding a conflict can seem like the easiest option. However, when issues are ignored, they can escalate, impacting the project’s success.

* Accommodating: This involves giving in to the other party’s demands to maintain harmony. While it can be effective in the short term, it may lead to resentment or unaddressed problems in the long run.

* Competing: This is a more aggressive style where one party seeks to win at the expense of the other. While useful in high-stakes situations, it can damage relationships if overused.

The organizational culture also plays a key role in conflict management. A culture that values open communication, mutual respect, and collaboration will make managing dissent easier. On the other hand, a hierarchical or rigid organizational culture might discourage dissent and create an environment where important issues are ignored or downplayed. Acknowledging and adapting to an organization’s culture is essential for navigating conflicts and ensuring that issues are addressed in a timely and effective manner.

Dissenting Views and Project Governance

One of the tricky dynamics in project management is managing situations where your professional view differs from the project sponsor’s or the project board’s view. When should you assert your independent opinion, and when should you go along with the sponsor’s or board’s direction?

In an ideal world, project managers should be able to provide honest, professional assessments, even if those assessments challenge the prevailing viewpoint. However, in reality, dissent can be difficult, particularly when project managers are seen as mere reporters of others’ views rather than independent decision-makers. Striking the right balance between offering dissenting views and aligning with the sponsor’s direction is crucial.

A tragic example of the consequences of ignoring dissenting views is the Challenger Space Shuttle disaster, where engineers raised concerns about the launch temperature, but those concerns were ignored by senior management. This example underscores the importance of listening to dissent and giving it due weight when making critical decisions.

Typical Risks and Issues That Require Escalation

1. Resource Shortages: When a project lacks the necessary personnel, skills, or equipment, it can severely impact timelines and quality. These issues must be flagged early, with potential solutions and escalations to senior leadership.

2. Budget Overruns: If the project is at risk of exceeding its budget, this needs to be addressed promptly. Providing clear, data-backed reporting ensures stakeholders understand the financial risks and can take appropriate action.

3. Timeline Delays: If timelines are slipping, it’s vital to communicate the delay early to prevent any misunderstandings or unrealistic expectations.

4. Regulatory Compliance Issues: Non-compliance with regulations such as data protection, safety, or industry-specific rules can have significant legal and financial consequences. These must be immediately escalated to the relevant compliance or legal teams.

5. Risk to Project Deliverables: If key objectives or deliverables are in jeopardy, this requires immediate attention and formal documentation, ensuring the project can be reassessed or redirected if necessary.

Top Tips for Addressing These Issues

1. Be Proactive in Communication: Don’t wait for problems to escalate into crises. Regularly update stakeholders on potential risks, ensuring they are aware of the issues before they become urgent.

2. Document Issues Clearly and Concisely: When escalating issues, document them objectively with supporting data. Avoid blaming individuals and focus on the facts.

3. Use a Structured Escalation Process: Establish a clear and structured process for escalating issues, ensuring that all relevant stakeholders are informed and that actions are taken swiftly.

4. Foster a Culture of Open Communication: Encourage open dialogue with stakeholders, where issues are addressed early, and all parties can collaborate on solutions.

5. Balance Formality and Flexibility: Avoid overwhelming the project with bureaucracy, but ensure that critical issues are formally documented when necessary. Find the right balance based on the nature of the problem and the project’s context.

Conclusion

Navigating the balance between informal communication and formal documentation is a critical aspect of effective project management. Project managers must know when to escalate issues and when to maintain a flexible, informal approach. By using structured risk management frameworks, understanding conflict management styles, adapting to organizational culture, and fostering open communication, project managers can address problems effectively while maintaining strong relationships with stakeholders. Ultimately, the ability to manage conflict, escalate appropriately, and document issues ensures that projects are more likely to succeed, even when facing significant challenges.

Navigating the Tension Between Project Managers and Stakeholders: Managing Difficult Conversations and Maintaining Professionalism

In project management, one of the most challenging situations arises when project managers are tasked with reporting difficult realities: insufficient funds, resource shortages, and escalating risks. These issues can trigger defensiveness or cognitive dissonance among stakeholders, especially when the news is unwelcome. However, the role of the project manager is to act as a servant to the project, ensuring that risks are flagged, resources are adequate, and objectives are met. Despite this, project managers may find themselves in difficult situations where their reports are not well received, particularly when they are at odds with sponsors or other senior stakeholders.

Typical Scenarios

1. Under-Resourced Projects
A project manager might realize that the team lacks the necessary resources, whether in terms of personnel, skills, or budget. When presenting this issue to senior leadership, the project manager may encounter resistance, as stakeholders might feel that acknowledging these gaps will delay or derail the project. The cognitive dissonance occurs when leaders prefer to push ahead with the project, ignoring the problems in the hope that they will resolve themselves.

2. Budget Shortfalls
Often, a project manager is asked to complete a project within an unrealistic budget. When the project manager brings up the issue, they risk being seen as an obstacle to progress. Sponsors or senior leaders might feel that reporting financial issues is an unnecessary disruption or sign of incompetence, rather than a necessary step toward project success.

3. Unrealistic Timelines
Deadlines are a common point of tension in many projects. If the timelines are not feasible, a project manager may feel pressured to either meet the deadlines or be seen as incompetent. When they voice concerns about project delays, they risk appearing like a barrier to progress, especially if leadership is set on delivering the project on time.

4. Lack of Alignment and Support
Project managers sometimes face a disconnect between different departments, teams, or stakeholders. If communication and collaboration are insufficient, the project manager may find themselves reporting a lack of alignment—something that is often uncomfortable for those involved. Senior leadership might dismiss the concerns, particularly if it involves delicate interpersonal dynamics or interdepartmental politics.

Top Tips for Addressing These Challenges

1. Be Transparent and Data-Driven
When delivering unwelcome news, rely on objective data to support your claims. Providing evidence-based reports (e.g., resource utilization, budget tracking, timeline projections) helps establish credibility and makes it harder for stakeholders to dismiss concerns. Use visuals like charts, graphs, and forecasts to demonstrate the impact of issues clearly.

2. Frame the Message Constructively
Instead of merely presenting problems, offer potential solutions. Frame the discussion around risk mitigation and opportunity creation. For example, “We have identified some resource gaps that, if addressed now, will keep the project on track for delivery within the next quarter.” By focusing on solutions rather than just problems, you present yourself as a problem-solver rather than a barrier to progress.

3. Foster Collaborative Dialogue
When reporting problems, always invite open discussion and collaboration. For example, “Given these concerns, it would be helpful to explore potential options together.” Framing the conversation as a shared challenge fosters a collaborative approach to problem-solving and prevents you from becoming a scapegoat.

4. Maintain Professional Integrity
It’s critical not to compromise on professional ethics, especially when faced with pressure to overlook problems. Remaining objective, impartial, and transparent is essential. While managing relationships with stakeholders is important, your primary duty is to the project’s success and its integrity. Aligning your actions with professional standards is key to maintaining trust and respect, both within the team and with senior stakeholders.

5. Develop Supportive Relationships
Building strong relationships with sponsors and stakeholders can help create a more supportive environment for difficult conversations. As a project manager, you should be proactive in communicating with your sponsors regularly, not just when problems arise. By keeping them informed and involved throughout the project, you are more likely to gain their support when challenges emerge.

6. Know When to Escalate
If attempts to resolve issues through dialogue and collaboration fail, project managers must know when to escalate the matter. Escalating concerns doesn’t mean acting out of turn, but rather bringing attention to critical issues that require leadership intervention. Make sure to escalate professionally and with a clear explanation of the risks involved.

7. Seek Mentorship or External Support
Navigating the delicate balance of reporting risks while maintaining good relationships with sponsors can be daunting. Seeking mentorship from more experienced project managers or external advisors can help you gain insights into effective strategies for managing these complex dynamics.

Conclusion

Project managers often find themselves at the intersection of reporting difficult news and maintaining good relationships with stakeholders. The key to success lies in balancing transparency, professionalism, and constructive dialogue. By being data-driven, framing challenges constructively, and fostering collaboration, you can navigate these challenges effectively while maintaining trust and integrity. A project manager’s role is not just to manage the project but also to safeguard its success through careful, transparent communication—no matter how difficult the news may be.

Embracing Change: Navigating the Human Journey from Resistance to Acceptance

Change is often perceived as a daunting challenge, an obstacle that stirs resistance and uncertainty. Yet, the story of human progress is rich with examples of individuals and societies overcoming these fears and moving from resistance to acceptance. The journey of change is as much about psychological growth and collective experiences as it is about the external factors that shape our world. This article explores the evolution of our willingness to embrace change and the mechanisms that can facilitate or hinder this process.

Inspired by Psychological reactance to system-level policies before and after their implementation
https://www.pnas.org/doi/10.1073/pnas.2409907122

Thanks to Elizabet Gomes dos Santos
Doctorate Researcher UCL GBSH; Clinical Lead for Cancer Services and Screening; Consultant in Medical Oncology

Context…

I served as the project manager for the incorporation of Jersey Harbour, Jersey Airport, and Jersey Post Office, and was also a member of the Incorporation Steering Group for the incorporation of Jersey Telecoms. In this context, “incorporation” refers to the process of transforming a public sector department, traditionally led by politicians, into a private company governed by a board. However, the public sector, specifically the Treasury Department, typically retains majority or full ownership of the company. This model ensures continued public interest and oversight while granting the company commercial freedoms, such as the ability to borrow, engage in joint ventures, and pursue capital projects, which may have been challenging if the organization remained within the public sector.

TimHJRogers

MBA Management Consultant | Prince2 Project Manager, Agile Scrum Master | AMPG Change Practitioner | BeTheBusiness Mentor | ICF Trained Coach | Mediation Practitioner | 4 x GB Gold Medalist | First Aid for Mental Health | Certificate in Applied Therapeutic Skills

The Power of Trailblazers: From Impossible to Possible

One of the most striking examples of overcoming perceived limits is Roger Bannister’s groundbreaking achievement of breaking the 4-minute mile. Prior to Bannister’s success, the idea that humans could run a mile in under 4 minutes was considered physically impossible. However, once Bannister achieved this feat in 1954, the mental barrier that had been holding back other athletes was shattered. Not long after, numerous athletes followed suit, and the once impossible barrier was surpassed repeatedly.

This phenomenon is a key concept in change management. The idea that seeing a trailblazer succeed makes it easier for others to follow is consistent with Kotter’s 8-Step Change Model, which emphasizes the importance of creating a vision for change and rallying others around it. When Bannister demonstrated that the 4-minute mile was possible, he provided others with a clear vision and the confidence to pursue the same goal. This model illustrates how leadership, vision, and demonstrated success can catalyze widespread change, making it less intimidating for others to adopt new ways of thinking.

Suggested Reading: Kotter, J. P. (1996). *Leading Change*. Harvard Business Review Press.

The Evolutionary Basis of Resistance to Change

Humans are naturally cautious, a trait shaped by thousands of years of evolution. Our survival once depended on being vigilant for potential threats—whether it was a predator or an environmental shift. This instinct to avoid change is an evolutionary survival mechanism, hardwired into our psyche. However, as social creatures, we are also influenced by the behaviors of those around us.

The concept of cognitive dissonance—where individuals experience discomfort when their behaviors conflict with their beliefs—plays a role in why people resist change. When confronted with change, especially at the individual level, we feel the tension between what we’ve always known and the new ways of doing things. This discomfort is amplified when we lack examples of success. However, when others begin to embrace change, the pressure to follow suit increases. This is why change becomes more palatable when witnessed collectively, as seen in the COVID-19 pandemic, when entire industries were forced to adapt to remote work. With nearly every organization transitioning in the same direction, resistance decreased significantly.

Suggested Reading: Festinger, L. (1957). *A Theory of Cognitive Dissonance*. Stanford University Press.

The Role of Experience: Personal Growth Through Challenge

When individuals or organizations face significant challenges, they often come out stronger on the other side, with a transformed attitude toward risk. Consider the adventurer who, after reaching the summit of a mountain or traveling to the North Pole, feels a significant shift in their perception of what is possible. The arduous journey gives them the confidence to tackle smaller obstacles that once seemed insurmountable.

This change in perspective is essential for change management. When teams or organizations experience a successful transformation, it builds their confidence in their ability to manage future challenges. Hersey and Blanchard’s Situational Leadership Theory posits that as individuals and teams mature through experience, they become more capable of embracing and leading change. As people gain confidence and competence from overcoming previous challenges, they are more likely to embrace new challenges and take the initiative to lead future change efforts.

Suggested Reading: Hersey, P., & Blanchard, K. H. (1982). *Management of Organizational Behavior: Utilizing Human Resources* (5th ed.). Prentice Hall.

Safety in Numbers: Collective Change and Psychological Safety

Change is easier to navigate when we’re not alone in it. The concept of psychological safety, as discussed by Amy Edmondson, refers to the environment in which individuals feel comfortable taking risks, making mistakes, and offering new ideas without fear of judgment or retribution. During the COVID-19 pandemic, for example, the widespread shift to remote work across industries created a collective experience, providing psychological safety that made change feel less risky. As businesses and employees faced the same challenges, the fear of failure diminished, and the acceptance of change became easier.

Additionally, the Overton Window concept can shed light on this collective shift. By witnessing extreme shifts in the landscape—such as rapid adoption of digital transformation during the pandemic—individuals and organizations recalibrate their perception of what is acceptable. When society sees that drastic changes can be implemented successfully, more modest changes seem more achievable and easier to accept. This aligns with Lewin’s Change Management Model, which emphasizes the importance of unfreezing old behaviors before implementing new ones.

Suggested Reading: Edmondson, A. (1999). *Psychological Safety and Learning Behavior in Work Teams*. Administrative Science Quarterly, 44(2), 350-383.

Suggested Reading: Overton, J. (2008). *The Overton Window of Political Possibility*. The Mackinac Center for Public Policy.

Liminal Spaces and Archetypal Transitions

Humans undergo significant transitions in both personal and professional realms—transitions often marked by liminal spaces, moments of uncertainty between old and new identities. These spaces can be uncomfortable, as they represent periods of ambiguity where people are neither fully who they were nor fully who they will become. Archetypal transitions, such as moving from youth to adulthood or from working life to retirement, exemplify these liminal spaces.

In organizations, these transitions can manifest as employees move between roles, departments, or leadership positions. Similarly, in life, individuals often experience resistance to these transitions until they realize they are not alone in their journey. Peer pressure and collective experience play a critical role in facilitating these transitions. The support networks created by shared experiences—whether in professional organizations or social circles—offer the psychological safety needed to navigate these liminal spaces successfully.

Suggested Reading: Turner, V. (1969). *The Ritual Process: Structure and Anti-Structure*. Aldine Publishing.

Conclusion: Change as a Natural Part of the Human Journey

Change is not an isolated event but a continuous, evolving process that is deeply embedded in the human experience. Whether it’s overcoming a personal challenge, adopting new technologies, or shifting organizational cultures, change is necessary for growth and survival. As we look at the patterns of human behavior—caution, collective experience, personal growth, and psychological safety—we begin to see that the fear of change is often overcome by understanding and shared experience.

Leaders, trailblazers, and collective experiences all play vital roles in guiding organizations through change. By drawing inspiration from the experiences of others, embracing psychological safety, and supporting transitions through liminal spaces, we can move from resistance to acceptance. Ultimately, change is not something to fear but something to embrace—an opportunity for growth, innovation, and shared success.

Suggested Reading: Kotter, J. P. (1996). *Leading Change*. Harvard Business Review Press.

The Role of Culture in Project Management: How to Build Effective Project Teams

In project management, success often depends on more than just well-defined roles, clear goals, and tight controls. It’s also about the culture within the project delivery teams, as well as the broader organizational culture that the project is being delivered into. A strong project culture is essential for ensuring that the team follows through on plans and that projects stick when delivered. Without a culture that emphasizes accountability, time management, and cost-awareness, even the best-planned projects will struggle.

Culture Within Culture: A Complex Dynamic

One of the most interesting dynamics in project management is the idea of “culture within culture.” A project team may operate under one set of cultural norms, values, and practices, while the organization they are delivering into may have a completely different style of operation. This mismatch can cause friction, making it harder for the project to succeed. The challenge, however, is not necessarily in the project management practices themselves—such as tasks, budgets, or deliverables—but in aligning the mental models, attitudes, behaviors, and priorities of these two cultures.

In any organization, there are often multiple levels of culture at play. The culture of a team may differ from that of the broader department, and the department’s culture may not align with that of the organization as a whole. This reality is further complicated by the existence of different cultural dynamics between regional or international offices. It’s important to recognize that organizational culture is rarely one uniform entity. There are always subcultures that can influence the success or failure of a project.

Tools for Influence and Behavioral Change in Project Management

Understanding these cultural dynamics is crucial when managing projects, as it offers insight into how to influence behaviors both within the project team and within the receiving department. Various frameworks can help guide project managers in shaping the right cultural environment for successful project delivery.

Two such frameworks—MINDSPACE and LIMES—are rooted in behavioral economics and can provide useful strategies for shaping behaviors and managing cultural challenges in project management.

MINDSPACE: A Framework for Behavioral Change

The MINDSPACE framework is a tool from behavioral economics that helps project managers, marketers, and policymakers design interventions that influence people’s behaviors in positive ways. Here’s a breakdown of the components:

1. Messenger: The person delivering the message matters. People are more likely to be influenced by credible, authoritative, and trustworthy individuals.

2. Incentives: Positive and negative incentives drive behavior. Immediate rewards or the avoidance of loss can often be more motivating than delayed gains.

3. Norms: Social norms heavily influence behavior. People often conform to the actions of their peers, so emphasizing what others are doing can help encourage certain behaviors.

4. Defaults: People tend to stick with the default option because it’s easy. Setting beneficial default choices can lead to better outcomes.

5. Salience: Information that stands out and grabs attention is more likely to influence decisions.

6. Priming: Subtle cues can influence decisions. By exposing people to specific stimuli, you can guide their actions without them even realizing it.

7. Affect: Emotional responses are powerful. Positive emotions encourage behavior, while negative emotions can deter it.

8. Commitment: People are more likely to follow through with actions they’ve publicly committed to. Encouraging small commitments can lead to larger behavior changes.

9. Ego: People are motivated by the desire to maintain or enhance their self-image. Appealing to personal identity or status can drive action.

MINDSPACE is a particularly effective framework when planning communications within a project team or to the receiving organization, as it ensures that psychological and behavioral factors are taken into account.

LIMES: A Complementary Framework

Another useful framework for designing persuasive communications and managing cultural dynamics is LIMES, which stands for Losses, Information, Motivation, Emotion, and Social Influence. Here’s a closer look:

* Losses: People are often more motivated by the fear of loss than by potential gains. Framing messages around the avoidance of negative outcomes can be a powerful motivator.

* Information: Clear, actionable information is critical for driving behavior change. Providing the right level of detail helps people make informed decisions.

* Motivation: Tailoring messages to align with emotional and psychological needs can encourage action. This could be intrinsic motivation (e.g., personal growth) or extrinsic (e.g., rewards).

* Emotion: Emotional appeals are highly effective in influencing behavior. If a message resonates emotionally, it’s more likely to drive action.

* Social Influence: People are often influenced by the opinions and actions of others. Using social proof—such as testimonials or endorsements—can encourage individuals to align their behaviors with those around them.

Practical Applications in Project Management

Incorporating MINDSPACE and LIMES into your project management strategy can help guide cultural change, motivate your team, and prepare the receiving department for the upcoming changes. Whether it’s about creating an environment where accountability is a priority or aligning the culture of the project with the broader organization, these frameworks provide a systematic approach for influencing behavior and ensuring project success.

For instance, when delivering a project, you might:

* Incentivize progress by setting smaller, incremental rewards for achieving milestones.
* Use social influence to demonstrate that the majority of the team or organization supports a particular approach.
* Frame key decisions in terms of losses (e.g., the risk of not meeting deadlines or exceeding budgets), which could drive urgency and focus.
* Commit publicly to key deliverables, ensuring that team members hold each other accountable.

Conclusion: A Unified Culture is Key to Project Success

The intersection of organizational culture and project culture is crucial for successful project management. It’s not enough to have excellent plans and controls if the culture within the team and the receiving department doesn’t align with the objectives. By understanding and leveraging frameworks like MINDSPACE and LIMES, project managers can influence the behaviors of team members and stakeholders, aligning their goals and values to ensure smoother project delivery and lasting success.

References:

* MINDSPACE Framework: Dolan, P., Hallsworth, M., Halpern, D., King, D., & Vlaev, I. (2010). *MINDSPACE: Influencing behaviour for public policy*.
* LIMES Framework: R. Thaler & C. Sunstein, (2008). *Nudge: Improving Decisions About Health, Wealth, and Happiness*.

Project Management: Hands-On or Hands-Off? Finding the Right Approach for Your Organization

Project management can take many forms depending on the maturity of the organization and the scale and complexity of the projects being managed. In this post, I will explore the various levels of engagement within a Program Management Office (PMO) and discuss how each approach fits different organizational contexts.

1. Simple Reporting: The Basic PMO

At its most basic, a PMO simply tracks all active projects. It reports on the project owner, sponsor, budget, timescale, risk rating, and progress. This level of oversight ensures that the senior leadership team, executive board, or steering committee has visibility over all projects. Based on this, they can invite relevant project managers to discussions if any project is flagged amber or red, or if it’s approaching a significant milestone.

2. Objective Oversight: Moving Beyond Reporting

At the next level, the PMO offers more than just a status report. It provides an objective, dispassionate view on the project’s status, issues, and risks. This approach ensures that the PMO can challenge project managers with an independent perspective, guaranteeing that they receive an assessment free from personal biases and subjective opinions. The PMO now assumes a more hands-on role in business assurance, holding projects to account in a more active manner.

3. Proactive Support: Guiding and Mentoring

The PMO can evolve further by becoming an active participant in project success. In this layer, the PMO intervenes to provide guidance, support, and mentoring to project teams when difficulties arise. If requested by the project manager, project sponsor, or team, the PMO offers expertise to resolve issues or bolster weak areas. This approach is much more hands-on and focused on continuous support for project success.

4. Air Traffic Control: Coordinating Projects at Scale

At its most complex, the PMO provides not just templates and training but also takes on the role of overseeing the entire project portfolio. Acting like air traffic control, the PMO coordinates projects, ensuring they are properly aligned and that resources are allocated efficiently. While the project manager still maintains direct control over the project, the PMO’s responsibility extends to ensuring that all projects are running smoothly, preventing overlaps, and managing dependencies. This high level of oversight requires a deep understanding of organizational strategy and is critical for large-scale, interdependent projects.

Which Approach is Right for Your Organization?

The PMO’s role depends heavily on the maturity of the organization and the volume and complexity of its projects. A smaller organization may only need basic reporting and oversight, while a larger, more complex organization may benefit from the proactive support and coordination provided by a more hands-on PMO. Consider the needs of your organization and the scale of your projects to determine which approach will be most effective.

At the end of the day, there is no one-size-fits-all answer. The key is to tailor the PMO’s involvement to fit your organization’s specific needs and project environment.

What type of PMO do you have? How has it evolved in your organization? Let’s discuss in the comments!

The Cultural Challenges of Project Management: Why Accountability is Key to Success

Project management is often simplified as the ability to define tasks, allocate roles, and ensure things get done on time, on budget, and to specification. Through tools, templates, and training, we teach people how to manage these elements effectively. In many ways, project management is straightforward. However, the real challenge lies in the cultural aspects, which are often overlooked. In fact, we tend to treat project change and project delivery as separate from cultural change, but the two are inextricably linked.

The Role of Culture in Accountability

Consider the allocation of roles and responsibilities in a project. You might be clear about the tasks and timelines, but are you culturally ready to hold people accountable? For example, when you assign a task that will take 10 hours over the next four weeks, are team members culturally set up to take ownership and deliver it within the given timeframe? Or is there a prevailing mindset of, “We’ll get to it eventually” or “It’s not urgent because we have other things to focus on”?

This issue extends to budgeting as well. Are your team members culturally prepared to have tough conversations if something is over budget or if projections don’t align with expectations? Or do you find yourself in a situation where cost overruns are accepted without scrutiny, where contingency funds are used as a quick fix, or where requests for additional funds are seen as the easy solution?

Similarly, when it comes to contracts, are you firm on deliverables? Do you tie payments to clear criteria, ensuring payment is only made once the agreed-upon deliverables are fully met? Or do you find yourself being flexible, thinking that “we’ll sort it out later,” or accepting subpar work with the plan to flag it as a minor issue later?

Top Insights on Project Management and Accountability

1. Cultural Readiness Drives Accountability
Successful project management doesn’t just depend on clear plans and timelines—it depends on whether the team is culturally aligned to handle the challenges that come with accountability. A report by the Project Management Institute (PMI) shows that 80% of successful projects have a strong organizational culture that supports accountability.

2. Communication is a Key Factor
According to McKinsey’s research, poor communication is one of the top reasons why projects fail. Teams need clear, consistent communication not just about tasks, but about the level of accountability expected. Culturally ingraining open, honest, and sometimes difficult conversations about progress, challenges, and deliverables ensures clarity.

3. The Role of Trust and Integrity
A study by the Harvard Business Review highlights that trust in project teams directly correlates with their ability to meet deadlines and stay on budget. Trust is not built solely through positive interactions but also through the ability to have constructive, sometimes difficult conversations that hold team members accountable.

4. Cultural Resistance Can Lead to Delays and Cost Overruns
According to the PMI’s 2020 Pulse of the Profession report, 39% of projects fail due to poor project management practices related to lack of accountability, ineffective governance, and resistance to cultural shifts. This is especially true in environments where teams are not accustomed to open dialogue about shortcomings or performance.

Accountability in Project Management

Good project management is easy when everything is clear-cut. But without a culture that embraces accountability, it is nearly impossible to be successful. Success hinges on your team’s ability to follow through on tough conversations, maintain integrity, and hold themselves and others to high standards. It’s not about being rigid or combative; it’s about respecting the boundaries that ensure projects run smoothly and delivering what was promised.

A project’s plans, budgets, schedules, and tasks are essential—but all of this becomes meaningless if your culture is not set up for accountability. If your team is not prepared to face scrutiny, manage oversight, and maintain focus on performance and integrity, your project is destined to face dysfunction.

While relationships are key to project success, they should never overshadow accountability. Strong relationships are built on professionalism and respect, not on compromising standards to avoid difficult conversations. It’s not about being “happy and fun”—it’s about setting clear boundaries and respecting roles and responsibilities.

Top Tips for Success in Project Management and Accountability

1. Establish Clear Roles and Responsibilities from the Start
Ensure that every team member understands their role, the scope of their work, and the level of accountability they have. Define this early on, so there are no ambiguities that could derail the project later.

2. Encourage Honest, Open Communication
Create a culture where difficult conversations about delays, budget concerns, and performance can happen without fear of retribution. Foster an environment where feedback is welcomed, not feared.

3. Set Up Strong Governance and Monitoring Processes
Define project success criteria and ensure that progress is measured regularly. Use tools like KPIs, project dashboards, and regular check-ins to track performance and hold team members accountable.

4. Promote Integrity in Decision-Making
Project leaders must set the example by making decisions based on facts, not feelings, and ensuring that all stakeholders stick to the project’s terms. Accountability shouldn’t be watered down for the sake of relationships or convenience.

5. Celebrate Accountability, Not Just Results
Reward and recognize team members who step up, speak the truth, and hold themselves accountable. This creates a culture where people feel comfortable taking ownership, knowing they will be supported.

6. Balance Relationships with Results
Strong project teams thrive on good relationships, but not at the cost of accountability. Build a culture where respect is shown through clear boundaries, mutual understanding, and the collective drive to deliver.

Conclusion

Cultural readiness is the often-overlooked factor in successful project delivery. Accountability, integrity, and respect for the process are foundational to achieving project goals. By fostering a culture that values these principles, you can ensure that your project management processes lead to meaningful outcomes and high performance. Without the right cultural foundation, even the best-planned projects are at risk of failing.