Search

ITIL Let's start with ITIL as its so popular and is really the accepted DNA of service management environments. ITIL & The Help Desk in ITIL Version 4 ITIL (Information Technology Infrastructure Library) remains the most widely used framework for defining best practices in IT service management, even under the ITIL version 4 framework. It continues to establish a common language and processes that nearly all organizations use when discussing IT support and services. While ITIL isn't the sole framework available, it remains the common language spoken by virtually every Help Desk, IT manager, and vendor, whether they are consciously aware of it or not. While much of the terminology and process structure aligns with ITIL, organizations often customize it to suit their specific needs, ensuring it's a practical fit for their operations. Introducing ITIL ITIL, in its version 4, still stands as a globally recognized framework of best practices for managing and delivering IT services. It emphasizes aligning IT services with the needs of businesses and organizations. Originally developed by the UK government's Central Computer and Telecommunications Agency (CCTA), ITIL has evolved into comprehensive guidelines that organizations use to optimize their IT service management (ITSM) practices. The Advantages: ITIL version 4 continues to provide a standard language and approaches for IT service management. It has evolved over the years with extensive thought and review. It remains scalable and adaptable, catering to the needs of both small businesses and large enterprises. Training accreditations, especially in the UK, retain their value. The Challenges: ITIL version 4 can still appear overwhelming when first introduced. Explaining the workings and benefits of ITIL to staff can sometimes lead to disinterest. The reference materials can be extensive, taking up significant shelf space. Higher-level training qualifications can require considerable effort to attain. The Structure of ITIL Version 4 In ITIL version 4, the framework retains its structure around a service lifecycle, consisting of five core stages, each with specific aspects of IT service management (ITSM): Service Strategy Service Portfolio Management: Defines and maintains the organization's service portfolio in alignment with business objectives. Financial Management: Manages budgeting, accounting, and charging for IT services to ensure cost-effectiveness. Demand Management: Balances the demand for IT services with available resources and capacity. Business Relationship Management: Builds relationships with business stakeholders to better understand and meet their needs. Service Design Service Catalog Management: Develops and maintains a comprehensive service catalog. Service Level Management: Establishes and maintains service level agreements (SLAs) to ensure services meet performance standards. Capacity Management: Ensures IT resources are sufficient to meet current and future service demands. Availability Management: Optimizes IT service availability to meet business requirements. Continuity Management: Develops and maintains plans for restoring IT services quickly following disruptions or disasters. Security Management: Protects IT services and supporting infrastructure from security threats. Service Transition Change Management: Manages and controls IT service and infrastructure changes to minimize risk and ensure stability. Configuration Management: Maintains accurate information about IT assets and their relationships. Release and Deployment Management: Plans, tests, and deploys new or updated IT services into the production environment. Service Operation Incident Management: Manages and resolves incidents to minimize disruptions and maintain service quality. Problem Management: Identifies and resolves the root causes of recurring incidents to prevent future occurrences. Event Management: Monitors and responds to events affecting IT services, ensuring timely resolution or escalation. Request Fulfillment: Processes and fulfills user service requests, such as access to resources or information. Continual Service Improvement (CSI) CSI in ITIL version 4 continues to focus on the ongoing measurement, analysis, and improvement of IT service quality and performance. It involves identifying areas for improvement, implementing changes, and monitoring their impact to ensure the continuous enhancement of IT services. ITIL & The Help Desk While ITIL version 4 maintains a broad spectrum of practices across the IT service lifecycle, certain aspects are of particular interest to the Help Desk. These aspects align with ITIL's core processes: Incident Management: ITIL version 4's incident management process directly aligns with the primary function of a Help Desk, which is to manage and resolve incidents and user issues. This process streamlines incident handling for faster and more consistent resolution. Request Fulfillment: ITIL version 4's request fulfillment process supports the Help Desk's role in processing and fulfilling user service requests, ensuring a timely and efficient response to user needs. Event Management: ITIL version 4's event management process enables a Help Desk to proactively monitor and respond to events that may impact IT services, allowing them to address potential issues before they escalate into incidents. Problem Management: ITIL version 4's problem management process aids the Help Desk in identifying and addressing the root causes of recurring incidents, reducing the overall workload and preventing future occurrences. Service Catalog: Ownership of a service catalog, especially its customer-facing view, often falls within the purview of the Help Desk. When it's not assigned to someone else, it's suggested that the Help Desk takes on this responsibility because of their keen interest in clarifying the services offered to both themselves and customers. Service Level Management: Service Level Agreements (SLAs) are often defined, monitored, and reported on by the Help Desk, both internally to senior leadership and externally to customers. While other teams or individuals may own this, it is commonly assumed to be a responsibility of the Help Desk. In ITIL version 4, these elements remain crucial to the primary activities of a Help Desk, and their alignment with the framework is officially recognized. The processes within Service Operation often overlap with those in Service Design, emphasizing the integration of ITIL principles throughout the service lifecycle. Other IT Best Practice Frameworks There are numerous other approaches. Here are a couple of the more well-known ones so that you can nod sagely if they are ever mentioned; COBIT Control Objectives for Information & Related Technologies (COBIT) is a framework for IT governance and management that aims to align IT processes with business objectives. It provides a comprehensive set of guidelines and best practices for organisations to improve their overall performance and control of their IT functions. ISO 20000 This international standard for IT service management, ISO 20000, specifies the requirements for an organisation to deliver managed IT services effectively. It aligns closely with ITIL principles and provides a formalised and measurable approach to IT service management. The following is a high-level summary of the similarities and differences between them. I recommend learning more about these if you feel a more rigid framework is needed for guidance, assessment or auditing. Now I feel confused. Which one should I use? None, all, whatever you want. ITIL is a great framework that everyone attempts to copy and simplify. COBIT is much more a tick list of processes, roles & responsibilities and matrix management. It says much about the 'what' but not the 'how'. ISO 20000 is excellent if you want someone to certify your capabilities and undertake ongoing audits, which can help underpin maturity. However, it is more than just a help desk, it does stretch across functions and processes, so it is a commitment from the entire IT team. I believe in the value of understanding these things and having a 'reference book' of good practice, so if you are looking for advice here, I'd suggest ITIL and a blend of Service Operation & Service Design. It's always valid to rip up the book and toss it out the window, bend the rules, and apply things your way IF you have a frame of reference and understand what best practice looks like.

In today’s fast-paced and information-saturated world, critical thinking has become a vital skill for success in various aspects of life. It empowers individuals to make informed decisions, solve problems effectively, and navigate the complexities of everyday life. But how does one go about developing these essential critical thinking skills? This blog post aims to provide a comprehensive guide on how to develop critical thinking process skills in 2023, exploring the essence of critical thinking, mastering key skills, and overcoming common barriers. Let’s dive in and start thinking critically! Short Summary Critical thinking involves analyzing and evaluating information to make informed decisions, questioning assumptions, considering different perspectives and being aware of personal biases. Mastering analytical thinking, open-mindedness and effective communication is essential for successful critical thinking. Practical strategies such as reflective practice, seeking feedback & constructive criticism can help improve critical thinking skills in real life situations. The Essence of Critical Thinking Critical thinking is a valuable skill that involves rational analysis, understanding logical connections between ideas, and effective problem-solving and decision-making. It is highly valued by employers and is a necessary tool for discerning truth in the current climate of misinformation and conflicting evidence. Developing critical thinking ability, including the critical thinking skill of effective problem solving, is essential for success in various aspects of life, from personal decisions to professional challenges. To become a good critical thinker, one must not accept information at face value, but rather analyze and evaluate it before making a decision. This involves questioning assumptions, considering different perspectives, and being aware of personal biases. By honing critical thinking skills, individuals can make better decisions, solve problems more effectively, and navigate the complexities of everyday life with confidence. The Core Components of Critical Thinking The core components of critical thinking include observation, analysis, problem-solving, decision-making, and the capacity to think objectively and assess perspectives. These essential elements enable individuals to break down complex problems into smaller, manageable parts and examine them systematically to find solutions. For example, when faced with a spreadsheet formula malfunction, a critical thinker would identify the problem and the factors contributing to it. To develop these core components, individuals should practice identifying problems, gathering relevant information, and analyzing the data objectively. This process requires self-regulation, the ability to control one’s thoughts and put aside personal inclinations to reach the most advantageous decision. By mastering these critical thinking skills, individuals can make more informed decisions and effectively solve problems in various aspects of life. The Role of Critical Thinking in Decision-Making Critical thinking plays a crucial role in decision-making by helping individuals gather and evaluate information, assess personal strengths and weaknesses, and consider possible outcomes and ways to avoid negative impacts. In the workplace, for instance, critical thinking enables individuals to uncover novel and improved solutions, even in circumstances where something appears to be functioning adequately. A good critical thinker can analyze a situation, evaluate the available information, and make informed decisions to achieve the desired outcome. To become an effective decision-maker, one must be able to: Examine a single element from more than one point of view Uncover any possible risks associated with the chosen course of action Acknowledge personal characteristics, preferences, and biases Make allowances for them when considering potential next steps Develop critical thinking abilities and apply them in decision-making By doing so, individuals can ensure better outcomes and more successful results in various aspects of life, taking into account their personal preferences. Mastering Key Critical Thinking Skills To become a proficient critical thinker, one must master key critical thinking skills such as analytical thinking, open-mindedness, and effective communication. These skills are essential for success in various aspects of life and work, as they enable individuals to analyze complex problems, consider different perspectives, and convey their thoughts, ideas, and solutions clearly and persuasively. Developing these important critical thinking skills requires practice, self-awareness, and a willingness to challenge one’s own beliefs and assumptions. By constantly refining these skills, individuals can improve their critical thinking abilities and become more adept at making informed decisions, solving problems effectively, and navigating the complexities of everyday life. Analytical Thinking Analytical thinking involves: Decomposing complex issues into smaller, manageable components Assessing them methodically to discover solutions Examining data and accumulating facts Logically evaluating causes and effects Analytical thinking assists in problem-solving, decision-making, and critical analysis. By practicing analytical thinking, individuals can: Break down complex problems or situations into their individual components to comprehend and assess them Identify underlying issues Determine the most effective course of action Make better decisions and solve problems more efficiently This skill is crucial for problem-solving and decision-making. Open-mindedness Open-mindedness is the capacity to contemplate different points of view, concepts, and opinions without prejudice, which is indispensable for effective critical thinking. Being open-minded allows individuals to evaluate various perspectives, concepts, and opinions, which is fundamental for successful critical thinking. Developing open-mindedness involves questioning one’s own beliefs and assumptions, seeking out alternative viewpoints, and being willing to change one’s mind in light of new information. This skill helps individuals to think more objectively, avoid cognitive biases, and ultimately make better decisions by considering their own opinions and solving problems more effectively. Effective Communication Effective communication is of paramount importance to critical thinking, as it assists individuals in: articulating their thoughts, notions, and solutions in an intelligible and convincing manner expressing information effectively and accurately comprehending and interpreting the emotions and intentions behind the message Examples of effective communication skills include: Speaking Active listening Providing feedback Delivering messages in a concise manner By honing these communication skills, individuals can better convey their ideas, arguments, and solutions to others, ultimately enhancing their critical thinking abilities and ensuring more successful outcomes in various aspects of life and work. A Step-by-Step Guide to the Critical Thinking Process To apply critical thinking effectively, it’s essential to follow a step-by-step process. This process includes identifying the problem or question, gathering relevant information, and thinking critically by analyzing and evaluating evidence. By following this structured approach, individuals can ensure a more systematic and thorough analysis of the issue at hand, ultimately leading to better decision-making and problem-solving outcomes. Identifying the Problem or Question Recognizing the problem or query is the initial step in the critical thinking process, as it assists individuals to concentrate on the issue at hand and establish concrete objectives. Identifying the problem or question is of great importance as it establishes the basis for problem-solving and critical thinking. It assists in elucidating the objective, concentrating the research or analysis, and directing the decision-making process. To effectively identify the problem or question, individuals should practice recognizing problems, gathering pertinent information, and analyzing the data objectively. This process requires self-regulation, the capacity to control one’s thoughts, and put aside personal inclinations to reach the most advantageous decision. Gathering Relevant Information Once the problem or question is identified, the next step in the critical thinking process is gathering relevant information. This involves researching and collecting data, opinions, and arguments from various sources to make informed decisions. During the research process, pertinent information pertaining to the issue at hand, such as data, statistics, historical project information, team input, and so forth, should be gathered from the appropriate sources. Gathering varied information is of paramount importance for the application of the critical thinking process, as a lack of sufficient information may lead to a decision being biased by its source. By collecting a diverse range of data and perspectives, individuals can ensure a more comprehensive and unbiased analysis of the issue at hand, ultimately leading to better decision-making outcomes. Analyzing and Evaluating Evidence After gathering relevant information, the next step in the critical thinking process is to analyze and evaluate the evidence. This involves: Assessing the reliability, significance, and relevance of the information gathered Critically examining evidence to identify any flaws or inconsistencies Forming well-supported arguments Preventing making erroneous claims By following these steps, individuals can effectively analyze and evaluate evidence, leading to more informed and logical decision-making. To effectively analyze and evaluate evidence, individuals should consider the credibility of the source of the evidence, contemplate the context in which the evidence was obtained, and evaluate the pertinence of the evidence to the matter in question. By doing so, they can ensure that their opinions are based on concrete facts rather than assumptions or biases, ultimately leading to more informed decisions and successful outcomes in various aspects of life and work. Practical Strategies to Improve Critical Thinking Skills Improving critical thinking skills requires practice and dedication. Some practical strategies to enhance critical thinking abilities include engaging in reflective practice, seeking feedback and constructive criticism, and embracing a growth mindset. To improve your critical thinking, it’s essential to commit to these strategies and consistently apply them in your daily life. By implementing these strategies and conducting their own research, individuals can foster a lifelong quest for knowledge and personal growth, ultimately leading to more successful outcomes in various aspects of life and work. Engaging in Reflective Practice Reflective practice involves systematically analyzing one’s thoughts, beliefs, and actions in order to gain insights and refine critical thinking skills. By engaging in reflective practice, individuals can recognize and question assumptions, cultivate self-awareness, and enhance decision-making abilities. Strategies that can facilitate reflective practice include journaling, inquiring, and soliciting feedback from others. By regularly engaging in reflective practice, individuals can identify areas for improvement, develop a deeper understanding of their own thought processes, and ultimately become better critical thinkers. Seeking Feedback and Constructive Criticism Soliciting feedback and constructive criticism is of great importance as it: Furnishes us with alternative perspectives Facilitates the refinement of our work Assists us in recognizing our strengths and weaknesses Furnishes us with valuable guidance for growth and development. By seeking feedback from others, individuals can gain insights into their own thought processes and decision-making abilities, ultimately enhancing their critical thinking skills and ensuring more successful outcomes in various aspects of life and work. Furthermore, feedback and constructive criticism aid us in refining our concepts, developing our abilities, and formulating more informed decisions. Embracing a Growth Mindset Adopting a growth mindset is of great significance as it enables individuals to: Trust in their capacity to learn and progress Overcome obstacles and construct resilience Accomplish their objectives Embrace novel opportunities Solicit feedback Continuously improve themselves A growth mindset engenders a positive outlook towards learning and promotes a lifelong quest for knowledge and personal growth. Examples of how to embrace a growth mindset include: Being open to feedback Taking calculated risks Learning from errors Being inquisitive and posing questions Seeking out novel challenges Engaging in self-reflection By adopting a growth mindset, individuals can acquire the competencies needed to think critically and make judicious decisions. Real-Life Examples of Critical Thinking in Action In real-life scenarios, critical thinking can be applied to solve problems and make informed decisions in various contexts. For instance, in the workplace, a team implementing a corporation’s pricing procedure might use critical thinking to analyze the situation, evaluate available information, and make informed decisions to achieve the desired outcome. In another example, a store manager might carefully examine cash flow data and create graphical representations to illustrate that concentrating on more popular products could result in a 40% growth in store revenue. These examples demonstrate how individuals can apply critical thinking skills to address issues and make informed decisions in various situations. By developing and honing these skills, individuals can ensure better outcomes and more successful results in various aspects of life and work. Overcoming Common Barriers to Critical Thinking Common impediments to critical thinking include cognitive biases, information overload, and resistance to change. To overcome these barriers, individuals must be aware of their own biases and make a conscious effort to think more objectively. By recognizing and acknowledging personal biases, individuals can avoid making irrational judgments or decisions based on personal inclinations or convictions. Another strategy to overcome barriers to critical thinking is to manage information overload by prioritizing and focusing on the most relevant and reliable sources of information. By adopting a systematic and methodical approach to gathering and analyzing data, individuals can effectively overcome common barriers to critical thinking and ensure more successful outcomes in various aspects of life and work. Summary In conclusion, developing critical thinking process skills is essential for success in various aspects of life and work. By understanding the essence of critical thinking, mastering key skills, and following a step-by-step process, individuals can make informed decisions, solve problems effectively, and navigate the complexities of everyday life. By embracing practical strategies such as reflective practice, seeking feedback and constructive criticism, and adopting a growth mindset, individuals can continue to enhance their critical thinking abilities and achieve greater success in both personal and professional endeavors. It’s time to cultivate a critical thinking mindset and embrace the opportunities that await! Frequently Asked Questions What are the 5 stages of critical thinking? Critical thinking consists of five distinct steps: identification of assumptions, evaluation of arguments, analysis of implications and consequences, generation of alternative perspectives and interpretations, and reflective conclusion. What are the 7 processes involved in critical thinking? Critical thinking involves actively and skillfully conceptualizing, applying, analysing, synthesizing and evaluating information gathered through observation, experience, reasoning and communication. This is done by following seven steps: identifying the problem, gathering data, analysing and evaluating, recognizing assumptions, establishing significance, making a decision, and communicating. What are the 5 core skills needed for critical thinking? The 5 core skills needed for critical thinking are analysis, interpretation, inference, explanation, and self-regulation. Additionally, open-mindedness, problem-solving, identifying biases, curiosity, and judging relevance are important elements to hone when honing one’s critical thinking skills. These skills can be developed through practice and experience. It is important to be able to recognize when one is being biased or when one is not considering all the facts. Additionally, it is important to learn about the importance of education. How can a growth mindset help improve critical thinking skills? A growth mindset encourages receptivity to new ideas, questioning of assumptions, and consideration of alternative perspectives, all of which can improve critical thinking skills. These skills are essential for success in the modern world, as they allow us to think more deeply and creatively about the problems we face. They also help us to better understand the perspectives of others, which can lead to more effective communication. What are some practical strategies to improve critical thinking skills? Practicing reflective thought, accepting feedback, and cultivating a willingness to learn are practical strategies to foster critical thinking skills.

In the fast-paced world of project management, understanding the differences and similarities between popular agile methodologies can be invaluable. Scrumban and Kanban are two such methodologies that offer unique benefits and challenges. In this blog post, we will explore the key aspects, advantages, and limitations of “Scrumban vs Kanban”, providing you as project managers with the knowledge you need to make informed decisions about which methodology best suits your team and project needs. Scrumban vs Kanban Key Takeaways Scrumban and Kanban share similarities such as focus on continuous improvement, visualization, and pull systems. Key differences include planning approach, team roles/structure, iterations/workflow & board management. Understanding Scrumban and Kanban Scrumban and Kanban are both examples of agile methodology that have gained popularity in recent years due to their adaptability and focus on continuous improvement. While they share some similarities, there are also several key differences that set them apart. Teams seeking to enhance their project management processes and optimize workflow will benefit from a thorough comprehension of these methodologies. Scrumban is a hybrid approach that combines the structure of Scrum with the flexibility and visualization of Kanban. This unique combination allows teams to reap the benefits of both methodologies, leading to increased adaptability and more efficient processes. On the other hand, Kanban is a visual workflow management method that emphasizes continuous improvement and minimizing work in progress. The core principles of Kanban focus on visualization, limiting work in progress, and managing the flow of tasks, making it a popular choice for project management in various industries. Scrumban Explained Scrumban combines the agility of Scrum with the simplicity of Kanban, allowing teams to maintain a balance between structure and flexibility. Like Scrum, Scrumban employs specific roles for team members, such as the Product Owner and Scrum Master, and follows a similar sprint planning process. However, it also incorporates elements of Kanban, such as the use of Kanban boards for visualization and adaptability. The benefits of Scrumban are numerous, including: Facilitating the transition of existing Scrum teams to Kanban and explore lean methodologies Employing a pull principle, which means that tasks are not assigned by a project manager. Instead, each team member selects which task to complete next from the “To Do” column, based on priorities and capacity Encouraging team members to take ownership of their work and fosters a culture of continuous improvement Kanban Board Explained The Kanban method, on the other hand, is a methodology that focuses on visualizing workflows and limiting work in progress to help teams become more agile and efficient. By breaking down complex problems with intertwined workflows into smaller components and visualizing these components on a shared board in real-time, Kanban allows teams to stay aligned on objectives while maintaining focus. Kanban’s core practices revolve around continuous improvement, making it an ideal choice for support and maintenance teams looking to monitor their progress and efficiency. Performance metrics like the Cumulative Flow Diagram (CFD) and Lead Cycle time are often employed in Kanban to help teams identify areas for improvement and ensure that they are delivering value to their customers in the most efficient way possible. Key Differences Between Scrumban and Kanban Discerning the key variations between Scrumban and Kanban is vital for teams to make knowledgeable decisions about the most suitable methodology for their needs. These differences include: Planning approach Team roles and structure Iterations and workflow Board management The subsequent sections will provide an in-depth comparison of Scrumban and Kanban, further exploring their differences. Planning Approach One of the primary differences between Scrumban and Kanban lies in their approach to planning. Scrumban organizes tasks into one to four-week sprints, with planning initiated when the planning trigger is activated, which is associated with the number of tasks remaining in the “To Do” section of the board. This allows team members to choose tasks based on priorities and capacity. During the planning event, it is recommended to prioritize tasks by assigning numbers to the tasks or ordering them by priority in the column. When comparing different project management methodologies, the debate of “kanban vs” other approaches often arises. Kanban, in contrast, emphasizes continuous flow and provides the option to prioritize tasks. With no predefined iterations, Kanban teams operate continuously while setting either short or longer-term goals, with only a few constraints on their workflow. This approach allows for greater flexibility in responding to changes in priorities or customer needs, making it an attractive option for teams that need to adapt quickly to evolving requirements. Team Roles and Structure - Scrum Team & Scrum Master? Another key difference between Scrumban and Kanban is the way they handle team roles and structure. Scrumban, like Scrum, has more clearly defined roles, such as the Product Owner, Scrum Master, and Team Members, allowing for a structured approach to project management. In contrast, Kanban has fewer prescribed roles and encourages collaboration among team members, focusing on the shared responsibility of managing the workflow and completing tasks. This distinction in team roles and structure is a crucial aspect to consider when evaluating scrum vs other project management methodologies. This distinction in team roles and structure can have a significant impact on how teams operate and collaborate. For example, in Scrumban, the Scrum Master is responsible for ensuring that the team follows the Scrum framework and resolves any obstacles that may arise during the project. In Kanban, however, no specific role is responsible for the overall workflow, and each team member is responsible for their own steps in the process. This difference allows Kanban teams to foster a more collaborative environment and a greater sense of ownership over their work. Iterations and Workflow - Sprint Planning? The approach to iterations and workflow is another area where Scrumban and Kanban differ. In Scrum, the estimated hours of planned work items must not exceed the duration of the sprint, while Kanban and Scrumban employ Work-In-Progress (WIP) limits to regulate the amount of tasks that can be handled concurrently. This makes Scrumban and Kanban suitable for cross-functional teams, as they can better manage their workloads and adjust to changes in priorities or customer needs. Scrumban incorporates defined iterations with a board structure similar to that of Kanban, allowing teams to benefit from the flexibility and visualization that Kanban offers while still adhering to the time-boxed structure of Scrum. On the other hand, Kanban does not have any predefined iterations and instead employs a continuous board, providing teams with greater flexibility in managing their workflow and responding to changes in priorities or customer needs. Board Management Board management is another area where Scrumban and Kanban diverge. Scrumban boards combine elements of Scrum and Kanban boards, allowing teams to visualize their workflow in a way that is both structured and adaptable. Tasks are organized into backlogs and workflow stages, with work-in-progress limits set to ensure that tasks are completed in a timely manner. Kanban boards, on the other hand, focus on visualizing the workflow and limiting work in progress to help teams become more agile and efficient. By breaking down complex problems with intertwined workflows into smaller components and visualizing these components on a shared kanban board in real-time, Kanban allows teams to stay aligned on objectives while maintaining focus. The simplicity and adaptability of Kanban boards make them an attractive option for teams that need to respond quickly to changing priorities or customer needs. Key Similarities Between Scrumban and Kanban Despite their differences, Scrumban and Kanban also share several key similarities that make them both effective methodologies for project management. Both methodologies emphasize continuous improvement, visualization, and pull systems, allowing teams to optimize their workflow and adapt to changing priorities or customer needs. The next sections will delve into these similarities more thoroughly, shedding light on the shared principles of Scrumban and Kanban. Continuous Improvement Continuous improvement is a cornerstone of both Scrumban and Kanban methodologies, enabling collaborative transformation based on factual data, metrics, and feedback. By regularly reviewing and refining the process and workflow of a team, continuous improvement promotes a culture of ongoing learning and adaptation, enabling teams to make incremental improvements to their work practices and ultimately produce better results. Testing hypotheses is integral in achieving continuous improvement, as it facilitates ongoing improvement by validating or disproving assumptions about the effectiveness of the team’s workflow and processes. By continually analyzing data and metrics, teams can identify areas for improvement and make data-driven adjustments to their workflow, ultimately enhancing their efficiency and productivity. Visualization Visualization is another key aspect of both Scrumban and Kanban, using boards to display tasks and progress in a clear and easily understandable way. This visualization helps teams stay organized and focused on their goals while providing a real-time overview of the project’s progress. By making the workflow visible, teams can better identify bottlenecks, allocate resources more effectively, and ensure that tasks are completed in a timely manner. In both methodologies, boards are organized into columns that represent different stages of the workflow, with tasks represented as cards that move from one column to another as they progress through the process. This visual representation of the workflow enables teams to quickly identify the status of tasks and make informed decisions about prioritization and resource allocation. Pull Systems Pull systems are another common feature of both Scrumban and Kanban methodologies, allowing team members to choose tasks based on priorities and capacity. This contrasts with a push system, which involves pushing work onto teams regardless of their capacity. Pull systems help prevent team overburden and increase workflow efficiency, ensuring that tasks are completed in a timely manner and resources are allocated effectively. By allowing team members to select tasks according to their priorities and capacity, pull systems and experienced teams foster a sense of ownership and responsibility for the work. This encourages team members to: Take the initiative in choosing and completing tasks Improve their time management skills Increase their productivity Collaborate more effectively with their teammates Feel more engaged and motivated in their work Ultimately, pull systems lead to more efficient workflows and better project outcomes. When to Choose Scrumban or Kanban Choosing between Scrumban and Kanban ultimately depends on the unique requirements of your development team and the factors that team members choose to consider. These factors may include the project’s scope, the team’s structure, and the desired level of flexibility in the development process. The upcoming sections will tackle the particular factors that might affect your choice of Scrumban or Kanban, supplemented with instances where each methodology could be most fitting. Factors to Consider Scrumban is well-suited for teams that need to maintain a balance between structure and flexibility, as well as for large projects that involve collaboration across teams. By combining the structured approach of Scrum with the adaptability of Kanban, Scrumban allows teams to manage their workloads effectively while remaining agile and responsive to changing priorities or customer needs. On the other hand, Kanban is an ideal choice for teams with consistent processes and a preference for flexibility and experimentation. Kanban’s focus on visualizing workflows and limiting work in progress makes it particularly suitable for teams that need to respond quickly to changes in priorities or customer needs, such as support and maintenance teams, or teams working on projects with a high volume of requests of varying priority and size. Choosing Scrumban Scrumban may be the ideal choice for software development teams that require a balance between structure and flexibility, as well as for large projects that involve cross-team collaboration. Examples of situations where Scrumban is particularly beneficial include software development, marketing, and customer service teams. By combining the structure of Scrum with the adaptability and visualization of Kanban, Scrumban allows teams to manage their workloads effectively while remaining agile and responsive to changing priorities or customer needs. Before implementing Scrumban, it is important to ensure that your team is properly trained in the methodology and understands the benefits of combining Scrum and Kanban elements. Providing guidance on how to prioritize tasks, set work-in-progress limits, and hold daily stand-up meetings will enable your less experienced team members to effectively adopt Scrumban and reap the benefits of this hybrid approach. Choosing Kanban Kanban is an attractive option for teams that prefer greater flexibility in their workflow and wish to focus on continuous improvement and experimentation. Some examples of situations where Kanban is particularly beneficial include projects with a high volume of requests of varying priority and size, customer-driven development, and shorter project timelines. Implementing Kanban requires a commitment to continuous improvement, experimentation, and analytics. To begin, follow these steps: Assess the project requirements and gain an understanding of the Kanban methodology. Decide the most suitable approach to implement Kanban in your organization. Visualize workflows to make them more transparent and manageable. Set work-in-progress limits to prevent bottlenecks and improve efficiency. Manage the flow of tasks to ensure smooth progress and timely completion. By following these steps, your team can effectively adopt Kanban and benefit from its focus on efficiency and adaptability. Implementing Scrumban or Kanban in Your Organization Successfully implementing Scrumban or Kanban in your organization involves understanding the selected methodology, setting up the appropriate boards, and training your team members in the new approach. Adhering to the guidance in this blog post and customizing the methodologies to your team’s distinct requirements can aid in the successful integration of either Scrumban or Kanban into your organization, thereby enhancing your project management processes. Getting Started with Scrumban To get started with Scrumban, create a scrum board, with backlogs and workflow stages, set work-in-progress limits, and hold daily stand-up meetings. By clearly defining the columns, tasks, and workflow on your scrum boards, your team can visualize their progress and better understand the complexities of their projects, such as processes and risks. Training your team on Scrumban involves explaining the methodology, demonstrating how to use the board, and providing guidance on how to prioritize tasks. By ensuring your team is properly trained and understands the benefits of combining Scrum and Kanban elements, they can effectively adopt Scrumban and reap the benefits of this hybrid approach. Getting Started with Kanban To implement Kanban in your organization, start by visualizing the workflow on a board, setting work-in-progress limits, and managing the flow of tasks. This visualization allows your team to stay aligned on objectives while maintaining focus on their goals, and enables them to quickly identify bottlenecks and allocate resources more effectively. Training your team on Kanban involves explaining the methodology, demonstrating how to use the board, and providing guidance on how to prioritize tasks and manage the flow of work. By ensuring your team is properly trained and understands the benefits of Kanban, they can effectively adopt this methodology and benefit from its focus on efficiency and adaptability. Real-World Examples of Scrumban and Kanban Real-world examples of Scrumban and Kanban can provide valuable insights into the benefits and challenges of each methodology in different industries. For instance, ClickUp and Asana are examples of project management tools that utilize the Scrumban approach, allowing teams to balance structure and flexibility in their workflow. Trello and Jira, on the other hand, are popular examples of Kanban in use, helping teams visualize their work and manage their workflows more efficiently. By examining these real-world applications, you can gain a better understanding of how Scrumban and Kanban can be implemented in your own organization. Summary In conclusion, Scrumban and Kanban are both effective agile methodologies that offer unique benefits and challenges to teams and organizations. By understanding the key differences and similarities between these methodologies, you can make informed decisions about which approach best suits your team’s needs and project requirements. Whether you choose to implement Scrumban for its balance of structure and flexibility or Kanban for its focus on continuous improvement and adaptability, both methodologies can help your team optimize their workflow and achieve better project outcomes. Frequently Asked Questions What is Scrum Kanban and Scrumban? Scrum, Kanban and Scrumban are popular Agile project methodologies used globally to facilitate product/service delivery. Scrum was created by Ken Schwaber and Jeff Sutherland, while Kanban has its roots in Lean project management. Scrumban is the hybrid of the two frameworks, which started as a way to switch between them but has become its own standalone methodology. What is the difference between Scrum and Kanban flow? Kanban focuses on reducing the time a project takes from start to finish by using a kanban board, while Scrum organizes work around sprints and commits to completing increments of potentially shippable work. Additionally, Kanban is a visual methodology, whereas Scrum structures workflow and team culture. What is the difference between Scrumban and Kanplan? Kanplan allows teams to prioritize tasks without sprints, whereas Scrumban uses sprints as the primary method of task organization. Therefore, teams that prioritize agility and flexibility often move away from Scrum towards Kanplan. How do team roles differ between Scrumban and Kanban? In Scrumban, team roles are more flexible while Kanban encourages collaboration with fewer pre-defined roles. When should I choose Scrumban over Kanban? If your team needs a balance between structure and flexibility or if you're dealing with a large project that requires cross-team collaboration, then Scrumban is the way to go.

The following article includes a downloadable OKR template and guidance on completing Objective and Key Results (OKRs) of your own. Creating Objectives and Key Results (OKRs) is an essential practice for organisations and individuals who aim to achieve ambitious goals. This management strategy is popular among tech giants and startups alike for its focus on setting measurable, outcome-oriented objectives. Here, we will walk you through the process of creating and tracking OKRs effectively. Plus, don’t miss out on our downloadable Word template that lets you input your own OKRs with ease! What Are OKRs? OKRs stand for Objectives and Key Results. The "Objective" is the overarching goal you aim to achieve, while "Key Results" are specific, measurable indicators that show you’re progressing toward that objective. Why Use OKRs? Alignment: OKRs help align your personal or organisational goals with overarching strategies. Focus: By setting specific metrics, OKRs force you to concentrate on what truly matters. Accountability: Assigning OKRs ensures that everyone knows their role in achieving objectives. How to Create OKRs Step 1: Define Your Objectives Start by setting 1-3 objectives for the quarter or year. Objectives should be: Specific Inspiring Aligned with your overall strategy Step 2: Establish Key Results For each objective, create 3-5 key results that are: Measurable Outcome-oriented Realistic yet challenging Step 3: Assign Ownership Designate an owner for each key result. The owner is responsible for monitoring and updating the status of the key result. Step 4: Track and Update Keep tabs on your key results. Regularly update their status to one of the following: Not Started In Progress Completed Issue Summarise the progress briefly for better understanding and future planning. Step 5: Review and Adjust Conduct regular reviews, typically on a quarterly basis, to evaluate performance and adjust your OKRs as necessary. Using Our OKR Template We’ve created a handy Word template to help you effortlessly keep track of your OKRs. The template allows you to input: Objective Description: A detailed narrative of what you aim to achieve. For each Key Result: Summary: A brief outline of the key result. Owner: The person responsible for the key result. Status: Indicates whether the key result is "Not Started," "In Progress," "Completed," or has an "Issue." Summary of Progress: A concise update on how things are progressing. OKR Template & Guidance Conclusion OKRs offer a robust framework for setting and achieving goals, whether you're an individual or part of a larger organisation. By implementing OKRs into your workflow, you set the stage for clearer communication, higher levels of productivity, and more effective achievement of your most important objectives. Don’t forget to download our OKR template to help streamline this beneficial practice! Article : Overcoming the issues of implementing OKRs Article : How to use OKRs in projects Article : Overview of OKRs

In today’s fast-paced business landscape, research and development (R&D) projects hold the key to unlocking innovative breakthroughs and maintaining a competitive edge. However, managing such projects can be a daunting task, riddled with complexities and uncertainties. In this post, we’ll explore the essential strategies and best practices for successful project management for R&D, guiding you through the unique challenges and helping you unlock the full potential of your R&D endeavors. Key Takeaways Skilled project management is essential for navigating the complexities of R&D projects. Leveraging modern technology and tools, such as Project Portfolio Management software and Knowledge Management systems, can lead to more efficient and successful R&D project management processes. Regular communication of progress to stakeholders ensures transparency while optimizing resource management leads to improved outcomes in reduced time with increased profitability. Navigating the Complexities of R&D Project Management R&D project management is intrinsically complex, characterized by uncertainty and change that demand a skilled project manager to navigate. Traditional project management approaches often fall short when applied to the unique project environment of R&D projects. Managing collaborative R&D projects can be particularly challenging due to unpredictable outcomes, conflicting priorities, and the potential for major project updates or cancellations at any phase. Flexibility and a keen focus on strategic objectives are vital for effective management of R&D projects. The utilization of modern technology and tools can significantly improve the planning, monitoring, and management of R&D projects. These tools provide convenient access to knowledge and experts without the need for extended searches for the appropriate information or personnel, allowing for more informed decision-making and efficient management. Moreover, they enable planning and what-if scenario simulations, assisting in the management of budgets, costs, and other elements in R&D project management, which is more complex than traditional projects. Embracing Uncertainty and Change Change is a constant in R&D project management. The requirements for R&D projects, especially product development projects, can often change over time, making it difficult to stay agile and flexible enough to accommodate those changes. Project managers and stakeholders must maintain focus on the strategic objectives and overall purpose of the R&D project, even amidst uncertainty and change. In this way, they can adapt to evolving circumstances and mitigate project-related risks. Modern knowledge management can play a significant role in enhancing R&D collaboration by facilitating efficient communication, providing access to existing knowledge, and enabling the documentation of insights. This contributes to successful project completion and allows the project team to leverage predictive capabilities to minimize uncertainty and associated risks in R&D project management. Focusing on Strategic Objectives Staying true to strategic objectives ensures alignment of R&D projects with overarching business goals. Development teams working on complex projects must keep project objectives in mind at every stage of the project to make informed decisions and ensure that the project progresses towards its intended goal. Customer involvement in R&D projects is paramount, facilitating the creation of user-friendly deliverables, ensuring customer satisfaction, and boosting a company’s profitability. By maintaining focus on strategic objectives and involving customers in the R&D process, project managers can better align their projects with market trends and competitive advantage, ultimately leading to a higher likelihood of success. This strategic alignment also helps in efficiently managing resources and keeping project stakeholders informed about the project’s progress. Key Components of Successful R&D Project Management Successful management of R&D projects hinges on the recognition and implementation of key components like the phase gate process, effective resource management, and customer participation. The phase gate process is crucial for R&D projects, as it helps maintain project progress and optimize resource utilization while minimizing the risk of failure by providing a well-defined project management approach. Resource management is also vital for the successful completion of R&D projects, given their complexity and large-scale nature. Customer involvement, on the other hand, can prove beneficial by providing valuable feedback on the project and ensuring that it meets customer needs, contributing to effective resource utilization and project progress. These key components, when applied effectively, can significantly improve the chances of a successful R&D project outcome. The key components are: Phase gate process: This process breaks down projects into manageable stages, allowing for a more structured and organized approach to project management. Efficient resource management: This involves anticipating the resources needed for a project and managing them effectively. Customer involvement: This ensures that the project is progressing as planned and meeting customer requirements. By implementing these key components, you can increase the likelihood of a successful R&D project outcome. Phase Gate Process Implementation The phase gate process is a valuable tool for managing R&D projects. It divides them into manageable stages, enabling planning work and resources phase-by-phase while taking into account risks and uncertainties. The process comprises the following phases: Ideation Scope Business Case Development Testing Launch This provides a clear roadmap for project completion. By assessing work done at the gates and allowing for experience to plan subsequent phases, the phase gate process helps in minimizing risks and ensuring a well-coordinated project team. Implementing the phase gate process in R&D project management offers several benefits: Breaking down complex projects into smaller, more manageable tasks Ensuring effective allocation of resources throughout the project Enabling development teams to stay focused on project goals Making data-driven decisions that lead to successful project outcomes This structured approach to project management can greatly improve the efficiency and effectiveness of R&D projects. Efficient Resource Management Managing resources efficiently is critical for the successful completion of R&D projects, as it helps in anticipating the exact resources needed for a project and adjusting resource allocation based on the unpredictable timeline for completion. Tools like Epicflow can be employed to optimize task priorities across all projects, increasing resource efficiency and ensuring timely completion of multiple projects running in a company. Epicflow’s Competence Management feature offers the following benefits: Insight into team members’ competences and available capacity Enables project managers to allocate resources more effectively Helps in efficiently managing resources and anticipating the resources required for the project Ensures that R&D projects progress smoothly and stay on track to meet their objectives. Customer Involvement and Feedback Involving customers in the R&D process is essential for obtaining valuable feedback and producing desirable, cost-effective results. By actively engaging customers in the research and development process, such as gathering customer feedback, conducting market research, and involving customers in product testing and validation, project managers can ensure that their projects are meeting customer needs and progressing as planned. The advantages of customer involvement in R&D project management include: Guaranteeing that the R&D project is in line with customer requirements and preferences, consequently leading to the creation of successful products or services. Facilitating customer satisfaction, loyalty, and profitability for the company. By involving customers in the R&D process, project managers can create a more user-friendly, profitable, and successful project outcome. Best Practices for Managing R&D Projects Effectively Adopting best practices that bolster project success is a key factor in effectively managing R&D projects. These best practices include prioritizing communication and collaboration, leveraging modern technology and tools, and continuous improvement and learning. Emphasizing communication and collaboration enables project managers to align stakeholders, hasten task completion, and address any potential project issues promptly. Utilizing modern technology and tools, such as project management software, cloud-based collaboration tools, and data analytics tools, can help streamline the R&D project management process and ensure a more efficient and successful outcome. Another essential best practice for effective R&D project management is embracing continuous improvement and learning. This approach involves systematically evaluating and refining processes, decisions, and outcomes to maximize efficiency and effectiveness. By documenting project processes, decisions, and outcomes, project managers can gain valuable insights that can help optimize future projects and improve overall project success. Prioritizing Communication and Collaboration Successful R&D project management hinges on effective communication and collaboration. By fostering open communication and collaboration among team members, project managers can ensure a smooth flow of information and ideas, enabling the team to work together more efficiently and effectively. To enhance communication, project managers should: Establish a communications plan that encompasses when and how meetings will be conducted Define preferred communication methods Utilize technologies such as project management or knowledge-sharing platforms By implementing these strategies, project managers can enhance communication and collaboration within their teams. Prioritizing communication and collaboration also helps in building trust and promoting innovation among team members. By creating an environment where team members feel comfortable sharing their ideas and expertise, project managers can encourage innovation and creativity, ultimately leading to a more successful project outcome. Leveraging Modern Technology and Tools Employing modern technology and tools is vital for making R&D project management more efficient. Project management software, cloud-based collaboration tools, and data analytics tools can greatly enhance the planning, monitoring, and management of R&D projects. For instance, a Software-as-a-Service Project Portfolio Management (SaaS PPM) solution can help project managers track project progress, allocate resources, and manage budgets more effectively. Knowledge management systems, such as those that enable anonymous questions, empower team members to seek assistance without worrying about being perceived as inadequate. By leveraging modern technology and tools, project managers can ensure a more efficient and successful R&D project management process, ultimately leading to better project outcomes and overall success. Continuous Improvement and Learning Promoting continuous improvement and learning is key to ensuring timely and budget-compliant project completion, process optimization, and prompt recognition and resolution of potential issues in R&D project management. This process involves systematically evaluating and refining processes, decisions, and outcomes in order to maximize efficiency and effectiveness. Documenting project processes, decisions, and outcomes is critical for facilitating continuous improvement and learning. By creating comprehensive reports, noting key points from meetings, and noting project milestones, project managers can gain valuable insights that can be leveraged to optimize future projects. Additionally, utilizing the documented information provides a benchmark for comparison between different projects, allowing project managers to identify patterns and trends that can contribute to the overall success of their R&D projects. Measuring R&D Project Outcomes and Progress Assessing R&D project outcomes and progress is pivotal in project management, aiding in keeping projects on course to meet their goals and furnishing useful insights for future projects. Identifying relevant metrics and communicating progress to stakeholders are essential methods for measuring project outcomes and progress. By determining the appropriate metrics for R&D projects and regularly communicating project progress to stakeholders, project managers can maintain transparency and ensure consistency with expectations, leading to greater project success. Regular and consistent communication with stakeholders is paramount in R&D project management, as these projects are crucial for organizations. Documenting all communications with stakeholders is necessary to ensure proper monitoring of the project’s progress and to acquire valuable insights for future projects. By measuring project outcomes and progress and communicating this information to stakeholders, project managers can effectively manage R&D projects and achieve successful project outcomes. Identifying Relevant Metrics Identifying suitable metrics to track R&D project progress and success is a key aspect of project management. Organizations should identify the metrics to monitor and the data sources to draw conclusions about current performance and future steps. Data analysis can be instrumental in achieving the desired outcome of the project, enabling project managers to make informed decisions based on the data collected. Upon reviewing key performance indicators and overall progress, it can be concluded if any changes needs to be made in budget or timelines. Such discussion might then follow. By identifying relevant metrics and utilizing data analysis, project managers can effectively measure project outcomes and progress, ensuring that R&D projects stay on track and achieve their intended goals. Communicating Progress to Stakeholders Regularly updating stakeholders about the project’s progress is vital for maintaining transparency and aligning with their expectations. A recommended approach to monitoring progress for R&D project management is to report progress on a regular basis and make it easily accessible to team members, for example via a dashboard. This ensures that stakeholders are kept apprised of project progress and that their expectations are satisfied. Transparency and adhering to expectations are essential when communicating progress to stakeholders, as it provides them with a clear understanding of the project’s progress and helps to build trust and confidence in the project team. By regularly communicating project progress to stakeholders, project managers can effectively manage R&D projects and ensure a successful outcome. Case Study: Successful R&D Project Management in Action PM Solutions, a leading provider of project management solutions across various industries, offers a real-world example of successful R&D project management. Through their case studies, PM Solutions demonstrates the successful management of research and development projects by implementing key components such as: The phase gate process Resource management Customer involvement Best practices like communication and collaboration Leveraging technology and tools Continuous improvement and learning In one case study, PM Solutions helped a global pharmaceutical company streamline its R&D project management process by implementing a phase gate process, optimizing resource management, and involving customers in the development process. As a result, the company achieved significant improvements in project outcomes, reduced time to market, and increased profitability. This case study highlights the importance of adopting the essential components and best practices discussed throughout this post in managing R&D projects effectively. By implementing these strategies and continuously refining their approach, organizations can unlock the full potential of their R&D endeavors and maintain a competitive edge in their respective industries. Summary In conclusion, effective R&D project management requires navigating the complexities of uncertainty and change, focusing on strategic objectives, implementing key components like the phase gate process and resource management, involving customers, and adopting best practices such as communication and collaboration, leveraging technology and tools, and continuous improvement and learning. By mastering these essential strategies and continuously refining their approach, project managers can ensure the successful completion of their R&D projects, ultimately driving innovation, growth, and profitability for their organizations. Embrace the challenge of R&D project management and unlock the potential of your projects to shape a brighter, more innovative future. Frequently Asked Questions What is the role of R&D in project management? R&D project management involves the process of discovering new ideas, technologies, and solutions to create or improve products and services. It requires the implementation of rigorous control processes to review progress and make adjustments accordingly. Research and development is often the first stage in product development, and R&D managers are responsible for researching, planning, and implementing new protocols and programs into their organization. Is project management part of R&D? Project management is an integral part of R&D, as R&D personnel must be trained in project management to facilitate continuous review and regular reporting to stakeholders. How do you manage a R&D department? Successfully managing a R&D department requires defining and maintaining clear objectives and metrics, providing room for experimentation, focusing on business awareness and problem solving, establishing communication mechanisms, and adhering to best practices such as working with business objectives in mind, wise resource management, phase gates process, documenting knowledge bases, keeping stakeholders informed, and using a SaaS PPM software. What are the three types of R&D projects? Research and development includes three distinct activities: basic research, applied research, and experimental development. What does an R&D project manager do? As an R&D Project Manager, you are responsible for planning, tracking and managing the research and development project, including evaluating scopes, performing risk assessments, identifying and mitigating challenges, negotiating budgets and managing financial overruns.

Contents Introduction What is Project Management? Why Choose a Career in Project Management? How to Start a Project Manager Career Key Skills for a Project Manager Career Pathways in Project Management Salary and Job Outlook Certifications Introduction If you're considering stepping into the dynamic world of project management or looking to scale the ladder of success in your existing project manager career, you've landed in the right place. The project management labour force is expected to grow by 33%, or 22 million new jobs, by 2027 The term "project manager careers" has seen a remarkable search surge, indicative of the growing relevance and demand for this role across various industries. In this comprehensive guide, I'll explore everything from the skills you need to the pathways you can take. What is Project Management? Okay, it's pretty basic, but it is always the place to start. Project management is the discipline of initiating, planning, executing, controlling, and closing the work of a team to achieve specific goals within a given timeframe and budget. A project manager is the central figure in this process, overseeing all aspects to ensure successful completion. A project manager is the linchpin that holds various project elements together. A typical project manager will oversee the following; Initiation: Defining the scope and objectives of the project. Planning: Creating a detailed project plan, including timelines, milestones, and resource allocation. Execution: Overseeing the work being done, ensuring that it aligns with the project plan and falls within budget. Monitoring and Controlling: Regularly assessing progress to ensure the project stays on course, making adjustments as necessary and mitigating risks. Communication: Acting as the main point of contact between stakeholders, team members, and sometimes clients, ensuring everyone knows the project's status. Quality Management: Ensuring that the project meets the pre-defined quality standards and requirements. Risk Management: Identifying potential risks and developing contingency plans to mitigate them. Budget Management: Monitoring and controlling costs to ensure the project stays within budget. Resource Management: Allocating and managing resources such as manpower, materials, and time efficiently. Closure: Wrapping up all project activities, delivering the final output, and conducting a post-project evaluation. Why Choose a Career in Project Management? Simply put, it can be gratifying, especially if you like a challenge. A couple of criteria define projects; They are temporary - That is to say, they should have a definitive start and end and not just run forever (although, honestly, I've seen some that do!) They have unique objectives - So, normally, a project is doing something unusual that hasn't been done before. These things can be challenging. They require working with people, problem-solving and attention to detail. It's not a career for people who can't manage themselves, aren't organised, or don't like to engage with others. So, if you are serious, then be serious about your strength and your suitability. I hope so. Growing Demand The growing complexity of business operations has led to an increase in multi-disciplinary projects, thereby driving up the demand for skilled project managers. 46% of organisations are prioritising project management as a priority, and it is growing. A staggering 70% of projects 'fail' or hit significant troubles, which is due to people running projects but not having experience. So, project managers with good skills are in increasing demand. Financial Rewards Project managers are among the top industry earners, making it a financially rewarding career. Jump to the salary section. So, if that sounds interesting, you are looking at a solid pay check each month, but you will need to build up experience. Flexibility With project management, I've found you aren't tied to one specific industry. For example, if someone works in underwriting mortgages, that skill might not be as transferrable outside financial services. However, most organisations need some level of project management, regardless of what they are doing as an output. You could jump from textile manufacturing to event planning. There's a lot of flexibility. I would, however warn that there are many niche specialisms in project management, such as software development or construction. If you can start to specialise, then the rewards can be even greater. How to Start a Project Manager Career Educational Requirements A bachelor's degree in management, business, or a related field is typically required. Some also opt for post-graduate courses and certifications such as PMP® or PRINCE2®. But more so, to apply for a project management role, relatable experience is needed. But how do you get experience? Well, there are two main ways; Manage Internal Projects Put yourself forward for project management opportunties in your organisation (or perhaps an outside community you belong to). If you see an opportunity, put your hand up, and try to employ some of the learnings you've acquired. There are lots of accessible sources of training and information out there (including this site, hint, hint). It's certainly how I started. You can also take a slightly more complex piece of work and maybe wrap some light project management around it. This may demonstrate to those you work with the value and benefits of project management and lead to more opportunities. Look for Entry-Level Roles Starting positions often include roles like project administrator, junior project manager, project coordinator, or project analyst. These roles won't typically be looking for a lot of experience, and they are a great place to learn the craft—none of the pressures of running a project yourself, but all of the experiences. Critical Skills for a Project Manager Several vital skills would be looked for in a project manager; Communication: The ability to convey ideas effectively is paramount. Leadership: Guiding your team to success is a primary responsibility. Risk Management: Identifying and mitigating risks is crucial. Time Management: Meeting deadlines is often the difference between success and failure. Technical Proficiency: Familiarity with project management software like Jira or Asana can be a game-changer. All of these can be learned, but leadership and communication are slightly different because you will need a natural tendency in these areas. You will need to lead and influence people, and you will need to communicate frequently with different layers of the organisation and its stakeholders. Career Pathways in Project Management I spoke earlier about specialisms. Here is a brief list of areas where people tend to specialise and could be seen as advanced project management niches. IT Project Manager: Specialising in technology-related projects. Construction Project Manager: Focused on construction and infrastructure. Healthcare Project Manager: Managing projects in the healthcare sector. Consulting Project Manager: Providing expert advice in a specific domain. Freelance Project Manager: Offering project management services on a contractual basis. Salary and Job Outlook According to the Project Management Institute (PMI), project managers can earn upwards of $100,000 annually. The job outlook continues to be positive, with a 33% growth rate expected by 2027. The average project manager salary in the US is $87,411 at the time of writing, with a low of $56k and a high of $135k. Certifications Certifications have become more than just a feather in one's cap; they are often a critical requirement for advancing your project management career. I've certainly hit dead ends on occasion through not having the specific certification that people are looking for, despite having the experience. Credibility and Recognition Project management certifications are globally recognised validations of your skills and knowledge in the field. Earning a certification can set art apart from your peers and could be the tie-breaker in a competitive job market. Skill Enhancement These certifications are designed not just to test but also to train. The study enriches your understanding of the principles and practices of project management, thus honing your skills and making you a more effective manager. Career Growth Being certified opens doors to higher-level positions, challenging projects, and increased earning potential. Employers view certified project managers as assets who can improve project success rates. Popular Project Management Certifications PMP® (Project Management Professional): Offered by PMI, this is arguably the most recognised and respected certification globally. PRINCE2® (Projects IN Controlled Environments): This UK-based certification focuses on process-driven project management and is popular in Europe and Australia. CAPM® (Certified Associate in Project Management): Also offered by PMI, this is aimed at those new to project management. Agile and Scrum Certifications: These specialised certifications are ideal for project managers in rapid development environments. CSM (Certified ScrumMaster): Geared towards understanding Scrum methodology, this certification is ideal for project managers in the tech industry. If you're serious about your career in project management, obtaining a relevant certification should be high on your list of priorities. It validates your skills and gives you the practical knowledge to improve project performance, making it a win-win for both you and your organisation. Final Thoughts The term "project manager careers" encompasses a range of opportunities that are diverse, rewarding, and ever-evolving. With the right skills, education, and focus, you can carve a fulfilling and lucrative career in this field. So, if you plan to embark on or advance in your project manager career, now is the time to take action. Equip yourself with the necessary knowledge and skills, and you'll be well on your way to becoming an indispensable asset in any organisation.

Hi. I'm excited to share a tool I've been working on, designed to alleviate some common pain points in project management: the Project Complexity Calculator. What is the Project Complexity Calculator? Simply put, it's a tool to help you measure how complex a given project is. Using a set of criteria, the calculator allows you to assess a project quantitatively, removing the guesswork from the equation. It offers an overall complexity score and categorises the project into levels like 'Low Complexity,' 'Moderate Complexity,' and 'High Complexity.' How Does It Work? The Project Complexity Calculator is an intuitive tool that requires you to answer a series of questions about the project you are assessing. Each question corresponds to a specific aspect of project management, such as project size, scope, end-user impact, technologies used, and so on. For each question, you choose one of three predefined answers, each assigned a value of either 1, 3, or 5. These values are then summed to calculate a project's total complexity score. Based on this score, the calculator provides a complexity level that gives you an idea of how challenging the project might be. Why Do You Need the Project Complexity Calculator? Remove Arbitrariness The first major benefit is the removal of arbitrary decision-making. Let's be honest; we're only human. We tend to underestimate or sometimes overestimate how complex a project is. Emotions, optimism, and subjective opinions can muddy the waters. With this calculator, you have a set of criteria to evaluate the project objectively. This ensures you don't overlook or dismiss any critical factors as inconsequential. Compare and Contrast Projects The second advantage is the ability to compare projects head-to-head. By scoring each project using the same criteria and methodology, you can rank them according to their complexity and risk factors. To get a visual representation, you can even plot these scores on a graph, mapping complexity against reward. This will help you prioritise the most valuable projects to undertake, enabling more effective resource allocation and strategic planning. How Can You Use the Calculator? Well, that's the easiest part. All you have to do is navigate through a series of dropdown boxes and choose the option that best describes your assessment criteria. Once you've reviewed all the questions, hit the 'Calculate Complexity' button, and voilà! Your project's complexity score and level will be displayed. Wrapping Up The Project Complexity Calculator is more than just a tool; It streamlines the decision-making process, offers a measurable way to evaluate projects, and provides a roadmap for what could otherwise be a convoluted journey. I'm confident this calculator can be a valuable addition to your project management toolkit. I'd love to hear your thoughts and feedback on how it has helped you or can be improved further. Until then, happy project planning!

The Communication Plan template guides you through creation of a structured approach to project comms Introduction Our Communications Plan Template is essential to facilitate effective and efficient communication within your project teams and stakeholders. Designed to work with your project’s unique needs, it is a roadmap for how, when, and with whom to communicate. What is the Purpose of the Communications Plan Template? The Communications Plan Template aims to outline a structured approach for disseminating crucial project information. It ensures that everyone involved— from the project team to the client to advisory roles like IT security— knows what to expect, where to find information, and how to provide feedback. This improves project transparency, stakeholder engagement, and overall project success. Where and When to Use the Communications Plan Template? The Communications Plan Template is versatile and can be utilised across various project stages and scenarios: During the planning phase to set expectations. Throughout the project to guide ongoing communications. At project closure for reviews and audits. What's Inside? The Communications Plan Template is replete with key sections for a well-rounded communication strategy: Objectives: Explains the aim and significance of your communication plan. Stakeholders & Roles: Lists the different stakeholders, their roles, and their communication needs and preferences. Communication Matrix: Outlines the types, objectives, audience, frequency, and other details for each kind of communication. Communication Guidelines: Sets rules for emergency situations, document storage, and feedback mechanisms. Schedule: Provides a timeline for various types of communication. Approval & Review: Specifies the plan's approval process and review schedule. Additional Information Customisable: Easily adapt the template to the needs of your project. User-Friendly: Comes in a format that is easy to fill out and follow. Secure: Suitable for various document classification levels, from public to classified to internal use only. Why Choose Our Communications Plan Template? Efficient: Helps you save time by providing a pre-established framework. Comprehensive: Ensures that you cover all bases in terms of who needs to know what, when, and how. Consistent: Maintains uniformity in the way you communicate across projects or even within different phases of a single project. Best Practices: Built on industry standards to ensure effective and compliant communications. Our Communications Plan Template is a one-stop solution for establishing a well-defined communication strategy, helping your projects run smoothly.

The Feasibility Study template helps guide you through the viability of a project idea. Introduction This Feasibility Study Template serves as an indispensable tool for project managers, sponsors, and stakeholders in evaluating the practicability of a proposed project. The template offers a structured approach to assessing various elements like market conditions, financial viability, and technical requirements, among other factors. What is the Purpose of the Feasibility Study Template? The purpose of this template is to guide you through the crucial initial phase of project planning. The structured format ensures all aspects of feasibility—including market, technical, financial, and legal—are thoroughly assessed. This comprehensive evaluation aids in making informed decisions on whether to proceed with, adjust, or abandon a project. Where and When to Use the Feasibility Study Template? This versatile template can be utilised across various sectors and project types. It's particularly useful: During the project initiation phase. For risk assessment in ongoing projects. When pitching a new project to stakeholders or potential investors. What's Inside? The Feasibility Study Template is compartmentalised into several key sections, each designed to capture essential data: Executive Summary: A snapshot of key findings and recommendations. Introduction & Objectives: Detailed background and aims of the project. Scope: Definition of what’s in and out of the project’s purview. Methodology: Explanation of the approach for data gathering and analysis. Market, Technical, Financial, Legal, and Operational Feasibility: In-depth analyses on these critical aspects. Risks and Contingencies: A review of potential challenges and mitigation strategies. Conclusion & Recommendations: A summary verdict and suggested next steps. Additional Information Customisable: Adapt the template to your specific project needs. Guidance Notes: Helpful hints and examples are provided within the template to assist you in filling it out. Compatibility: Designed to be user-friendly and compatible with various document formats. Why Choose Our Feasibility Study Template? Comprehensive: Covers every facet of project feasibility, ensuring nothing is overlooked. Efficient: Save time on creating a study format from scratch and focus more on the analysis. Informed Decision-Making: Offers stakeholders a complete picture, enabling better investment decisions. Professional Standards: Aligns with best practices in project management and feasibility assessment. The Feasibility Study Template is your go-to resource for starting your projects on a foundation of thorough and effective planning.

The Business Case template guides you through creation of a project's justification Introduction Our Business Case Template is designed to provide a rigorous and comprehensive framework for evaluating and presenting business issues, opportunities, and solutions. Ideal for decision-makers and stakeholders, this template makes it easier to weigh options, assess risks, and decide on the best course of action. What is the Purpose of the Business Case Template? The template aims to facilitate the methodical examination and documentation of a business proposition. It provides a comprehensive approach for defining objectives, identifying problems or opportunities, assessing solution options, and more. All these are framed to help the organisation meet its strategic goals. Where and When to Use the Business Case Template? The Business Case Template is versatile, suitable for a wide range of sectors and project types, including: When seeking project approval from decision-makers. During the planning phase of a new project or venture. As part of a pitch to investors or other external stakeholders. What's Inside? The template is divided into numerous important sections to help you cover all bases: Executive Summary: A high-level summary containing key points from all sections. Introduction & Business Objectives: Background, context, and goals aligned with corporate strategy. Problem Statement: A detailed account of the issue or opportunity being addressed. Solution Options: Comprehensive descriptions of potential solutions, with pros and cons. Cost-Benefit Analysis: A breakdown of financial aspects, including ROI. Market Analysis: An assessment of relevant market conditions. Technical Requirements: A list of technological needs. Risk Assessment: Identification and mitigation strategies for potential risks. Governance and Compliance: Details on oversight and legal considerations. Project Plan: A high-level overview of timelines and resource allocation. Recommendations & Conclusion: Final endorsement of the selected solution. Appendices: Supplementary data, charts, or documentation. Additional Information Customisable: Easily tailor the template to meet your specific needs. User-Friendly: The template is easy to use and follows a logical flow. Compatibility: Works well with various document formats and software. Why Choose Our Business Case Template? In-Depth: Its comprehensiveness ensures that no critical aspect is missed. Decision-Facilitating: Helps in making informed choices based on data and assessments. Alignment with Best Practices: Follows industry standards for effective business case development. Time-Efficient: Enables you to focus on the content rather than the structure. This Business Case Template is an invaluable tool for anyone looking to make compelling and well-supported business decisions.

In my ongoing journey through management and project execution, I've found myself repeatedly exasperated by a common phenomenon – "analysis paralysis". The term describes a situation where over-analysis or overthinking prevents one from making a decision. A decision which, in many cases, doesn't necessarily have a right or wrong answer. It's all too easy to fall into the trap of seeking perfection. The ideal solution. The perfect route forward. Yet, what many fail to recognise is that sometimes 'good' is, in fact, good enough. It seems to me, that this is particuarly a problem in organisations where roles & responsibilities, and more explicity 'accountability' isn't well defined. In these circumstances teams start trying to make decisions by consensus. Hell, I'd never get dressed in the morning if the decision were to be made by some of the teams I've worked with. The Quest for Perfection Every manager or project leader has been there: multiple paths lie ahead, each one potentially fruitful. But instead of moving forward, we stall, deliberating and weighing options, in the vain hope of unearthing that elusive perfect choice. Paradoxically, situations with no apparent bad options can be the most challenging of all. Here's a revelation I've come to understand: sometimes, the pursuit of the perfect decision can be more detrimental than making a 'good-enough' decision swiftly. You are probably reading this and saying 'duh. yeah.' But here's my point; it just doesn't happen very often. We all know the experiments that demonstrate that we know we shouldn't sit in a room filling with smoke, but we are influenced by what others are doing or not doing in the situation, rather than taking critical decisions, we look to what others are signalling. This isn't a call to be reckless, but rather an observation on the value of the 'ready, fire, aim' mentality. Yes, that sentence is in the right order. 'Ready, Fire, Aim' - Embracing the Bias Towards Action There's a beauty in biasing oneself towards action. It's about doing, refining, and evolving, rather than remaining stationary in contemplation. The 'ready, fire, aim' approach suggests that we should act first and calibrate our methods along the way. This method resonates with the philosophy of the Lean Startup methodology, which encourages rapid prototypes, continuous testing, and quick pivots based on feedback. We talk about being 'agile' and 'failing fast' all the time. Do I ever witness it? Rarely. They become just words that are thrown around like kids with expletives they don't understand. Why Do We Fall into the Trap? Understanding the underlying psychological causes of analysis paralysis can empower us to identify when we're at risk and implement strategies to break free. Here's a little of the research I've made into these psychological triggers: Fear of Failure: Deep-rooted Evolutionary Instincts: Our aversion to failure can be traced back to our evolutionary roots. Early humans associated failure with life-threatening consequences. While the stakes are not as high in modern management, the primal fear remains. There are no life-or-death scenarios in the average meeting room, certainly none that I've encountered. Social and Professional Repercussions: In today's corporate culture, mistakes are often magnified. Managers fear the potential loss of respect, position, or even employment. The irony is that most social repercussion in a work environment is through inactivity and the things that weren't acted upon, not the ones that were (recognising I'm talking about situations outside of the office Christmas party here). Loss Aversion: Studies in behavioural economics have shown that humans feel the pain of loss more acutely than the pleasure of gain. This disproportionate fear of negative outcomes can cripple decision-making. I could, and probably will write an entire blog on this at some point. It fascinates me. Mitigating the Fear: Recognising that mistakes are opportunities for learning and growth is vital. Moreover, one should also weigh the costs of inaction, which can often exceed the costs of a wrong decision. Desire for Control: Illusion of Predictability: Individuals believe they can predict and control future events by analysing every potential outcome. This sense of predictability provides a comforting illusion of control in uncertain scenarios. Those of us that suffer from anxiety (and I often drink from that cup, my friend), get stuck here. We can obsess about possible outcomes and focus on the worst, even if it's likelihood is next to nothing. Avoidance of Responsibility: Over-analysis can sometimes be a shield to defer responsibility. If one spends all their time analysing, they can avoid taking action and, consequently, avoid blame for potential failures. We've all seen this. "If I don't take a decision, I can't be blamed for any failure'". Challenge of Letting Go: Delegating decisions or accepting the inherent unpredictability of certain scenarios is difficult for many. Recognising the limits of control and embracing adaptability can pave the way for more dynamic decision-making. Cognitive Overload: Information Era's Double-Edged Sword: While the digital age provides unprecedented access to information, it also inundates us with vast quantities of data, not all of which is relevant or valuable. If you want evidence of that, just look at Twitter, or X, or whatever it is this week, if it even exists when you read this. Diminishing Returns of Information: Beyond a certain point, additional information doesn't aid in decision-making but rather muddles it. This can result in ‘choice paralysis’, where too many options or too much data makes it impossible to decide. If you start to think you are in this trap, then you probably are faced with the opposite of the Kobayashi Maru and the unlosable situation. IYKYK. LLAP. Tackling Overload: Effective filtering of information, setting clear objectives, and prioritising quality over quantity of data can assist in navigating the sea of information without getting lost. Understanding these psychological underpinnings is the first step in breaking free from the clutches of analysis paralysis. By being aware of these tendencies, managers and leaders can make more informed, timely, and effective decisions. Well, that's the theory. At the end of the day, it's down to you. Let's look at some of the ways of escaping the sinkhole of over-analysis. Recognising and Escaping Analysis Paralysis Realising that one is ensnared in the analysis paralysis web is half the battle. But once you've identified it, how do you move forward? The strategies below are preventative measures and ways to pull oneself out of the paralysis vortex. Set Deadlines: The Power of Constraints: Constraints, oddly enough, foster creativity and urgency. When time is limited, it forces the mind to focus and make decisions. I personally find timeboxing very effective. I'll sit down at a desk and say 'I'm not moving until I have made a decision." Not out loud, you understand; that'd just be weird. Pomodoro Technique: Adopting time-management methods like the Pomodoro Technique can create short bursts of concentrated work, interspersed with breaks. This pattern can reduce the window for overthinking. I found it here on Wikipedia, must be true. Limit Information: The 80/20 Rule: Also known as the Pareto Principle, it suggests that 80% of results come from 20% of efforts. Similarly, a significant chunk of essential information is usually found in a fraction of the available data. I love the 80/20 rule. It's so often misquoted that it's hilarious. Watch somebody sometime when they quote it in a meeting, looking like they understand it. At that point, you and I can nod and wink at each other virtually. Use Tools: Tools like those explored in this article can help (Link). Even AI can help distil data into digestible insights. For example, you could feed documents into Claude or ChatGPT and ask it to summarise the benefits of each into a table. It'd help solidify things, perhaps. Trust Your Intuition: The Subconscious Processor: Our brain constantly processes information, even when we're not aware of it. These background calculations often present themselves as gut feelings or instincts. Malcom Gladwell wrote an amazing book called 'Blink' about 'thin-slicing', or using your experiences to analyse something quickly to make a conclusion, but without articulating how you reach a certain answer. The results of this approach can be astonishing. Great book. Balancing Act: Here's a health warning which really doesn't need saying, but while intuition is powerful, it's essential to balance it with logic. Ensure that gut feelings don't override empirical evidence but rather complement it. Seek External Opinions: Breaking the Echo Chamber: When engrossed in a problem, it's easy to get caught in a loop of repetitive thought. An external perspective can introduce fresh angles and solutions. Get out of it, and take external input. Even talking to the dog can help, although mine isn't honestly much help. It's the act of speaking out loud and seeking external input or even acknowledgement. Diversity of Thought: Engaging with individuals from different backgrounds or industries can offer innovative approaches. The diversity of thought can prevent stagnation and drive progress. I cannot tell you how many times I've had a block on something at work and spoken to my wife about it, and she's proved to be the key. That abstraction from the situation is often the key. Ask an expert: There is always, always, someone out there that has done a similar thing before and has experiences they are ready to share. Go find them. Ask them for guidance or input. Unless it's me. I'm really busy this afternoon. In essence, while analysis is invaluable, it should serve as a platform for informed action, not as an obstacle to it. By incorporating these strategies, one can navigate the delicate balance between thoughtful deliberation and decisive action. While it's essential to be thoughtful and informed in our decisions, it's equally crucial not to let the pursuit of perfection hamper progress. As Voltaire once said, "Perfect is the enemy of good". Honestly, I had to look who said that up, but it's a good line to end on.

Have you ever had a Eureka moment – an idea you're convinced will transform your business and set the market ablaze? If so, you're not alone. In fact, you're in the company of countless businesses or individuals that embark on ambitious projects every year, buoyed by high expectations. Yet, as many of us will have experienced, the chasm between expectation and reality can often be wider than anticipated. Perhaps you've also been part of projects that achieved their immediate objectives but fell short of realising their promised benefits. We've all been there, from internal infrastructure projects that failed to streamline processes in quite the way we'd hoped to customer-facing deliveries that didn't ignite the market. And, hands held high, I've been there too in some of my own ventures. So, what do we do when we find ourselves in this situation? Do we throw up our hands and toss everything away, baby and bathwater alike? Or do we seek to learn, adjust, and bounce back stronger? Here are two key points to consider: 1) Challenge the Business Case: Before embarking on a project, it is vital to scrutinise the original business case and the projected benefits rigorously. These should be tested and examined, drawing on as much evidence and as many sources as feasible. There will, however, be times when it's not possible to gather all the evidence we'd like. In these cases, we may need to take a leap of faith, but even then, this leap should be informed. Here are some quick suggestions; Market Assumptions: Assess the understanding of market size, trends, and competitive landscape. Are these assumptions supported by reliable data? Why are you seeing a gap others haven't, and what is it that you uniquely bring to the table that others can't (sometimes called the 'unfair advantage'). Find Early Adoptors To Test the Business Case: Find the customers that will pay for your product or the internal users that are keen to use it right up front. The outcome should be something that people will want to "pull" from you, not have thrust upon them. So, if there is real enthusiasm from those whom it is designed for, find them. Not a salesman, not the idea originator, but someone entirely independent that gets excited (not just lukewarm to be polite) about the prospect of the delivery. You probably need to refactor your thinking if you can't find them. Benefit Projections: Review the projected benefits. Are these backed up by robust data and research? Are the benefits quantifiable, and is there a plan to measure them over time? Exactly what problem are you solving, and for whom? It's often said, but there's an absolute truth in this. Ask it over and over until you 100% know the answer. Cost Estimates and Timeframe: Evaluate the cost estimates and proposed timeline. Are they realistic or overly optimistic? Do they account for potential delays and all associated costs? Your idea may be a killer one, but your ROI might drop through the floor if it costs you double to deliver it, thereby scuppering any benefits. Feasibility: ITIL teaches us that services/products need to be looked at in two lights; Warranty and Utility. 'Utility' refers to the functionality of a service that meets a particular need or provides a specific benefit, often summed up as "what the service does". 'Warranty' refers to the assurance that a product or service will meet agreed requirements, encapsulating aspects such as availability, capacity, security, and continuity, essentially answering "how it is delivered". So often, we focus on one but miss the other. I've more than once been caught in a project that totally underestimated the Utility aspects, and they came crashing down after delivery. Imagine a mobile phone; it can have greater features, bells and whistles, but if the battery lasts an hour or the coverage is poor, then the whole thing is a failure. Many years ago, I delivered a project (under direct instruction!) to give field workers laptops to help their reporting and admin. The laptops proved unwieldy, slow to start, difficult to connect and didn't work offline at all. We had to pull 40+ units out of the field and replace them with tablets and new software that worked offline. Once that was done, the whole thing was a huge success, and the benefits were amazing to the workers, enhancing their workday hugely. 'Bear Pit' Ideas with Stakeholders: 'Bear-pitting' in a business context refers to a rigorous evaluation method in which an idea or proposal is presented to experts or critical thinkers for intense questioning and scrutiny. The process aims to uncover potential flaws, strengthen the idea, and prepare for any challenges it may face in implementation. Check if the project aligns with the company's broader strategic goals and if all key stakeholders are on board. Business ideas. 2) Learn and Refactor: Just because a project doesn't deliver the anticipated benefits doesn't mean that all is lost. Far from it. Remember, many great successes have come from learning from missteps, refactoring, adjusting, and then coming back stronger. Consider Edison and his legendary multitude of attempts before inventing a functional light bulb. Or J.K. Rowling, who was rejected multiple times before Harry Potter became a global sensation. Even certain films, initially dismissed as flops, like Blade Runner, eventually found their audience and are now considered classics. Failure is the pathway to success. Remember, if a project doesn't achieve the anticipated benefits, it doesn't necessarily equate to total failure. Yes, it can be disheartening, especially when you've invested so much time and energy into the project. But rather than throwing the baby out with the bathwater, which I've seen over and over again, consider reframing this experience as an opportunity to learn, improve, adapt, and come back stronger. So the next time you're faced with a business case that didn't live up to its promises, take a deep breath and a step back. Look for the lessons, refactor your strategy, and remember that it's not the end of the world. Instead, it could be the beginning of something even better. After all, sometimes, the path to success is paved with stepping stones of unmet benefits.