5 Whys Analysis is a problem-solving method used to explore the root cause of an issue by asking the question ‘Why?’ five times in succession. Each answer forms the basis of the next question, helping to move beyond surface-level symptoms and identify underlying causes. It is a straightforward technique that encourages critical thinking and effective…
A Fishbone Diagram, also known as an Ishikawa or cause-and-effect diagram, is a visual tool used to systematically identify the possible causes of a specific problem. It helps teams break down complex issues by categorising potential factors that contribute to the problem. The diagram looks like a fish skeleton, with the main problem at the…
Workflow analysis is the process of examining how work is done within an organisation or team. It involves looking at each step in a process, identifying who does what, when, and how tasks are handed off. The goal is to find ways to improve efficiency, reduce errors, and make work easier for everyone involved.
Process optimisation strategy is a planned approach to making a workflow or set of tasks run more efficiently and effectively. It involves analysing current processes, identifying areas where time, resources, or costs can be reduced, and making changes to improve overall performance. The goal is to achieve better results with less waste and effort, often…
Change Impact Assessment is a process used to identify and evaluate the consequences of making a change within a system, project, or organisation. It helps people understand what might be affected, such as processes, teams, technology, or customer outcomes. By assessing the potential impacts in advance, organisations can plan for risks and ensure smoother transitions…
Non-functional requirements describe how a system should perform rather than what it should do. They focus on qualities like speed, reliability, security, and usability. These requirements help ensure the system meets user expectations beyond its basic features.
A functional specification is a detailed document that describes what a system, product, or application is supposed to do. It outlines the features, behaviours, and requirements from the user’s perspective, making it clear what needs to be built. This document serves as a guide for designers, developers, and stakeholders to ensure everyone understands the intended…
A Business Requirements Document, or BRD, is a formal report that outlines the goals, needs, and expectations of a business for a specific project or process. It describes what the business wants to achieve, the problems to solve, and the features or outcomes required. The BRD acts as a guide for project teams, ensuring everyone…
Kano Model Analysis is a method used to understand how different features or attributes of a product or service affect customer satisfaction. It categorises features into groups such as basic needs, performance needs, and excitement needs, helping teams prioritise what to develop or improve. By using customer feedback, the Kano Model helps organisations decide which…
MoSCoW Prioritisation is a method used to decide what is most important in a project or task list. The name comes from the initials of four categories: Must have, Should have, Could have, and Won’t have. This technique helps teams agree on which features or tasks are essential, which are desirable, and which can be…