Adapt Consulting Company

Black Cloud Thinking: Undermining Change in Organizations

“Black cloud thinking” is a strategic approach that focuses on resistance, obstruction, and creating confusion to prevent or undermine change initiatives in organizations. Drawing from principles of subterfuge and anarchy (as seen in the CIA’s manual on destabilization), this method can be used to intentionally derail or disrupt organizational change, particularly in service delivery.

While using these methods is neither ethical nor recommended for fostering positive change, understanding them can help identify and mitigate resistance tactics before they take root.

Key Tactics to Undermine Change

1. Confusion and Ambiguity

Goal: Create ambiguity around the change initiative, its objectives, and its benefits.
Methods:

Spread misinformation about the change process, making it unclear whether the changes are truly necessary or beneficial.
Use complex language or bureaucratic jargon that confuses employees and stakeholders, reducing clarity and hindering understanding.
Present conflicting messages from different levels of leadership, creating confusion about the overall direction of the change effort.
Impact: This tactic undermines trust in the change initiative and reduces the ability of employees to engage with it effectively.

2. Divide and Conquer

Goal: Foster division and mistrust among key stakeholders, team members, or departments.
Methods:

Exploit existing silos and rivalries within the organization to deepen divisions, suggesting that one group’s success is at the expense of another.
Pitting departments or key individuals against each other by promoting self-interest over the collective goal.
Discrediting certain individuals or teams that are advocating for the change, framing them as out of touch or unqualified.
Impact: This leads to internal conflict, reduces collaboration, and makes it difficult for the organization to work cohesively toward change.

3. Lack of Accountability

Goal: Make it difficult to assign clear ownership or responsibility for the change process.
Methods:

Encourage a culture where blame is avoided and no one takes ownership of the new initiatives.
Create ambiguity about who is responsible for specific aspects of the change, leading to finger-pointing when things go wrong.
Highlight failures without providing constructive feedback or solutions, ensuring that the blame is placed on the change initiative rather than addressing the root causes.
Impact: This leads to a lack of accountability, making it harder to measure progress or achieve success, as no one is directly accountable for the outcomes.

4. Procrastination and Delay

Goal: Slow down the change process to prevent progress or to exhaust the proponents of change.
Methods:

Create unnecessary obstacles, delays, or procedural hurdles that slow down decision-making and the implementation of change.
Force repeated meetings to discuss details already settled, increasing frustration and diminishing morale.
Disrupt communication channels, either through a lack of feedback or pushing for irrelevant details to be addressed.
Impact: This tactic wears down support for the change and delays progress, giving the impression that the initiative is ineffective or not urgent.

5. Appeal to Emotion

Goal: Stir up emotional resistance to the change process.
Methods:

Amplify fear, uncertainty, and doubt (FUD) regarding the implications of the change, suggesting that it will lead to job losses, additional stress, or a negative work environment.
Use personal anecdotes to undermine the rationale for the change, framing the change as a personal attack on certain individuals or groups.
Frame the change as unnecessary or overly disruptive, invoking nostalgia for the past and portraying the new direction as a threat to the status quo.
Impact: Emotional resistance causes individuals to act based on fear rather than reason, slowing the adoption of change and fostering anxiety within the organization.

6. Bureaucratization and Red Tape

Goal: Turn the change process into a bureaucratic nightmare.
Methods:

Introduce excessive documentation requirements and approval processes that slow down the pace of change.
Create policies and procedures that, while ostensibly meant to support the change, make the process so cumbersome that employees give up on following through.
Encourage layers of review and constant modification of plans without ever reaching a final decision or implementation.
Impact: This reduces the agility of the organization, frustrates employees, and undermines the momentum needed to drive the change forward.

7. Infiltration and Subversion

Goal: Actively sabotage the change process from within.
Methods:

Identify key supporters of the change initiative and subtly undermine their credibility or influence by spreading doubts or misrepresenting their motives.
Introduce competing projects or priorities that seem more pressing, effectively redirecting attention away from the change.
Use backchannel communication to sow discord, presenting alternative agendas that oppose the change while appearing to support the broader goals.
Impact: By planting seeds of doubt in key individuals or groups, this tactic fragments support for the change and disrupts efforts at rallying the organization behind the initiative.

8. Focus on Short-Term Disruptions

Goal: Overstate or magnify any short-term issues caused by the change.
Methods:

Highlight any early challenges or failures of the change process as evidence that the entire initiative is doomed to fail.
Create a narrative that emphasizes disruption, even if it is minor or temporary, making employees feel that the pain isn’t worth the potential gain.
Organize protests or dissent within the organization, making noise about the disruption caused by the changes to ensure that external stakeholders notice.
Impact: This tactic ensures that the organization focuses on the immediate pain of change rather than the long-term benefits, weakening morale and diminishing trust in leadership.

Conclusion

While using black cloud thinking to undermine change is an unethical and destructive approach, understanding these tactics is crucial for recognizing and addressing resistance in an organization. By fostering transparency, promoting clear communication, and involving employees in the change process, leaders can minimize the effectiveness of these resistance strategies and create a more collaborative, supportive environment for change. The best defense against these tactics is proactive engagement, clear ownership, and creating an atmosphere of trust and accountability.

What is Holacracy?

Holacracy is a system of organizational governance that distributes authority and decision-making across self-organizing teams, rather than relying on a traditional hierarchical structure. It aims to empower employees by giving them more autonomy, clarity about their roles, and a more flexible way to operate. Holacracy attempts to create a more agile and adaptable organization where decision-making is more decentralized and the usual rigid hierarchy is replaced with clear roles and structured processes.

Key Principles of Holacracy

1. Distributed Authority: In Holacracy, authority is distributed across roles rather than centralized in a hierarchy. Each individual holds specific roles within the organization, and these roles come with the authority to make decisions related to the responsibilities assigned to them. This is in stark contrast to traditional management structures where decision-making power resides with a few senior leaders.

2. Roles over Job Titles: Instead of traditional job titles, employees have a set of defined roles that are flexible and can change over time. A person may hold multiple roles, and each role comes with clear responsibilities. This helps avoid the rigidity of a fixed job title and allows individuals to contribute in ways that align with their skills and the organization’s needs.

3. Circle Structure: Holacracy organizes teams into circles, each of which is responsible for specific functions or projects within the organization. Circles have autonomy over their own decision-making, and members are encouraged to contribute and make decisions that impact their circle. Circles are interconnected, and each has a lead link to represent them in higher-level circles.

4. Governance and Tactical Meetings: Holacracy incorporates structured meetings to ensure transparency and effective decision-making. Governance meetings allow for the creation and modification of roles, policies, and responsibilities. Tactical meetings focus on solving day-to-day operational issues and ensuring that the work is getting done.

5. Transparent and Dynamic Roles: The roles within a Holacracy system are clearly defined, with expectations outlined for each one. These roles are dynamic and can evolve based on the organization’s needs and the individuals in those roles. This helps organizations stay agile and responsive.

6. Clear Decision-Making Process: In a Holacracy, decisions are made based on what is best for the organization, rather than who holds the most authority. The process ensures that decisions are made quickly and with input from those directly involved or impacted, ensuring that there is less bureaucracy and faster decision-making.

Advantages of Holacracy

1. Empowerment: By giving employees more autonomy and control over their roles and responsibilities, Holacracy fosters a greater sense of ownership and accountability. People have the authority to make decisions within their scope, which can lead to increased job satisfaction and motivation.

2. Agility: Because the structure is decentralized, Holacracy allows for more rapid adjustments to changes in the business environment. Smaller, self-organizing teams can pivot quickly without needing approval from a centralized authority, making the organization more adaptable.

3. Clarity: Holacracy provides clarity around roles, responsibilities, and decision-making processes. Everyone knows what they are responsible for, which reduces confusion and increases accountability.

4. Collaboration: Holacracy encourages collaboration and communication among teams. Since decisions are made within circles and cross-functional teams, employees often have to work together to solve problems, fostering a more collaborative culture.

Challenges of Holacracy

1. Initial Complexity: Holacracy can be difficult to implement and requires significant training and a mindset shift. Employees used to traditional hierarchical structures may find it challenging to adapt to the new system, and organizations may face resistance in the early stages.

2. Implementation Costs: The transition to a Holacracy system often requires time, effort, and resources to redesign processes, roles, and meetings. This investment can be challenging for smaller organizations or those with limited resources.

3. Potential for Over-Structure: While Holacracy aims to eliminate bureaucracy, some critics argue that it introduces its own form of over-structure, with its many rules, meetings, and processes. This can potentially lead to an over-reliance on the system and reduce flexibility in some areas.

4. Confusion in Large Organizations: As organizations grow, the complexity of managing and coordinating numerous circles and roles can become overwhelming. The system works best in smaller to mid-sized organizations where roles can be more fluid and flexible, but it may struggle to scale in larger, more complex environments.

Examples of Holacracy in Practice

* Zappos: One of the most well-known companies to adopt Holacracy is Zappos, the online retailer. Zappos implemented Holacracy in 2014 in an attempt to create a more agile and innovative organization. However, the shift was met with resistance, and the company has since modified the approach to better fit their unique culture.

* Medium: The blogging platform Medium also experimented with Holacracy. While they initially embraced it, they later adjusted their approach. Medium’s journey with Holacracy highlights both the potential benefits and challenges of implementing a decentralized governance system at scale.

* The Morning Star Company: A company in the tomato-processing industry, The Morning Star Company, has been using a form of self-management for years that is similar to Holacracy. This system has helped them maintain high levels of innovation and employee satisfaction.

Conclusion

Holacracy represents a radical departure from traditional organizational structures. It has the potential to make organizations more agile, collaborative, and empowering by decentralizing decision-making and providing clarity around roles and responsibilities. However, its complexity, particularly in large organizations, and the challenges involved in transitioning to such a system should not be underestimated. While it offers significant advantages for smaller or more agile companies, larger organizations need to carefully consider the scalability and the necessary support structures before implementing Holacracy.

Co-Creation in Organizational Design: The Power and Limits of Collaboration

As an advocate for co-production, collaboration, cooperation, and teamwork, I’ve witnessed firsthand how these principles drive success, especially when applied to product and service design. Small, agile teams excel when collaboration is at the core of their operations. However, while I am a strong believer in co-production and teamwork for driving innovation, I remain cautious about applying the principle of co-creation at the scale of an entire organization, particularly large ones.

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.

The Case for Co-Creation in Small Teams

Co-creation works effectively when a small, focused group collaborates to design a product or service. For example, Airbnb’s early success came from co-creating their platform with users in small teams, ensuring that feedback directly influenced the product. This allowed the co-founders to remain agile and responsive to user needs. Small teams, by nature, are dynamic, flexible, and capable of making quick decisions. Communication is direct, relationships are close, and feedback loops are short—factors that enable rapid iteration and clearer alignment on goals. This has long been advocated by thinkers such as Clayton Christensen, whose work in *The Innovator’s Dilemma* emphasizes that innovation is often driven by small, nimble teams.

Studies, such as Hackman’s (2002) research on group dynamics, reinforce the idea that smaller teams outperform larger ones in terms of collaboration and decision-making. In these environments, cooperation is seamless, which fosters a greater sense of collective ownership. This makes co-creation highly effective for new ventures and early-stage product design.

The Challenge of Co-Creation in Large Organizations

While co-creation may flourish in small teams, it faces significant obstacles when scaled to larger organizations. A company with hundreds or thousands of employees presents challenges that smaller teams do not experience. The dynamics that make small teams effective—clear communication, fast decision-making, and shared values—become much more complex as the size of the team increases.

1. Communication Breakdown: As Tushman & O’Reilly (1996) noted in their research on organizational ambidexterity, larger teams face difficulties in balancing innovation with efficiency due to structural and communication barriers. In large organizations, communication often becomes fragmented. Multiple factions, departments, and hierarchical layers complicate the flow of information. This makes it harder to align on shared goals and slows down decision-making. Zappos’ adoption of Holacracy provides an example where decentralized decision-making attempts to address these issues. However, despite its promise, Holacracy faces its own set of challenges in maintaining coherent communication across a large, diverse workforce.

2. Diversity of Interests and Perspectives: Large teams naturally have diverse interests, which can lead to fragmentation. Different departments and teams will have competing priorities, making collaboration difficult. Geert Hofstede’s Cultural Dimensions Theory highlights how differences in national culture, department culture, and personal values affect communication within large organizations. This cultural fragmentation can dilute the effectiveness of co-creation efforts.

3. Slower Decision-Making: The Agile methodology, known for its flexibility in smaller teams, has also been adapted in larger organizations like Spotify to maintain a focus on collaboration. However, the larger the organization, the slower the decision-making process becomes. In a large organization, co-creation may require too many decision-makers or too many layers of approval, reducing its effectiveness. Hackman (2002) also found that in larger teams, the overhead of managing diverse opinions and feedback often results in delayed outcomes.

4. Cultural Fragmentation: A unified organizational culture can be difficult to maintain as a company grows. In large organizations, subcultures can emerge in different departments or regions, which can hinder collaboration and co-creation efforts. This makes aligning values and goals across the entire organization particularly challenging. Chris Argyris’ work on organizational learning also highlights how, in large organizations, the internal silos can lead to “defensive routines” that block open communication, a key aspect of co-creation.

The Limits of Co-Creation in Large-Scale Design

While co-creation has proven successful in the early stages of product and service design, the application of this process to an entire organization presents significant challenges. The idea of co-creating a large organization of 1,000 people is impractical due to the complexities of communication, coordination, and decision-making. The growth of the organization inherently introduces more layers of communication, slower decision-making processes, and more fragmented interests, making true co-creation at scale nearly impossible.

Large-Scale Co-Creation Models

While traditional co-creation in large organizations is challenging, there are frameworks and models that attempt to reconcile large-scale collaboration:

* Agile Methodology: Some large companies, like Spotify and ING, have adopted Agile practices to maintain flexibility and collaboration despite their size. Agile emphasizes short feedback loops, decentralized decision-making, and iterative improvements, allowing for co-creation within smaller teams while keeping the broader organizational goals aligned. However, scaling this approach across an entire organization requires careful consideration of how teams interact and share insights.

* Decentralized Decision-Making (Holacracy): As seen with Zappos, Holacracy is an attempt to decentralize decision-making and give teams more autonomy. While this can facilitate greater participation in decision-making, it is not a silver bullet for large organizations. The key challenge remains balancing autonomy with the need for a unified organizational strategy.

See Holacracy

These models demonstrate that while co-creation may be difficult at an organizational level, it is not entirely unfeasible if framed appropriately within smaller, more autonomous teams.

Conclusion: Balancing Co-Creation with Leadership

Co-creation is a powerful tool for innovation and growth, especially in smaller teams where communication and decision-making are straightforward. As organizations scale, however, the effectiveness of co-creation diminishes due to structural complexities. That said, leadership still plays a critical role in fostering a culture of collaboration, even in larger organizations. By leveraging models like Agile and Holacracy and focusing on smaller, more manageable teams, companies can still create environments that encourage innovation while maintaining the focus and direction needed for success.

Leaders in large organizations should strike a balance between maintaining centralized control and allowing decentralized decision-making within smaller teams. By understanding the limits of co-creation at scale and applying collaborative processes in appropriate contexts, organizations can thrive while staying true to the principles of teamwork and collaboration.

The Value of Process Improvement Workshops: Building Stronger Teams and Solving Real Problems

Process improvement workshops provide organizations with an opportunity to tackle issues head-on, enhance team collaboration, and drive measurable results. By combining team-building activities with problem-solving techniques, these workshops foster ownership, accountability, and empowerment, while also addressing immediate challenges. Below, we explore the benefits of these workshops for individuals, teams, and the organization as a whole.

1. Clear Problem Definition with Leadership

The first step in any process improvement workshop is to collaborate with leadership to clearly define the problem to be addressed. By setting specific parameters—such as a budget, timeline, and measurable benefits—teams can focus their efforts on finding practical, actionable solutions. For instance, a team may be tasked with identifying a process improvement that saves £25k within 12 weeks, using only internal resources.

2. Skill Development and Empowerment

Process improvement workshops offer significant personal benefits for participants. By working on real-world problems, individuals develop essential skills in problem-solving, critical thinking, and project management. This hands-on experience empowers employees, providing them with the confidence and tools to contribute meaningfully to the organization’s success. Furthermore, team members develop a sense of ownership, which leads to increased accountability and higher job satisfaction.

3. Enhanced Collaboration and Team Dynamics

The team-building nature of these workshops creates opportunities for participants to improve their collaborative skills. When team members from diverse functions come together to solve problems, they build stronger interpersonal relationships and enhance team cohesion. This collective problem-solving fosters a culture of open communication and mutual respect, resulting in a more productive and engaged workforce.

4. Innovation and Efficiency in Process Improvement

Workshops focused on process improvement encourage innovative thinking. By analyzing existing workflows and identifying inefficiencies, teams can propose creative solutions that streamline operations. The structured approach also ensures that improvements are sustainable, as they are rooted in a clear understanding of both the problem and the solution. As a result, processes become more efficient, and the organization benefits from increased productivity and reduced costs.

5. Cost Savings and Strategic Alignment

One of the key benefits of process improvement workshops is the potential for cost savings. By identifying inefficiencies or areas of waste, teams can propose solutions that deliver measurable financial benefits. Moreover, the solutions developed during the workshop are designed with strategic alignment in mind. This ensures that proposed changes support the organization’s long-term goals, maintaining coherence with overarching business objectives.

6. Employee Engagement and Organizational Learning

Process improvement workshops drive employee engagement by actively involving team members in decision-making. This engagement not only enhances job satisfaction but also contributes to the development of a learning culture. As teams review their results and gather lessons learned, the organization as a whole benefits from a continuous feedback loop, which improves future performance. Employees are empowered to take on new challenges, which fosters a culture of growth and development.

7. Scalability and Consistency

Another significant advantage of process improvement workshops is their scalability. The framework can be applied to a variety of challenges across different departments, ensuring consistency in problem-solving and project delivery. Whether addressing operational inefficiencies, resource allocation, or customer service improvements, the methodology provides a repeatable, adaptable approach to resolving issues.

8. A Comprehensive and Actionable Plan

At the conclusion of the workshop, the team compiles all gathered information into a comprehensive proposal. This proposal includes a clear description of the current process, identified issues, proposed solutions, and a detailed action plan for implementation. With a clear set of deliverables and a defined timeline, the workshop provides both leadership and participants with a structured pathway for moving forward. The final presentation to leadership ensures that there is clarity around costs, benefits, and responsibilities, enabling swift decision-making and project approval.

Conclusion: A Transformative Approach to Problem Solving

In conclusion, process improvement workshops deliver value far beyond addressing specific problems. By empowering teams, enhancing skills, and fostering collaboration, they contribute to a culture of continuous improvement. Whether focused on streamlining processes, reducing costs, or boosting team morale, these workshops align with organizational goals, providing a measurable return on investment. Moreover, they help build a more agile, innovative, and engaged workforce, positioning the organization for long-term success.

This integrated approach is not just about solving problems; it’s about developing the team’s capacity to solve future challenges, driving sustained growth, and continuously refining processes for optimal efficiency and performance.

Some resources if you are interested in finding out more.

https://www.adaptconsultingcompany.com/product-workout/
https://www.adaptconsultingcompany.com/problem-solving-and-process-improvement-tools/

The Power of a Simple Spreadsheet for Project Prioritization and Impact Analysis

In any organization, managing multiple projects simultaneously can be a daunting task. Whether you’re overseeing a series of initiatives, leading teams, or supporting stakeholders, it’s essential to have a clear and simple way of tracking progress, prioritizing tasks, and understanding the collective impact of each project on your team and business. A well-structured project management spreadsheet can be a powerful tool for gaining visibility into all the moving parts of your organization’s projects.

A spreadsheet doesn’t have to be complex or overwhelming—it’s a straightforward tool that can help you and your colleagues quickly understand the status, needs, and dependencies of projects, allowing for better decision-making and resource allocation. Here’s why the information captured in your project management spreadsheet is valuable and why sharing it with your colleagues is crucial to understanding and prioritizing projects.

Key Components of Your Project Management Spreadsheet

Here’s a breakdown of the essential components that should be included in the rows of your Excel sheet and why each one is important:

1. ID

What it is: A unique identifier for each project.
Example: 001, 002, 003
Why it’s useful: It helps to clearly distinguish each project, making it easier to reference and track specific projects, especially in large organizations.

2. Project Name

What it is: The title of the project.
Example: “Website Redesign”, “Customer Onboarding Process”
Why it’s useful: The project name provides a clear reference to the project’s purpose, making it easy to understand at a glance.

3. Summary Description

What it is: A brief overview of the project’s goals and objectives.
Example: “Redesign the company website for better user experience.”
Why it’s useful: Provides context for the project, helping stakeholders and team members understand its purpose quickly.

4. Sponsor

What it is: The senior leader or key stakeholder responsible for the project.
Example: “John Doe, CEO”
Why it’s useful: Identifying the sponsor ensures accountability and provides a point of contact for strategic decisions.

5. Project Manager

What it is: The person managing the day-to-day aspects of the project.
Example: “Jane Smith, Senior Project Manager”
Why it’s useful: Ensures that someone is accountable for managing the project’s execution, timelines, and resources.

6. Start Date

What it is: The date when the project officially begins.
Example: “01/01/2025”
Why it’s useful: Allows you to track when the project starts, which is crucial for scheduling, comparing with other projects, and monitoring deadlines.

7. End Date

What it is: The date when the project is expected or has been completed.
Example: “31/12/2025”
Why it’s useful: Helps manage expectations around when the project will be finished and ensures that timelines are being met.

8. Stage

What it is: The current phase of the project (e.g., Mandate, Initiation, Execution, Close, Review).
Example: “Execution”
Why it’s useful: Knowing the project’s stage provides insights into its progress and helps manage tasks effectively.

9. Status (RAG)

What it is: The status of the project, often represented by Red, Amber, or Green (RAG).
Example: “Green”
Why it’s useful: RAG statuses give a quick snapshot of the project’s health—whether it’s on track (Green), at risk (Amber), or off track (Red).

10. Priority

What it is: The level of importance of the project.
Example: “High”, “Medium”, “Low”
Why it’s useful: Helps to determine which projects should be prioritized when resources are limited and ensures focus on the most impactful projects.

11. KPI (Key Performance Indicators)

What it is: Metrics that measure the project’s success and progress.
Example: “Increase website traffic by 30%”
Why it’s useful: Provides measurable outcomes for tracking the project’s effectiveness and success.

12. Last Update

What it is: The date of the most recent update to the project’s status.
Example: “15/04/2025”
Why it’s useful: Keeps the team and stakeholders informed of the most recent developments and ensures that everyone is working with the latest information.

13. Budget Code

What it is: The unique identifier for the budget or financial tracking associated with the project.
Example: “BC1001”
Why it’s useful: Helps link the project to its financial tracking system, ensuring accurate monitoring of project finances.

14. Budget

What it is: The total allocated budget for the project.
Example: “\$50,000”
Why it’s useful: Provides insight into the financial resources available for the project and helps track costs against the budget.

15. Actual Spend

What it is: The amount of money already spent on the project.
Example: “\$20,000”
Why it’s useful: Shows the financial progress of the project and helps in identifying any cost overruns or savings.

16. Forecasted Spend

What it is: An estimate of how much will be spent by the project’s completion.
Example: “\$45,000”
Why it’s useful: Helps anticipate any potential financial gaps or savings by the end of the project.

17. Variance

What it is: The difference between the budgeted amount and the actual spend.
Example: “\$5,000 over budget”
Why it’s useful: Identifying variances early allows for corrective actions to keep the project on financial track.

18. Risk Rating

What it is: The level of risk associated with the project, often represented by Red, Amber, or Green (RAG).
Example: “Amber”
Why it’s useful: Provides an early warning system to identify which projects are at risk and need attention.

19. Resource Allocation

What it is: The allocation of resources (e.g., personnel, equipment, etc.) for the project.
Example: “JS, AB, MK” (team members’ initials)
Why it’s useful: Ensures that the necessary resources are assigned to the project, and helps track whether resource allocation is aligned with project priorities.

20. Milestones

What it is: Key project achievements or deliverables, marked by specific dates.
Example: “First draft completed by 01/06/2025”
Why it’s useful: Milestones break the project into manageable parts and offer a clear view of progress and upcoming goals.

21. Completion Date

What it is: The date on which the project is either completed or is expected to be completed.
Example: “30/12/2025”
Why it’s useful: Allows for proper scheduling and aligns the project’s timeline with other organizational activities.

22. Owner

What it is: The person responsible for the overall success of the project.
Example: “John Smith”
Why it’s useful: Ensures clear accountability and a point of contact for the project’s management and execution.

23. Lessons Learned

What it is: A reflection on what worked well and what didn’t, noted either during or after the project.
Example: “Yes” or “No”
Why it’s useful: Helps capture insights for future projects to avoid repeating mistakes and foster continuous improvement.

24. Post-Project Review Date

What it is: A scheduled date to review the project after its completion.
Example: “15/01/2026”
Why it’s useful: Provides an opportunity to evaluate the project’s overall success, identify improvements, and ensure that any follow-up actions are addressed.

Why Sharing This Information Is Crucial

By sharing a simple but comprehensive project tracking spreadsheet with your colleagues, you provide a clear overview of the key projects happening in your organization. This transparency fosters better decision-making, as everyone involved has access to the same information about the progress, costs, and impact of projects.

Moreover, understanding dependencies and constraints is essential—especially when projects are interdependent. For instance, foundational work may need to be completed before other initiatives can proceed. Without visibility into these connections, there’s a risk that some projects may be delayed or executed in the wrong order. By clearly showing which projects must come first, you ensure that the right resources are available at the right time.

In summary, a well-organized project management spreadsheet is more than just a tool for tracking—it’s an essential resource for prioritizing projects, allocating resources, and ensuring that all initiatives align with organizational goals and cash flow. It provides a collective understanding of what’s happening across the business, helping everyone make informed decisions that ultimately lead to greater success and efficiency.

Sharing this information builds a culture of collaboration and ensures that everyone understands not only what’s happening but also how their work fits into the broader organizational strategy. Let’s embrace the power of simplicity and start using this tool to manage projects with confidence.

#ProjectManagement #Excel #PMO #ProjectPrioritization #ResourceAllocation #BusinessStrategy #Collaboration #BusinessEfficiency #Leadership #ProjectTracking

Beyond Winning: Conflict as a Path to Understanding, Not Defeat

Conflict is inevitable. How we respond to it—whether we seek to win, avoid, adapt, confront, or collaborate—says a lot about our values, our self-awareness, and our ability to co-exist with difference.

My own conflict profile shows a strong preference for cooperation, backed by adaptation, and occasionally avoidance. I approach conflict not as a zero-sum battle, but as an opportunity to build bridges. I rarely, if ever, use destructive confrontation, and compromise is not my default route either. That may seem paradoxical. If I don’t want to dominate or split the difference, what exactly am I doing?

The answer lies in a mindset shift: I don’t enter conflict to win—I enter to understand.

Conflict Management vs. The Pursuit of Understanding

Many approaches to conflict focus on management—de-escalation, containment, finding the middle ground. There’s value in that. But too often, “managing” conflict turns into a silent agreement to disagree, or a polite form of disengagement.

In contrast, the pursuit of understanding asks us to stay with the tension, not flee from it. It means saying:

“I hear your perspective. I understand how you got there. And I’m not here to erase my views or yours—we’re here to explore the space in between.”

Understanding doesn’t mean surrendering your truth. Nor does it mean needing to change someone else’s. It’s about staying present in the conversation long enough for both perspectives to breathe.

The Coffee, Tea, and Chocolate Metaphor

Let’s say I love coffee. You love tea. If we treat this as a contest, we’ll fight over what goes into the team flask. You’ll argue for tea, I’ll push for coffee, and someone will have to lose. That’s conflict as conquest.

But what if we step back? It turns out we both like hot chocolate. Neither of us is pretending to love it more than our favorite. We haven’t betrayed our preference. But we’ve found common ground that respects both of us.

So we fill the flask with chocolate—not because we’ve compromised who we are, but because we’ve co-created a solution that works for now.

I still love coffee. You still love tea. But today, we drink chocolate—together.

This Isn’t Compromise. It’s Coherence.

Compromise often implies loss. Each party gives up something. It could mean a flask of 50% coffee and 50% tea. But the approach I prefer is synthesis: holding space for both viewpoints and weaving them into a practical resolution.

It doesn’t mean I was wrong for liking coffee. Or that you were wrong for preferring tea. It just means we found a third option (rather than split the difference) that is a workable solution.

This isn’t about keeping the peace. It’s about achieving an acceptable outcome.

Conflict Style Reflections

My high cooperation score (91%) reflects this desire to find solutions that fully satisfy both sides, not dilute either.
My adaptation score (75%) shows a willingness to step back when needed, but not out of weakness—out of wisdom.
My low use of compromise (16%) makes sense. I don’t settle easily. I seek meaning, not just middle ground.
Avoidance (58%) plays a role too—I know when to walk away, not out of fear, but because timing and readiness matter.

Together, these traits allow me to engage in conflict in a way that’s neither combative nor complacent. It’s intentional. It’s human.

Final Thought: The Flask Is Just a Flask

At the end of the day, the drink in the flask matters less than the fact that we’re still walking the journey together. Conflict isn’t about proving whose drink is best. It’s about staying in relationship even when we order differently.

So let’s stop asking who’s right and who’s wrong.

Let’s ask: what do we both care enough about to carry forward?

And if that means filling the flask with hot chocolate—so be it.

Favours or Frameworks? Why We Need Both Trust and Transparency in How We Work

In some organizations, decisions happen over coffee, agreements are sealed with a handshake, and favours flow more freely than formal processes. This can foster warmth, speed, and camaraderie—a welcome alternative to bureaucracy. But when relationships replace records entirely, we risk losing more than just paperwork.

I understand the resistance to bureaucracy. No one wants to be buried in forms, contracts, and checklists that feel like a barrier to action. In smaller teams or values-driven organisations, especially in the voluntary or creative sectors, formality can feel at odds with flexibility and trust.

But governance isn’t about red tape—it’s about clarity, consistency, and accountability.

As Ronald Reagan famously said: “Trust, but verify.” Paperwork shouldn’t replace human connection. But it should support it. Meeting minutes, agreements, and action plans are shared anchors—they help ensure we remember what we agreed, uphold our responsibilities, and stay aligned.

Consider what happens when those coffee-room deals are forgotten, or when someone leaves the team. What protects trust then? Without documentation, we risk confusion, inequity, or disputes—not from malice, but from misremembering or misinterpretation.

This matters even more in public services or highstakes environments. The COVID Inquiry, the Post Office Horizon scandal, the contaminated blood tragedy—all reveal what can go wrong when decisions go undocumented, when accountability is avoided, or when loyalty overrides learning.

In those cases, the absence of records didn’t just hinder operations—it hurt people.

So how do we strike a balance?

For relational cultures, we can keep things human—but still put agreements in writing as a sign of mutual respect, not mistrust.
For process-driven environments, we can simplify documentation to make it accessible and meaningful, not performative.
For the public interest, we must always ensure transparency, not just internally but to those we serve.

In short, favours can build goodwill—but frameworks safeguard fairness.

Let’s not let our desire to “just be nice” become a reason to avoid responsibility. Clear documentation isn’t bureaucracy for its own sake—it’s an expression of care, professionalism, and commitment to doing right by each other.

Trust is vital—but trust thrives best when supported by transparency.

Creating Collaboration and Specialisation: A Matrix Model for CoProduction

In a recent conversation with a friend in the voluntary sector, we found ourselves reflecting on one of the most persistent challenges in collaborative environments: how to get people to coproduce effectively—sharing ideas, avoiding duplication, and building something greater than the sum of its parts—while also allowing individuals or groups to specialise and go deep in specific areas. The answer we kept circling back to was simple, elegant, and proven: the matrix structure.

This article outlines how a structured matrix can support coproduction through vertical specialisation and horizontal integration—allowing small, dynamic teams to operate with both autonomy and awareness of the wider system.

1. The Matrix Model: Vertical Themes, Horizontal Communication

Imagine a grid.

Vertically, you have Workstreams or Themes—specific areas of focus such as:

Housing and Homelessness
Mental Health and Wellbeing
Youth Engagement
Environmental Sustainability
Digital Inclusion

Each of these themes holds its own series of meetings where a small, focused group delves deeply into issues, opportunities, and actions relevant to their domain. These groups act as specialist silos, allowing for deep work and dedicated focus.

Horizontally, there is a system of crosscutting communication and information sharing, coordinated at regular intervals through structured meeting rounds. After each round:

All minutes and key takeaways are collected centrally.
These are then collated, summarised, and redistributed to every participant across all workstreams.

2. The Cyclical Rounds of Communication and Learning

Each meeting round follows a consistent pattern:

Round 1: Each theme meets independently and discusses its priorities and ideas.
PostRound 1: Minutes from all theme meetings are collected and shared with everyone.
Round 2: Each theme reconvenes, now fully informed about what every other team discussed in Round 1. This creates a foundation for interdependency awareness, aligning efforts and avoiding duplication.
PostRound 2: Updated records are again collected, collated, and redistributed.
This process continues through Rounds 3, 4, and 5, building a cocreated, coherent strategy with shared understanding and alignment.

3. Oversight, Administration, and Flow of Information

This model only works effectively with two key support functions in place:

a. Central Oversight or Steering Group

A lighttouch governance layer ensures:

Themes stay aligned with the shared purpose.
Emerging gaps or overlaps between themes are addressed.
Resources or blockers are escalated and resolved.

b. Administrative Backbone

An admin or coordination team handles:

Minutetaking, collation, and distribution.
Scheduling and synchronising meetings across themes.
Ensuring version control and accessibility of shared documents.

This backbone is essential for enabling agility without confusion and for turning the matrix from a theoretical model into a working reality.

4. The Outcome: CoProduction with Integration and Specialisation

By the time teams reach Round 4 or 5:

Each workstream will have developed a strong, focused plan grounded in deep thematic expertise.
Each team member will also be aware of how their plan aligns, connects, and supports the work of others.
The result is a holistic, integrated strategy that combines:

Specialist focus (vertical)
Collaborative alignment (horizontal)

This enables small teams to stay nimble while still being connected to the big picture.

5. Why This Works

It avoids large, slowmoving committees by keeping teams small and focused.
It ensures collective intelligence by circulating knowledge.
It enables realtime learning and adaptation, as each round builds on the last.
It reinforces a culture of transparency, trust, and cocreation.

Conclusion

This matrix model is a powerful structure for any organisation or coalition aiming to balance collaborative coproduction with thematic specialisation. With careful facilitation, administrative support, and a commitment to shared learning, it becomes a simple yet scalable way to generate integrated, inclusive strategies that work across silos while respecting the depth of each domain.

It’s a living system—agile, informed, and joinedup—and it might just be the framework your next collaborative project needs.

Navigating Communication in a Busy Work Environment: The Challenge of Finding Time for Meaningful Conversations

In today’s fast-paced work culture, time is one of the most valuable resources. Everyone is juggling multiple responsibilities, and busy schedules often leave little room for meaningful conversations. Whether you’re managing projects, working on client deliverables, or handling team dynamics, it’s increasingly difficult to find time to sit down and talk, let alone engage in in-depth discussions. For many professionals, this challenge is made even more difficult by a lack of regular meetings, limited face-to-face time with key decision-makers, and the absence of a structured communication process.

The Reality of Modern Work Environments

In many organizations, employees and managers alike are caught in a constant cycle of meetings, tasks, and deadlines, often leaving little space for reflective, strategic conversations. Communication, especially when it comes to decision-making or prioritization, is often ad hoc. Those few minutes of face-to-face time with superiors or team members can feel rushed, with no clear agenda or objectives, and often, no clear path forward for addressing key challenges.

This issue isn’t just confined to the higher levels of the hierarchy. From junior staff to senior leadership, everyone is caught in a web of competing priorities. Even when there is an opportunity for conversation, it’s hard to ensure that every relevant point is addressed thoroughly. The result is a frustrating drift—waiting for decisions or guidance that often don’t materialize because the necessary time and space for discussions simply aren’t available.

Solutions for Improving Communication

Despite the challenge, there are ways to improve communication, even in environments where time is scarce. Here are a few strategies to consider:

1. Maximize Limited Time

When face-to-face interactions are limited to only a few minutes, it’s essential to make the most of the time you have. Preparing brief, focused updates is key. Prioritize the most urgent issues and present them concisely, offering clear options for decision-making. A “quick decision format,” where you present a few options with pros and cons, can help guide the conversation and make it more actionable, even in short bursts of time.

2. Create Your Own Informal Agenda

While formal meetings might not always be feasible, informal agendas can still provide a sense of direction. Before you have a brief conversation with a colleague or manager, mentally organize your thoughts and questions. A mental checklist of key issues can help steer the conversation and ensure that you don’t leave with unanswered questions or unresolved tasks.

3. Leverage Technology for Continuous Updates

In an environment where emails might not be well-received or where face-to-face meetings are rare, technology can help bridge the gap. Shared documents, task boards, or collaborative platforms like Google Docs or project management tools (e.g., Trello, Asana) can serve as continuous touchpoints for key updates. These platforms allow you to track issues, prioritize tasks, and share progress asynchronously, providing visibility into ongoing work without needing a formal meeting.

4. Suggest Short Weekly Check-ins

Even when regular meetings are not possible, a brief weekly check-in, even if informal, can help to ensure alignment. A five- or ten-minute meeting can offer the space needed to discuss updates, prioritize tasks, or make decisions. If this type of check-in seems impractical, suggest a quick video or phone call to stay connected and ensure that progress is being made.

5. Accept the Status Quo and Adapt

Sometimes, attempting to change the way communication flows can be counterproductive. If you’re in a workplace where time is consistently tight and meetings aren’t prioritized, you might need to adjust your approach to fit within the existing culture. This means becoming highly self-sufficient, creating your own systems for tracking priorities, and adjusting expectations accordingly. While it may not be ideal, learning to work within these constraints can help you remain effective without constantly feeling frustrated by the lack of structured communication.

6. Improve Self-Direction and Decision-Making

In environments where decision-making is not always clear-cut, fostering your own decision-making skills becomes essential. By cultivating the ability to prioritize tasks, make informed decisions, and act without constant supervision, you’ll be able to move projects forward even without the direct guidance that you might prefer.

7. Focus on Peer Collaboration

If getting time with higher-ups is difficult, turn to your colleagues. Peer collaboration can provide the space to discuss ideas, brainstorm solutions, and gain different perspectives. You may not always be able to meet with a superior, but engaging with colleagues and cross-functional teams can help move initiatives forward.

Navigating the Future of Communication in the Workplace

The challenge of finding time for communication in a busy work environment is unlikely to disappear anytime soon. As organizations grow more complex and workforces become more distributed, time and attention are increasingly fragmented. However, with the right tools and strategies, professionals can adapt to these new realities. Whether it’s maximizing the value of brief interactions, leveraging technology for continuous updates, or learning to navigate without traditional meeting structures, the key to success in today’s work culture is adaptability.

As businesses evolve, it’s crucial to embrace flexibility and find ways to maintain momentum even when time feels scarce. By focusing on self-sufficiency, clear priorities, and continuous communication, professionals can ensure that they remain effective, regardless of the constraints of modern work life.

Effective Procurement and Contract Management: A Structured Approach

1. Procurement and Contracts: Engaging Suppliers and Paying for Services

Effective procurement is essential for securing the right goods and services at the best possible value. It involves clear agreements with suppliers, from the initial engagement to the final payment for services rendered. A well-managed procurement process can prevent costly mistakes and ensure that projects are delivered on time and within budget.

2. Planning and Preparation: Laying the Groundwork for Successful Procurement

A thorough planning phase is critical to a smooth procurement process. Key steps include:

Clarity of Service: Ensure you are 100% clear on the service being procured. Clearly define the scope and expected outcomes before proceeding.
Selection Criteria: Develop specific selection criteria to evaluate potential suppliers, ensuring they align with your organizational goals.
Risk Assessments: Conduct risk assessments to identify and mitigate potential procurement risks, ensuring that you are prepared for any unforeseen issues.
Legal and Regulatory Compliance: Verify compliance with all relevant procurement laws, regulations, and policies to avoid legal pitfalls.
Timeline and Milestones: Set clear timelines, deadlines, and milestones to guide the procurement process and track progress.
Budget Management: Regularly update the procurement budget to reflect any changes in costs or scope, ensuring you stay within financial limits.

3. Quality and Performance: Ensuring Value for Money

To guarantee value for money and successful project delivery, consider these factors:

Competitive Bidding or Market Testing: Use competitive bidding or market testing to compare suppliers and ensure you are getting the best deal.
Quality Standards: Define quality standards and set clear approval processes for evaluating goods or services.
Payment Structure: Structure payments based on successful outcomes, rather than on effort or attempts that did not meet expectations.
Clear Outcome Measures: Clearly outline the expected outcomes, ensuring both the process and results are well-defined and measurable.
Monitor Performance: Regularly monitor supplier performance against agreed-upon Key Performance Indicators (KPIs) to ensure continuous improvement and adherence to the contract terms.

4. Documentation and Agreements: Safeguarding Against Disputes

Having the right documentation in place is vital for managing relationships with suppliers and resolving disputes:

Contractual Documents: Always have a formal contract, memorandum of understanding (MOU), or other relevant agreements in place to define expectations and resolve potential disputes.
Mediation Clause: Include a mediation clause or clear method for resolving disagreements, which helps in addressing issues without resorting to legal action.
Exit and Renewal Plans: Plan for contract exit or renewal well in advance, considering both the potential for contract extension and the end of service.
Transparency and Accountability: Document all decisions and communications throughout the procurement process, promoting transparency and accountability.

5. Stakeholder Engagement and Oversight: Collaborative Success

Successful procurement doesn’t happen in isolation; it requires input from relevant stakeholders:

Engage the Right Stakeholders: Involve the appropriate stakeholders in the service delivery, acceptance, and approval processes to ensure alignment with organizational needs.
Encourage Feedback: Foster feedback from stakeholders, both during and after the procurement process, to identify areas for improvement in future procurement efforts.
Proactive Issue Resolution: Report and address issues promptly as they arise, ensuring that potential problems are dealt with before they escalate.

By following a structured approach to procurement and contract management, organizations can optimize their purchasing processes, manage risk, ensure compliance, and secure value for money. These best practices help build strong, transparent, and accountable supplier relationships, leading to better outcomes and long-term success.