ENG5100 Chap.5 Professional Communication, Business Cases and Co-creation

Professional Communication, Business Cases and Co-creation

Professional communication is designed for a decision. Identify the audience's authority, prior knowledge, time and consequence of misunderstanding. Lead with the decision and its basis, then make evidence and uncertainty inspectable.

Detail belongs where the audience can verify it; hiding assumptions in an appendix no one can find is not transparency.

A business case compares options, including continuation or minimum intervention. It links strategic fit, stakeholder value, benefits, costs, risks, capability, procurement, implementation and review. A financial total is one dimension.

If benefit depends on adoption, reliability or avoided harm, those causal assumptions must be visible and tested.

Benefits should have an owner, baseline, measure and realisation path. Avoided cost is not cash received, and productivity released is not automatically removed from budget. Double counting occurs when one operational improvement appears as both labour saving and extra output without capacity constraints.

Trace each benefit to an observable change.

Uncertainty should be structured through ranges, scenarios, sensitivity and decision thresholds. A base case is not the truth. Identify the assumptions with the greatest effect and the evidence available before commitment.

Where uncertainty is reducible, stage the decision or run an experiment; where it is irreducible, choose robustness and contingency.

Co-creation gives affected parties structured influence over problem definition, option design, testing or delivery. It is not asking for feedback after a decision is complete. Participation depth should match impact and knowledge.

Document how input changed the design or why it was not adopted. The accountable owner still makes and explains the decision.

Written communication uses claim, evidence, implication and action. Oral communication adds pace, signposting and response to questions. Visuals should make comparison or mechanism easier to inspect, not decorate.

A risk heat map without underlying estimates or controls can create false certainty; show the decision it supports and limitations.

Worked business case: projected savings assume 90% adoption in six months, but no workflow test has occurred. Treat adoption as a critical uncertainty. Use staged funding with a pilot, define leading indicators, measure transition workload and include a lower-adoption scenario.

The case becomes a controlled commitment rather than an optimistic forecast.

Relationship building includes listening, follow-through, conflict and boundary management. Trust grows when commitments are reliable and bad news arrives early. It does not require agreement or concealment.

Declare conflicts of interest and distinguish advocacy for an option from stewardship of the decision process.

For the team project and oral presentation, maintain a source and assumption ledger. Assign slide ownership but use one narrative: decision, why now, options, evidence, recommendation, risk and next review. Prepare answers to the strongest objection, not only friendly questions.

Reflection should identify which communication choice changed understanding or action.

Business-case governance continues after approval. Baselines can drift, benefits can be reassigned and project teams can dissolve before realisation. Establish an owner who remains accountable for the outcome, a method for measuring attribution and a post-implementation review that can stop further spend.

Separate forecast accuracy from decision quality: a reasonable decision can face an adverse surprise, while a lucky outcome can follow a weak process.

Communication ethics includes material omission, not only factual correctness. A technically true statement can mislead if it suppresses a critical comparator, uncertainty or affected group.

Present the strongest counterargument, explain why the recommendation remains preferable and state what would reverse it. This earns trust because the audience sees the decision boundary rather than polished certainty.

A decision brief should allow a sceptical reader to reconstruct sources, assumptions, rejected options and the authority behind the final commitment.

What this chapter covers

• 01

  business case

• 02

  co-creation

• 03

  decision trace

• 04

  build a traceable recommendation whose evidence, economics, audience and stakeholder contribution can be audited

• 05

  Polished slides and positive engagement do not replace option comparison, evidence quality or accountable decision rights.

Stress-test an adoption assumption

Key terms

business case

A decision document comparing options through benefits, costs, risks, capability, implementation and strategic fit.

co-creation

Structured participation in which affected parties contribute to defining, testing or delivering value.

decision trace

A record linking assumptions, evidence, options, trade-offs, authority and the reason for a choice.

Professional Communication, Business Cases and Co-creation FAQ

Assessment move

Reconstruct one decision trace, challenge its strongest assumption, apply a changed stakeholder or risk condition and state the review trigger.

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