Component 2: Decision-making models — Eduqas A-Level Business
Test yourself on Component 2: Decision-making models with EDUQAS A-Level practice questions.
7 days Premium · Then free forever · No card, no charge
Component 2: Decision-making models explained
Decisions sit on a ladder defined by time horizon, resource commitment and how easily they can be undone.
Read the full explanation
At the top, long range choices about which markets to serve and how to compete are taken by directors, commit large sums and are costly to reverse, which is why Ansoff or Porter's generic strategies are the usual tools there. In the middle sit medium term choices about how to deliver that direction, such as which promotional mix or supplier to use, taken by middle managers over months. At the base are routine daily choices about rotas, reordering and scheduling, delegated to supervisors and easily corrected. Tesco choosing to enter banking is one level; setting this week's staffing is another, and confusing the two wastes senior time.
Explain the importance of decision-making to a business
Every choice allocates scarce resources, so every choice has an opportunity cost, the value of the next best use of the money, capacity or management time given up. Sound choices move the firm towards its stated objectives, whether growth, profit or survival, and show up in measurable outcomes such as return on capital employed, market share and labour turnover. Poor ones destroy value quickly: Gerald Ratner's joke about his own products wiped hundreds of millions from the company's worth and cost him the business. Speed matters too, since a slow but thorough process can miss the window while a fast one raises the risk of acting on thin information, and the quality of the data available sets a ceiling on the quality of the outcome.
Understand that decision-making tools can be scientific or intuitive
One approach follows an evidence trail: set the objective, gather data, weigh the options with a technique such as investment appraisal, break even analysis, market research or a decision tree, choose, implement and then review the outcome against the target. The other rests on experience, pattern recognition and gut feel, and is fast, free and often the only option when a market is brand new or a crisis leaves no time. The structured route is defensible to shareholders and repeatable, but it is slow, costly and only as good as its inputs, and it can smother creative leaps. The intuitive route is prone to bias and hard to justify at a board meeting, so most firms use judgement to frame the question and analysis to test the answer.
Explain the nature and purpose of decision tree analysis commenting on the benefits and limitations of the technique
This is a diagram that maps options against uncertain outcomes so that risky choices can be compared in money terms. Squares mark points where the managers choose, circles mark points where chance decides, and the probabilities leaving any circle must total one. Each outcome carries an estimated value in pounds, and the tree is worked backwards from right to left: expected value equals the sum of each probability multiplied by its outcome value, and the net gain of an option equals that expected value minus the cost of taking it. The option with the higher net gain wins on the numbers. Its strength is that it forces assumptions into the open and shows the downside as well as the upside; its weakness is that every input is a forecast.
Construct decision trees, interpret and evaluate the results
A decision tree maps options as squares and uncertain outcomes as circles, and its whole value is that it forces a manager to put a number on risk before committing cash. At each chance node the expected value is the sum of each probability multiplied by its payoff in pounds, and the net gain of an option is that expected value minus the cost written on its branch. Work from right to left, carry the winning figure back to the square and choose the branch with the highest net gain. A confectionery firm weighing a new product launch against extending an existing line would use one exactly this way. The weakness is that the probabilities are estimates, often made by the manager who already favours one option, and everything that is not money is left off the diagram.
Explain the nature and purpose of critical path analysis (CPA), commenting on the benefits and limitations of the technique
The technique breaks a project into activities, each with a duration and a list of what must finish before it can start, and draws them as a network so the shortest possible completion time falls out of the arithmetic rather than out of a guess. Each node carries an earliest start time worked forward and a latest finish time worked back, and where the two figures are equal the activity has no float, so any delay to it delays the whole project. Managers use it to order materials just in time, to place supervision where slippage is expensive and to defend a deadline written into a penalty clause. It is blind to cost and to quality, the durations are estimates, and a network drawn at the start of a long build is out of date within weeks.
Complete CPA diagrams, interpret and evaluate the results
Given a table of activities, durations and immediate predecessors, the network is built left to right with numbered nodes. The forward pass fills in earliest start times, and where two arrows meet you take the highest figure, because nothing can begin until every preceding activity is finished. The backward pass fills in latest finish times from the final node, and where paths converge you take the lowest figure. Total float for an activity is its latest finish time minus its duration minus its earliest start time, measured in days or weeks. Activities with zero float form the critical path, and the earliest start time at the final node is the minimum project duration. The higher marks sit in interpretation: which delay would cost this firm money, and which activity could quietly slip without moving the finishing date.
Explain the nature and purpose of cost benefit analysis (CBA), commenting on the benefits and limitations of the technique
This technique puts a money value on every consequence of a project, not just the ones that reach the accounts, so private costs and revenues sit alongside external effects such as noise, congestion, pollution and time saved by the public. Future flows are discounted to present value, and the scheme is judged worthwhile when benefits exceed costs. It is the standard tool for public investment, and the Department for Transport used it on the High Speed Two rail scheme, where the benefit to cost ratio was argued over for a decade. Private firms reach for it when a proposal has a large social footprint, such as a distribution depot needing planning consent. Its weakness is that the values placed on intangibles are estimated by people with an interest in the answer, and shifting the discount rate can flip the verdict.
Carry out cost benefit analysis, interpret and evaluate the results
The arithmetic is a tally in pounds. Add every private and external cost, add every private and external benefit, then subtract to give net social benefit; dividing total benefits by total costs gives the ratio, where anything above one says the scheme is worth doing and anything below one says it is not. Where flows run over several years each is discounted, so a benefit of one million pounds arriving in year ten counts for far less than the same sum today. A ratio close to one is fragile, because a modest rise in construction cost or a slightly higher discount rate turns a positive verdict negative. Interpretation marks come from saying whose costs and whose benefits these are, since a scheme with a healthy national ratio can still be a disaster for the residents living beside it.
Evaluate the advantages and disadvantages of using decision trees, CPA and CBA for business decision-making
Each technique answers a different question, and saying so is the frame that earns the evaluation marks. One ranks options where the outcome is uncertain, one schedules activities where timing is the problem, and one weighs effects that fall outside the accounts. What all three share is that they convert judgement into a single number, and that number is only as good as what was fed in, since probabilities, activity durations and money values placed on intangibles are estimates dressed as data. Their genuine strength is that they make assumptions visible and arguable, and they discipline a board that would otherwise decide on instinct. Their genuine weakness is false precision, the time and cost of producing them, and silence on morale, reputation and ethics. The defensible verdict is that they inform a decision rather than make it.
Explain the key role played by information technology in business decision-making
Technology touches every stage of a decision: capturing raw data, storing and sorting it, modelling the options and then communicating the choice. Point of sale systems and loyalty schemes hand a supermarket millions of transactions, so stock can be reordered automatically and promotions aimed at the shoppers who respond to them rather than at everybody. Spreadsheets let a finance team rerun a break even chart or a discounted cash flow in seconds, which makes sensitivity testing routine rather than a luxury. Dashboards push key figures to managers daily, shortening the feedback loop and making it safe to delegate decisions down the hierarchy. The costs are real: systems and training are expensive, personal data must be handled lawfully, poor quality data produces confident nonsense, and a manager buried in reports can decide more slowly than one with a single good figure.
Your focus
- Explain the types of decisions a business makes including strategic, tactical and operational
- Explain the importance of decision-making to a business
- Understand that decision-making tools can be scientific or intuitive
Show all 11 objectives
- Explain the nature and purpose of decision tree analysis commenting on the benefits and limitations of the technique
- Construct decision trees, interpret and evaluate the results
- Explain the nature and purpose of critical path analysis (CPA), commenting on the benefits and limitations of the technique
- Complete CPA diagrams, interpret and evaluate the results
- Explain the nature and purpose of cost benefit analysis (CBA), commenting on the benefits and limitations of the technique
- Carry out cost benefit analysis, interpret and evaluate the results
- Evaluate the advantages and disadvantages of using decision trees, CPA and CBA for business decision-making
- Explain the key role played by information technology in business decision-making
Component 2: Decision-making models exam tips
Marking Points
- Classifies by time horizon, level in the hierarchy, resource commitment and reversibility rather than by topic area
- Gives a correctly matched example at each level for the business in the case
- Links the top level to a strategy model such as Ansoff's matrix or Porter's generic strategies
- Explains why delegation of the routine level frees senior managers and motivates staff, referring to Herzberg or Maslow on responsibility
- Notes that the boundaries blur, since a run of poor routine choices can wreck a sound long term plan
- Explains opportunity cost as the benefit of the next best alternative forgone whenever resources are committed
- Connects decision quality to the achievement of stated corporate objectives and to measurable results such as profit, market share or return on capital employed
- Recognises the trade off between speed of decision and the amount and reliability of information gathered
- Uses a real consequence, such as the Ratners collapse or a product recall, to show the cost of getting it wrong
- Identifies risk and uncertainty as the reason decisions need tools, contingency plans and review
- Sets out the stages of a structured process, from objective setting through data gathering and analysis to implementation and review
- Names at least one analytical technique, such as net present value in pounds, payback in years, break even output in units or decision tree expected values
- Explains when experience based judgement is appropriate, for example under time pressure, in a new market or where no reliable data exist
- Evaluates each approach on cost, speed, reliability and accountability rather than simply labelling one as better
- Concludes that the two are complementary, with judgement framing the problem and analysis testing the options
- Identifies squares as decision nodes, circles as chance nodes, and states that probabilities from one chance node sum to one
- Calculates expected value as the sum of probability multiplied by outcome value, then subtracts the cost of the decision to give net gain in pounds
- Works from right to left and selects the branch with the highest net gain, showing the rejected branch struck through
- Gives benefits: it quantifies risk, forces explicit assumptions, compares all options on one basis and suits repeated decisions where probabilities are reliable
- Gives limitations: probabilities and values are estimates, qualitative factors such as morale and reputation are excluded, the tree is static and the person drawing it can bias it
- Credit for correct structure: squares for decision points, circles for chance nodes, probabilities on each branch summing to one, and payoffs written at the far right.
- Credit for the expected value worked properly, each probability multiplied by its payoff and the products summed at the chance node, then the cost of that branch deducted to give net gain in pounds.
- Credit for rolling back from right to left and stating the chosen option with its net gain figure quoted from the working.
- Evaluation credit for questioning where the probabilities came from, how reliable the payoffs are, and which qualitative factors the diagram cannot show.
- Credit for a definition tied to a use: a network of dependent activities that identifies the minimum project duration and the activities that cannot be allowed to slip.
- Credit for float explained as latest finish time minus duration minus earliest start time, with zero float identifying the critical path.
- Applied benefits: just in time delivery of materials, better cash flow timing, resources concentrated where delay is costly, and a clear basis for telling a customer when the job will be done.
- Limitations for evaluation: durations are forecasts, the network says nothing about cost or quality, it must be redrawn as conditions change, and very large projects become unreadable.
- Credit for a correctly drawn network: every activity labelled with its duration, nodes numbered, dependencies respected and no activity left dangling.
- Credit for the forward pass taking the highest incoming figure and the backward pass the lowest, with the two figures agreeing at the final node.
- Credit for float calculated with the formula and expressed in time units, and for naming the critical path as a sequence of activity letters.
- Interpretation credit for saying what a stated delay does to the completion date and what that means for the business, such as a missed contract deadline or extra labour cost.
- Credit for a definition that separates it from ordinary appraisal: external costs and benefits falling on third parties are valued and counted alongside the private ones.
- Credit for the method in sequence: identify all effects, place money values on them, discount future flows to present value, then compare, often as a benefit to cost ratio.
- Credit for purpose in a decision: it justifies a project where market prices do not capture the full effect, which is why planning authorities and government departments demand it.
- Limitation credit for subjective valuations of intangibles, sensitivity to the discount rate chosen, optimism bias in forecasts and very long time horizons.
- Credit for totalling costs and benefits separately and showing the subtraction, with the answer given in pounds and labelled as net social benefit.
- Credit for the benefit to cost ratio, correctly calculated as total benefits divided by total costs, with the decision rule stated: proceed above one.
- Credit for recognising discounting, so that sums arriving in later years are restated at present value before anything is compared.
- Evaluation credit for testing how robust the result is and for commenting on who gains and who loses, not only on whether the total is positive.
- Credit for distinguishing what each technique is actually for, rather than treating the three as interchangeable ways of doing the same job.
- Applied advantages: risk is quantified, the cost of delay is exposed, third party effects are brought into the argument, and a case can be put to a lender, a board or a planning committee.
- Applied disadvantages: results are only as sound as the estimates behind them, a diagram is static once drawn, qualitative factors are excluded, and the analysis itself costs time and money.
- Evaluation credit for a judgement made conditional on the quality of the data, the size and reversibility of the decision, and the time available before a choice must be made.
- Credit for linking technology to identifiable stages of the decision: data capture, storage and analysis, modelling of options, communication and then monitoring of the outcome.
- Applied credit for a named system doing a named job for the business, such as stock control triggering reorders or customer records driving a targeted offer.
- Credit for the consequence for decision-making itself: faster decisions, more evidence behind them, options tested before money is committed, and authority pushed further down the structure.
- Evaluation credit for the limits: capital and training costs, data protection obligations, the reliability of the data, information overload and the loss of experienced managerial judgement.
Examiner Tips
- 💡Use a quick three part structure with one worked example per level, since examiners reward correct classification in context
- 💡Watch for a case that describes a board meeting or a five year plan, as that wording signals the long range category
- 💡If asked to assess, argue about which level the firm's problem really sits at, because misdiagnosis is a strong evaluative line
- 💡Anchor the answer in the objectives stated in the case, because importance is always importance relative to a goal
- 💡Bring in one quantitative measure so the point is evidenced rather than asserted
- 💡In longer answers argue that the process matters as much as the choice, since a reviewable process improves the next decision too
- 💡Name a specific technique rather than saying the firm should use data, since the named tool is what earns the application mark
- 💡Use the reliability of the case's own data as your evaluative hinge, because weak forecasts weaken every calculation built on them
- 💡Watch for entrepreneurial cases, where the examiner usually expects you to defend experience based judgement rather than dismiss it
- 💡Show the expected value written on each circle and the net gain beside each option, because method marks are available even if the arithmetic slips
- 💡Round money answers sensibly and keep the units in pounds throughout, stating clearly which option the numbers favour
- 💡Save your evaluation for where the estimates came from, since arguing that the probabilities are guesses is the standard high level criticism
- 💡The probabilities and payoffs are printed in the case, so show probability, payoff and product for every branch: method marks survive an arithmetic slip only when the working is visible.
- 💡These questions almost always pair a calculation with a recommendation, and the judgement half carries at least as many marks as the arithmetic.
- 💡State the answer with a pound sign and say which branch it belongs to, then add one non financial factor that could still change the decision.
- 💡Expect a short explain worth a few marks followed by a longer question on whether this particular business should invest in the technique, so budget your writing accordingly.
- 💡Tie every benefit to the firm named in the case: a construction company facing liquidated damages values it far more than a small workshop doing repeat jobs.
- 💡Finish an evaluation with a condition rather than a verdict, for example that it is worth the effort only where activities genuinely depend on one another.
- 💡Draw the network even when the question asks only for float or for the critical path, because the diagram itself carries method marks.
- 💡Delay questions have two cases and markers reward both: a critical activity moves the end date by the full delay, a non critical one only matters once the delay exceeds its float.
- 💡Label your units every time, since a bare number with no days or weeks attached is worth less than the same number labelled.
- 💡The usual shape is a short explain followed by an evaluate on whether the organisation should rely on this technique, so keep most of your writing for the judgement.
- 💡One named scheme used in a single clause is worth more than a paragraph of general theory about externalities.
- 💡When you evaluate, attack a specific valuation or the discount rate rather than saying the figures might be wrong.
- 💡Every figure in the table belongs on one side or the other, so a number you have not used is usually a mark you have not earned.
- 💡Show the formula, then the substitution, then the answer with its unit, because that is the order the mark scheme follows.
- 💡End with a decision and one condition it depends on, such as the construction estimate holding, rather than a summary of what you calculated.
- 💡This is the extended answer on the paper, so plan before writing: one developed paragraph per technique, then a comparative judgement that ranks them for the business named.
- 💡Build a hierarchy in your conclusion by naming the decision the firm actually faces, since a construction contractor and a supermarket chain need different tools.
- 💡Counter yourself at least once, for example accepting that a tree quantifies risk before pointing out who supplied the probabilities.
- 💡The case study names the systems the business already runs, so quote those rather than inventing generic examples of technology.
- 💡An explain question wants chains of cause and effect, so push every point two steps: the system does this, which means the manager can now do that.
- 💡If the question invites judgement, weigh the cost of the system against the value of the decisions it improves, not against its purchase price alone.
Common Mistakes
- Deciding the category by how important the decision sounds instead of by time horizon and who takes it, so pricing gets called strategic in every case
- Giving definitions with no example drawn from the named business, which caps the answer at knowledge marks
- Assuming the levels are independent, when the middle and lower levels exist only to deliver the direction set at the top
- Writing that decisions are important because businesses have to make them, which is circular and scores nothing
- Ignoring opportunity cost, so a project is judged good simply because it is profitable rather than more profitable than the alternative
- Assuming more information always gives a better decision, forgetting the cost of research and the risk of paralysis while rivals act
- Assuming the numerical approach is automatically superior, when its outputs depend entirely on forecast data that may be little more than informed guesswork
- Treating instinct as laziness rather than as accumulated experience, which misses the entrepreneurs who succeed on judgement in untested markets
- Describing the stages of a decision process without applying any of them to the business or problem in the case
- Forgetting to subtract the cost of the decision, so the expected value is reported as the net gain and the wrong branch is chosen
- Adding rather than multiplying at a chance node, or letting the probabilities on one set of branches total something other than one
- Calculating correctly and then stopping, with no comment on how shaky the probability estimates are for a genuinely new product or market
- Adding the payoffs at a chance node instead of weighting each one by its probability, which inflates every branch and usually reverses the recommendation.
- Forgetting to subtract the cost written on the decision branch, so the option with the largest gross expected value wins even though it is the most expensive to pursue.
- Treating the expected value as money the business will actually receive, when it is a long run average that no single one off decision ever pays out.
- Stating that the critical path is the longest route through the network and stopping there, without explaining that the longest route is precisely what sets the shortest possible completion time.
- Describing float as spare time every activity enjoys, when activities on the critical path have none at all.
- Claiming the technique makes a project finish on time, when it only shows where a delay would matter and leaves the managing to managers.
- Taking the lowest earliest start time where two activities converge, which shortens the project on paper and makes every figure to the right of that node wrong.
- Reporting a positive float for an activity that lies on the critical path, when by definition its float is zero.
- Answering a delay question by saying the project is late, without checking whether the delayed activity had enough float to absorb it.
- Describing it as a list of advantages and disadvantages, with no money values attached and no discounting, which is not the technique at all.
- Counting only the costs and benefits falling on the firm, which makes the answer a description of ordinary investment appraisal.
- Asserting that the technique is objective because it produces numbers, when the hardest numbers in it are the ones somebody chose.
- Netting an external cost against a private benefit inside the working, so no total ever appears and the marker cannot see how the figure was reached.
- Reporting the ratio with a pound sign, or reporting the net social benefit as a ratio, which shows the two measures have been confused.
- Concluding that the scheme should go ahead because the benefits are large, without noticing that the costs are larger still.
- Listing textbook advantages and disadvantages of each technique with no reference to the business in the case, which is knowledge and earns nothing for evaluation.
- Claiming the techniques remove risk, when at best they measure it and organise what is already known.
- Concluding that all three are useful, which is not a judgement, instead of arguing which one matters most for this firm and this decision.
- Listing software and devices with no decision attached, so the answer reads as a description of technology rather than an analysis of how choices get made.
- Assuming that more data automatically produces better decisions, ignoring both data quality and the time it takes a manager to read it.
- Writing only about benefits and never about the cost, the training or the resistance from staff who must use the new system.