Applied

Case Studies

Composite situations from startups, corporates and factories — each with the challenge, the Gita reading, the action taken and the lesson you can reuse.

Search case studies

Showing 8 of 8 case studies

EntrepreneurshipChapter 3, Verse 35 — svadharma

The startup that could not let go

A Series A team held a beloved product for three quarters after retention flatlined, out of loyalty to early users and to the founding story.

The challenge

Every pivot conversation collapsed into identity: killing the product felt like admitting the founding thesis was wrong.

Arjuna mindset — attachment to identity mistaken for duty

Gita reading

Svadharma is not the first thing you built; it is the capability you uniquely hold. The team's real strength was distribution into a hard-to-reach buyer, not that particular product.

Action taken

The team ran a Svadharma Canvas, separated capability from artefact, and repositioned as an infrastructure layer for the same buyers.

Outcome

Attachment released, capability retained; net revenue retention recovered above 110%.

Key takeaway

Ask what capability you are protecting, not what product. Products are disposable; capability is svadharma.

EthicsChapter 2, Verse 31 — considering your own duty, do not waver

The ethical dilemma in a growth quarter

A revenue leader was offered a channel deal that would hit the number but obscure true unit economics from the board.

The challenge

The deal was legal, the quarter was short, and no one downstream would notice for at least two reporting cycles.

Dharma as a pre-filter, not a trade-off

Gita reading

When ethics is applied after ranking, it always loses to the number. Applied before, the option simply never enters the option set.

Action taken

The leader moved the ethics screen ahead of scoring, declined the deal, and disclosed the projected miss to the board six weeks early.

Outcome

Deal declined, miss disclosed early, board trust materially strengthened for the next raise.

Key takeaway

Move the ethics gate earlier in the process and it stops being a sacrifice.

CrisisChapter 2, Verse 11 — reframing before instruction

The plant shutdown call

A manufacturing head had 48 hours to decide on a shutdown affecting 400 people, with contradictory safety data.

The challenge

Both options looked catastrophic: shut down and lose the quarter, or continue and risk an injury nobody could forgive.

Krishna's counsel — reframe before deciding

Gita reading

The question was not 'shut down or not' but 'what is the least reversible harm'. Reframing revealed a staged option no one had modelled.

Action taken

Partial line halt with full pay, independent safety verification, daily briefings to the whole plant.

Outcome

Safety verified in nine days, zero attrition, insurer premium unchanged.

Key takeaway

In a crisis, spend the first hour on the question, not the answer.

ChangeChapter 14, Verses 5–9 — the three qualities

Two cultures, one org chart

After acquiring a smaller rival, a services firm merged two delivery organisations with incompatible operating habits.

The challenge

The acquired team read every process change as a loss of identity; the acquiring team read every objection as resistance.

Guna diagnosis — rajas colliding with tamas

Gita reading

The acquirer was rajas-dominant (constant motion), the acquired firm tamas-dominant (protective inertia). Neither was wrong; both needed a route to sattva.

Action taken

A 90-day integration charter: three changes only, jointly designed, with an explicit stop-doing list on the acquirer's side.

Outcome

Voluntary attrition in the acquired team fell from 22% to 7% over two quarters.

Key takeaway

Name the cultural mode on both sides before you write the integration plan.

PeopleChapter 3, Verse 21 — whatever a great person does, others follow

The manager everyone avoided

A technically brilliant engineering manager delivered on time but produced consistent attrition on their team.

The challenge

Performance metrics said keep; exit interviews said act. The leadership team had avoided the conversation for a year.

Leadership by example — the standard you tolerate

Gita reading

Tolerating a corrosive standard broadcasts it. The tolerated behaviour, not the values page, became the company's real culture document.

Action taken

A direct, specific conversation with measurable behavioural expectations, coaching support and a 90-day review date.

Outcome

Behaviour changed on two of three dimensions; the manager moved to an individual-contributor architect role by mutual agreement.

Key takeaway

The behaviour a leader tolerates is the behaviour the company is teaching.

Decision-makingChapter 2, Verse 38 — treating gain and loss alike

Pricing with no good data

A SaaS company had to reprice for a new segment with no comparable benchmarks and a board expecting a number.

The challenge

Every analysis produced a different answer, and each week of delay cost pipeline.

Equanimity — symmetric treatment of gain and loss

Gita reading

The data would never be sufficient. What was missing was not information but a pre-committed way to judge the decision after the fact.

Action taken

A Detachment Decision Ledger: written reasoning, expected range, kill criteria, and a 90-day review of the reasoning rather than the result.

Outcome

Priced in nine days instead of a quarter; the ledger review kept the second price change calm and evidence-led.

Key takeaway

When data runs out, upgrade the decision process, not the analysis.

LeadershipChapter 2, Verse 48 — steadiness before action

Burnt out three weeks before launch

A product team hit exhaustion just before the most important launch of the year.

The challenge

Pushing harder risked defects and resignations; slipping the date risked a competitor's window.

Established in yoga, perform your work

Gita reading

Sustainable performance is a stable baseline plus consistent effort. Crunch borrows from the quarter after the launch at a punitive interest rate.

Action taken

Scope cut to the two features that carried the promise, a protected no-meeting block daily, and a fixed post-launch recovery week.

Outcome

Shipped on date with 40% fewer critical defects than the previous launch; no resignations.

Key takeaway

Cut scope, not people. Rhythm is a strategy, not a perk.

StrategyChapter 4, Verse 34 — learn by enquiry and service

Two founders, one decision right

Co-founders deadlocked over whether to serve enterprise or self-serve customers, each with a credible case.

The challenge

The disagreement had become personal, and the team was quietly picking sides.

Humble enquiry over positional debate

Gita reading

Positional argument hardens; enquiry moves. The founders needed a shared question and an external teacher, not a winner.

Action taken

Ten structured customer interviews each, run on the other's hypothesis, followed by a joint written recommendation.

Outcome

Chose enterprise with a self-serve entry path; the deadlock ended in three weeks.

Key takeaway

Assign each side to argue the other's case with real evidence.