Category: Uncategorised

When it comes to calculating cost savings, there’s often a blurry line between *true* savings and *notional* savings. Here’s a quick example to highlight the difference and what to watch out for in these calculations:

Let’s say I wash the dishes and charge my wife £100 an hour for it. She finds that ridiculous, so instead, my son steps in and washes the dishes for £40 an hour. How much money have we actually saved?

The answer might seem obvious, but let’s break it down: no money has actually been saved in the family bank account. We haven’t gained anything we can spend on dinners out, holidays, or anything else.

It’s easy to argue that we’ve saved £60 per hour by choosing the cheaper alternative. However, this is a *notional* saving—it’s just a shift in resource allocation, not an increase in wealth. There’s no *true* financial gain here, just a reduction in cost by changing who performs the task at hand.

In business, it’s essential to distinguish between *actual* savings—where money is saved, such as reducing overheads or increasing efficiency—and *notional* savings, where the only change is shifting resources without increasing profitability.

Best practices when calculating savings:

1. True Savings: Make sure you’re measuring actual savings in terms of cash flow, not just the cost of resource allocation. For example, reducing waste, improving productivity, or lowering overhead that directly impacts your bottom line.

2. Notional Savings: These are useful for internal reporting or comparisons but shouldn’t be mistaken for actual savings. It’s important to communicate clearly that these are “shifts,” not gains.

3. Reinvestment: If cost reductions lead to reinvestment in the business (e.g., you save money on one function, which allows you to improve another area), that’s a *true* benefit to the business and should be calculated accordingly.

In summary, while cost-saving exercises are crucial, always ensure you’re clear about whether you’re calculating true savings or just shifting costs, and when it is internal costs one persons cost reduction is another persons revenue loss.

Case Study: Effective Project Management Without Micromanagement

Over three decades of experience working on projects, process improvements, and organizational changes, I’ve encountered various scenarios that highlight the importance of balanced project management. My case studies are drawn from these experiences and provide anonymized, generalized insights that may apply to different organizations. However, they are based on real-life situations that carry important lessons for all project managers.

Project Management: A Broad Overview

In my experience, project management should never be confused with micromanagement. While it’s crucial to establish a project timetable that outlines targets and milestones, it’s equally important to recognize that these schedules are not rigid to-the-minute mandates. Rather, they are indicative guidelines to help teams understand the overall trajectory and timeline of the project. However, the human element and practical considerations often introduce flexibility in how tasks are executed within those timelines.

Project schedules should reflect broader milestones, critical checkpoints, and the overall flow of the project rather than prescribing each individual’s exact work time. It’s especially relevant when managing teams balancing business-as-usual tasks along with project deliverables. These individuals are often managing multiple priorities, so a rigid schedule becomes impractical. A focus on flexibility and understanding is crucial for project success.

Trusting the Team: The Power of Autonomy

One of the key principles I’ve found in managing projects is trusting the expertise and judgment of the team. For example, if I request a task to be completed on a particular day but it’s delayed by a couple of days due to unforeseen issues such as holidays, sickness, or urgent matters, I don’t see it as an immediate cause for concern. What matters most is that the task gets done within a reasonable timeframe. As long as there’s transparency, communication, and no major barriers, I believe the team should manage the task details themselves. Micromanaging individual tasks, especially when they are handled by experts, serves little purpose.

Each task on a project plan can represent a series of smaller, detailed tasks that the assigned team member must address. Often, a simple task on a project chart may mask a complex set of actions. This is where trust comes into play: the project manager’s role is to ensure the project is moving forward while allowing the experts to manage the specific details.

Understanding Tolerances and Milestones

While flexibility is vital, project managers must be clear on acceptable tolerances for completion times. It’s unreasonable to dictate precise minutiae like when someone takes a break, as long as the task is completed. In today’s world, where remote work and flexible schedules are increasingly common, a project manager’s role isn’t to enforce strict time-bound tasks but to ensure the project progresses as expected, meeting major deadlines without sacrificing the well-being and autonomy of the team members.

That being said, it is critical to identify and understand the key milestones or non-negotiable dates that are central to the project’s success. For instance, a product launch, a contractual obligation, or a go-live date cannot be delayed without serious consequences. Project managers need to remain focused on these key dates while providing the team the freedom to manage their tasks within a reasonable timeframe.

Lessons from Athletics: The Importance of Timing

Drawing from my background as an athlete, I recognize that timing is crucial. In sports, preparing thoroughly is necessary, but it’s also important to execute the plan on time. There is no value in completing your preparation after the race has already been run. Similarly, in business, completing a task three months after it’s due, or delivering a product post-event, is not acceptable. It is critical to stay aligned with the project’s key dates and milestones.

While understanding major program dates is essential, project managers must also recognize the difference between managing the big milestones and micromanaging the day-to-day tasks. A cooperative and collaborative environment, with open channels for escalation and regular updates, fosters a culture of trust and teamwork, allowing the project to be managed effectively while ensuring deadlines are met.

Conclusion

Project management is a balance of structure and flexibility. Understanding key milestones, trusting the expertise of the team, and fostering an environment of communication and collaboration are vital for success. As project managers, we must navigate the complex task of ensuring the big picture stays on track while giving our teams the autonomy they need to execute their work.

Top Tips and Best Practices

1. Set Clear Milestones: Define clear project milestones and key dates, but avoid micromanaging every small task.
2. Trust Your Team: Empower your experts to manage the finer details of their tasks while maintaining oversight of the broader project.
3. Accommodate Flexibility: Life happens—understand that delays are part of managing a team, especially when balancing multiple priorities.
4. Create Open Communication Channels: Regular meetings and an open escalation path are crucial to ensuring transparency and addressing potential issues early.
5. Identify Non-Negotiable Dates: Understand which dates are immovable and keep the focus on these critical deadlines.
6. Foster Teamwork and Collaboration: Success lies in cooperation. A collaborative environment encourages problem-solving and ownership of tasks.
7. Adapt to Changing Environments: Recognize that flexibility, especially in today’s work-from-home culture, is important for long-term success.

By adhering to these practices, you can ensure a smoother project journey, promoting a healthy balance between structure and flexibility, and ultimately achieving your desired outcomes.

#ProjectManagement #Leadership #WorkplaceFlexibility #Teamwork #TrustInTeams #BusinessSuccess #MilestoneManagement #ProjectLeadership #Collaboration #RemoteWork

Unlocking Project Success: The Essential Guide to Effective Governance

Effective project governance is crucial for ensuring successful outcomes, especially when dealing with complex projects and multiple stakeholders. Whether you are managing a small internal project or a large, multi-stakeholder initiative, having a clear governance structure in place is key to maintaining focus, controlling risks, and delivering value.

What is Project Governance?

At its core, project governance defines the framework within which decisions are made, roles and responsibilities are allocated, and progress is monitored. It ensures that all involved parties are aligned with the project’s objectives and provides a structured approach for managing resources, risks, and communication.

For any project of size or complexity, effective governance can be broken down into several key components: oversight, clear roles, structured processes, and consistent communication.

Let’s explore these elements in more detail, along with some top tips and best practices for setting up project governance.

1. The Steering Group: High-Level Oversight

A steering group provides the overarching leadership for a project. This group typically consists of senior stakeholders, including the Senior Responsible Owner (SRO) and key decision-makers. The steering group has several key functions:

Approval and Direction: They review and approve project plans, deliverables, and overall strategy.
Alignment with Business Objectives: They ensure the project aligns with broader organizational goals and objectives.
Risk and Issue Management: They intervene when issues arise, particularly those that require senior-level decisions.

Best Practice Tip: Ensure your steering group meets regularly—at least monthly. This frequency allows for timely decision-making and course correction while maintaining a strategic overview of the project.

2. The Project Delivery Team: Operational Execution

While the steering group focuses on high-level direction, the Project Delivery Team handles the operational side of things. This team works on the day-to-day management, executing tasks, and ensuring the project progresses according to the plan. Their responsibilities typically include:

Task Execution: Delivering the work as per the project plan.
Risk Management: Identifying and mitigating risks in real time.
Progress Tracking: Reporting progress and ensuring the project stays within scope, time, and budget constraints.

Best Practice Tip: Schedule weekly meetings for the delivery team. These meetings should focus on progress updates, risk and issue tracking, and reviewing next steps. Keeping the meetings short and focused ensures momentum is maintained without overwhelming team members.

3. Key Documents: The Backbone of Governance

To support both the steering group and delivery team, several key documents are essential for clarity and transparency. These documents help align the team, track progress, and define the project’s objectives and constraints.

Project Initiation Document (PID): This comprehensive document outlines the project’s goals, scope, risks, and resources. It provides a clear framework for the project, ensuring all stakeholders understand their roles and responsibilities.

Best Practice Tip: While a full PID can be exhaustive, aim to create a high-level summary for smaller or sensitive projects. This project charter can cover essential points like governance structure, roles, responsibilities, and key objectives.

Project Plan: The project plan is the roadmap for the project. It defines tasks, milestones, deadlines, and the responsible parties. A well-structured plan provides clarity for both the steering group and the delivery team, helping to track progress and identify potential delays.

Best Practice Tip: Break down the project plan into manageable workstreams and tasks. This approach prevents overwhelming the team and ensures clear accountability at every level.

Regular Reporting: Ongoing communication is key for project success. Regular reports—whether monthly or weekly—help ensure that everyone is kept up-to-date with progress, risks, and issues.

Best Practice Tip: Adopt a visual reporting format (like dashboards) to highlight key metrics and progress. This makes it easier for stakeholders to quickly grasp the project’s status and makes reporting more effective.

4. RACI Matrix: Defining Roles and Responsibilities

A RACI matrix is an invaluable tool that helps clarify roles and responsibilities, ensuring no one is left in the dark. RACI stands for:

Responsible: The person who performs the task.
Accountable: The person who is ultimately accountable for the success of the task.
Consulted: People who provide input or expertise.
Informed: People who need to be kept updated on progress.

Best Practice Tip: Regularly revisit and refine the RACI matrix as the project evolves. As tasks or roles change, keeping the RACI matrix up-to-date helps ensure continued alignment across the team.

5. Clear Communication: The Key to Collaboration

Effective communication is the glue that holds project governance together. Establishing clear communication channels and regular touchpoints ensures that all stakeholders are informed, consulted, and included as needed. Communication should be two-way, ensuring that feedback flows freely both upwards and downwards.

Best Practice Tip: Foster an open communication culture where issues can be raised without hesitation. Ensure key decisions, risks, and changes are communicated promptly to all relevant stakeholders. This minimizes misunderstandings and ensures alignment.

Final Thoughts: Balancing Structure with Flexibility

While governance is essential, it’s equally important to avoid over-complicating the structure. A robust framework doesn’t mean drowning in bureaucracy. The goal is to create a governance setup that ensures accountability, keeps projects on track, and empowers your team to focus on delivery.

As you set up governance for your project, consider your project’s complexity, stakeholder needs, and organizational culture. Use these best practices to guide you, but be open to adapting them based on the project’s unique demands.

Remember, good governance is not just about control—it’s about creating the conditions for success by ensuring collaboration, clarity, and timely decision-making.

#ProjectManagement #Governance #Leadership #Teamwork #StakeholderManagement #ProjectDelivery #BestPractices #RACI #Communication #ProjectSuccess

Introduction

With over three decades of experience in managing projects, process improvements, and organizational changes, I have encountered a variety of situations that illustrate the nuances of project management and assurance. The following case studies combine real-life experiences, offering generalized observations. Some of these insights may resonate with your organization, while others may not, but they remain valuable lessons that can help refine your approach to project oversight and assurance, particularly within a structured framework like PRINCE2.

Case Study: Project Assurance and Its True Role in PRINCE2

Project updates and assurance functions often differ significantly from how they are portrayed. From my own experience as a project manager, I have witnessed instances where the pace of expenditure on a project outstripped the available budget. Recognizing this risk, I raised the issue with the project assurance team, asking them to independently review the situation and, where appropriate, escalate the issue to the project sponsor. While I, as the project manager, am responsible for providing oversight and updates, it is the role of project assurance to objectively validate, review, and assess. In a PRINCE2 framework, the Project Assurance role is an independent function, tasked with providing guidance and oversight to ensure that the project stays aligned with the business case, quality expectations, and overall objectives.

The purpose of project assurance is to be independent, impartial, and objective—something that is not always present from the project manager’s perspective. Often, a project manager’s natural inclination is to report success and maintain positive relationships, making it difficult to be entirely candid about issues that could potentially tarnish the project’s progress. This tendency to “spin” information can skew an accurate picture of the project’s reality. For this reason, assurance must serve as an independent, objective check to ensure all parties involved are made aware of issues as they arise. PRINCE2 clearly defines the role of Project Assurance as one that should provide impartial oversight, ensuring that the project remains aligned with its strategic objectives.

However, the reality of project assurance can sometimes be disappointing. On more than one occasion, I have observed that project assurance professionals, while ostensibly acting as a safeguard for the project’s success, can often adopt a less critical stance in favor of being “liked” or maintaining a positive relationship with stakeholders. I have seen situations where project assurance has been unwilling to take a robust stance in addressing project risks, opting instead to reassure the project manager with emotional support rather than providing the necessary technical insights and evaluations.

In one example, I flagged the potential for a client to be in breach of data protection regulations—a matter technically outside my immediate remit as the project manager but still crucial to the integrity of the overall project. When I escalated this concern to the project assurance team, I was met with a response that essentially dismissed the issue, claiming it was the client’s responsibility to manage legal compliance. While this may be true from a legal perspective, project assurance failed to step in and provide any meaningful guidance or recommendation, thus neglecting the key function of ensuring all aspects of the project are on track, including legal and regulatory compliance.

In the instance above [expenditure on a project outstripped the available budget], I observed that a vendor was burning through the project’s budget at an alarming rate, despite claims that we were still within budget. The project’s trajectory, however, suggested that we would soon exceed the agreed-upon budget if spending continued at the same pace. When I raised the issue with project assurance, I was told that unless the budget was actually exceeded, any concerns were speculative and not actionable. This lack of proactive risk management ultimately led to the project surpassing its budget, with the client eventually having to make a commercial settlement with the vendor, who had mismanaged the project scope and resources.

In both of these cases, project assurance failed to deliver on its key responsibilities. Rather than providing the necessary oversight, they instead acted more as a neutral party, avoiding difficult conversations and instead offering a sense of emotional assurance. This is a classic example of project assurance being ineffective, as it did not fulfill its role of safeguarding the client’s interests and ensuring the project’s success.

PRINCE2 clearly establishes that the Project Assurance role is about being independent, robust, and proactive in overseeing the project’s progress. Project assurance should not be about creating an emotionally comfortable environment or offering positive reassurance when difficult issues arise. Its role is to provide robust, impartial assessments, offer technical recommendations, and take necessary actions to prevent failure. It should be prepared to enter difficult conversations and provide objective insights into the project’s health, including any risks, issues, or concerns that may arise. The primary role of assurance is to anticipate and avoid failure—not simply to track and report it after the fact.

Project assurance in PRINCE2 also includes regular reviews of project performance against the business case, helping to ensure that the project continues to meet its original objectives. If the project is in danger of falling short, assurance professionals must be ready to take a tough stance and intervene in a way that keeps the project on track. Rather than merely acting as a sounding board for the project manager, assurance must serve as a critical safeguard for the project’s long-term success.

Top Tips and Best Practices for Project Assurance:

1. Clarity of Role: In a PRINCE2 framework, ensure that everyone understands the core responsibility of project assurance. It should be an independent, impartial body that validates and checks all aspects of the project, from budgeting to legal compliance and beyond.

2. Be Objective and Robust: Assurance professionals should avoid the temptation to simply reassure stakeholders. They must provide clear, factual assessments and highlight risks, even if it means delivering uncomfortable news.

3. Proactive Risk Management: Don’t wait until problems manifest. Use data, trends, and careful analysis to anticipate potential issues before they become significant problems.

4. Accountability: Project assurance should be accountable for identifying risks and making recommendations to mitigate them, not just monitoring progress.

5. Effective Communication: Develop a culture of transparency. Project assurance must be willing to engage in difficult conversations and advocate for the best interests of the project, even if it means challenging other stakeholders.

6. Commercial Awareness: Assurance professionals should also have a solid understanding of commercial dynamics and be able to act as mediators in commercial disputes to protect the client’s interests.

7. Guardianship Role: Project assurance is there to safeguard the project’s integrity. This includes ensuring financial health, compliance with legal and regulatory standards, and the overall performance of the project.

8. Anticipate Failure, Don’t Just Track It: Assurance must focus on avoiding failure by identifying potential risks early, rather than simply tracking issues after they occur.

By following these best practices, project assurance can transform from a passive function into a dynamic, value-adding component that plays an essential role in safeguarding the project’s success.

Conclusion

In conclusion, project assurance should not be viewed as a “cheerleader” or a source of emotional support, but rather as a critical function that provides independent oversight, identifies risks, and ensures the project remains aligned with its business case. In the PRINCE2 framework, the assurance role is about being proactive, robust, and transparent, safeguarding the project’s success by ensuring that any issues are addressed before they escalate. By ensuring that assurance professionals fulfill their true role, projects will have a much better chance of staying on track and delivering the intended value.

#ProjectManagement #Assurance #RiskManagement #ProjectSuccess #Leadership #BusinessStrategy #Compliance #ProjectOversight #Risk #Accountability #Management #ProjectAssurance

Lean Six Sigma: A Tool for Transformation or a Force for Harm?

Lean Six Sigma is widely regarded as a set of methodologies designed to improve processes, enhance efficiency, and reduce costs. These frameworks are built around the principles of Lean (eliminating waste, improving flow) and Six Sigma (reducing defects and variability), offering organizations the tools to achieve operational excellence. However, as with any widely adopted methodology, Lean Six Sigma has its advocates and critics, each with strong opinions on its application and impact. This article explores the pros and cons of Lean Six Sigma, how it can be a force for good, how it can sometimes be misused, and the divisiveness it creates within organizations.

The Basics of Lean Six Sigma: Philosophy, Process, and Toolkit

At its core, Lean and Six Sigma offer organizations a structured approach to identifying inefficiencies and implementing improvements. Lean focuses on maximizing value by eliminating waste—be it time, materials, or energy—while Six Sigma aims to reduce process variability and defects, typically through the use of data and statistical analysis. When combined, Lean Six Sigma provides a powerful toolkit for improving productivity, lowering costs, and delivering higher quality to customers.

However, there is a delicate balance to strike in how these methodologies are applied. Strict adherence to the methodologies may create rigid processes, while too much flexibility can dilute their effectiveness. The distinction between the toolkit, the process, and the philosophy is key to understanding how Lean Six Sigma should be applied. Too often, organizations attempt to simplify the approach to a set of predefined steps, missing out on the broader philosophical and strategic benefits.

The Force for Good: Transforming People, Processes, and Products

When implemented thoughtfully, Lean and Six Sigma can be transformational. These methodologies have the potential to improve not only processes but also the individuals and teams working within those processes. Lean Six Sigma encourages collaboration, problem-solving, and a focus on continuous improvement. It empowers employees to identify areas for enhancement, test hypotheses, and implement changes that lead to better outcomes for both the organization and its customers.

For example, Lean’s focus on waste reduction can lead to smoother workflows and less downtime, while Six Sigma’s emphasis on quality control ensures that processes deliver consistently high standards. When used in the right context, Lean Six Sigma can enhance the overall quality of products and services, increase employee engagement by giving them a sense of ownership in the improvement process, and create a culture of continuous learning.

In industries where operational efficiency is critical, Lean Six Sigma can have a profound impact. Healthcare systems, for example, have used these tools to streamline patient care processes, reduce wait times, and improve outcomes. In manufacturing, Lean Six Sigma has driven significant reductions in defect rates and production costs. The methodologies work best when they are seen as part of a broader philosophy of improvement, where people are valued as the key drivers of change and quality.

The Potential for Misuse: Cost-Cutting at the Expense of People and Quality

While Lean Six Sigma can be a transformative force, it can also be misused. In many cases, organizations deploy these methodologies as tools for cost-cutting or reducing headcount, often without considering the long-term impact on product quality, employee morale, and organizational culture. This approach undermines the core purpose of Lean Six Sigma, which is not just to reduce costs but to enhance value for customers and improve overall efficiency.

A common misuse of Lean Six Sigma is demanding more from employees with fewer resources. For instance, employees may be asked to take on additional tasks with limited training or reduced time, all while being told to deliver higher output. This not only increases the risk of burnout but can also result in mistakes that compromise the quality of products or services. The relentless pursuit of efficiency can lead to employees feeling undervalued and disengaged, eroding the very morale that drives a high-performance culture.

Moreover, a narrow focus on cost reduction can lead to an unhealthy obsession with cutting corners, which compromises the quality of the final product or service. When Lean Six Sigma is applied solely as a mechanism for reducing costs, organizations risk losing sight of customer value and long-term sustainability.

The Divisiveness of Lean Six Sigma: Passionate Advocates and Cynical Detractors

Lean Six Sigma is a highly divisive topic. On one hand, you have passionate advocates who believe in the methodologies’ potential to revolutionize organizations. These purists argue that Lean Six Sigma provides a structured, proven approach to solving business problems, and they emphasize the importance of adhering strictly to the prescribed methods to achieve consistent, reliable results.

On the other hand, there are those who are deeply skeptical of Lean Six Sigma, viewing it as a simplistic, over-hyped approach to complex problems. Critics argue that these methodologies can be too rigid and formulaic, stripping away the nuances of real-world challenges. They see Lean Six Sigma as a “McDonald’s approach”—a standardized, one-size-fits-all solution to diverse and multifaceted business issues.

The truth, however, is likely somewhere in between. Lean Six Sigma is not inherently flawed, but it must be applied with a clear understanding of an organization’s specific needs and culture. A rigid, one-size-fits-all application of these methodologies can lead to mediocre results, while a more flexible, nuanced approach can yield significant benefits. The key is to strike the right balance—adopting the tools and techniques of Lean Six Sigma without losing sight of the broader organizational context.

Blending Methodologies: Striking the Right Balance

An interesting and often debated question is whether Lean Six Sigma can be effectively blended with other methodologies, such as Agile, Scrum, or Theory of Constraints. Each of these frameworks offers distinct advantages, and when combined, they can create a more comprehensive approach to process improvement.

For instance, Agile’s focus on flexibility and iterative development can complement Lean’s emphasis on continuous improvement, while Six Sigma’s data-driven approach can enhance the rigor and precision of Agile’s processes. By blending these methodologies, organizations can create a more holistic approach to change management that addresses both short-term agility and long-term sustainability.

However, blending methodologies is not without its challenges. Agile’s flexibility sometimes clashes with Six Sigma’s rigid, data-centric processes. Similarly, the Theory of Constraints focuses on identifying and alleviating bottlenecks, which can sometimes be at odds with Lean’s broad focus on waste reduction. The success of blending methodologies depends on how well they are integrated into the organization’s culture and how they align with the organization’s goals.

Conclusion: Lean Six Sigma as a Tool for Continuous Improvement

Lean Six Sigma is a powerful set of tools, but like any tool, it must be used correctly to yield positive results. When applied with care and a deep understanding of organizational needs, Lean Six Sigma can lead to transformative improvements in processes, products, and people. However, when misused as a tool for cost-cutting or oversimplified to the point of rigidity, it can undermine the very things it was designed to improve.

The key to success lies in finding the right balance—adopting Lean Six Sigma as a framework for continuous improvement, while remaining flexible and responsive to the unique challenges of each organization. By blending methodologies, focusing on employee engagement, and keeping the customer at the center of every decision, organizations can use Lean Six Sigma to drive sustainable, meaningful change that benefits everyone involved.

Ultimately, Lean Six Sigma is not just about improving processes; it’s about improving the entire system in a way that creates value, fosters engagement, and delivers quality results. When approached with this mindset, Lean Six Sigma has the potential to be a powerful force for good.

Case Study: Navigating the Complexities of Estimating and Evidencing Project Benefits
Introduction
Over three decades, I’ve had the privilege of working on numerous projects, process improvements, and organizational changes. My case studies combine different experiences across industries, which have led to valuable insights—some of which may be directly relevant to your organization, while others may offer broader lessons. These observations, based on real situations, are important to recognize as they provide practical guidance in navigating common project management challenges.

Case Study: Estimating and Evidencing Project Benefits
Estimating and evidencing the benefits of a project can often be a difficult task. For example, you might calculate that a new process will save 10 minutes per day, and that these savings multiply across hundreds of people, leading to hundreds of hours saved per year. While this is certainly a measurable consequence, the actual impact may not be as clear-cut as it seems. The savings are often framed in terms of full-time equivalents (FTEs) or salaries, but it’s important to recognize that these savings don’t always translate directly into headcount reduction.

For instance, during my time at RBSI (Jersey), I progressed modest improvements in the payments department. Given the volume of transactions handled by the bank, even modest improvements had a significant compound effect on efficiency. However, rather than reducing headcount, we created capacity for staff to focus on more valuable tasks, rather than eliminating jobs. Improving processes is not always about reducing staff numbers; it’s about increasing capacity for more strategic, higher-value work.

However, there are times when organizations aim to do more with less, which could result in headcount reduction or, at the very least, a shift in roles toward more profitable activities. In these cases, the focus shifts to productivity and profitability per employee. If employees are now working on more profitable tasks, their output should theoretically increase, and measuring this shift becomes a critical element in understanding the success of a process improvement initiative.

That being said, the reality of human behavior often doesn’t align with the mathematics of process improvements. Even if a process is faster, cheaper, or more efficient, there’s no guarantee that people will fully engage with or adopt it. For example, a process might save hundreds of hours, but if employees are not motivated to use it or don’t see the value in it, the anticipated time savings might never materialize. This is a common issue, particularly in change management, where engagement becomes a crucial factor in determining the success of a project.

One experience stands out where a sponsor identified significant cost savings from process improvements. However, once those savings were agreed upon, their budget was reduced by the exact amount of the savings, creating pressure for them to deliver on those promises. The same phenomenon occurs when new processes are introduced with the expectation that they will generate increased revenue. At this point, teams are often given new, higher revenue targets, which creates an imperative to meet or exceed those targets, especially when the sponsors are measuring success based on those metrics.

While this approach can drive engagement, it’s important to note that the financial targets set by senior leadership may not always align with the priorities of staff working at the operational level. The reality is that employees on the ground are generally less motivated to work faster or harder simply to increase company profits. They are far more likely to be motivated by tangible improvements that benefit them directly—such as better working conditions, a simpler process, or a reduction in risk. This “what’s in it for me?” mindset is a powerful driver for engagement and adoption of new processes.

Therefore, measuring the success of a project requires a holistic approach. It’s not enough to focus solely on time and cost savings. You must also measure engagement, satisfaction, risk reduction, quality, and other softer factors that might not show up on the balance sheet but are just as critical to the long-term success of the project. Some of these factors may involve sentiment or subjective feedback, while others may directly impact the company’s financial performance.

This brings us to the issue of “notional savings.” Many organizations, especially in IT departments, may adopt a notional charge rate for their services—say, £100 an hour. If you reduce the time spent on IT services by 50%, you might calculate that you’ve saved £50 an hour. However, these savings aren’t actual cash in the bank; they are simply reductions in costs that are often internalized within the organization. It’s important to differentiate between “notional” savings and real, tangible savings that affect the organization’s financial performance.

The phrase “revenue is vanity, profit is sanity, and cash is king” rings true in these cases. While revenue growth can be an exciting indicator, it’s important to focus on the bottom line—profitability and actual cash flow. These are the true measures of success and should be at the core of any financial assessment of a project or process improvement initiative.

Top Tips and Best Practices
1. Measure More Than Just Time and Cost Savings: Beyond financial metrics, consider measuring employee engagement, process satisfaction, risk reduction, and quality improvement to get a fuller picture of success.
2. Engage Employees in the Change Process: Employees are more likely to adopt new processes if they see personal benefits, such as better working conditions or reduced risk. Make sure to communicate these benefits clearly.
3. Align Organizational Goals with Employee Priorities: Senior management’s targets may not always align with the operational priorities of frontline workers. Ensure that your goals resonate with staff to drive engagement.
4. Be Cautious of Notional Savings: Understand the difference between notional and real savings. Notional savings may look good on paper but don’t always translate into tangible financial benefits.
5. Focus on Profit and Cash Flow: Don’t get distracted by revenue growth alone. Profitability and cash flow are the true indicators of business success and should be central to your performance metrics.
6. Ensure Clear Communication Across All Levels: Successful projects require alignment at every level, from senior leadership to operational staff. Transparent communication is key to ensuring everyone is on the same page and committed to the shared goals.

This comprehensive approach to measuring project success, considering both hard and soft factors, will ensure more sustainable and impactful outcomes for your organization.

#ProjectManagement #BusinessTransformation #ProcessImprovement #EmployeeEngagement #Profitability #ChangeManagement #Leadership #BusinessSuccess #OrganizationalChange

Understanding Different Types of Risks in Project Management and Their Reporting

In project management, risks are an inevitable part of any initiative, but not all risks are created equal. The risks you encounter will vary in scope and impact depending on the level of the work you’re managing—be it a task, a project, a program, or even at the broader operational or business level. Understanding the differences between these risk types and how to manage them effectively is crucial to maintaining control and steering projects toward success.

1. Task Risk
Definition: Task risks are the risks that affect individual tasks or activities within a project. These are usually the smallest and most specific risks, typically tied to deadlines, resources, or task dependencies.

Examples:
A delay in receiving a required document from a stakeholder.
Unavailability of a key team member due to illness.

Risk Reporting & Escalation:
Task risks are generally managed at the individual team level. They should be documented in the task’s risk log and communicated to the project manager, who can decide if escalation is necessary. If unresolved, they may be escalated to the project level, but typically, these are low-priority risks that can often be mitigated within the team.

2. Project Risk
Definition: Project risks are those that impact the overall success of the project. These risks may relate to the project’s scope, budget, schedule, or quality.

Examples:
Scope creep due to unclear requirements.
Budget overruns due to unforeseen costs.
Delays due to external factors like regulatory changes.

Risk Reporting & Escalation:
Project risks should be captured in the project risk register and discussed during project status meetings. They are typically reported to the project manager or senior project team for resolution. In case of serious threats, these risks may require escalation to the program or portfolio level to secure additional resources or decision-making authority.

3. Program Risk
Definition: Program risks are risks that affect a collection of related projects (i.e., a program). These risks tend to have broader implications and can impact multiple projects within the program.

Examples:
A change in a strategic objective that impacts several projects.
Resource conflicts between projects within the program.
A technology platform that affects multiple projects.

Risk Reporting & Escalation:
Program risks should be escalated to the program manager, who is responsible for ensuring that risk management is coordinated across the entire program. They must be reported at a higher level, often through a program risk register, and may require cross-project solutions or adjustments. Escalation typically goes to senior management if program risks threaten the overall program delivery.

4. Operational or Business Risk
Definition: Operational or business risks refer to risks that can affect the day-to-day running of an organization. These risks are often external and can have long-term consequences on the business’s strategic direction.

Examples:
Market shifts leading to decreased demand for a product.
Operational inefficiencies or supply chain disruptions.
Regulatory changes that impose new compliance requirements.

Risk Reporting & Escalation:
Operational risks should be tracked in an enterprise-level risk management framework. These risks are typically reported to senior executives or the risk management committee, who are responsible for broader organizational strategies and decisions. The escalation process for these risks usually involves executives or board-level discussions, with mitigation strategies put in place at the organizational level.

Key Takeaways for Risk Management and Reporting:
Task Risk: Managed at the team level, with reporting to the project manager and escalation when necessary.
Project Risk: Managed at the project level, with reporting to the project manager or senior team. Escalated when the project’s objectives are at risk.
Program Risk: Managed across projects in a program, with reporting to the program manager and escalation to senior management if necessary.
Operational/Business Risk: Managed at the organizational level, with reporting to senior executives or a risk management committee. Escalation typically involves top-level decision-makers.

By recognizing the scope of risk at each level and implementing an effective reporting and escalation process, you can ensure that risks are managed proactively and do not derail your efforts. Having a clear structure for managing and communicating risks improves decision-making, maintains alignment with project goals, and safeguards against broader organizational challenges.

—

What’s your experience with risk management across different project levels? Feel free to share your insights and best practices in the comments!

The Benefits of Folder and File Naming Structures for Collaborative Project Work

In today’s fast-paced business environment, effective collaboration is key to the success of any project. Whether you’re managing a cross-functional team or working with external stakeholders, one of the most overlooked yet essential elements of a successful project is the way files and documents are organized. A well-structured folder system and clear file naming conventions are the backbone of efficient teamwork, streamlining communication, and preventing the chaos of unorganized data.

1. Enhanced Collaboration
A structured folder system allows project teams to easily locate the documents they need, ensuring smooth collaboration. When everyone knows where to find what they’re looking for, the time spent searching for files is minimized, which translates into more time spent on productive work. Whether you’re working with local teams or collaborating with remote stakeholders, a consistent and transparent file structure provides a centralized location for all project materials.

Tip: Ensure that folders are categorized logically—by project phases, tasks, or departments—to make navigation intuitive for all team members.

2. Clear and Consistent File Naming
One of the most frustrating experiences in project work is dealing with confusing or inconsistent file names. Without a clear naming convention, it becomes incredibly difficult to track which version of a document is the latest, or what content is inside a file. A standard file naming system should include relevant details such as project phase, document type, and version number.

Example: “ProjectX_Plan_v2_Draft” tells you that the document is related to Project X, is a draft version of the plan, and is the second version.

A consistent naming structure helps avoid duplicates, errors, and confusion—making it much easier to understand the context of each file at a glance.

3. Access Control & Security
While collaboration is essential, controlling access to sensitive documents is just as important. A well-organized folder structure should integrate with your access control system, allowing you to specify who has permission to view, edit, or delete certain files. This ensures that sensitive information is protected, and only the appropriate stakeholders have access to critical data.

For example, you might grant different levels of access to project managers, team members, and external consultants, ensuring that confidential documents are restricted while still promoting collaboration among the right people.

Tip: Consider using tools that support both file structure organization and access control, like cloud-based project management platforms.

4. Better Than Email for File Sharing
One of the most common ways teams share documents is through email, but this can quickly become unmanageable. Searching for files in email threads is time-consuming, and version control becomes a nightmare when multiple people are working on the same document. Not only that, but emails can easily get lost, leading to missed updates or duplicate versions of the same document.

In contrast, a well-structured folder system eliminates the need for email-based file sharing. Instead of attaching files to email threads and potentially losing track of the latest version, team members can access documents directly from a shared folder or project management platform, ensuring everyone is working from the most up-to-date file.

Tip: Cloud platforms such as Google Drive, OneDrive, or Dropbox offer version control features, allowing teams to track edits and revert to previous versions if needed.

5. Document & Version Control
Version control is another area where a folder structure system shines. As projects evolve, documents go through multiple iterations, and keeping track of these versions manually through emails or ad hoc file-saving methods can be a huge challenge. However, with a structured file naming system that includes version numbers (e.g., “V1”, “V2”), or a platform that tracks changes automatically, you can easily see which version is the latest and what changes have been made over time.

This makes it easy to trace the evolution of a document and avoid confusion or errors due to outdated versions.

6. Improved Productivity & Reduced Risk of Errors
A consistent folder and file naming structure boosts productivity by providing clarity, reducing time spent searching for documents, and minimizing the likelihood of mistakes. When team members are confident that files are well-organized and named consistently, they can focus on their work rather than wasting time on administrative tasks. This not only improves efficiency but also reduces the risk of errors caused by miscommunication or outdated documents.

Conclusion
In today’s collaborative work environment, a clear folder and file naming structure is essential for managing documents efficiently, controlling access, and ensuring smooth teamwork. By organizing files logically, adopting a consistent naming convention, implementing access control, and avoiding the chaos of email-based sharing, you can improve collaboration and prevent costly mistakes. It’s time to move beyond the inefficiencies of email threads and embrace a structured approach to file management that supports both collaboration and control.

By creating a clear, organized system that everyone on the team can follow, you’ll ensure your project is not only efficient but also secure and streamlined for the long term.

Here’s a suggested folder structure for managing a project:
1. Project Overview
• 1.1 Project Charter
• 1.2 Business Case
• 1.3 Scope Statement
• 1.4 Stakeholder Register
• 1.5 Communication Plan
2. Planning
• 2.1 Project Plan
• 2.2 Schedule (Timeline)
• 2.3 Budget & Cost Estimates
• 2.4 Risk Management Plan
• 2.5 Quality Management Plan
• 2.6 Resource Plan
• 2.7 Procurement Plan
3. Execution
• 3.1 Task Assignments & Deliverables
• 3.2 Team Collaboration/Meeting Notes
• 3.3 Change Requests
• 3.4 Progress Reports
• 3.5 Issues Log
• 3.6 Risk Log
4. Monitoring & Control
• 4.1 Stage Reviews
• 4.2 Performance Reports
• 4.3 Quality Control Logs
• 4.4 Budget & Cost Tracking
• 4.5 Resource Utilization Reports
• 4.6 Issue Resolution
5. Closing
• 5.1 Final Deliverables
• 5.2 Post-Implementation Review
• 5.3 Lessons Learned
• 5.4 Project Closure Report
• 5.5 Final Audit/Assessment
6. Reference
• 6.1 Templates
• 6.2 Policies & Guidelines
• 6.3 Meeting Minutes
• 6.4 Contracts/Agreements
• 6.5 Correspondence
This structure ensures that all project elements are easily accessible and organized, promoting transparency and efficient management of the project lifecycle.

What are your best practices for file management in collaborative projects? Feel free to share your thoughts or tips in the comments below.

Top Tips for Running a Successful Public Engagement Forum

Running an effective public engagement forum can be challenging but rewarding. Whether you’re leading a technology panel, government discussion, or community meeting, ensuring a structured and respectful environment is key to maintaining engagement and trust. Based on past observations here are some best practices for running a public engagement forum:

1. Audience Estimation & Preparation:
It’s important to accurately estimate the number of attendees to ensure appropriate seating and resources. Consider using an Eventbrite-style booking system to forecast attendance and make adequate preparations.

2. Pre-Meeting Communication:
Providing clear, concise materials beforehand—such as an agenda, objectives, and roles—sets expectations and helps reduce confusion. Including a public feedback survey and relevant resources can also enhance attendee engagement.

3. Facilitation and Structure:
Appoint a dedicated facilitator to guide discussions, manage time, and keep questions on-topic. A lack of clear facilitation can lead to confusion, off-topic debates, and frustration, extending the meeting unnecessarily.

4. Clear Role Definition:
Ensure all participants (politicians, subject experts, business, public or charity representatives) understand their roles. Address any potential confusion up front, so attendees can direct questions appropriately. This helps prevent misunderstandings and keeps the conversation on track.

5. Manage Time Effectively:
Set a clear timetable and stick to it. Time management issues can lead to frustrations, especially when meetings run over their allotted duration. Be proactive in ensuring that discussions stay focused and efficient.

6. Address the Press:
Distribute a “press pack” to ensure accurate coverage. Without this, media outlets might miss the key messages or key resources you want to share with the community through the media.

7. Engage Key Stakeholders:
Involve a diverse set of subject matter experts, including politicians and business, public or charity representatives, to address a wider range of questions. This reduces the burden on specific individuals and helps avoid frustration among attendees.

8. Build Trust with Transparency:
Address any potential misunderstandings about the role of participants, especially for panels that are there to provide advice rather than make decisions. Clarifying these roles can help manage expectations and prevent unnecessary debates.

9. Encourage Active Participation:
Ensure that all stakeholders are prepared to contribute to the conversation. Their passive involvement can create a sense of disengagement and may lead to dissatisfaction among attendees.

By focusing on structure, clarity, and engagement, you can create a productive and transparent public forum that encourages open dialogue, fosters trust, and drives meaningful outcomes. Emphasizing clear communication, effective time management, and diverse representation will not only improve the quality of the discussion but also ensure that all voices are heard in a respectful and focused environment.

#PublicEngagement #Leadership #CommunityForums #StakeholderEngagement #TimeManagement #Facilitation #BestPractices

Is Efficiency Always a Win?

In the world of process improvement, methodologies like Lean Six Sigma and the Theory of Constraints offer logical, structured approaches to enhancing productivity and efficiency. As a programmer by background, I naturally gravitate toward these tools because they align with my understanding of how systems should function—efficiently and without unnecessary complexity. Just as extraneous code is not only wasteful but can lead to breakdowns, so too can redundant processes in organizations. Waste in time, money, resources, and skills doesn’t just detract from value—it can significantly disrupt the smooth functioning of any operation

I fully support the idea of process improvement, especially when it’s driven by bottom-up insights. Gaining an understanding of the lived experiences of both customers and employees, and using that information to drive incremental, systematic improvements, is powerful. However, I also advocate for a top-down perspective: Do we even need to be doing certain tasks? Over time, there’s a real danger of optimizing processes that, in the end, aren’t necessary at all. A periodic top-down review of roles, services, and products is vital for clarity and ensuring that we are aligned before making efficiency gains. Efficiency is wasted on processes that don’t contribute value.

One aspect of process improvement that concerns me is the growing reliance on metrics and dashboards. While these tools can be great for communication, they should never replace thoughtful analysis. The pursuit of success, driven by the constant monitoring of numbers, can lead to dashboards full of green indicators and seemingly positive results. Yet, these numbers often measure what’s easy to track, not necessarily what truly matters. Metrics should reflect real value creation, not just the things that make us look good.

I have mixed feelings about the idea of an “Information Room,” where data is displayed for all to see. While the convenience of having relevant information at our fingertips is appealing, it’s the conversation around that data that really matters. Dashboards can be useful for sparking discussion, but they should never replace in-depth dialogue. The key is in the conversations we have with teams—the ones that uncover the underlying issues, challenges, and progress that data alone can’t reveal. After all, life, much like any project, is a journey, not a snapshot.

While the concept of the Information Room sounds intriguing, the real issue lies in the prevalence of quick, shallow updates—like 10-minute PowerPoint presentations—without the necessary discussions that enable us to truly understand the content. With time and capacity often stretched thin, many organizations fall into the trap of simply skimming over presentations before rushing on to the next task.

For genuine and lasting improvement, we must go beyond the quick fixes and focus on deeply embedding Lean Six Sigma and the Theory of Constraints into our systems. It’s about truly understanding our processes and actions, rather than just implementing superficial changes and moving on to the next cycle. Sustainable progress requires a thoughtful, continuous approach.

#ProcessImprovement #LeanSixSigma #Productivity #Leadership #OrganizationalChange