ISYS90049 Chap.4 Stakeholders and Elicitation

Stakeholders and Elicitation

Stakeholders differ in decision power, operational knowledge, exposure to change and willingness to participate. A map should explain why each perspective matters and how engagement will occur. Influence is not the same as impact: low-authority users can carry the greatest implementation burden.

Attitude may change as costs or benefits become clearer, and an overlooked stakeholder can acquire veto power through regulation or dependency. The map is therefore a working hypothesis, not a permanent ranking. Executives support automation while service staff fear that exception handling will become invisible. Staff have limited formal authority but essential process knowledge and high change impact.

Record the rationale and evidence behind each placement. Avoid using stakeholder categories to silence groups; choose engagement methods that fit access, power and information needs. For stakeholder map, separate external context, internal capability and stakeholder experience instead of placing all observations in one framework box. Translate influence into a specific implication and rank it against the objective.

A solution option should answer that implication through a traceable capability change. Keep change impact in the decision log so later scope movement does not erase why one route was accepted or rejected. Prepare elicitation for stakeholder map by writing the decision and unknown first. Choose participants because they hold experience, authority or affected interest relevant to influence.

During analysis, retain disagreement and exceptions as data. Confirm the interpretation, then connect change impact to a measurable acceptance or value condition without presenting stakeholder preference as the whole business case. Elicitation starts with an objective, participant rationale and question or observation plan. During the session, the analyst probes examples, contradictions, exceptions and tacit work.

Afterwards, findings are documented, interpreted and confirmed with participants or other evidence. Interviews can surface experience; workshops expose disagreement; observation reveals workarounds; documents show formal rules but not always actual practice. Combining methods can triangulate a claim, provided their different limitations remain explicit.

A procedure says refunds require two approvals, but observation shows staff share credentials during peak periods. An interview explains the pressure; confirmation with process owners separates common practice from an isolated event. Distinguish quotation, observation and analyst inference in the notes. Ask neutral questions, record unresolved conflict and confirm meaning before converting a statement into a requirement.

A workshop or diagram concerning elicitation is an elicitation instrument, not self-validating evidence. Record whose knowledge it captures, where participants disagreed and what independent source could test triangulation. Convert findings into need or requirement statements only after confirmation.

When confirmation remains unresolved, assign further investigation and preserve the uncertainty in evaluation rather than averaging views into false consensus. Challenge the root-cause branch for elicitation with one prediction. Seek process data, observation or document evidence that distinguishes it from a rival involving triangulation. Frequency ranking can guide attention but cannot prove mechanism.

The conclusion about confirmation should state scope, confidence and the next evidence needed before intervention cost is committed.

What this chapter covers

• 01

  Stakeholder analysis predicts engagement needs

• 02

  Elicitation is prepared, conducted and confirmed

Worked application: Stakeholder analysis predicts engagement needs

Key terms

Stakeholder analysis

Stakeholder analysis predicts engagement needs — Stakeholders differ in decision power, operational knowledge, exposure to change and willingness to participate. A map should explain why each perspective matters and how engagement will occur. Influence is not the same as impact: low-authority users can carry the greatest implementation burden. Record the rationale and evidence behind each placement. Avoid using stakeholder categories to silence groups; choose engagement methods that fit access, power and information needs.

Elicitation cycle

Elicitation is prepared, conducted and confirmed — Elicitation starts with an objective, participant rationale and question or observation plan. During the session, the analyst probes examples, contradictions, exceptions and tacit work. Afterwards, findings are documented, interpreted and confirmed with participants or other evidence. Distinguish quotation, observation and analyst inference in the notes. Ask neutral questions, record unresolved conflict and confirm meaning before converting a statement into a requirement.

Stakeholders and Elicitation FAQ

Exam move

Build a traceability chain for Stakeholders and Elicitation. Keep source evidence, interpretation, need, decision, owner and value measure in separate fields. Begin with stakeholder map and reconstruct the causal or institutional route without copying the worked response. Change one feature of the case and decide whether influence still supports the same interpretation.

Write a credible rival account and identify the observation that would discriminate between them. Return to confirmation 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