12. Solution Design and Business Case Evaluation

Introduction and Context

A logistics project does not create value merely because it identifies a problem. Value is created when the project team designs a feasible response, demonstrates that the response is economically and strategically justified, and provides decision-makers with sufficient evidence to approve implementation. Solution design and business case evaluation therefore form the bridge between diagnosis and action.

In earlier project stages, logistics professionals typically define the problem, establish objectives, collect evidence, analyse root causes, and identify performance gaps. At this stage, the central question changes from “What is wrong?” to “Which intervention should the organisation adopt, under what conditions, and with what expected return?” The answer may involve warehouse redesign, transport-network restructuring, inventory-policy changes, supplier-development programmes, digital visibility tools, automation, outsourcing, or a combination of interventions.

A sound decision cannot be based on purchase price alone. Logistics alternatives differ in service impact, implementation complexity, risk, flexibility, sustainability, capability requirements, and strategic fit. The least expensive option may create unacceptable service risk, while the most technologically advanced option may be unaffordable or organisationally premature. Business case evaluation provides a disciplined method for comparing these trade-offs.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the purpose and structure of solution design in logistics projects.

2. Generate realistic and sufficiently distinct solution alternatives.

3. Assess alternatives using feasibility analysis and multi-criteria decision methods.

4. Prepare cost-benefit, ROI, payback, and net present value calculations.

5. Incorporate risk, uncertainty, scenarios, and sensitivity into investment decisions.

6. Evaluate strategic, ethical, sustainability, and organisational alignment.

7. Construct and communicate a defensible logistics business case.

From Problem Diagnosis to Solution Architecture

Solution design translates a diagnosed performance gap into an operating intervention. It should begin with the project’s objectives and constraints rather than with a preferred technology or supplier. A useful solution statement specifies the required outcome, the process affected, the resources needed, the implementation horizon, and the measures by which success will be judged.

For example, “install a warehouse management system” is a narrow technology proposal. “Improve inventory accuracy from 94 per cent to at least 99 per cent, reduce order-cycle variability, and provide location-level visibility within twelve months” is an outcome-oriented design requirement. Several alternatives may satisfy this requirement, including process standardisation, barcode controls, a new warehouse management system, outsourced fulfilment, or a phased combination.

A solution architecture normally considers six connected dimensions:

• process design: how activities, decisions, and controls will change;
• physical design: facilities, equipment, storage, material flow, and transport interfaces;
• information design: data, systems, integration, reporting, and decision rights;
• people and organisation: roles, skills, governance, and change requirements;
• commercial design: contracts, sourcing, pricing, and supplier relationships; and
• performance design: targets, measures, incentives, and control mechanisms.

The design must avoid local optimisation. A faster picking system may be unattractive if it increases replenishment congestion; lower transport cost may be harmful if it raises inventory or damages customer service. The relevant unit of analysis is the end-to-end supply chain and its total cost-to-serve.

Generating and Structuring Alternatives

Alternative generation should be broad before it becomes selective. Teams can use process mapping, benchmarking, design workshops, scenario planning, supplier proposals, pilot results, and lessons from comparable operations. Alternatives should be genuinely different in logic, not merely different brands of the same solution.

Common strategic alternatives include improving the existing operation, redesigning the process, investing in technology or automation, outsourcing an activity, partnering with another organisation, changing the network structure, or postponing investment while gathering more evidence. A “do minimum” or status quo option is essential because every proposal should be compared with the consequences of not acting.

Each alternative should be documented in a standard concept sheet containing:

• problem addressed and expected benefits;
• scope, assumptions, and exclusions;
• required resources and capabilities;
• implementation duration and dependencies;
• capital and operating costs;
• service, risk, sustainability, and compliance implications; and
• key measures and conditions for success.

At this stage, precision is less important than transparency. Unsupported optimism should be avoided, but early estimates can be expressed as ranges and progressively refined through feasibility work.

Feasibility Analysis: Can the Solution Work?

Feasibility analysis examines whether an alternative can be implemented and sustained. It is broader than financial appraisal. A financially attractive project may fail because the facility cannot accommodate the equipment, the data are unreliable, the workforce lacks required skills, or regulatory approval is unavailable.

Technical and operational feasibility

Technical feasibility considers system compatibility, equipment capacity, data quality, network reliability, cybersecurity, scalability, and integration with enterprise platforms. Operational feasibility asks whether the proposed process can function under real demand, peak volumes, labour conditions, supplier behaviour, and customer requirements. Simulation, site surveys, prototypes, pilot tests, and capacity calculations are valuable evidence.

Financial and commercial feasibility

Financial feasibility assesses whether funding is available and whether expected returns justify the investment. Commercial feasibility considers supplier capability, contract structure, market conditions, switching costs, and the organisation’s negotiating position. Costs must include implementation, training, data cleansing, transition, disruption, maintenance, licences, energy, and eventual replacement—not only acquisition price.

Organisational and human feasibility

A solution may be technically sound but organisationally infeasible if responsibilities are unclear or affected employees resist it. Assessment should address leadership sponsorship, change readiness, labour relations, training, decision rights, and the maturity of project governance.

Legal, regulatory, and sustainability feasibility

The project must comply with relevant transport, customs, health and safety, employment, data-protection, competition, product, and environmental requirements. Sustainability feasibility includes energy use, emissions, packaging, waste, resource consumption, and the possibility that benefits in one part of the network create impacts elsewhere.

A feasibility assessment should distinguish between fatal constraints, remediable weaknesses, and assumptions requiring validation. This distinction prevents a weak assumption from being disguised as a confirmed fact.

Comparing Alternatives Through Multi-Criteria Decision Analysis

Logistics decisions commonly involve conflicting objectives. Multi-criteria decision analysis (MCDA) provides a transparent method for comparing alternatives across financial and non-financial criteria.

The weighted-scoring method is widely used. First, the team defines criteria such as total cost, service improvement, implementation risk, flexibility, sustainability, strategic fit, and workforce impact. Second, it assigns weights whose total equals 100 per cent. Third, each alternative receives a rating on a common scale. The weighted score is:

Total score = Σ (criterion weight × alternative rating).

Suppose service has a weight of 30 per cent and an alternative receives a rating of 4 on a five-point scale. Its contribution is 0.30 × 4 = 1.20. The same scale and rating definitions must be applied consistently. A score of 5 should have a documented meaning, such as “substantially exceeds the target with strong evidence.”

Weights express decision priorities, not objective truth. They should therefore be agreed by relevant stakeholders and tested through sensitivity analysis. If a small change in weights reverses the ranking, the decision is strategically fragile and requires further investigation. MCDA should support judgement, not create false mathematical certainty.

Other useful methods include the analytic hierarchy process, outranking methods, cost-effectiveness analysis, and the technique for order preference by similarity to ideal solution. The method should match the decision’s complexity, data quality, and need for explainability.

Building the Economic Case

The economic case converts operational effects into financial consequences while recognising uncertainty. It should use incremental analysis: compare the future with the project against the credible future without it. Benefits that would occur anyway must not be attributed to the project.

Cost categories

Relevant costs may include capital expenditure for equipment, facilities, software, integration, and installation; implementation expenditure for consultancy, testing, training, and temporary labour; and recurring operating expenditure for licences, maintenance, energy, support, staffing, and transport. Opportunity costs, transition disruption, and disposal or decommissioning costs should also be considered.

Benefit categories

Benefits may arise from labour productivity, reduced inventory, fewer errors, lower transport cost, reduced damage, improved asset utilisation, avoided overtime, lower stockouts, better revenue retention, or avoided future expenditure. Benefits should be linked to measurable operational drivers. For example, a reduction in picking errors should be translated through avoided returns, rework, replacement freight, and customer-service costs.

Benefits may be tangible or intangible. Improved resilience, employee safety, data visibility, and strategic flexibility may be difficult to monetise but should not be ignored. They can be presented separately, scored through MCDA, or valued using carefully stated assumptions.

ROI and payback

Return on investment is commonly expressed as:

ROI = (total benefits − total costs) / total costs × 100.

Payback period estimates the time required for cumulative net cash benefits to recover the initial investment. These measures are intuitive but incomplete. ROI can be distorted by the time period selected, and payback ignores benefits after recovery and usually ignores the time value of money.

Net present value

NPV discounts future cash flows to their present value:

NPV = Σ [CFₜ / (1 + r)ᵗ] − initial investment,

where CFₜ is the net cash flow in period t and r is the discount rate. A positive NPV indicates that the project is expected to create value above the required return, given the assumptions and discount rate. NPV is generally more theoretically robust than simple ROI because it recognises timing and scale.

For example, assume a logistics project requires an initial investment of $500,000 and produces net cash flows of $220,000, $240,000, and $230,000 over three years. At a 10 per cent discount rate, the present value of the cash flows is approximately $561,000, giving an NPV of about $61,000. The project appears economically attractive, but the conclusion should be tested against implementation delay, benefit shortfall, and cost escalation.

Risk-Adjusted Evaluation and Scenario Thinking

Forecasts are not facts. Logistics projects are exposed to demand variation, fuel prices, labour availability, supplier failure, inflation, cyber incidents, exchange rates, adoption delays, and changes in customer requirements. Risk analysis makes these uncertainties visible.

A useful approach is to define at least three scenarios: a downside case, a base case, and an upside case. The downside case may assume delayed implementation, lower benefits, and higher costs; the base case uses the most defensible estimates; and the upside case reflects stronger adoption or demand. Expected monetary value can be estimated by multiplying each outcome by its probability, although probabilities must be justified rather than invented.

Sensitivity analysis changes one assumption at a time, such as benefit realisation, discount rate, project cost, or volume growth. It identifies variables to which the business case is most sensitive. Break-even analysis asks what level of volume, saving, or adoption is required for NPV to reach zero. These analyses help managers define safeguards, contractual protections, pilot requirements, and approval conditions.

Risk-adjusted decisions should not be reduced to one number. A project with a slightly lower expected NPV but substantially lower operational risk may be preferable to a high-return alternative that could disrupt critical customer flows. Options such as phased investment, pilot deployment, termination clauses, modular technology, and dual sourcing can preserve flexibility and reduce downside exposure.

Strategic Alignment and Governance

A business case is strategic when it explains how the proposed solution contributes to organisational purpose and competitive position. Alignment may involve customer service, cost leadership, responsiveness, resilience, growth, sustainability, regulatory compliance, or digital transformation. The case should identify which strategic priorities are advanced and what trade-offs are accepted.

Governance determines who owns the decision, who funds it, who accepts risk, and how benefits will be measured. A strong business case identifies an accountable executive, a project sponsor, a benefits owner, decision gates, reporting arrangements, and escalation routes. Benefits should remain tracked after implementation; otherwise projected savings may disappear into general operational variation.

Ethical governance is also important. Automation and outsourcing can affect employment, privacy, safety, supplier dependence, and service access. Data used in optimisation must be accurate, lawfully obtained, and appropriately protected. Managers should not present uncertain projections as guaranteed savings or conceal assumptions that would change the recommendation.

Technology, Analytics, and Digital Decision Support

Digital tools can strengthen solution evaluation. Spreadsheet models support transparent financial analysis; simulation tests capacity and congestion; digital twins allow alternative network configurations to be explored; and dashboards track benefits after implementation. Machine-learning models may forecast demand or predict equipment failure, but their outputs require validation, monitoring, and human oversight.

Technology does not remove the need for managerial judgement. Poor master data can produce precise but misleading analysis. Automated recommendations may reproduce historical bias or optimise a narrow metric at the expense of resilience and service. Model assumptions, data lineage, access controls, cybersecurity, and explainability should therefore be documented.

Illustrative Case: Selecting a Regional Distribution Solution

Background

This illustrative case concerns Meridian Home Products, a fictional distributor serving retailers from a central distribution centre. Annual volume has increased, order accuracy has declined, and deliveries to northern customers frequently require premium transport. Management is considering three alternatives.

Situation and analysis

Alternative A retains the current network but introduces process standardisation, barcode scanning, and targeted workforce training. Alternative B establishes a small northern cross-dock supplied from the existing distribution centre. Alternative C introduces a highly automated central fulfilment system and retains the single-node network.

The project team identifies decision criteria and weights: annualised financial value 35 per cent, service improvement 25 per cent, implementation risk 15 per cent, scalability 10 per cent, sustainability 10 per cent, and workforce impact 5 per cent. Financial modelling shows that Alternative A requires $180,000 and has an estimated three-year NPV of $260,000. Alternative B requires $650,000 and has an estimated NPV of $310,000, largely through lower northern delivery cost and improved lead time. Alternative C requires $1.8 million and has an estimated NPV of $420,000, but its downside case is negative because adoption delays and integration costs are high.

The MCDA ranking places Alternative B first in the base case, Alternative A second, and Alternative C third. However, sensitivity analysis shows that Alternative B loses its advantage if northern demand falls by more than 20 per cent. Alternative A has the lowest risk and can be implemented quickly, while Alternative C offers the greatest long-term capacity but requires stronger technical capability.

Recommended approach

The team recommends a staged strategy. Meridian first implements Alternative A as a low-cost stabilisation programme and collects reliable volume, service, and cost data for six months. A decision gate then determines whether the northern cross-dock should be introduced. Automation is deferred until data quality, process discipline, and volume justify it. The business case includes explicit trigger conditions, such as sustained northern volume above a defined threshold and achievement of the first-stage accuracy target.

Outcome and learning points

The illustrative case demonstrates that the highest theoretical return is not automatically the best immediate choice. A staged portfolio can balance rapid improvement, learning, flexibility, and future capability. It also shows why status quo and minimum-change alternatives should remain visible, why sensitivity analysis matters, and why strategic recommendations should specify conditions rather than rely on a single forecast.

Common Errors and Practical Safeguards

Several weaknesses recur in logistics business cases. Teams may define the solution before understanding the problem, compare alternatives with inconsistent assumptions, omit transition costs, double-count benefits, treat non-financial criteria as afterthoughts, or use optimistic adoption rates. Another error is confusing activity completion with benefit realisation: installing a system does not prove that productivity or service improved.

Safeguards include maintaining an assumptions register, separating one-time and recurring effects, using independent challenge or peer review, documenting calculation logic, testing downside conditions, and assigning benefits to named owners. The analysis should state what evidence is known, estimated, uncertain, or excluded. A recommendation should also explain why rejected alternatives were not selected.

Best-Practice Decision Sequence

A disciplined sequence is to clarify objectives; establish the baseline; generate a broad set of alternatives; screen fatal feasibility constraints; develop concept designs; estimate costs and benefits; compare alternatives using MCDA; model scenarios and sensitivities; assess strategic, ethical, and regulatory alignment; select a preferred option or staged portfolio; and define governance, measures, and decision gates. This sequence is iterative rather than strictly linear. New evidence may require redesign or a revised business case.

Chapter Summary

Solution design converts logistics problems into implementable interventions. Effective design considers process, physical, information, people, commercial, and performance dimensions and compares genuinely distinct alternatives, including the status quo. Feasibility analysis tests technical, operational, financial, organisational, legal, and sustainability conditions. MCDA makes trade-offs explicit, while cost-benefit analysis, ROI, payback, and NPV provide complementary economic perspectives. Because forecasts are uncertain, scenario analysis, sensitivity testing, break-even analysis, and risk-adjusted evaluation are essential. A strong business case aligns the preferred solution with strategy, assigns governance and benefit ownership, addresses ethical and regulatory obligations, and may use staged investment to preserve flexibility. The quality of a decision depends not on numerical sophistication alone but on transparent assumptions, relevant evidence, and disciplined managerial judgement.

Key Terms

Business case: A structured justification for approving an investment or intervention.

Solution architecture: The integrated design of processes, physical resources, information, people, commercial arrangements, and performance controls.

Feasibility analysis: Assessment of whether a proposed solution can be implemented and sustained.

Incremental analysis: Comparison of project-related future effects with the credible without-project position.

Total cost-to-serve: The complete cost of fulfilling a customer, product, order, or channel requirement.

Multi-criteria decision analysis: A method for comparing alternatives across weighted financial and non-financial criteria.

Weighted scoring: A decision technique that multiplies criterion ratings by their assigned weights.

Capital expenditure: Spending on assets or capabilities expected to provide benefits over multiple periods.

Operating expenditure: Recurring expenditure required to operate and maintain a solution.

Return on investment: Net benefit expressed as a proportion of investment cost.

Payback period: Time required for cumulative net cash benefits to recover an initial investment.

Net present value: The present value of future cash flows less the initial investment.

Discount rate: The rate used to convert future cash flows into present values.

Sensitivity analysis: Testing the effect of changing one or more assumptions on the decision outcome.

Scenario analysis: Evaluation of outcomes under defined combinations of assumptions.

Break-even analysis: Determination of the point at which benefits equal costs or NPV becomes zero.

Risk appetite: The level and type of risk an organisation is willing to accept.

Benefits realisation: The process of ensuring that forecast improvements are achieved and sustained.

Decision gate: A formal point at which evidence is reviewed before continuing, changing, or stopping a project.

Strategic alignment: The degree to which a solution supports organisational priorities and competitive direction.

Review Questions

Short Answer Questions

1. Why should the status quo be included when comparing logistics alternatives?

2. Distinguish between technical feasibility and organisational feasibility.

3. What is the purpose of weighting criteria in MCDA?

4. Why is NPV generally more informative than simple payback?

5. What is meant by benefits realisation?

Long Answer Questions

1. Explain how a logistics team should move from problem diagnosis to a complete solution architecture.

2. Discuss the principal cost and benefit categories that should be included in a logistics business case.

3. Explain the strengths and limitations of weighted-scoring MCDA.

4. Describe how scenario, sensitivity, and break-even analysis improve investment decisions.

5. Discuss the governance, ethical, and strategic requirements of a high-quality logistics business case.

Analytical / Application Questions

1. A warehouse automation project has a high base-case NPV but a negative downside-case NPV. What additional analysis and safeguards would you recommend before approval?

2. Design an MCDA framework for choosing between outsourcing transport, improving the internal fleet, and creating a transport-management partnership. Specify criteria and justify their weights.

3. A proposed cross-dock has a positive NPV only when regional volume exceeds a specified threshold. Develop a staged recommendation and identify the measures that should trigger the next investment decision.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes the purpose of solution design in a logistics project?

A. To select a technology vendor before analysing operational needs

B. To translate a diagnosed performance gap into an implementable intervention

C. To calculate financial returns without considering service effects

D. To document only the activities already completed

Correct Answer: B. To translate a diagnosed performance gap into an implementable intervention

Question 2

Which item is most directly associated with operational feasibility?

A. Whether the process can function under peak demand and real workforce conditions

B. Whether the project has a positive accounting profit in year one

C. Whether the organisation's mission statement mentions logistics

D. Whether a supplier offers the lowest purchase price

Correct Answer: A. Whether the process can function under peak demand and real workforce conditions

Question 3

In a weighted-scoring model, a criterion's contribution to an alternative's score is calculated by:

A. Adding the criterion weight to the rating

B. Dividing the rating by the weight

C. Multiplying the criterion weight by the rating

D. Subtracting the rating from the weight

Correct Answer: C. Multiplying the criterion weight by the rating

Question 4

Why should a business case use incremental analysis?

A. To include every cost incurred by the organisation since its formation

B. To compare project-related effects with the credible future without the project

C. To ensure that intangible benefits are excluded

D. To replace all operational measures with financial measures

Correct Answer: B. To compare project-related effects with the credible future without the project

Question 5

What is a principal limitation of simple payback analysis?

A. It cannot be applied to projects involving capital expenditure

B. It usually ignores benefits occurring after the investment is recovered

C. It requires a discount rate for every monthly cash flow

D. It always produces a negative result for logistics projects

Correct Answer: B. It usually ignores benefits occurring after the investment is recovered

Question 6

A project requires $500,000 initially and has a present value of future cash flows of $561,000. What is its approximate NPV?

A. $61,000

B. $500,000

C. $1,061,000

D. -$61,000

Correct Answer: A. $61,000

Question 7

What does sensitivity analysis primarily reveal?

A. The legal owner of each project activity

B. The effect of changing assumptions on the decision outcome

C. The exact probability of every future event

D. The number of suppliers available in a market

Correct Answer: B. The effect of changing assumptions on the decision outcome

Question 8

Which recommendation best reflects risk-adjusted decision-making?

A. Approve the alternative with the highest base-case NPV regardless of downside risk

B. Reject every project containing uncertainty

C. Use staged investment, pilots, and decision gates where uncertainty is material

D. Choose the lowest-cost alternative without assessing service impact

Correct Answer: C. Use staged investment, pilots, and decision gates where uncertainty is material

Question 9

In the illustrative Meridian case, why was automation deferred?

A. It had no possible long-term value

B. Its high downside risk and capability requirements were not yet justified

C. Automation cannot be used in distribution operations

D. The cross-dock had a higher purchase price

Correct Answer: B. Its high downside risk and capability requirements were not yet justified

Question 10

Which practice most strengthens benefits realisation?

A. Assigning benefits to named owners and tracking them after implementation

B. Treating system installation as proof that benefits have been achieved

C. Removing non-financial measures from performance reports

D. Avoiding decision gates after project approval

Correct Answer: A. Assigning benefits to named owners and tracking them after implementation