Manoj Pareek

What is a Case Study

 Case studies typically consist of a brief story ( Usually 5 to 25 pages) written from the
perspective of a company management or business leader facing a problem. Case studies
give readers an overview of the major issue, as well as information about the institution,
industry, and people involved, as well as the circumstances that led to the problem or
choice in question.

 Case studies are occasionally disguised versions of actual occurrences or composites

based on the faculty authors' experience and understanding of the subject and are based
on interviews or public sources.

 The case method allows students to think and behave like managers, while omitting more
traditional methods such as interaction with lecturers and textbooks.

 The cases are frequently based on real-life situations and show a critical decision-making
position for a company or an individual. Students must choose solutions from among the
many options offered to them and recommend a plan of action as well as a backup plan in
case their first recommendation fails.
Benefits of Case Study Method
• Encourages active learning by providing diverse points of view and allowing you to think in
new ways.

• Be analytical in your thinking and confident in your communication.

• The case method prepares you to make decisions under pressure and within tight timelines.

• It hones your attention to detail, teaches you how to ask appropriate questions, and moulds
you into a better listener.

• The case approach teaches you how to make decisions in the face of ambiguity. You will never
have comprehensive data, and you may not even have data in an appropriate form, while
making decisions, just as you will never have complete data in real life.

• The case technique allows you to gain a better understanding of your peers as individuals.
 Some Common Fallacies
regarding case method
• The case study frequently contains no right solution.

• A case study is not a method for determining the best solution

(i.e. The process matters, not the final result)

• A case discussion is not a chance for students to show their professor that they have discovered the
correct answer.

• A case discussion is not an attempt to silence opposing ideas. It's an opportunity to combine intuition
and knowledge to create new knowledge.
 Process for Solving a case
• Quickly read the case to identify the most important topics, such as the problem,
participants, and industry structure

.• Go over the exhibits again to make sure you comprehend the facts you have.
• Go over the discussion questions again. If you aren't given any discussion questions,
figure out what the main issue is.

• Read the case thoroughly while keeping an eye out for answers to the questions
.• Come up with your own point of view

.• Defend your own position • Have a discussion with your team. • Take down notes
Suggested - Process of solving a Case Study
INTRO Situational Analysis/ Brief Summary/Synopsisof the case

CHALLENGE
What is the problem faced by the firm or Individual in the case

Analysis/ What are the various alternatives available to the firm Present Alternative
Solution 1, 2, 3,4 ….

EVALUATE Weigh each alternative. Bring out pros and Cons of considering
each alternative
Need your POV (Point of View) . What could be the one best
Best alternative ?
Alternative (Long Term Solution)

Recommendation on how choosing the best solution can be

Conclusion helpful
 Process
ALTERNATIVES
PROBLEM SOLUTION EVALUATION
Best Solution
CHALLENGE –WHY WEIGH
ANALYSIS LONG TERM
QUESTIONS ALTERNATIVES

Conclusion
Business Models which can be used in Analysis

 SWOT ANALYSIS

 PESTEL

 BCG MATRIX

 Michael Porter – 5 forces

 Fish Bone ( Root Cause Analysis)

 DMAIC ( Six sigma)

 ANSOFF MATRIX etc…

SWOT ANALYSIS
 THREAT OF NEW ENTRY

• Not too expensive to enter the industry

• Experience needed, but training easily available

• Some economies of scale

• No technology protection

SUPPLIER POWER BUYER POWER

• Moderate number of COMPETITIVE RIVALRY • Few, large supermarkets

suppliers • Maybe Co-operatives?

INDUSTRY ANALYSIS –
• Very many competitors
• Suppliers large • Very large orders
• Commodity products
• Similar products • Homogenous product
• Low switching costs
• Able to substitute • Extreme prove sensitivity
• Low customer loyalty

PORTER’S FIVE
• Able to change • Ability to substitute
• High cost of leaving market
• Neutral supplier power • High Buyer power

FORCES

THREAT OF SUBSTITUTION

• Some cross-product substitution

• Ability to import food

• Some geographical substitution

 Product

PRESENT NEW

Market Penetration Product Development

Trying to take a greater share Extending existing products

PRESENT
of an existing product, for within existing markets.
example by relaunching or
increasing awareness.

COMPANY ANALYSIS
LOW RISK MEDIUM RISK

Market
– ANSOFF MATRIX
Market Development Diversification

Finding or creating new Creating new product lines or

markets for existing products ranges for sale in new market.
NEW

MEDIUM RISK HIGH RISK

 FISHBONE (CAUSE-AND-EFFECT) DIAGRAM

Customers Warehouse Customer service R&D

Not enough time

Want more choices Inadequate tracking Understaffed
for research

Outdated software No 24x7 support No longer quality

Tech savvy
pants

Need more space Not trained in product

Loss of
Sales
Phone system outdated Budget cut

Damaged goods Database crashed Increased agency fees Testing rushed

Outdated screening
Packing not “green” Understaffed Less ads and sponsorships
process

Delivery Fulfillment Marketing Testing

 DMAIC – SIX SIGMA

DEFINE MEASURE ANALYZE IMPROVE CONTROL

Assess the Evaluate Current Make Changes to

Identify the needs Maintain Improvement
current process Processes Improve Processes

Find the gap between

Problem causes:
Problem: current & required Brainstorm solutions Monitor improvement
(prioritized list)
performance

Create process How process inputs Find simplest &

Customer (VOC, CTQ): Create a control plan
performance baseline affect outputs: Easiest solutions

Check measurement for Test solutions

Process to improve: Locate root causes: Update documentation
accuracy & precision (Plan-do-check-act)

Establish a high-level
Project goal: Anticipate risks
baseline

Establish a high-level Create

Project scope:
baseline implementation plan
THANK YOU