By the end of this chapter, you will be able to:
These skills will help you make smart decisions that lead to successful projects in your trade!
Compiled by: Kevin Kamau
Developing a business case is a critical phase in project inception that provides a structured justification for initiating a project. It enables decision-makers across various sectors in Kenya to evaluate the value, feasibility, and risks associated with a proposed initiative before committing resources. Whether in healthcare, county government, banking, or agriculture, a well-crafted business case ensures alignment with organizational goals and stakeholder expectations. This chapter focuses on understanding the statement of the problem, which forms the foundation of any compelling business case.
In every professional field, clearly identifying and articulating the problem that a project intends to solve is essential. The statement of the problem sets the direction for the entire business case by defining the issue in a way that stakeholders can understand and relate to. In Kenya’s diverse sectors such as education, hospitality, and retail, an accurate problem statement helps prevent misallocation of resources and enhances project success rates.
The purpose of the statement of the problem is to pinpoint the gap or challenge that necessitates a project intervention. It acts as the foundation upon which the business case builds its justification and guides all subsequent analysis and planning.
The statement must clearly describe the issue without ambiguity, enabling stakeholders from different professional backgrounds to grasp its scope. For instance, at a county referral hospital, a vague statement like "improve patient services" would be less effective than "reduce patient waiting times in outpatient clinics by 30% within 12 months."
A precise problem statement narrows down the objectives and outcomes the project aims to achieve. At a university, identifying "low student retention rates in science courses" helps focus on targeted interventions such as curriculum review or enhanced student support.
It provides a common understanding for all stakeholders, including county government officials, SACCO members, and hotel management teams, facilitating their input and buy-in. When stakeholders recognize the problem’s impact, they are more likely to support resource allocation.
By examining the problem thoroughly, potential risks and challenges related to the project can be anticipated early. For example, a retail business might identify supply chain disruptions as a key problem, allowing risk mitigation strategies to be developed.
The problem statement justifies the need for investment by linking the issue to tangible consequences such as financial losses or service inefficiencies. At NEMA, articulating environmental degradation caused by improper waste management can justify funding for new monitoring technologies.
An effective problem statement possesses distinct attributes that enhance its utility during project inception and approval.
It must focus on a particular issue rather than a broad or general concern. For example, a SACCO’s problem statement might specify "high loan default rates among youth borrowers" instead of a generic "poor loan performance."
Quantifiable elements should be included to track progress and evaluate solutions. A hotel may state "a 20% decline in customer satisfaction scores over the last year," which can be measured through surveys.
The problem should align with the organization’s strategic priorities and address a real need. For instance, a farm cooperative focusing on "declining crop yields due to pest infestation" addresses a direct threat to livelihoods and income.
The statement must be brief yet comprehensive enough to convey all essential details. Overly lengthy descriptions may confuse stakeholders or dilute focus.
It should identify underlying causes rather than symptoms. A county government office might avoid stating "delays in service delivery" as the problem and instead specify "inefficient document processing systems causing service delays."
Developing a robust problem statement involves systematic analysis and consultation to ensure accuracy and relevance.
Conduct Preliminary Research: Gather data and insights from relevant sources such as reports, stakeholder interviews, and performance metrics. For example, a retail business analyzing sales trends and customer feedback to identify declining revenue causes.
Engage Stakeholders: Consult with those affected by the problem, including employees, clients, and management, to capture diverse perspectives. At a county hospital, engaging clinicians and patients can reveal service delivery bottlenecks.
Define the Problem Context: Describe where and when the problem occurs and whom it affects. A university might specify that "student absenteeism is highest in first-year mathematics classes during the second semester."
Identify Root Causes: Use techniques like the “5 Whys” or cause-and-effect diagrams to move beyond symptoms. A SACCO could discover that loan defaults stem from inadequate borrower education rather than economic hardship alone.
Draft the Problem Statement: Write a clear, concise description incorporating key findings and measurable elements. For instance, "The county government’s document approval process currently takes an average of 15 days, exceeding the desired 5-day turnaround, leading to service delivery delays."
Validate the Statement: Review with stakeholders to ensure accuracy and consensus before finalizing. This step avoids misunderstandings and builds ownership.
Failing to articulate the problem effectively can have significant negative impacts on project outcomes and organizational resources.
Without a clear problem statement, project objectives may not address the real issues, leading to wasted efforts. For example, a hotel investing in new booking software may miss the actual problem of poor staff training on customer relations.
Funds, time, and human resources may be expended on irrelevant or ineffective solutions. A county government office may procure expensive equipment when process redesign would have sufficed.
Ambiguity breeds confusion and disagreement among stakeholders, undermining collaboration. Employees at a retail business might resist a project they do not understand or see as irrelevant.
Unidentified or misunderstood problems lead to unforeseen risks during implementation. An agricultural cooperative might fail to anticipate pest resistance if the problem is not analyzed deeply.
Ultimately, the project may fail to deliver expected benefits, damaging organizational reputation and morale. A university’s initiative to improve graduation rates may falter if the core issue of inadequate academic support is overlooked.
Create a free account to open more of this chapter.
Free: practical guides, quick cards, workplace scenarios and more.
Create a free accountThis chapter explored the process of developing a business case, starting with a clear statement of the problem that identifies the core issue requiring attention. It then examined alternative solutions, considering various options to address the problem effectively. The chapter emphasized the importance of conducting a thorough cost benefit analysis to evaluate the financial and non-financial impacts of each alternative. Based on this analysis, a solution recommendation is made, selecting the option that offers the greatest value and feasibility. Finally, the chapter discussed the implementation phase, outlining the steps necessary to put the chosen solution into action and achieve the desired outcomes. Understanding these stages ensures that projects are grounded in sound reasoning and practical planning from inception to execution.
At the start of this chapter we promised you would be able to:
Tick each one you can genuinely do.
So, are you there yet?
You're competent when you can confidently do 50% or more of what this chapter promised.
Sign in to record how you're doing.