PMGT5811 Chap.2 Assumptions, Inference and Counter-cases

Assumptions, Inference and Counter-cases

Define assumption

The course material gives this chapter a concrete anchor: Current tutorial questions require students to move beyond opinion by making reasoning paths discussable. That assumption anchor controls how inference is explained and how counterexample is tested in changed practice.

Assumptions, Inference and Counter-cases frames a decision through assumption, inference and counterexample.

The objective is to surface the propositions that connect project evidence to a recommendation and test them with a counter-case, so the chapter should be read as a chain from problem definition to evidence, option comparison and accountable action.

Start with assumption and name the decision owner, affected stakeholders and time horizon.

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

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

Apply counterexample when comparing options.

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

For the application — surface the propositions that connect project evidence to a recommendation and test them with a counter-case — finish with an actor, action, rationale and review trigger.

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

Trace inference

Build a decision ledger. Separate the current condition, the stakeholder affected, the evidence supporting assumption, the mechanism represented by inference and the criterion supplied by counterexample.

If a counterexample 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 under counterexample, who bears cost or risk, what capability implementation requires and what evidence would reveal failure.

This comparison is essential when students need to surface the propositions that connect project evidence to a recommendation and test them with a counter-case, because an attractive option is not defensible until its trade-offs are visible.

Rehearse the PMGT5811 assumption 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 inference move that needs more support. This protects the argument structure under a strict word or time limit.

A complete response should make the task visible before the detail: identify what must be decided, define the relevant terms, connect the evidence to inference, and use counterexample to test the result.

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

The controlling limit is specific: An assumption is not automatically false, but it must be visible enough to examine and monitor.

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

For revision, retrieve assumption, inference and counterexample without notes, explain their relationship aloud, then complete a changed version of the application: surface the propositions that connect project evidence to a recommendation and test them with a counter-case.

Record the first failed inference reasoning move and repair it before attempting another case.

What this chapter covers

• 01

  assumption

• 02

  inference

• 03

  counterexample

• 04

  Applying assumption

• 05

  Limits of inference and counterexample

AskSia practice: apply Assumptions, Inference and Counter-cases

Key terms

assumption

A proposition treated as given within reasoning even though it may require testing or evidence. Use this definition when the task is to surface the propositions that connect project evidence to a recommendation and test them with a counter-case.

inference

A reasoned move from evidence and premises toward a conclusion with a stated degree of support. Use this definition when the task is to surface the propositions that connect project evidence to a recommendation and test them with a counter-case.

counterexample

A case showing that a general claim, rule or explanation does not hold without qualification. Use this definition when the task is to surface the propositions that connect project evidence to a recommendation and test them with a counter-case.

Assumptions, Inference and Counter-cases FAQ

Assessment move

Reconstruct the relationship among assumption, inference and counterexample; complete the chapter application without notes; then test the result against this limit: An assumption is not automatically false, but it must be visible enough to examine and monitor.

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