Business Problem Solving Training Course

Duration 5 days 10 modules · 33 contact hours
Level Intermediate Certificate on completion
Who attends Business Managers, Process Improvement Specialists and others
Fee from USD 1,100 KSh 95,000 for Kenyan organisations
Where 52 cities + online See dates by city
Next start 16 Nov 2026 Course code SD-IC-019

Before you join: Participants should have experience working on business, service, process, product, customer, policy, or operational improvement assignments.

Dates & prices

Two start dates a month in every city, and live online on weekdays or weekends. Fees are per participant; classroom fees include tuition, materials, lunch and refreshments, and the certificate.

Suggest a date or city

Showing the next six months. Later dates, other cities and private deliveries for your team are available on request.

Course overview

Business teams are often asked to create innovative solutions when the actual issue has not been defined, evidence is thin, and stakeholders disagree about success. A delayed loan approval process, rising customer complaints, failed digital adoption, or a costly manual control may reflect several interacting causes. Selecting the first plausible fix wastes budget and can create new operational, regulatory, or customer risks. This course provides a disciplined route from an ambiguous challenge to a tested solution concept.

Participants learn to frame problems from the customer, operational, and commercial perspectives; gather and interpret evidence; identify root causes and system constraints; and generate options beyond familiar responses. They use Design Thinking, Jobs to Be Done, systems mapping, SCAMPER, Business Model Canvas, prototyping, experimentation, and decision analysis to develop solutions that are desirable, feasible, viable, and suitable for implementation. The course also addresses stakeholder alignment, investment reasoning, pilot design, change impacts, and decision communication.

Teaching combines concise instructor briefings with realistic case work, facilitated group analysis, problem-solving simulations, and structured application planning. Participants work through the full problem-solving cycle using tools that can be transferred to live assignments. They leave with a business problem solution dossier containing a framed challenge, stakeholder analysis, root-cause map, solution concepts, selection criteria, experiment plan, value case, and pilot roadmap.

The course is suited to managers and specialists who must improve services, processes, products, customer experiences, controls, or operating models. It is particularly relevant where a problem crosses departmental boundaries and requires evidence-based decisions rather than a single technical answer.

What you will be able to do

  • Frame ambiguous business challenges using problem statements, stakeholder maps, and measurable success criteria
  • Gather customer and operational evidence through interviews, observation, and structured research plans
  • Diagnose root causes using process maps, Five Whys, fishbone diagrams, and systems maps
  • Generate diverse solution concepts using How Might We questions, brainwriting, SCAMPER, and morphological analysis
  • Develop solution concepts using value propositions, service blueprints, and business model assumptions
  • Evaluate options using weighted decision matrices, impact-effort analysis, risk registers, and pre-mortems
  • Design prototypes and experiments with hypotheses, success metrics, evidence thresholds, and learning logs
  • Present a pilot-ready business case with benefits, implementation roadmap, governance, and decision request

Benefits of attending

For you

  • A repeatable method for turning vague requests into defined problem statements
  • Stronger facilitation of solution discussions with competing stakeholder views
  • Practical tools for producing evidence before recommending investment
  • Greater confidence testing ideas before committing significant time or budget
  • A structured dossier for presenting recommendations to senior decision-makers

For your organisation

  • Fewer premature solution commitments based on assumptions or seniority
  • Better prioritisation of improvement opportunities using explicit decision criteria
  • Earlier identification of customer, operational, regulatory, and implementation risks
  • More credible pilot proposals with measures, ownership, and decision gates
  • Shared problem-solving language across business, technology, operations, and service teams

Course modules

10 modules over 5 days

Participants can define an ambiguous business challenge with boundaries, stakeholders, assumptions, and measurable outcomes.

  • Distinguishing symptoms, constraints and root causes in ambiguous problem statements
  • Problem statement canvas defining user, need, outcome and boundaries
  • SMART success measures paired with leading and lagging indicators
  • Stakeholder mapping using power-interest grids and influence assumptions
  • Assumption mapping separates known facts, beliefs, risks and unknowns
  • Context diagrams expose interfaces, dependencies and decision ownership
  • Problem framing reframes requests without prematurely selecting solutions

Participants can create an evidence plan that reveals stakeholder needs, behaviours, and knowledge gaps.

  • Research plan sets learning questions, evidence sources, methods and timing
  • Stakeholder interviews use laddering questions, probing and neutral prompts
  • Observation protocols record workarounds, delays, handoffs and environmental cues
  • Voice-of-customer statements distinguish stated needs from underlying jobs
  • Jobs to Be Done identifies functional, emotional and social progress
  • Affinity mapping converts field notes into themes and opportunity areas
  • Evidence quality checks assess source bias, recency, validity and gaps

Participants can identify causal factors, bottlenecks, and system interactions behind a business problem.

  • Process mapping traces customer journeys, handoffs, queues and failure points
  • Five Whys tests causal chains without mistaking correlation for cause
  • Fishbone diagrams structure people, process, technology, policy and environment causes
  • Pareto analysis isolates high-frequency or high-impact problem categories
  • Systems maps reveal feedback loops, delays and unintended consequences
  • Constraint analysis identifies bottlenecks limiting throughput, service or adoption
  • Problem decomposition creates manageable subproblems with explicit interfaces

Participants can generate a broad set of relevant solution ideas without settling on familiar responses too early.

  • Design criteria translate evidence into solution requirements and trade-offs
  • How Might We questions open productive solution spaces
  • Brainwriting 6-3-5 generates ideas before group discussion anchors thinking
  • SCAMPER challenges existing offers through substitution, combination and reversal
  • Analogous industries supply patterns for transfer without copying surface features
  • Morphological analysis combines independent solution dimensions into novel concepts
  • Forced connections disrupt familiar categories using random stimulus prompts

Participants can turn selected ideas into coherent concepts with explicit customer value and operational requirements.

  • Concept posters specify target user, value proposition, mechanism and assumptions
  • Value Proposition Canvas tests customer pains, gains and jobs
  • Business Model Canvas links value creation, delivery, revenue and costs
  • Service blueprints connect frontstage interactions with backstage operational requirements
  • Assumption-to-test tables define evidence thresholds and decision consequences
  • Storyboards make future service experiences concrete before implementation
  • Concept portfolios preserve alternative options under material uncertainty

Participants can compare solution concepts transparently and identify risks before allocating resources.

  • Weighted decision matrices compare concepts against agreed selection criteria
  • Desirability, feasibility and viability assess solution quality from three perspectives
  • Impact-effort matrices sequence quick wins, strategic bets and deferments
  • Cost-benefit analysis states assumptions, ranges, cash effects and nonfinancial impacts
  • Pre-mortems identify likely failure modes before committing resources
  • Risk registers assign owners, controls, triggers and contingency actions
  • Ethical screening identifies distributional effects, consent concerns and exclusion risks

Participants can design proportionate prototypes and tests that produce decision-relevant evidence.

  • Prototype fidelity matches the question, audience, risk and available time
  • Paper prototypes test workflows, messages, interfaces and service interactions
  • Service role-play reveals handoff failures and behavioural responses
  • Usability test scripts define tasks, prompts, observations and success criteria
  • Experiment canvases state hypothesis, test method, metric and threshold
  • A/B test design controls variables, segments and exposure conditions
  • Learning logs document evidence, interpretation, decisions and next tests

Participants can construct a concise case for investment based on expected value, uncertainty, and implementation choices.

  • Problem economics quantifies baseline costs, revenue leakage, risk and delay
  • Benefits maps link solution features to measurable operational outcomes
  • Three-point estimates express cost, benefit and timing uncertainty
  • Scenario analysis compares base, downside and upside value cases
  • Investment narratives connect evidence, strategic priorities and implementation choices
  • Decision papers distinguish recommendations, assumptions, alternatives and approval requests
  • Executive storytelling uses message hierarchy, evidence and concise visual logic

Participants can convert a selected concept into a governed pilot with clear ownership, measures, and change actions.

  • Pilot charters define scope, cohort, hypothesis, measures and governance
  • Minimum viable product boundaries prevent pilots becoming uncontrolled implementations
  • Implementation roadmaps sequence dependencies, milestones, owners and decision gates
  • RACI matrices clarify accountabilities across business, technology and suppliers
  • Change impact assessments identify affected roles, processes, skills and controls
  • ADKAR plans address awareness, desire, knowledge, ability and reinforcement
  • Control plans monitor performance, exceptions, ownership and corrective action

Participants can facilitate structured problem-solving decisions and create an application plan for a live business challenge.

  • Structured problem-solving agendas balance divergence, convergence and decision making
  • Six Thinking Hats surfaces evidence, risks, benefits and alternatives
  • Conflict protocols separate interests, criteria and options during evaluation
  • Decision logs record rationale, dissent, assumptions and review dates
  • Facilitation techniques manage dominant voices, silence and premature consensus
  • Personal application plans define priority problem, sponsors, milestones and first actions
  • Peer review strengthens framing, test design and implementation assumptions

Exercises and examples are adapted to each cohort's sectors and roles.

What you take back to work

  1. Business problem statement canvas
  2. Stakeholder and assumption map
  3. Root-cause and systems analysis pack
  4. Solution concept and selection matrix
  5. Prototype and experiment canvas
  6. Pilot business case roadmap

Who should attend

  • Business Managers — responsible for resolving cross-functional performance, service, or growth issues
  • Process Improvement Specialists — need structured methods to diagnose issues and test interventions
  • Innovation Managers — require repeatable approaches for moving concepts toward investable pilots
  • Product Managers — need evidence-led methods for defining customer problems and prioritising solutions
  • Project Managers — must convert uncertain opportunities into scoped, governed implementation plans
  • Policy and Programme Managers — need practical ways to design services and interventions around stakeholder needs

Skills and tools covered

Problem framingRoot-cause analysisCreative ideationSolution prototypingBusiness case developmentPilot planning

Tools and standards

Design Thinking, Jobs to Be Done, Business Model Canvas, ADKAR

How the course runs

Training methodology

The course uses short instructor briefings followed by case analysis, group exercises, simulations, peer review, and individual application planning. Participants frame a business challenge, collect and interpret evidence, map causes, generate concepts, select options, design tests, and construct a pilot case. Cases can reflect banking, public services, NGOs, customer operations, technology delivery, or corporate functions. Facilitated discussion focuses on decision quality, stakeholder alignment, evidence thresholds, and practical implementation choices.

Requirements and prerequisites

Participants should have experience working on business, service, process, product, customer, policy, or operational improvement assignments. They should be comfortable discussing a business challenge, interpreting basic performance information, and working with colleagues from different functions. Familiarity with project management, process mapping, customer research, or financial cases is useful but not required. No prior qualification in innovation, design, strategy, data analysis, or finance is required. Participants do not need specialist software or technical design skills.

A typical training day

08:30 – 10:30First session
10:30 – 10:45Refreshment break
10:45 – 12:30Second session
12:30 – 13:30Lunch and networking
13:30 – 15:00Third session
15:00 – 15:15Refreshment break
15:15 – 16:30Workshop and daily review

Live online deliveries follow the same structure in East Africa Time, with shorter screen blocks and longer breaks.

What the fee includes

  • Instruction by a practitioner facilitator
  • Full course workbook and materials
  • Exercise files, templates and case studies
  • Refreshments and lunch on classroom deliveries
  • Certificate of completion
  • Post-course application plan

Frequently asked questions

Participants should have experience of business, service, process, product, operational, or programme work. No previous training in innovation, design, strategy, finance, or data analysis is required.

Bring a current or recent business challenge that has unclear causes, competing stakeholder views, or several possible solutions. You can use it during application planning, although all core work can be completed through course cases.

It is designed for managers, product and service professionals, improvement specialists, project managers, analysts, and programme leads. It suits people who need to shape and test solutions rather than receive a predefined technical answer.

The course uses selected Design Thinking methods but extends beyond ideation into option selection, experimentation, investment reasoning, pilot governance, and change planning. It also uses process and root-cause tools where the problem may be operational rather than customer-facing.

The methods can be used for a service failure, customer journey issue, process bottleneck, product opportunity, policy intervention, or control weakness. Participants leave with templates and an application plan that can structure a live assignment.

Each training day runs from 08:30 to 16:30 and provides approximately 6.5 contact hours. The five days move from problem framing and research through diagnosis, ideation, testing, value cases, pilot planning, and application planning.

Questions about this course?

Ask about dates, fees, group bookings or running it for your team. Our training team replies by email.