Problem definition in Business Analysis: Define the Decision and Evidence

Problem definition becomes useful when the work improves requirements that produce measurable business change rather than merely producing a polished output. This Business Analysis lesson shows how to define the business outcome, scope and decision rights.

It is written for an analyst who must separate facts, assumptions and decision criteria for another reviewer. You will apply the method to Map a broken process, challenge one assumption deliberately, and retain process evidence, traceability, options and outcome measures so the result can be checked without private explanation.

Boundary: the exercise is not complete if it hides documentation volume replacing shared understanding and acceptance. Use Diagram tool only after writing the expected normal result, the unsafe result and the condition that should stop the work.

What a defensible Problem definition result must prove

Your goal is to define the business outcome, scope and decision rights. Work with the Map a broken process scenario, write the expected result before using Diagram tool, and preserve a normal case plus one deliberately difficult case. The lesson is complete only when the evidence supports requirements that produce measurable business change and makes the remaining uncertainty visible.

Model Problem definition around requirements that produce measurable business change

In this lesson, problem definition is the part of business analysis that helps you define the business outcome, scope and decision rights. Treat it as a decision with inputs, boundaries and a rejection condition. The professional standard is not familiarity with terminology; it is a result another person can inspect using process evidence, traceability, options and outcome measures.

For Problem definition, use Diagram tool as the primary practice surface and Spreadsheet only for its distinct supporting role. Write the expected Business Analysis behavior first, record which evidence each tool produces, and remove any tool that adds no testable value. This avoids mistaking a larger tool stack for a stronger Problem definition result.

The boundary for this Problem definition exercise is a decision memo built from explicit assumptions. Inside that boundary, separate observations, estimates and stakeholder preferences. Outside it, stop and obtain permission, better data or a qualified review. This distinction is part of the skill, not an administrative detail added after the work.

Inputs, decisions and evidence for Problem definition

Map a broken process: isolate the Problem definition decision

The project is intentionally narrow. You are testing problem definition, not claiming to finish all of Business Analysis in one sitting. Create a folder named business-analysis-01-problem-definition and keep the brief, sample input, output and review notes together.

1. Write the Business Analysis brief. Name the intended user of “Map a broken process”, the decision or task being improved, and one result that would be unacceptable.
2. Prepare the Problem definition sample. Create three ordinary inputs and one edge case. Remove personal information, credentials and any material you cannot lawfully use.
3. Predict before running Problem definition. Write what you expect Diagram tool or the manual procedure to produce for every Map a broken process sample, including the edge case.
4. Run the smallest Business Analysis version. Capture Problem definition commands, settings or calculation steps; do not silently repair the input after seeing the result.
5. Compare Map a broken process evidence. Mark each Problem definition expected-versus-actual difference as an input, method, implementation or acceptance-criteria failure.
6. Correct one Problem definition cause. Change only the relevant factor, repeat the same check and preserve both outcomes in the Problem definition review log.

Automate one repeatable Problem definition evidence check

The following programs validate a compact completion record for this exact Business Analysis / Problem definition exercise. Choose one tab and run it locally. The implementations use only each language’s standard runtime; they do not send project data to an external service.

const evidence = {
  skill: "Business Analysis",
  lesson: "Problem definition",
  problem: "Map a broken process: apply problem definition to one defined outcome",
  normalCase: "saved normal-case input and output",
  failureCase: "recorded one failed or invalid case",
  correction: "explained the change and retest result",
  limitation: "stated one condition where the result is not reliable"
};

const required = ["problem", "normalCase", "failureCase", "correction", "limitation"];
const missing = required.filter((field) => !evidence[field]?.trim());

if (missing.length > 0) {
  console.error(`NEEDS WORK - missing: ${missing.join(", ")}`);
  process.exitCode = 1;
} else {
  console.log(`${evidence.skill} / ${evidence.lesson}: READY`);
}

evidence = {
    "skill": "Business Analysis",
    "lesson": "Problem definition",
    "problem": "Map a broken process: apply problem definition to one defined outcome",
    "normal_case": "saved normal-case input and output",
    "failure_case": "recorded one failed or invalid case",
    "correction": "explained the change and retest result",
    "limitation": "stated one condition where the result is not reliable",
}

required = ("problem", "normal_case", "failure_case", "correction", "limitation")
missing = [field for field in required if not evidence.get(field, "").strip()]

if missing:
    raise SystemExit(f"NEEDS WORK - missing: {', '.join(missing)}")

print(f"{evidence['skill']} / {evidence['lesson']}: READY")

<?php
$evidence = [
    "skill" => "Business Analysis",
    "lesson" => "Problem definition",
    "problem" => "Map a broken process: apply problem definition to one defined outcome",
    "normalCase" => "saved normal-case input and output",
    "failureCase" => "recorded one failed or invalid case",
    "correction" => "explained the change and retest result",
    "limitation" => "stated one condition where the result is not reliable"
];

$required = ["problem", "normalCase", "failureCase", "correction", "limitation"];
$missing = array_values(array_filter(
    $required,
    fn(string $field): bool => trim($evidence[$field] ?? "") === ""
));

if ($missing) {
    fwrite(STDERR, "NEEDS WORK - missing: " . implode(", ", $missing) . PHP_EOL);
    exit(1);
}

echo $evidence["skill"] . " / " . $evidence["lesson"] . ": READY" . PHP_EOL;

import java.util.LinkedHashMap;
import java.util.List;
import java.util.Map;

public class Main {
    public static void main(String[] args) {
        Map<String, String> evidence = new LinkedHashMap<>();
        evidence.put("skill", "Business Analysis");
        evidence.put("lesson", "Problem definition");
        evidence.put("problem", "Map a broken process: apply problem definition to one defined outcome");
        evidence.put("normalCase", "saved normal-case input and output");
        evidence.put("failureCase", "recorded one failed or invalid case");
        evidence.put("correction", "explained the change and retest result");
        evidence.put("limitation", "stated one condition where the result is not reliable");

        List<String> required = List.of(
            "problem", "normalCase", "failureCase", "correction", "limitation"
        );
        List<String> missing = required.stream()
            .filter(field -> evidence.getOrDefault(field, "").isBlank())
            .toList();

        if (!missing.isEmpty()) {
            System.err.println("NEEDS WORK - missing: " + String.join(", ", missing));
            System.exit(1);
        }
        System.out.println(evidence.get("skill") + " / " + evidence.get("lesson") + ": READY");
    }
}

using System;
using System.Collections.Generic;
using System.Linq;

var evidence = new Dictionary<string, string>
{
    ["skill"] = "Business Analysis",
    ["lesson"] = "Problem definition",
    ["problem"] = "Map a broken process: apply problem definition to one defined outcome",
    ["normalCase"] = "saved normal-case input and output",
    ["failureCase"] = "recorded one failed or invalid case",
    ["correction"] = "explained the change and retest result",
    ["limitation"] = "stated one condition where the result is not reliable"
};

string[] required = { "problem", "normalCase", "failureCase", "correction", "limitation" };
var missing = required.Where(field =>
    !evidence.TryGetValue(field, out var value) || string.IsNullOrWhiteSpace(value)
).ToArray();

if (missing.Length > 0)
{
    Console.Error.WriteLine($"NEEDS WORK - missing: {string.Join(", ", missing)}");
    Environment.ExitCode = 1;
}
else
{
    Console.WriteLine($"{evidence["skill"]} / {evidence["lesson"]}: READY");
}

Every tab implements the same evidence quality gate. Choose the language you can run locally, replace the example strings with links or notes from your real exercise, then deliberately empty one required field to confirm that the failure path works. The programs use only standard libraries. For this lesson, replace the placeholder statements with real evidence from “Map a broken process”. A passing message confirms that required notes exist; it does not prove those notes are accurate, lawful or professionally reviewed. Label this record specifically as Problem definition evidence.

Stress-test Problem definition against documentation volume replacing shared understanding and acceptance

Start with the risk “Writing a solution before understanding the problem”. Reproduce a harmless version inside a decision memo built from explicit assumptions. Record the visible symptom, the underlying cause and why an inexperienced reviewer might accept the result. Then apply one correction and run the original case again. Treat the symptom as a Problem definition case, not a generic Business Analysis failure.

Rebuild the Problem definition decision without the walkthrough

Answer these questions without looking back: What problem does Problem definition solve inside Business Analysis? Which assumption has the greatest effect on “Map a broken process”? What evidence would falsify your conclusion? Which boundary protects against false precision, undisclosed assumptions and personalised regulated advice? What would you learn next before using this work for a real customer?

Package Problem definition evidence for an independent reviewer

Publish a concise case study only when you have permission to share every artefact. Describe the initial state, your Problem definition decision, the normal and failure cases, the correction and the remaining limitation. Attach sources, formulas, alternatives, risks and follow-up measures. Remove secrets and personal data, and never present a practice project as paid client experience.

A credible reviewer of your Problem definition case study should see why the Business Analysis approach was chosen, how “Map a broken process” was checked, and what would make you reject the result. That evidence is more useful than an unsupported expert label or income promise.

Verify Problem definition and continue to Stakeholders

Verify terminology and current capabilities in IIBA Business Analysis Resources. The official resource is a starting point, not permission to copy its wording or structure. Record the page and review date beside any fast-changing Business Analysis claim. For Problem definition, also record the exact section or version that supports the implementation decision.

Created and reviewed by Muhammad Azhar. This free lesson teaches a verifiable learning process and does not guarantee employment, freelance income, certification or professional competence. The reviewed subject on this page is Problem definition.