Consulting, Cases and Applied Problem-Solving

Introduction

Management education ultimately becomes valuable when it improves the quality of decisions made under conditions of uncertainty, competing interests, incomplete information and limited time. Consulting and case-based problem-solving provide a disciplined bridge between conceptual knowledge and managerial action. They require more than identifying an attractive idea: the analyst must define the problem accurately, establish credible evidence, compare alternatives, assess implementation feasibility and communicate a recommendation that decision-makers can act upon.

A complex business problem is rarely presented in a clean form. A client may report declining profits, while the underlying issue is an unprofitable customer segment, poor capacity utilization, weak pricing discipline or an ineffective operating process. Similarly, a request for “a digital strategy” may conceal unresolved questions about customer value, organizational capability, data governance and investment priorities. Professional problem-solving therefore begins by separating symptoms from causes and decisions from analysis.

This chapter develops an integrated approach to consulting and applied case analysis. It combines structured diagnosis, hypothesis-driven inquiry, evidence evaluation, financial reasoning, implementation design and executive communication. The emphasis is not on producing a large report but on producing a defensible decision.

Learning Objectives

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

1. Distinguish symptoms, problems, causes and decision questions.
2. Structure ambiguous business situations into analytically manageable components.
3. Formulate and test hypotheses using qualitative and quantitative evidence.
4. Evaluate strategic alternatives using financial, operational, organizational and ethical criteria.
5. Assess implementation feasibility, risks and stakeholder implications.
6. Communicate recommendations concisely to executive audiences.
7. Critically evaluate the limitations of consulting frameworks and case evidence.

1. The Nature of Consulting and Applied Problem-Solving

Consulting is a temporary professional relationship in which an adviser helps a client understand a problem, make a decision or implement change. The consultant does not merely supply information. The professional contribution lies in framing the issue, improving the quality of reasoning and helping the organization act.

Applied problem-solving differs from academic analysis in three important respects. First, the question is usually decision-oriented: whether to enter a market, close a plant, change a price, acquire a firm or redesign a process. Second, evidence is imperfect and time is constrained. Third, the usefulness of the work depends on adoption, not only analytical correctness.

A useful distinction is:

• Symptom: an observable condition, such as falling sales.
• Problem: an undesirable gap between actual and desired performance.
• Root cause: a factor that materially produces or sustains the problem.
• Decision question: the choice that management must make.
• Objective: the result the decision should achieve.
• Constraint: a condition that limits feasible action.
• Recommendation: a proposed course of action supported by evidence.

For example, “profit has declined” is a symptom. “The firm must restore operating profit within two years without compromising regulatory compliance” is a decision context. The relevant causes may include price erosion, rising input costs and an inefficient product portfolio.

1.1 Well-Structured and Ill-Structured Problems

A well-structured problem has a defined objective, reliable data and a limited set of alternatives. An ill-structured problem has ambiguity regarding objectives, causal relationships, stakeholders and available evidence. Most senior-management problems are ill-structured. They require judgment as well as analysis.

A strong analyst does not eliminate ambiguity prematurely. Instead, the analyst makes assumptions explicit, identifies what is known and unknown, and designs evidence-gathering activities that reduce decision-relevant uncertainty.

2. Problem Definition and Issue Structuring

2.1 From Broad Concern to Decision Statement

A useful problem statement identifies four elements:

1. Performance gap: What is happening compared with what should happen?
2. Scope: Which business, customer, geography, process or time period is involved?
3. Decision owner: Who can act on the recommendation?
4. Time horizon: By when must the decision produce results?

A weak statement is: “How can we improve the business?” A stronger statement is: “How can the retail division increase contribution margin by 15% over 24 months while maintaining service levels and avoiding regulatory breaches?”

The statement should not embed an untested solution. “How should we launch an app?” assumes that an app is the answer. “How can we reduce customer-service cost while preserving satisfaction?” keeps the solution open.

2.2 Issue Trees and MECE Structure

An issue tree decomposes a broad question into smaller questions whose answers collectively support a decision. A common profitability identity is:

Revenue may be decomposed as:

where i indexes products, services, customers or markets. Operating costs can be divided into fixed and variable components, provided the classification is appropriate for the decision horizon.

A profitability issue tree might therefore examine:

• Revenue: price, volume, mix, retention and new-customer acquisition.
• Costs: labor, materials, logistics, overhead and rework.
• Scope: product, customer segment, geography and channel.
• External conditions: competitors, regulation and macroeconomic changes.

Issue trees should be mutually exclusive and collectively exhaustive—often abbreviated MECE. The principle is useful but not absolute. Categories may overlap in real organizations, and forcing perfect separation can obscure important interactions. The purpose is clarity, not formal elegance.

2.3 Hypothesis-Driven Analysis

A hypothesis is a provisional explanation or proposition that can be tested. For example: “The decline in profit is primarily caused by discounting in the enterprise segment rather than by lower demand.” A hypothesis-driven approach is more efficient than collecting all available data because it directs attention toward evidence that can change the decision.

A practical cycle is:

1. State the decision and initial hypothesis.
2. Identify observable implications.
3. Specify evidence that would support or refute the hypothesis.
4. Gather and test the evidence.
5. Revise the hypothesis or decision structure.
6. Repeat until the recommendation is sufficiently robust.

The approach must not become confirmation bias. Analysts should actively seek disconfirming evidence and record alternative explanations.

3. Evidence, Data and Causal Reasoning

3.1 Evidence Hierarchy

Relevant evidence may include financial records, operational data, customer interviews, surveys, market research, experiments, competitor information and regulatory documents. Evidence quality depends on validity, reliability, timeliness, relevance and independence.

A precise measurement of the wrong construct is not useful. For example, website visits may be reliable but may not measure customer profitability. Interview evidence can reveal motivations and implementation barriers, but it may be affected by recall error, political incentives or selection bias.

A useful evidence register records:

3.2 Descriptive, Predictive and Causal Claims

Descriptive analysis answers what happened. Predictive analysis estimates what may happen. Causal analysis asks what would happen if management intervened. These are not interchangeable.

A correlation between delivery delays and customer churn does not establish that delays caused churn. Both may be caused by a third factor, such as low-quality customers receiving fewer resources. Causal reasoning requires a credible comparison, such as a controlled pilot, natural experiment, longitudinal analysis or carefully justified quasi-experimental design.

3.3 Triangulation

Triangulation compares different sources or methods. If accounting data, customer interviews and process observations independently indicate that a premium segment is receiving inadequate service, confidence in the diagnosis increases. Triangulation does not guarantee truth, but it reduces dependence on one potentially biased source.

4. Analytical Frameworks for Managerial Decisions

Frameworks organize thought; they do not replace thought. Their value depends on fit with the problem and the quality of evidence used.

4.1 External and Industry Analysis

PESTLE analysis examines political, economic, social, technological, legal and environmental influences. Porter’s five forces considers rivalry, threat of new entrants, supplier power, buyer power and substitutes. These frameworks help identify structural pressures but can become static checklists. Analysts should connect each force to a measurable implication for demand, cost, risk or competitive behavior.

4.2 Internal and Capability Analysis

The resource-based view asks whether resources and capabilities are valuable, rare, difficult to imitate and effectively organized. The value chain identifies where the organization creates cost or differentiation advantages. Capability analysis should distinguish assets from routines: possessing data is not the same as being able to convert data into profitable decisions.

4.3 Customer and Business Model Analysis

Segmentation should use variables linked to behavior or value rather than only demographic description. A customer segment becomes strategically useful when the firm can identify it, serve it differently and earn an attractive return from it.

A business model analysis examines the customer problem, value proposition, channels, relationships, key resources, activities, partners and revenue logic. The central test is coherence: do the operating model and economics support the promised value?

4.4 Options and Decision Criteria

Alternatives should be compared against explicit criteria. Typical criteria include financial return, strategic fit, customer impact, speed, capability requirements, risk, reversibility and ethical consequences.

A weighted decision score can support structured comparison:

where Sⱼ is the score of option j, wᵢ is the weight assigned to criterion i, and rᵢⱼ is the rating of option j on criterion i. Weights should sum to 1, and ratings must use a consistent scale. The score is a decision aid, not an objective truth. Sensitivity analysis should test whether the ranking changes when weights or ratings change.

4.5 Financial Evaluation

For investment decisions, net present value is commonly defined as:

where CFₜ is net cash flow in period t, r is the discount rate per period, and n is the final period. CF₀ normally includes the initial investment and is often negative. The formula assumes cash flows are measured consistently, the discount rate reflects the relevant risk and cash-flow timing is correctly specified. A positive NPV indicates value creation relative to the discount rate, subject to the quality of forecasts and assumptions.

For operating decisions, contribution margin is often useful:

Break-even volume, under constant unit price, variable cost and fixed cost, is:

These formulas are not appropriate when prices, variable costs or capacity change materially with volume. In such cases, a scenario or nonlinear model is preferable.

5. From Diagnosis to Recommendation

A recommendation should answer five questions:

1. What should be done?
2. Why is it the best available option?
3. What evidence supports it?
4. What risks or conditions could invalidate it?
5. How will management implement and monitor it?

The distinction between findings and recommendations is important. A finding is evidence-based: “Customers in the premium segment experience twice as many late deliveries.” A recommendation is a choice: “Prioritize premium-segment orders through a dedicated scheduling process.” The latter requires additional reasoning about cost, capacity and fairness.

A robust recommendation usually contains a primary action, supporting initiatives, explicit conditions and a contingency. It should state what not to do when that prevents strategic drift.

6. Implementation Feasibility

Many analyses fail because they treat implementation as an appendix. Feasibility should be tested while alternatives are being developed.

6.1 The Four Feasibility Tests

• Technical feasibility: Can the required systems, processes and expertise be developed?
• Financial feasibility: Are investment, operating costs, cash requirements and benefits credible?
• Organizational feasibility: Do leadership, skills, incentives and culture support adoption?
• Stakeholder feasibility: Can customers, employees, suppliers, regulators and communities accept the change?

Implementation planning should specify workstreams, owners, milestones, dependencies, resources, decision gates and measures. A useful roadmap distinguishes quick wins from foundational changes and separates reversible from irreversible commitments.

6.2 Measurement and Control

Key performance indicators should connect activity to outcomes. For example, training completion is an activity measure; error reduction and customer retention are outcome measures. A balanced performance system may include financial, customer, process, people and risk indicators.

Targets should have a baseline, measurement definition, owner, frequency and action threshold. Without these elements, a KPI is merely a number.

6.3 Risk and Scenario Analysis

Risk analysis identifies events, causes, consequences, controls, owners and residual exposure. Scenario analysis examines how a recommendation performs under different assumptions, such as high inflation, weak demand or competitor retaliation.

A decision is robust when it remains acceptable across a plausible range of conditions, not merely when it produces the highest result in one forecast. Real-options thinking may favor staged investment when uncertainty is high and learning can be purchased through a pilot.

7. Executive Communication

Executives generally need a clear decision, not a chronological account of the analyst’s research. An effective communication structure is:

1. Answer first: state the recommendation.
2. Evidence: present two or three decisive findings.
3. Logic: explain how findings support the recommendation.
4. Economics and feasibility: show value, resources and constraints.
5. Risks: identify major risks and mitigations.
6. Decision required: specify what approval or action is needed now.

A good executive exhibit has one message, a visible source, clear units, a relevant comparison and an explicit implication. Avoid false precision, decorative charts, unexplained acronyms and data without a decision consequence.

The written executive summary should be understandable without the full report. It should distinguish facts, assumptions and judgments. If evidence is weak, credibility improves when uncertainty is disclosed rather than concealed.

8. Ethics, Governance and Responsible Use of Data

Consultants and managers have duties beyond client preference. Ethical practice requires honesty about evidence, confidentiality, conflicts of interest, competence and foreseeable harm. Analysts should not manipulate a model to produce a preferred conclusion or suppress inconvenient findings.

Data-driven consulting raises additional issues: privacy, consent, cybersecurity, discriminatory outcomes, explainability and accountability. A model that predicts employee attrition may create unfair surveillance or stigmatization. Artificial intelligence can accelerate document analysis, scenario generation and pattern detection, but generated outputs require verification. Sensitive data should not be entered into unapproved systems, and human decision-makers remain accountable for consequential choices.

Governance should define data ownership, access rights, retention, auditability, model validation and escalation procedures. Regulatory requirements vary by jurisdiction and industry; professional advice should not substitute for legal review.

9. Illustrative Case: Northstar Medical Devices

Background

Northstar Medical Devices is a fictional mid-sized manufacturer of diagnostic equipment. Its revenue increased by 8% over two years, but operating profit fell from 12% to 7% of revenue. The chief executive asks a consulting team to recommend how to restore profitability without reducing product reliability or withdrawing from public-health customers.

Problem Definition

The initial symptom is declining operating margin. The decision question is: “Which combination of pricing, product-portfolio and operating changes can restore the margin to at least 10% within 18 months while preserving reliability and essential-customer access?”

Initial Hypotheses

The team develops four hypotheses:

• H1: Margin erosion is concentrated in a small number of low-contribution products.
• H2: Discounting is not matched by customer lifetime value or service cost.
• H3: Expedited production and rework are increasing variable cost.
• H4: A broad price increase would damage strategic accounts and is therefore inferior to targeted pricing.

Analysis

Finance data show that three products generate 42% of revenue but only 18% of contribution. The products have high customization and frequent expedited orders. Interviews with sales staff reveal that discounts are often granted to win initial contracts, while service teams report that the same customers require extensive technical support.

A process review finds that 16% of orders in the three products require rework, compared with 5% for the rest of the portfolio. However, the team rejects the premature conclusion that production alone is responsible. Product complexity and incomplete customer specifications are also contributing causes.

The team evaluates three options using criteria of financial impact, customer risk, implementation speed and capability requirements. Ratings are assigned on a 1–5 scale, with criterion weights summing to 1. The weighted score is used only as a transparent comparison tool.

Further analysis estimates that targeted repricing would increase annual contribution by $2.4 million, while process redesign would cost $0.9 million initially and $0.3 million annually. These estimates are forecasts, not guaranteed benefits. Sensitivity testing shows that the combined option remains preferable if realized benefits fall by 25%, but not if benefits fall by 50% and implementation costs rise by 30%.

Recommendation

The team recommends a staged program:

1. Introduce segment-specific price floors based on service cost and strategic value.
2. Require senior approval for discounts below the floor.
3. Redesign the three high-rework products with customer input.
4. Introduce specification checklists and first-article approval before production.
5. Pilot the changes with two accounts for 90 days.
6. Review contribution, rework, delivery reliability and customer satisfaction before scaling.

The recommendation explicitly rejects immediate product withdrawal and a universal price increase. It preserves an exception process for public-health customers, subject to transparent criteria rather than informal favoritism.

Implementation and Outcome

The implementation plan assigns the commercial vice-president responsibility for pricing, the operations director responsibility for process redesign and the quality director responsibility for reliability controls. The pilot dashboard includes realized price, contribution per order, rework rate, on-time delivery, complaints and customer retention.

In this illustrative case, after three months the pilot reduces rework from 16% to 9% and improves contribution, but one account reports dissatisfaction with the approval process. Management therefore simplifies the process for low-risk orders while retaining controls for high-complexity work. The result demonstrates that implementation is iterative: evidence may refine the recommendation without invalidating its central logic.

Learning Points

The case illustrates the importance of distinguishing revenue growth from profitable growth, examining customer economics rather than average margins, testing multiple causes, protecting strategic and public-interest considerations, using pilots to manage uncertainty and defining implementation ownership before approval.

10. Common Failure Modes and Best Practices

Common failures include solving the stated request rather than the underlying problem, collecting data without a decision purpose, confusing correlation with causation, using averages that conceal segment differences, relying on a single forecast, ignoring organizational resistance and presenting a recommendation without an owner.

Best practices include:

• Start with a decision statement and success measure.
• Maintain an explicit hypothesis and issue tree.
• Separate facts, assumptions and judgments.
• Use contribution economics where averages obscure behavior.
• Seek disconfirming evidence.
• Test recommendations under adverse scenarios.
• Include implementers and affected stakeholders in the analysis.
• Pilot when learning is valuable and risks are manageable.
• Make uncertainty and limitations visible.
• Communicate the recommendation before supporting detail.

Contemporary Developments

Consulting is increasingly shaped by analytics platforms, remote collaboration, automated research and generative AI. These tools can reduce the cost of data preparation and expand the range of scenarios considered. They also increase the risk of fabricated citations, hidden model bias, intellectual-property leakage and overconfidence in automated outputs.

The future-oriented consultant therefore needs both analytical fluency and judgment. Technical tools should improve question formulation, evidence quality and decision speed, not replace accountability. The durable professional advantage remains the ability to connect evidence, human behavior, economics and execution.

Chapter Summary

Consulting and applied problem-solving convert ambiguous managerial concerns into defensible decisions. The process begins by distinguishing symptoms from problems, causes and decision questions. Issue trees and hypotheses structure inquiry, while triangulation and causal reasoning improve evidence quality. Frameworks such as PESTLE, industry analysis, capability analysis, customer economics and business-model analysis are useful when connected to the specific decision rather than applied mechanically.

Recommendations should compare alternatives against explicit criteria, financial consequences, risks and feasibility. NPV, contribution margin and break-even analysis can support decisions when their assumptions are satisfied. Implementation requires technical, financial, organizational and stakeholder feasibility, together with owners, milestones, measures and controls. Executive communication should lead with the answer and make evidence, assumptions, risks and required decisions clear. Ethical practice requires honesty, confidentiality, responsible data use and accountability for technology-assisted analysis. The central lesson is that high-quality consulting is not a polished report; it is disciplined reasoning that enables responsible action.

Key Terms

Problem statement: A precise description of the performance gap, scope, decision context and time horizon.

Symptom: An observable indication of an underlying condition.

Root cause: A factor that materially produces or sustains a problem.

Decision question: The choice that management must make.

Issue tree: A hierarchical decomposition of a broad question into smaller analytical questions.

MECE: A structuring principle meaning mutually exclusive and collectively exhaustive.

Hypothesis: A provisional proposition that can be tested with evidence.

Triangulation: Comparison of multiple sources or methods to strengthen inference.

Causal inference: Reasoning about whether an intervention produces an observed outcome.

Contribution margin: Selling price minus variable cost, usually measured per unit or transaction.

Net present value: The present value of expected cash inflows and outflows using a discount rate.

Weighted decision score: A structured comparison that combines criterion weights and option ratings.

Feasibility: The extent to which an alternative can be implemented technically, financially and organizationally.

Scenario analysis: Examination of performance under different plausible assumptions.

Pilot: A limited implementation designed to generate learning before broader rollout.

Key performance indicator: A defined measure used to monitor progress toward an objective.

Stakeholder: An individual or group affected by, or able to affect, a decision.

Executive synthesis: Concise communication of recommendation, evidence, implications and required action.

Responsible AI: Development and use of AI with attention to accuracy, fairness, privacy, security and accountability.

Review Questions

Short Answer Questions

1. Distinguish a symptom from a root cause and provide a business example.
2. What is the purpose of an issue tree?
3. Why should analysts seek disconfirming evidence?
4. Name four dimensions of implementation feasibility.
5. What information should an executive recommendation communicate?

Long Answer Questions

1. Explain how a consultant can move from an ambiguous client concern to a precise decision statement.
2. Compare descriptive, predictive and causal analysis in a managerial context.
3. Discuss the benefits and limitations of weighted decision scoring.
4. Explain how financial analysis and organizational feasibility should be integrated when evaluating an investment.
5. Evaluate the ethical and governance challenges associated with AI-supported consulting.

Analytical / Application Questions

1. A company’s revenue is rising but its operating profit is falling. Construct an issue tree and identify the evidence needed to test at least three possible causes.
2. Design a 90-day pilot for a firm considering a new customer-service process. Specify the hypothesis, treatment, measures, decision gates and major risks.
3. Using the Northstar case, explain why targeted repricing and process redesign may be more robust than either a universal price increase or immediate product withdrawal.

Multiple Choice Questions with Answers

Question 1

Which statement best represents a decision question?

A. Customer complaints increased during the last quarter.

B. The company must decide how to reduce service cost while preserving satisfaction.

C. Employees report that the scheduling system is slow.

D. The competitor introduced a lower-priced product.

Correct Answer: B. The company must decide how to reduce service cost while preserving satisfaction.

Question 2

In hypothesis-driven consulting, what should normally occur after a hypothesis is stated?

A. The analyst selects only supporting evidence.

B. The analyst identifies observable implications and tests them.

C. The analyst writes the final recommendation immediately.

D. The analyst eliminates all qualitative evidence.

Correct Answer: B. The analyst identifies observable implications and tests them.

Question 3

Which formula correctly expresses operating profit?

A. Revenue + operating costs

B. Operating costs − revenue

C. Revenue − operating costs

D. Revenue × operating costs

Correct Answer: C. Revenue − operating costs

Question 4

A product sells for $80 per unit and has a variable cost of $50. What is its contribution margin per unit?

A. $30

B. $50

C. $80

D. $130

Correct Answer: A. $30

Question 5

Which statement about NPV is correct?

A. A positive NPV guarantees that forecasts are accurate.

B. NPV discounts expected cash flows using a relevant discount rate.

C. NPV can be calculated without specifying the timing of cash flows.

D. NPV is applicable only to non-financial decisions.

Correct Answer: B. NPV discounts expected cash flows using a relevant discount rate.

Question 6

What is the primary purpose of triangulation?

A. To replace all quantitative data with interviews

B. To compare different evidence sources or methods

C. To guarantee that a causal relationship exists

D. To reduce the number of stakeholders involved

Correct Answer: B. To compare different evidence sources or methods

Question 7

Which is an outcome measure rather than an activity measure?

A. Number of employees trained

B. Number of meetings held

C. Reduction in processing errors

D. Number of manuals distributed

Correct Answer: C. Reduction in processing errors

Question 8

Which recommendation is most implementation-ready?

A. Improve operations as soon as possible.

B. Invest in technology because competitors are doing so.

C. Pilot the redesigned process for 90 days with an assigned owner and defined measures.

D. Increase marketing expenditure across all channels.

Correct Answer: C. Pilot the redesigned process for 90 days with an assigned owner and defined measures.

Question 9

Why should a consultant distinguish facts, assumptions and judgments?

A. To make the report longer

B. To conceal uncertainty from executives

C. To improve transparency and allow critical evaluation

D. To avoid making any recommendation

Correct Answer: C. To improve transparency and allow critical evaluation

Question 10

Which ethical risk is especially relevant to AI-supported consulting?

A. The possibility that every output will be perfectly objective

B. The possibility of privacy breaches, bias or fabricated supporting material

C. The elimination of all need for human accountability

D. The inability to process any business data

Correct Answer: B. The possibility of privacy breaches, bias or fabricated supporting material