ISYS90049 Chap.1 Business Need, Change and Value

Business Need, Change and Value

Business analysis begins with a problem or opportunity expressed through stakeholder outcomes, performance evidence and context. A proposed application may eventually be appropriate, but naming it as the need hides assumptions about why the current state fails. The analyst first describes what is happening, who experiences it and why change matters.

A slow transaction, repeated complaint or manual workaround is observable evidence; it may arise from policy, information, skill, process or technology. Treating the symptom as the cause can produce a technically elegant intervention that leaves the operating constraint intact. A retailer asks for a mobile app because customers abandon orders.

Interviews reveal that stock information changes after checkout and refunds take days. The app request is a candidate solution, while unreliable inventory and recovery are the needs to analyse. Write the need without a product noun, then list evidence, affected actors and desired outcome. Preserve alternative causal accounts until elicitation and process evidence discriminate among them.

An analysis trace for business need begins with an observed current outcome, an affected stakeholder and a decision that evidence must support. Keep outcome gap separate from the analyst's interpretation and from any favoured solution. Governance should identify who confirms the finding, who decides and where the version is stored.

Use solution bias to record the assumption or boundary that would force the scope or recommendation to be revised. A solution can combine process, people, information, policy and technology changes. Value appears only when those elements create an outcome a stakeholder or organisation recognises. Delivery is therefore an input to value, not proof that value has been achieved.

A broad promise such as efficiency needs a baseline, unit, observation period and accountable owner. Cost, risk, adoption and displaced work can offset a nominal benefit. The analysis should show when the value signal will become visible and who can act if it does not. An automated approval tool launches on schedule but managers continue using email because exception rules are unclear.

Software delivery is complete; cycle-time value is absent because behaviour and governance did not change. Link each solution component to a capability change, expected behaviour and metric. Do not add unrelated benefits after selection merely to make the preferred option appear stronger. Business-analysis evidence becomes valuable when solution changes a choice.

State the source, timing and confidence of the observation, then connect it through business value to a need, risk, capability or benefit. Compare an alternative causal account before defining a requirement. The treatment of benefit measure should show how the result will be validated with stakeholders and which owner can act if expected value does not appear.

Run a counterfactual for solution in which the preferred technology is unavailable. If the business need and value logic disappear, the analysis was solution-led. Digitisation converts analogue information into digital form; digitalisation uses digital tools to alter a process; digital transformation changes how the organisation creates value, coordinates work or relates to stakeholders.

The labels imply different scope, governance and evidence requirements. A new interface can improve one interaction without changing the operating model. Conversely, an apparently small data capability can reshape decisions across several units. Classify the change from its organisational consequences rather than the novelty of the technology. A university scans paper requests into PDF but preserves every approval handoff.

Information is digitised, yet decision rights and process time are unchanged. A later shared workflow with redesigned authority may constitute broader transformation. State what changes in capability, process, role and value logic. Avoid using digital as a synonym for beneficial or transformation as a marketing adjective.

For digital transformation, separate external context, internal capability and stakeholder experience instead of placing all observations in one framework box. Translate operating model into a specific implication and rank it against the objective. A solution option should answer that implication through a traceable capability change.

Keep change scope in the decision log so later scope movement does not erase why one route was accepted or rejected. Prepare elicitation for digital transformation by writing the decision and unknown first. Choose participants because they hold experience, authority or affected interest relevant to operating model.

A business analyst frames questions, gathers and models evidence, surfaces assumptions, connects stakeholders and evaluates options. The role can influence decisions strongly without replacing the sponsor's authority or the expertise of operational participants. Neutral facilitation does not mean pretending all claims have equal support. Useful analysis is iterative, context-sensitive and value-oriented.

It communicates at the audience's level, seeks multiple perspectives and maintains traceability. The analyst also discloses constraints and conflicts rather than smoothing disagreement into artificial consensus. A sponsor asks the analyst to remove a frontline objection from the report because it complicates the preferred option.

The analyst documents the evidence, tests its relevance and escalates the decision through agreed governance instead of silently editing it away. Record who recommends, who decides and who supplies evidence. Separate facilitation notes from validated findings, and retain dissent when it changes risk or feasibility. A workshop or diagram concerning analyst role is an elicitation instrument, not self-validating evidence.

Record whose knowledge it captures, where participants disagreed and what independent source could test decision rights. Convert findings into need or requirement statements only after confirmation. When traceability remains unresolved, assign further investigation and preserve the uncertainty in evaluation rather than averaging views into false consensus. Challenge the root-cause branch for analyst role with one prediction.

Seek process data, observation or document evidence that distinguishes it from a rival involving decision rights.

What this chapter covers

• 01

  A business need names an outcome gap

• 02

  A solution is a change package, not the value itself

• 03

  Digital transformation changes an operating model

• 04

  The analyst creates alignment without owning every decision

Worked application: A business need names an outcome gap

Key terms

Business need

A business need names an outcome gap — Business analysis begins with a problem or opportunity expressed through stakeholder outcomes, performance evidence and context. A proposed application may eventually be appropriate, but naming it as the need hides assumptions about why the current state fails. The analyst first describes what is happening, who experiences it and why change matters. Write the need without a product noun, then list evidence, affected actors and desired outcome. Preserve alternative causal accounts until elicitation and process evidence discriminate among them.

Solution-value distinction

A solution is a change package, not the value itself — A solution can combine process, people, information, policy and technology changes. Value appears only when those elements create an outcome a stakeholder or organisation recognises. Delivery is therefore an input to value, not proof that value has been achieved. Link each solution component to a capability change, expected behaviour and metric. Do not add unrelated benefits after selection merely to make the preferred option appear stronger.

Digital operating-model transformation

Digital transformation changes an operating model — Digitisation converts analogue information into digital form; digitalisation uses digital tools to alter a process; digital transformation changes how the organisation creates value, coordinates work or relates to stakeholders. The labels imply different scope, governance and evidence requirements. State what changes in capability, process, role and value logic. Avoid using digital as a synonym for beneficial or transformation as a marketing adjective.

Business Need, Change and Value FAQ

Exam move

Build a traceability chain for Business Need, Change and Value. Keep source evidence, interpretation, need, decision, owner and value measure in separate fields. Begin with business need and reconstruct the causal or institutional route without copying the worked response. Change one feature of the case and decide whether outcome gap still supports the same interpretation.

Write a credible rival account and identify the observation that would discriminate between them. Return to traceability and state the boundary it places on transfer to another setting. Check that each recommendation names a decision, responsible actor and observable consequence. Use the chapter questions for retrieval, then consult the detailed prose only to correct the mechanism or evidence limit.

ISYS90026 Information Systems Analysis and Design · ISYS90050 IT Project and Change Management · MGMT90141 Business Analysis and Decision Making