BUSM2577 Chap.2 Discovering Business Problems

Discovering Business Problems

Discovering Business Problems frames a decision through symptom versus problem, external and internal evidence and stakeholder observation.

The objective is to turn an initial complaint into an investigable problem statement, so the chapter should be read as a chain from problem definition to evidence, option comparison and accountable action.

Start with symptom versus problem and name the decision owner, affected stakeholders and time horizon.

The same fact can matter differently across those positions, so the opening frame determines which evidence is relevant.

Use external and internal evidence to explain how the present condition produces an opportunity, cost or risk. A strong mechanism states what changes, for whom and through which organisational, market or institutional process.

Apply stakeholder observation when comparing options.

Keep criteria distinct, test trade-offs and ask which assumption drives the recommendation. A score or matrix only helps when its criteria are justified by the case.

For the application — turn an initial complaint into an investigable problem statement — finish with an actor, action, rationale and review trigger.

This turns analysis into a recommendation while keeping the decision open to new evidence.

Build a decision ledger for Discovering Business Problems. Separate the current condition, the stakeholder affected, the evidence supporting symptom versus problem, the mechanism represented by external and internal evidence and the criterion supplied by stakeholder observation.

If a recommendation cannot point back to one of those entries, it is probably preference dressed as analysis rather than a consequence of the case.

Compare at least two feasible options against the same criteria. State who benefits, who bears cost or risk, what capability implementation requires and what evidence would reveal failure.

This comparison is essential when students need to turn an initial complaint into an investigable problem statement, because an attractive option is not yet a defensible choice until its trade-offs are made visible.

Rehearse the BUSM2577 response as a short briefing: one sentence for the decision, two for the evidence and mechanism, one for the alternative and one for the qualified recommendation.

Then expand only the move that needs more support.

This protects the argument structure when a report, presentation or timed case imposes a strict word or time limit.

A complete Discovering Business Problems response should make the task visible before the detail: identify what must be decided, define the relevant terms, connect the evidence to external and internal evidence, and use stakeholder observation to test the result.

The final sentence should answer the question actually asked rather than merely repeat the topic.

The controlling limit is specific: Early evidence narrows a problem but does not prove a single root cause.

Keep that limit beside the worked example, because it separates a careful BUSM2577 answer from one that sounds confident but claims more than the task or evidence supports.

For revision, retrieve symptom versus problem, external and internal evidence and stakeholder observation without notes, explain their relationship aloud, then complete a changed version of the application: turn an initial complaint into an investigable problem statement.

Record the first point at which your reasoning fails and repair that move before attempting another case.

What this chapter covers

• 01

  symptom versus problem

• 02

  external and internal evidence

• 03

  stakeholder observation

• 04

  Applying symptom versus problem

• 05

  Limits of external and internal evidence and stakeholder observation

Worked example: Discovering Business Problems

Key terms

PESTLE analysis and stakeholder mapping

PESTLE scans political, economic, social, technological, legal and environmental influences, while stakeholder mapping identifies affected actors and compares their interest, influence and relationship to the problem. In this chapter, use the concept when you turn an initial complaint into an investigable problem statement.

'How Might We' problem-definition question

A How Might We question reframes evidence about a user or system into an open, actionable design challenge without prescribing the solution in advance. In this chapter, use the concept when you turn an initial complaint into an investigable problem statement.

Cognitive bias in design thinking (bandwagon effect, confirmation bias, IKEA effect)

Cognitive bias is a systematic distortion in judgement; the bandwagon effect favours popular ideas, confirmation bias seeks supporting evidence, and the IKEA effect overvalues solutions people helped create. In this chapter, use the concept when you turn an initial complaint into an investigable problem statement.

Discovering Business Problems FAQ

Assessment move

Reconstruct the relationship among symptom versus problem, external and internal evidence and stakeholder observation; complete the chapter application without notes; then test the result against this limit: Early evidence narrows a problem but does not prove a single root cause.

Working through Discovering Business Problems in BUSM2577? Sia is AskSia’s AI Management tutor — ask any BUSM2577 Discovering Business Problems question and get a clear, step-by-step explanation grounded in how BUSM2577 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.