Category: Uncategorised

The Value of a Steering Group in Complex Projects

Managing complex projects—especially those with political sensitivities and public scrutiny—requires careful oversight and strategic coordination. A Steering Group is an essential component of governance for ensuring that such projects stay on track, meet strategic goals, and navigate potential risks. Here’s why a Steering Group can make or break a project, particularly those that are large-scale, high-stakes, and politically charged.

Centralized Governance and Oversight
A Steering Group provides a single point of governance, ensuring that all projects align with the overall strategic objectives of the organization. This centralized oversight ensures that efforts remain coherent and consistent, even across multiple interconnected projects.

Robust Documentation and Governance
One of the primary responsibilities of a Steering Group is ensuring thorough documentation and governance. This is crucial for maintaining accountability and transparency. It ensures the project is well-documented and prepared for scrutiny by oversight bodies or public inquiries (UK Post Office or Covid Inquiries) —helping to mitigate risks before they become critical issues.

Effective Risk Management
A key benefit of a Steering Group is its ability to identify, assess, and mitigate risks—particularly in complex projects that face public and political scrutiny. Steering Groups help manage interdependencies and aggregate risks, keeping a close watch on potential pitfalls that could derail the project.

Efficient Resource Management
Steering Groups play an instrumental role in allocating resources effectively, ensuring that projects are properly staffed and supported. By monitoring resource needs across multiple initiatives, they help prevent overburdening any single team and optimize resource distribution to meet the strategic goals.

Enhanced Communication
Clear, streamlined communication is vital in any project, especially one under public or political scrutiny. A Steering Group reduces the risk of miscommunication, eliminates information silos, and ensures that information is shared efficiently among stakeholders. This includes managing public and press queries to maintain a positive public image.

Strategic Prioritization
A Steering Group helps prioritize projects and tasks based on their strategic importance and urgency. This ensures that critical issues are addressed promptly, maintaining focus on the project’s key deliverables while managing the overall workload.

Coordination with Related Programs
Large-scale projects often have overlapping objectives with other programs. A Steering Group ensures that these efforts align effectively, promoting collaboration, addressing shared responsibilities, and making the most of common interests.

Enhanced Accountability
Accountability is a cornerstone of effective project management. A Steering Group provides a structured framework to document and justify decisions and actions, maintaining the credibility of the project and upholding trust among stakeholders—especially during public inquiries.

Learning from Past Inquiries
Steering Groups don’t just respond to immediate issues—they also learn from past experiences. By examining examples of both good and bad governance from past inquiries, they can implement best practices and avoid common pitfalls.

Risks of Proceeding Without a Steering Group

Without a Steering Group, the project can face significant challenges that compromise its success:

Lack of Coordination: Projects may operate in silos, leading to duplication of efforts, inconsistent messaging, and missed opportunities for synergy.
Increased Risk Exposure: Without proper oversight, risks may go unnoticed, leading to crises, particularly in politically sensitive projects.
Resource Mismanagement: Inefficient allocation of resources can cause projects to stall or fall behind.
Communication Breakdowns: Fragmented communication channels increase the risk of misunderstandings, errors, and delays.
Strategic Misalignment: Without a clear governing body, projects may veer off course, resulting in a lack of coherence and direction.

Key Roles in a Steering Group

To operate effectively, a Steering Group requires various key roles that contribute to its decision-making and oversight functions:

1. Project Sponsor: Provides the overall direction and funding, securing resources and ensuring alignment with organizational goals.
2. Project Manager: Oversees the day-to-day activities, ensuring tasks are completed on time and the project stays on track.
3. Subject Matter Experts (SMEs): Offer specialized knowledge and insights, essential for making informed decisions and solving technical challenges.
4. Stakeholder Representatives: Represent key stakeholders, ensuring their needs and concerns are considered in the decision-making process.
5. Risk Manager: Identifies and mitigates potential risks, safeguarding the project from issues that could derail progress.
6. Communications Lead: Manages both internal and external communications, ensuring information flows smoothly across all channels.
7. Finance Manager: Oversees the budget and financial planning, ensuring that resources are allocated efficiently.
8. Legal Advisor: Provides legal guidance and ensures the project complies with relevant regulations.
9. Quality Assurance Lead: Ensures that project deliverables meet quality standards and maintain integrity.
10. IT Support: Manages technical infrastructure and support, ensuring the project’s technological components run smoothly.

Conclusion

In summary, a Steering Group is essential for guiding complex projects through their lifecycle. With its oversight, coordination, and strategic direction, a Steering Group helps manage risks, resources, and communication, ensuring that the project stays on track to achieve its objectives. Especially when preparing for public scrutiny, a Steering Group provides the necessary structure to maintain good governance and avoid chaos or mismanagement. Without one, a project is at risk of misalignment, inefficiency, and missed opportunities, which can lead to costly setbacks and public disillusionment.

Optimizing Help Desk Processes: Ensuring Accuracy and Efficiency in Responding to Inquiries

In today’s fast-paced environment, customers and users expect quick answers to their queries. However, the most efficient approach to handling inquiries often requires more time to ensure that the response is accurate and comprehensive. While it may be tempting to provide an immediate answer, doing so without fully considering all aspects of the issue may result in incomplete or even inaccurate information. This is especially true when multiple stakeholders, opinions, or considerations are involved.

Structured help desk processes are essential for providing quality service while ensuring efficiency. Rather than jumping straight to an answer, a methodical approach often leads to better outcomes for both the customer and the organization.

The Importance of Team Collaboration in Addressing Complex Queries

When addressing complex queries, especially those involving multiple stakeholders or considerations, it’s vital to bring the right team together. Often, a single person won’t have all the necessary information or context to answer a question accurately. In such cases, convening a team of specialists, each bringing their expertise, can ensure that all aspects of the issue are covered.

For instance, in IT support, it’s not uncommon for a help desk to take the initial request and then coordinate with technical specialists who have the necessary expertise. The help desk serves as a hub, managing communication and directing the issue to the right person or department. This process not only ensures that the correct response is given but also frees up the technical specialists to focus on solving the problem rather than being distracted by handling incoming inquiries.

This model can be applied across industries and in public sector services, where accuracy is paramount, and off-the-cuff responses could lead to mistakes or misinterpretation.

Structuring Your Help Desk Approach

To manage incoming inquiries efficiently, a clear process must be in place. Here’s an enhanced approach that balances speed, accuracy, and collaboration:

1. Categorize Questions:
Direct Response: If the information is readily available and the question is straightforward, provide an immediate response.
FAQ Referral: For frequently asked questions, direct customers to the FAQ database. Regularly update FAQs to ensure that they reflect current issues and solutions.
Holding Response: For complex or multi-faceted queries, provide a holding response. Acknowledge the question, provide a timeline for when a full answer will be given, and ensure that relevant stakeholders are engaged.

2. Convener Role:
For complex inquiries, it’s crucial to convene a team of specialists or stakeholders who can address different aspects of the issue. This may involve scheduling meetings or coordinating efforts between departments, ensuring everyone contributes their expertise.
The person or team responsible for managing the query (often the help desk or customer service representative) should ensure that all relevant parties are brought into the conversation. This may include technical specialists, legal advisors, or subject matter experts, depending on the nature of the query.
This collaborative approach ensures that all opinions and considerations are addressed, and the final response is well-rounded and accurate.

3. Key Principles:
Clear Expectations: Set clear expectations for when an immediate response can be provided and when more time is needed.
Standardized Responses: Utilize pre-approved templates or responses for frequently asked questions. This ensures consistency across communication and reduces the workload on the team.
Collaboration and Coordination: When a question requires input from multiple departments or stakeholders, the convener must ensure that communication is streamlined, and all necessary perspectives are considered.
Commitment to Accuracy: Always prioritize the accuracy of the response over speed. It’s better to take a little more time to get the answer right than to provide a rushed, potentially incorrect response.

The Role of Communication in Building Trust

One of the most important aspects of handling inquiries is communication. Customers don’t mind waiting as long as they know when to expect a response and trust that the answer will be correct. The worst scenario is when there’s complete silence. Acknowledging the query and providing a timeline for follow-up demonstrates accountability and builds trust.

For instance, even if the issue requires days of investigation, acknowledging receipt and confirming the timeline for a response is often enough to maintain customer satisfaction. This commitment shows the customer that their concern is being taken seriously and that the organization values accuracy over expedience.

Top Tips for Managing Help Desk Queries Effectively:

1. Set Clear Expectations: Always inform the customer about when they can expect a response. Being transparent about timelines reduces frustration and sets realistic expectations.
2. Use the FAQ for Simplicity: Direct users to the FAQ when dealing with common questions. Regularly update the FAQ to keep it relevant and helpful.
3. Engage the Right People: When necessary, convene a team of specialists to ensure all aspects of a complex query are addressed thoroughly.
4. Acknowledge and Follow Up: Always acknowledge the query, even if a complete answer can’t be provided immediately. Communicate a follow-up timeline and stick to it.
5. Maintain Transparency: If there’s a delay or further investigation needed, let the customer know. Honesty about the process helps maintain trust.

Conclusion

Optimizing help desk processes isn’t just about answering questions quickly; it’s about ensuring accuracy, efficiency, and clear communication. By categorizing inquiries, convening the right team of specialists, and setting clear expectations, you can ensure that responses are comprehensive and well-informed. Ultimately, a thoughtful, structured approach to handling inquiries leads to better customer satisfaction, reduces mistakes, and improves overall organizational efficiency.

#HelpDesk #CustomerService #Efficiency #Accuracy #Teamwork #StakeholderEngagement #CustomerExperience #ProblemSolving #WorkplaceEfficiency

The Difference Between Tasks and Deliverables

In project management, understanding the distinction between tasks and deliverables is fundamental to achieving success. Tasks are the specific actions or steps that contribute to a larger objective, while deliverables are the tangible outcomes or products resulting from completing those tasks.

A task is typically something small and time-bound, like “conduct market research” or “write the project report.” Deliverables, on the other hand, represent the completed outputs of those actions—such as a finalized “market research report” or a “project summary.” Deliverables are often seen as the key milestones that signal a project’s progress.

The Benefits of Using Deliverables to Measure Progress

Shifting focus from tasks to deliverables offers several key advantages. While tasks represent individual actions, deliverables are concrete and measurable outputs that clearly indicate progress in a project. Tracking deliverables as the primary measure of progress ensures that the project moves toward its end goals in a meaningful way.

By focusing on deliverables, teams avoid getting bogged down in an endless list of tasks, which may not always reflect the overall success of the project. Deliverables, being tangible and outcome-oriented, provide a clearer picture of what has been completed and what is still needed. This shift also helps avoid the “busyness trap”—where teams are busy with tasks but may not be advancing the project in a meaningful direction.

The Role of a Deliverable Schedule or Log

A deliverable schedule or log is an invaluable tool for tracking the progress of a project. It provides a structured way to organize and monitor deliverables, ensuring clarity and accountability within the project team. This tool helps keep everyone on the same page and ensures that nothing falls through the cracks.

A typical deliverable log includes the following elements:
– Item: The deliverable number or identifier.
– Author: The individual responsible for producing the deliverable.
– Reviewer: The person responsible for reviewing and providing feedback on the deliverable.
– Approver: The person who will approve the deliverable once it’s complete.
– Target-Date: The date by which the deliverable is expected to be completed.
– Done-Date: The actual date when the deliverable is finished.
– Status: The current stage of the deliverable (e.g., draft, final, approved).
– Comments: Any notes or relevant updates.

For example:

Table

Item	Author	Reviewer	Approver	Target-Date	Done-Date	Status	Comments
Deliverabe 001	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	draft	Notes
Deliverabe 002	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	final	Notes
Deliverabe 003	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	approved	Notes
Deliverabe 004	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	draft	Notes
Deliverabe 005	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	final	Notes
Deliverabe 006	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	approved	Notes
Deliverabe 007	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	draft	Notes
Deliverabe 008	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	draft	Notes
Deliverabe 009	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	final	Notes
Deliverabe 010	Name	Name	Name	dd/mm/yyyy	dd/mm/yyyy	approved	Notes

How a Deliverable Log Enhances Accountability and Transparency

A well-maintained deliverable log boosts accountability by clearly assigning responsibility for each deliverable. It establishes a clear chain of command—from authorship to approval—ensuring that all stakeholders are aware of who is responsible for each piece of the project. Additionally, the log provides a transparent timeline for deliverables, helping teams and stakeholders stay informed of progress and deadlines.

The log also serves as a tool for proactive problem-solving. If a deliverable is delayed or encounters issues, the log makes it easy to identify which deliverable needs attention and which team member is responsible for addressing the problem. This ensures that any potential issues are spotted early, preventing delays in the overall project timeline.

Conclusion

By using deliverables as a key measure of progress, project managers can shift the focus from completing tasks to achieving tangible outcomes that drive the project toward completion. A deliverable schedule or log is an essential tool for tracking these milestones, ensuring accountability, and maintaining a clear and transparent project timeline. Ultimately, this approach leads to better project management, clearer communication, and more successful outcomes.

Effective Stakeholder Management through DISC, RACI, and the Power-Interest Matrix

Stakeholder management is a critical aspect of project success. Understanding your stakeholders’ communication preferences and aligning them with the project’s needs can make the difference between successful outcomes and missed opportunities. By incorporating tools like DISC, RACI, and the Power-Interest Matrix, project managers and leaders can create more structured, effective communication plans that cater to diverse stakeholder needs and ensure transparency and engagement throughout the project lifecycle.

Understanding DISC and Its Application in Stakeholder Communication

DISC is a well-known behavioral model used to understand individual communication styles and preferences. It divides personalities into four primary traits:

Dominance (D): Direct, results-oriented, and driven by challenges. People with a dominant style prefer quick, clear, and assertive communication. They value efficiency and want to get to the point quickly.
Influence (I): Enthusiastic, social, and focused on building relationships. Influencers prefer engaging, interactive communication and often need to feel emotionally connected to the message.
Steadiness (S): Calm, supportive, and team-oriented. Steady personalities prefer stable, predictable communication with a focus on collaboration and harmony.
Conscientiousness (C): Analytical, detail-oriented, and focused on accuracy. Conscientious individuals need precise, data-driven communication with a clear focus on facts and processes.

By understanding the DISC profiles of key stakeholders, you can tailor your communication to resonate with their unique preferences. For example, while a Dominant stakeholder might prefer concise reports, a Steady stakeholder may appreciate more thorough and thoughtful updates. This allows for better engagement, minimizing misunderstandings and fostering stronger relationships.

Incorporating the RACI Matrix into Stakeholder Management

The RACI matrix is an essential tool for clarifying roles and responsibilities within a project. RACI stands for:

Responsible: The person who performs the task or activity.
Accountable: The person who ensures the task is completed correctly and holds the final authority.
Consulted: Individuals whose opinions are sought before decisions are made.
Informed: Those who are kept up-to-date on progress or decisions.

Using RACI in conjunction with DISC can help define how stakeholders should be engaged and how information flows through the team. For example, individuals who are accountable for a task may need regular meetings, while those who are only informed may just require periodic updates. This ensures stakeholders receive the right amount of information at the right time, aligning their involvement with their roles and communication preferences.

The Power-Interest Matrix for Prioritizing Stakeholder Communication

The Power-Interest Matrix is a tool for assessing and categorizing stakeholders based on two key factors: their level of power (ability to influence the project) and their level of interest (degree of involvement or concern with the project’s outcomes).

Stakeholders can be classified into four categories:

High Power, High Interest: These are the stakeholders who need to be closely managed and communicated with frequently. They have both the ability to influence the project and a vested interest in its success.
High Power, Low Interest: These stakeholders may not be actively involved but still have the authority to affect the project. They require regular updates to keep them informed and maintain their support.
Low Power, High Interest: These stakeholders are highly engaged but lack decision-making power. They benefit from consistent communication, ensuring they are kept in the loop and their concerns are addressed.
Low Power, Low Interest: These stakeholders have minimal impact on the project. Communication with them can be less frequent and less detailed, focusing on keeping them informed as necessary.

Table

Power Interest Framework	Low Power	High Power
High Interest	Low Power, High Interest: These stakeholders are highly engaged but lack decision-making power. They benefit from consistent communication, ensuring they are kept in the loop and their concerns are addressed.	High Power, High Interest: These are the stakeholders who need to be closely managed and communicated with frequently. They have both the ability to influence the project and a vested interest in its success.
Low Interest	Low Power, Low Interest: These stakeholders have minimal impact on the project. Communication with them can be less frequent and less detailed, focusing on keeping them informed as necessary.	High Power, Low Interest: These stakeholders may not be actively involved but still have the authority to affect the project. They require regular updates to keep them informed and maintain their support.

By mapping stakeholders onto this matrix, you can prioritize communication efforts based on their influence and interest, ensuring that key players receive the necessary attention while avoiding overcommitting resources to less critical stakeholders.

Table

Stakeholders	Rep / Person	Role / Job / Inrerest	Benefit/Negative	For/Against	Last comm	How / Method	Style Preference
Stakeholder Group 1	Representative Name	BA	Benefits	For	02-Nov	F2F	Dominance (D)
Stakeholder Group 2	Representative Name	Consultant	Does not benefit	For	16-Jun	Email	Influence (I)
Stakeholder Group 3	Representative Name	BA	Benefits	Against	16-Jun	Coffee Meeting	Steadiness (S)
Stakeholder Group 4	Representative Name	Tech Lead	Does not benefit	Against	13-Nov	Web-Update	Conscientiousness (C):
Stakeholder Group 5	Representative Name	Proc Lead	Benefits	For	02-Nov	Newsletter	Dominance (D)
Stakeholder Group 6	Representative Name	Other	Benefits	For	16-Jun	Presentation	Influence (I)
Stakeholder Group 7	Representative Name	Other	Benefits	Against	16-Jun	Email	Steadiness (S)
Stakeholder Group 8	Representative Name	Other	Does not benefit	Against	13-Nov	Coffee Meeting	Conscientiousness (C):

Building a Simple and Effective Communications Plan

A robust communications plan ensures that all stakeholders are kept informed, engaged, and aligned throughout the project. The plan should specify the communication events, the target audience, the goals of each communication, the frequency, and the responsible party. Here’s an example of how to structure a communications plan:

Table

Communication Event	Audience	Goal	When / Frequency	Responsible	Method
Project Kick-Off Meeting	Project Steering Committee	Gather the information required for project initiation plan	Stage 3 – Project Planning & Kick-off	Project Manager	Meeting
Task Progress Updates	Task Owners / Project Manager	Share the progress made on project tasks	Daily	Task Owners / Project Manager	Project MS Teams Site / Email
Project Team Meeting	Project Team	To review tasks, actions, risks, issues etc	Weekly	Project Manager	Meeting
Project Status Reporting	Project Steering Committee & Team	Communicate the current status, risks, issues, highlight achievements and next planned tasks	Weekly	Project Manager	Report distributed via Email linked to projects MS Teams site
Project Budget Updates	Project Manager / Finance Team	Share the status of budget spent to date with the finance team for tracking purposes	Monthly	Project Manager	Budget updated and shared between PM & Finance team
Project Stage / Milestone Updates	Project Steering Committee	Review project status, signoff project stage allowing progressing to next stage	At Milestones	Project Manager	Meeting
PMO Office Reporting	ITComm / ExCo	Provide high level project overview via PMO office. PM to update PMO on current status	Monthly	Project Manager / PMO	Report / Meeting
Project Closure Meeting	Project Team	Review lesson learned register, prepare items for Project Closure Report	Stage 5 – Project Closure	Project Manager	Meeting

This structured approach ensures that communication is purposeful, focused on key milestones, and aligned with stakeholders’ needs. It also avoids information overload while maintaining the transparency and accountability necessary for successful project management.

Conclusion

By combining DISC, RACI, and the Power-Interest Matrix, you can create a stakeholder management strategy that is both structured and adaptable. Tailoring your communication to each stakeholder’s preferences ensures greater engagement and support throughout the project lifecycle. Whether you are leading a small team or managing a complex project, applying these frameworks will improve clarity, reduce conflicts, and enhance overall project success.

The Essence of Lean and Six Sigma: Easier, Better, Faster, Cheaper

When we think about Lean and Six Sigma, the first words that often come to mind are efficiency, improvement, and optimization. But at the core of these methodologies lies a simple yet powerful principle, which was first articulated by the legendary Shigeo Shingo, a key architect of the Toyota Production System. His approach to continuous improvement is not just about making things work—it’s about making them better in the right order.

Shingo famously said: “Make things easier, better, faster, and cheaper.”

This principle is so much more than a catchy phrase. It encapsulates the essence of what it means to be Lean and Six Sigma. Let’s break down why it’s important and how it works.

1. Easier First

The journey to improvement begins by simplifying processes. In the world of Lean and Six Sigma, removing complexity is the first priority. Streamlining processes, eliminating unnecessary steps, and reducing confusion creates the foundation for everything else. Once something is made easier, it opens up the potential for other improvements to take place more smoothly.

2. Better Follows

Once you’ve simplified your processes, you can begin focusing on making them better. In Lean, this means refining the flow of work, enhancing quality, and minimizing waste. In Six Sigma, it means improving consistency, reducing variability, and ensuring that processes meet the desired standards. By first making things easier, you lay the groundwork to refine and elevate the output.

3. Faster Comes Next

With easier processes and better quality, the next step is increasing speed. Lean principles emphasize the importance of reducing cycle time and eliminating bottlenecks. When processes are easier and better, they naturally become more efficient, allowing you to deliver products or services more quickly. This agility is a key driver in staying competitive in today’s fast-paced environment.

4. Cheaper Last

Finally, with improvements in ease, quality, and speed, you can reduce costs. Lean thinking teaches that when inefficiencies are eliminated, and processes are optimized, the result is lower operational costs. However, cost reduction isn’t the first focus; it’s the outcome of making things easier, better, and faster. Cost reductions are a natural consequence of the improvements that come before.

Why This Order Matters

The order in which Shingo proposed these improvements isn’t arbitrary. It’s about laying the proper foundation before jumping into cost-cutting. By focusing on making processes easier, we create an environment where further improvements are more sustainable and impactful. Trying to reduce costs without addressing the underlying inefficiencies first can lead to temporary fixes that don’t deliver long-term value.

In essence, Shigeo Shingo’s words capture the very spirit of Lean and Six Sigma: a focus on continuous, sustainable improvement. The process isn’t just about getting things done faster and cheaper—it’s about creating a culture where simplicity, quality, and efficiency go hand in hand.
Final Thoughts

Adopting the mindset of “easier, better, faster, cheaper” can transform the way we approach improvement in any organization. By following this approach, we ensure that each step of the process builds on the previous one, resulting in a cycle of continuous growth and refinement.

If you’re implementing Lean and Six Sigma in your organization, remember this simple yet profound idea. Start by making things easier, and let everything else follow naturally. When you do this, you’ll set yourself up for success that’s not just faster or cheaper, but more sustainable and impactful.

Mastering the RAID Log: A Unified Approach to Managing Project Risks

In the world of project management, effectively tracking and managing risks is crucial to ensuring the success of any initiative. One of the most common and widely used tools for managing risks is the RAID log, which stands for Risks, Assumptions, Issues, and Dependencies. These four elements are vital to identifying and mitigating potential obstacles that could affect the project’s timeline, cost, quality, and overall success. But how can you ensure that your RAID log remains a useful, actionable tool throughout the entire project lifecycle? And how can you streamline it to make sure you’re covering all the necessary bases without being bogged down by excessive documentation?

Understanding the Four Elements of the RAID Log

Each of the four categories in a RAID log plays an essential role in tracking the various elements of a project:

Risks: These are potential problems that may occur in the future and impact the project. They could affect any aspect of the project, including cost, scope, timeline, and quality. A well-defined risk is typically evaluated based on its likelihood and impact.

Assumptions: Assumptions are conditions or factors believed to be true for the success of the project. They often need validation but are accepted as part of the project framework. If assumptions turn out to be false, they could pose significant risks or issues to the project.

Issues: Issues represent current problems that are already affecting the project. Unlike risks, which are hypothetical, issues are tangible and require immediate attention and resolution.

Dependencies: Dependencies are external factors or other projects that your project’s success depends on. If these dependencies are delayed or face problems, it could affect your project’s outcome.

Streamlining the RAID Log: Combining Categories into One Spreadsheet

A common challenge with traditional RAID logs is that they can become fragmented, with different logs for risks, assumptions, issues, and dependencies. This fragmentation can make it harder to track interconnected elements and monitor progress. To make your RAID log more efficient, consider consolidating all four elements into a single, unified spreadsheet.

Each item can be categorized as a risk, assumption, issue, or dependency. By adding a simple checkbox or dropdown menu in your log, you can mark whether the entry pertains to a risk, assumption, issue, or dependency. This approach helps streamline the tracking process and ensures you aren’t duplicating efforts across multiple logs.

Additionally, the other elements—such as risk owner, mitigating actions, and impact descriptions—are often the same across all four categories. Therefore, maintaining them in a single log reduces repetition and simplifies data entry.

Sample RAID Log Template

Below is an example of how you could structure your consolidated RAID log to track risks, assumptions, issues, and dependencies effectively. This log includes essential fields such as risk ID, status, likelihood, impact, risk owner, and mitigating actions.

Table

ID	Type	Description	Impact	Likelihood (1-3)	Impact (1-3)	Severity	Mitigating Actions	Owner
R001	Risk	Project competing for resources with others	Delay in project timelines	3	3	9	Early communication, set clear priorities	EL
A001	Assumption	Team members will be available as needed	Delay if unavailable	2	3	6	Confirm resource availability early	CH
I001	Issue	Key stakeholder is unresponsive	Delay in decision-making	3	3	9	Escalate to higher management	CH
D001	Dependency	Completion of Task 1 is needed for Task 2	Delay in Task 2 completion	3	2	6	Monitor progress, communicate with Task 1 team	EL

By categorizing each entry as a risk, assumption, issue, or dependency, you ensure that all critical elements are being tracked in one place, making it easier to identify and address any obstacles that may arise.

Tracking Risks at Different Levels: Project, Program, and Business

A key part of risk management is ensuring that risks are being tracked at the appropriate levels. Risks should be considered at three levels:

Project Level: These are risks that directly affect the project’s outcome. They typically include factors such as time, cost, quality, scope, and communications. For example, resource shortages, delays in milestones, or unforeseen costs may all be project-level risks. It’s crucial to track and address these as part of your daily project management process.

Program Level: Risks at this level affect multiple projects within a program. For instance, if one project is delayed and that delay impacts other dependent projects, this becomes a program-level risk. Dependencies between projects should be carefully managed to prevent cascading effects across the entire program.

Business Level: These are the most severe risks, which can affect the entire organization. Failures in key projects can impact business operations, reputation, or financial health. For example, if a project to launch a new product fails, it could impact the company’s revenue, reputation, or market position. Business-level risks should be reported to senior leadership to ensure strategic decisions are made to mitigate these impacts.

Different Types of Risks

Understanding the types of risks that could affect a project is essential for effective mitigation. Some common categories include:

Operational Risks: These relate to the day-to-day functioning of the project or organization. They could involve process inefficiencies, resource shortages, or logistical issues.

Financial Risks: These include risks related to the project’s budget, funding sources, or financial stability. They may involve cost overruns, inadequate budgeting, or fluctuating exchange rates.

Reputational Risks: These risks affect the public perception of the organization or project. They could result from poor product quality, project delays, or mismanagement that damages the company’s image.

Compliance Risks: These relate to the potential for failing to comply with regulations, laws, or industry standards. Non-compliance could result in legal penalties or operational shutdowns.

Strategic Risks: These arise when projects fail to align with the organization’s strategic goals. For instance, pursuing a project that doesn’t align with the business’s vision or market needs could lead to failure.

Risk Management Strategies: Treat, Tolerate, Transfer, Terminate

Once risks are identified, it’s important to determine the most appropriate strategy to address them. The four main risk management strategies are:

Treat: Proactively addressing and reducing the risk’s impact or likelihood through mitigation plans. For example, implementing better training to reduce the risk of operational errors.

Tolerate: Accepting the risk if its impact is minimal or if mitigation is too costly. For example, a minor cost overrun might be tolerated if the project is still within budget.

Transfer: Shifting the responsibility for managing the risk to another party. For instance, transferring financial risks to an insurance provider or outsourcing a risky task to a third-party vendor.

Terminate: Eliminating the risk by changing the project scope, approach, or timeline. This might involve removing a problematic feature or adjusting the project’s deliverables to avoid unnecessary risks.

Conclusion

Managing risks is a cornerstone of successful project management. By consolidating risks, assumptions, issues, and dependencies into a single RAID log, teams can ensure better clarity and tracking. Categorizing and updating the RAID log at the project, program, and business levels ensures no risks are overlooked, and employing appropriate risk management strategies can help mitigate potential problems before they arise. With the right approach to risk tracking and management, projects can stay on track, even in the face of unexpected challenges.

#ProjectManagement #RiskManagement #RAIDLog #BusinessStrategy #RiskMitigation #ChangeManagement

The Merits of Simplifying Meeting Management: One Spreadsheet for All Actions, Decisions, and Reviews

In the fast-paced world of project management and organizational decision-making, keeping track of multiple documents for each meeting, decision, and task can quickly become overwhelming. Traditional methods often require separate agendas, meeting minutes, action logs, and various reports. While all these documents serve important purposes, they can create confusion, clutter, and inefficiency. What if you could streamline the entire process into a single, easy-to-manage spreadsheet? Here’s why consolidating your meeting management into one document makes life simpler, more efficient, and more organized.

Simplicity and Transparency in One Spreadsheet

Having a single spreadsheet for all your meeting actions, decisions, and reviews can significantly reduce complexity. Instead of toggling between different files and searching for specific details across multiple platforms, everything is in one place, easily accessible and instantly updateable. Whether you’re tracking tasks, decisions, or actions, you can quickly check who’s responsible, what the timeline is, and what progress has been made—all within the same document.

This approach offers a transparent view of all ongoing activities. Each item, from actions to decisions, is recorded with clear ownership, start and end dates, and progress notes. It’s all laid out in one concise spreadsheet, meaning you don’t have to waste time searching for the information you need.

Table

ID	Category	Item/Task	Owner	Start Date	End Date	Progress/Details	Reason/Decision	Consulted	Conclusion Date	Document Name
1	Action	Task 1	[Owner]	[Start Date]	[End Date]	[Progress/Notes]
2	Action	Task 2	[Owner]	[Start Date]	[End Date]	[Progress/Notes]
3	Decision	Decision 1		[Start Date]	[End Date]		[Reason/Decision]	[Consulted]	[Conclusion Date]	[Document Name]
4	Task	Task 3	[Owner]	[Start Date]	[End Date]	[Progress/Notes]

A Unified, Streamlined Approach

In traditional project management, you’re often juggling various types of documents:

Agendas for meeting preparations.
Meeting minutes to capture discussions and decisions.
Action logs to track who’s doing what and when.
Review documents to assess progress on individual deliverables.

Each of these documents requires updates, revisions, and careful attention to detail. More documents often mean more opportunities for mistakes, confusion, or missed details. By combining all of this into one spreadsheet, you eliminate the need for multiple documents that often repeat or overlap information. Now, you only need to update one sheet for a clear view of your project’s evolution, making your work more streamlined and manageable.

Focusing on the Essentials

This simplified approach doesn’t mean you’re sacrificing important details. On the contrary, it ensures that key aspects like accountability, progress, and decisions are captured in a streamlined way. Your spreadsheet will still include the critical elements such as:

Actions with owners, start and end dates, and progress notes.
Decisions with reasoning, consultations, and conclusions.
Tasks with deadlines and progress updates.

The result? You spend less time updating redundant documents and more time on what really matters: moving your projects forward.

Task and Deliverable Tracking

One of the greatest advantages of this unified spreadsheet approach is that it seamlessly integrates task management with deliverable tracking. If an action is part of a larger deliverable, it’s easy to add a note or link to the associated deliverable. This way, your spreadsheet not only keeps track of individual tasks but also provides insight into the broader project deliverables and timelines.

This is particularly helpful for daily or weekly meetings, where you can quickly review the status of each task or deliverable and update progress without having to consult multiple project plans. While a project plan remains essential as the overall blueprint for your initiatives, this spreadsheet gives you a dynamic tool to respond to that plan with real-time information on progress and changes.

An Easy-to-Update System for Real-Time Progress

In fast-moving environments, decisions and actions are made regularly, and changes happen frequently. A single spreadsheet allows you to keep track of everything in real time. Whenever new tasks arise, decisions are made, or progress is achieved, you only need to update one document. No need to redo meeting minutes or agendas—simply log the changes in your all-in-one sheet.

With all updates in one place, everyone involved can quickly see where things stand without the need for detailed follow-ups or status meetings. It also makes reporting much easier, as you don’t have to reference multiple documents or project plans. Just refer to the spreadsheet, and you’ll have everything you need at your fingertips.

A Clearer Focus on Team Performance

This simple, transparent system helps improve team accountability. With each action and decision clearly documented, everyone knows who is responsible for what and can track progress with minimal effort. It’s also easier to spot potential bottlenecks or issues early on, allowing for timely intervention and support. Additionally, by linking tasks directly to deliverables and timelines, you’ll maintain focus on the outcomes, not just the process.

Conclusion: The Power of One Spreadsheet

Ultimately, a single spreadsheet for actions, decisions, and reviews offers a more organized, efficient, and transparent way to manage your projects. It’s not meant to replace the project plan itself—rather, it complements it by providing a live, actionable record of your daily or weekly progress. Whether it’s a task or a major deliverable, having everything in one place gives you clear visibility into the current state of affairs, without the clutter of multiple documents. By making it simpler to track tasks, decisions, and progress, you free up time and energy for what really matters: getting things done.

Scrum + Waterfall = Scrummerfall: Bridging Structure and Flexibility

Waterfall approach

| he Waterfall approach is a traditional project management methodology that focuses on a linear, step-by-step process. It emphasizes structure, clear roles, accountability, and defined outcomes. With Waterfall, each phase flows into the next, and teams typically operate within a predefined set of rules and objectives. It’s ideal for projects with predictable, repeatable tasks, where clear planning and control are paramount. However, its rigid structure can falter in dynamic, complex environments where change is frequent, and outcomes are uncertain. For example, Waterfall struggles in areas requiring adaptability and quick shifts, such as political, emergent, or highly innovative projects.

Agile framework

In contrast, Scrum is an agile framework that thrives in uncertainty. It focuses on enabling teams, especially those of experts, to solve problems collaboratively. Rather than directing every step, Scrum facilitates the team’s self-organization, supporting innovation and adaptability. It allows for ongoing refinement of tasks based on new insights and changing conditions. Scrum emphasizes continuous improvement through short, iterative cycles (sprints), where teams review, plan, and adjust their approach frequently.

Combining

Combining these two frameworks creates a “Scrummerfall” approach, where the structured governance of Waterfall and the flexibility of Scrum coexist. This hybrid model allows teams to manage emergent tasks through Scrum while maintaining the rigorous controls and deliverables of Waterfall.

Project Plan

Phase / Task	Start	End	% Complete	Owner
Task 001	01-Mar	01-Mar	100	AB
Task 002	01-Mar	01-Mar	90	AB
Task 003	01-Mar	01-Mar	50	CD
Task 004	01-Mar	01-Mar	0	EF
Task 005	01-Mar	01-Mar	0	AB
Task 006	01-Mar	01-Mar	0	AB

Routine Meetings

Agenda	Who	Time
Review last meeting commitments	AB	5mins
Item or Deliverable No1	AB	5mins
Item or Deliverable No2	CD	5mins
Item or Deliverable No3	EF	5mins
Item or Deliverable No4	EF	5mins
Item or Deliverable No5	EF	5mins
Review risks, issues, decisions	EF	5mins
Actions and tasks for next meeting	EF	5mins

A key aspect of Scrummerfall is having a clear “To-Do List” for products or deliverables, much like Scrum’s product backlog. By using tools like Kanban boards or task logs, the team can ensure accountability and track progress without getting lost in a detailed Gantt chart.

Kanban boards

Deliverable / ToDo	Not Started	In Progress	Stuck	Complete
Document				x
Report			x
Item		x
Document	x
Report	x
Item	x

Deliverables To Do List

Deliverable / ToDo	Author	Reviewer	Approver	Notes / Status
Document	AB	CD	EF	Approved dd/mmm
Report	AB	CD	EF	Approved dd/mmm
Item	AB	CD	EF	Final
Document	AB	CD	EF	Final
Report	AB	CD	EF	Draft
Item	AB	CD	EF	Draft

Governance

Governance in Scrummerfall is achieved through structured meetings. These meetings should have a clear agenda, defined outcomes, and should focus on risks, issues, dependencies, and decisions. Action items and decisions are tracked in logs and serve as a record, not an alternative to conversation.

Project initiation documents (a nod to Waterfall) define the project’s scope and deliverables, while regular updates help teams stay focused on the tasks at hand. By combining both approaches, Scrummerfall ensures that teams maintain flexibility and innovation while staying aligned with overarching goals and timelines.

Structure and flexibility

Scrummerfall is the ideal solution for projects that require both structure and flexibility, where innovation and predictability need to coexist. By adapting to the needs of the project and leveraging the strengths of both methodologies, teams can achieve their goals efficiently and effectively.

#Scrummerfall #ProjectManagement #Agile #Waterfall #Scrum #HybridApproach #Governance #Innovation #Teamwork

How To Run Better Meetings: Choosing The Right Format For Engagement

Introduction

Meetings are essential for collaboration, but not all meetings are created equal. One of the biggest challenges in any organization is ensuring meetings are productive and engaging rather than time-consuming and ineffective.

Instead of defaulting to a standard meeting structure, choosing the right format based on the objective can significantly improve participation and outcomes. Below are five effective meeting types, when to use them, and how to make them work.

1. Daily Stand-Ups (Scrum Meetings)

Best for: Quick updates, project tracking, and team alignment.
Duration: 10–15 minutes.
Participants: Small teams (5–10 people).
Format: Everyone shares (1) what they did yesterday, (2) what they’re doing today, and (3) any blockers.

Why it works: Short, focused, and action-oriented.
Best practices:
>Stand up (literally) to keep it quick.
>Set a timer to avoid over-explaining.
>Follow up separately for detailed discussions.

2. Town Hall Meetings

Best for: Organizational updates, major announcements, Q&A sessions.
Duration: 30–60 minutes.
Participants: Large groups (company-wide or department-wide).
Format: A senior leader presents updates, followed by a structured Q&A session.

Why it works: Builds transparency, alignment, and employee engagement.
Best practices:
>Use pre-submitted questions to ensure relevance.
>Keep presentations concise and engaging.
>Allow multiple ways to participate (live, chat, anonymous).

3. Working Sessions

Best for: Collaborative problem-solving, brainstorming, deep work.
Duration: 60–120 minutes.
Participants: Small to medium-sized teams (4–12 people).
Format: Facilitator-led, focused on active contribution rather than passive listening.

Why it works: Encourages hands-on engagement and accelerates decision-making.
Best practices:
>Have a clear objective (solve X problem, design Y solution).
>Use whiteboards, sticky notes, or digital collaboration tools.
>End with a summary of next steps.

4. Decision-Making Meetings

Best for: Approving proposals, aligning stakeholders, resolving conflicts.
Duration: 30–60 minutes.
Participants: Key decision-makers only.
Format: Present options → Discuss pros/cons → Make a decision.

Why it works: Eliminates indecision and lengthy back-and-forth discussions.
Best practices:
>Use a pre-read document to ensure attendees arrive prepared.
>Define a decision-making framework (e.g., consensus, majority vote, executive sign-off).
>Assign action items post-decision.

5. One-on-One Check-Ins

Best for: Coaching, feedback, performance discussions, resolving individual concerns.
Duration: 15–45 minutes.
Participants: Two people (leader-employee, mentor-mentee).
Format: Informal but structured; focus on progress, challenges, and goals.

Why it works: Builds trust, aligns expectations, and improves communication.
Best practices:
>Listen more than you speak.
>Use a consistent structure (updates, feedback, goals).
>Take notes and follow up on commitments.

KEY TAKEAWAYS: CHOOSING THE RIGHT MEETING TYPE

Stand-ups → Quick team updates.
Town halls → Organization-wide alignment.
️ Working sessions → Hands-on problem-solving.
Decision-making meetings → Faster approvals, fewer delays.
One-on-ones → Personal growth and alignment.

Stop defaulting to generic meetings! Choose the right format, and you’ll see higher engagement, better decisions, and more productive collaboration.

CASE STUDY: ENGAGING STAKEHOLDERS IN MEETINGS – WHEN THEY DON’T SHOW UP OR CONTRIBUTE

Introduction

Over the past three decades, I have led and supported a wide range of projects, process improvements, and organizational transformations. My case studies blend insights from real-world experiences, drawn from multiple organizations, anonymized, and generalized to extract broader lessons. Some aspects may resonate with your organization, while others may not, but the core themes reflect recurring challenges in leadership, collaboration, and stakeholder engagement.

One of the most persistent issues in any project or organizational initiative is ensuring that meetings are productive and that the right people are engaged. A common frustration is when key individuals fail to attend or, when present, contribute little of value. Understanding why this happens and how to address it can make a significant difference in the success of any initiative.

WHY DO PEOPLE NOT SHOW UP OR ENGAGE?

Several factors determine whether people attend and actively participate in meetings. These can be categorized into three main areas: role clarity, personal motivation, and meeting effectiveness.

1. Understanding Stakeholder Roles (RACI Framework)

A key factor in engagement is the role an individual plays in the decision-making and execution process. The RACI model (Responsible, Accountable, Consulted, Informed) provides a useful framework:

Responsible: Those who are actively working on the task. They have a direct role in execution and decision-making.
Accountable: The person ultimately answerable for the outcome. Their presence in meetings is often critical.
Consulted: Those whose input is valuable but who do not have execution responsibility. If their expertise is needed, they should be engaged at the right moments.
Informed: People who need updates but do not need to participate in the meeting itself. If they are not attending, consider whether they need to be there at all.

If someone is consistently absent or disengaged, it is worth revisiting their role. Are they incorrectly classified? Have they been invited unnecessarily? Does their presence add value to the discussion, or are they being asked to attend out of habit?

2. Motivation and “Skin in the Game”

People are more likely to engage when they have a stake in the outcome. Some key factors influencing motivation include:

Direct impact on their role – If the meeting does not affect their work, they may deprioritize it.
Incentives and consequences – If attendance is not tied to performance, accountability, or outcomes, it may be seen as optional.
Respect for their time – If previous meetings have been unproductive, overly long, or lacking clear outcomes, attendees may disengage or avoid them altogether.

A lack of attendance can sometimes indicate resistance to the change being discussed. If key stakeholders are not engaging, it may be necessary to address underlying concerns rather than simply mandating participation.

3. The Meeting’s Necessity and Value

Not all meetings need to happen. Before scheduling a meeting, consider:

Is a meeting the best format? Some decisions or updates can be handled more effectively via email, shared documents, or asynchronous collaboration tools.
Are the right people included? Avoid bloating the invite list with people who do not need to be there.
Is there a clear agenda and purpose? Meetings without a defined outcome are more likely to be avoided.

If key individuals are consistently absent, this may signal that the meeting itself is not seen as valuable. Gathering feedback on meeting structure and purpose can help improve participation.

HOW TO FIX IT: STRATEGIES FOR BETTER ENGAGEMENT

If people are not attending or contributing, here are practical steps to address the issue:

1. Clarify Expectations and Accountability
Make it clear why someone is needed and what their role is in the meeting.
If accountability is an issue, escalate the importance of participation to leadership.
Follow up individually with key stakeholders who miss meetings, reinforcing the importance of their input.

2. Improve Meeting Quality
Set a clear agenda – Circulate a concise agenda beforehand to ensure attendees understand the purpose.
Timebox discussions – Keep meetings short and focused to respect attendees’ time.
Use facilitation techniques – Encourage participation through structured discussion formats like round-robin input, breakout discussions, or decision matrices.
Summarize and assign action points – Ensure meetings lead to tangible next steps.

3. Consider Alternative Formats
Asynchronous updates – If information-sharing is the primary purpose, consider shared documents or video briefings instead of live meetings.
One-on-one check-ins – If specific stakeholders are disengaged, a direct conversation may be more effective.
Smaller, focused working groups – Large meetings often lead to passive participation; breaking discussions into smaller, action-oriented teams can increase engagement.

4. Address Underlying Resistance
If disengagement stems from a lack of buy-in, take time to understand concerns.
Identify whether non-attendance is a sign of opposition to a proposed change.
Use change management techniques such as stakeholder mapping and targeted communication to address resistance proactively.

TOP TIPS & BEST PRACTICES

1. Use the RACI model – Ensure people are in meetings only if they have a defined role.
2. Respect time – Keep meetings short, structured, and purposeful.
3. Consider alternative communication – Not all discussions need to happen in a meeting.
4. Follow up with missing stakeholders – Understand why they are not attending and address concerns.
5. Use facilitation techniques – Actively engage participants rather than relying on passive attendance.
6. Test different formats – Sometimes, shifting from large group meetings to smaller working sessions increases participation.
7. Make attendance matter – Connect participation to accountability and decision-making outcomes.
8. Address underlying resistance – Non-attendance can signal deeper concerns about the project or decision.

By implementing these strategies, organizations can create meetings that are more engaging, productive, and valuable—ensuring that key stakeholders are present and contributing meaningfully.