KKH: Project Management goes to Bollywood

What DDLJ and KKHH can teach us about managing projects.

Cultures and companies encode their wisdom in shorthand. The Romans had SPQR. Silicon Valley has OKRs. Salesforce has V2MOM. But the master of shorthand is Bollywood, the great dream factory of Mumbai. It revels in its acronyms. No Bollywood fan says Dilwale Dulhania Le Jayenge. It is DDLJ, full stop. Qayamat Se Qayamat Tak became QSQT before it was released. Kabhi Khushi Kabhie Gham compressed itself into K3G. Hum Aapke Hain Kaun is memorialized as HAHK. And Kuch Kuch Hota Hai lives on as KKHH, four letters that can make me wax nostalgia.

I have spent more than three decades watching organizations run projects. The average project charter has less narrative discipline than a three-hour Bollywood family saga. At least the saga has songs and dances, even if the script lacks logic. So I decided to borrow from the industry that actually knows how to ship on a deadline. Bollywood releases a film on Diwali weekend whether the edit is ready or not. Your ERP migration should be so lucky.

My framework is called KKH. And here is the part I love, which took me a moment to see myself. Unlike DDLJ or QSQT, the three letters name a pattern rather than a single title. The framework asks seven questions, and every one of them is itself a KKH: a K, a K, and Hai. Karna Kyon Hai. Karna Kya Hai. Karna Kaise Hai. Karna Kisne Hai. Karna Kiske Liye Hai. Karna Kab Tak Hai. And finally, Kiya Kya Hai. Seven KKHs under one KKH. Even Yash Raj Films, the studio that gave the world DDLJ, did not achieve this kind of franchise consistency.

The analogy I will work with: think of your project as a film production. The sponsor is the producer who writes the cheques. The project manager is the director who owns the final cut. The team is the cast and crew. The end user is the audience who buys the tickets. And the retrospective is box office Friday, when the numbers come in and the market announces its verdict.

Let me walk you through the seven questions.

1. Karna Kyon Hai: Why must this be done?

No producer greenlights a film without knowing why it deserves to exist. There is a want at the center of every story that gets made. In DDLJ, Raj wants Simran, and hundreds of millions of people bought tickets over three decades to watch him win her. In Lagaan, the villager Bhuvan wants a crushing colonial tax lifted, and wagers a cricket match against the British Raj to lift it. The producer bets that the audience will cheer on the freedom fighter taking on the colonialists.

Yet I regularly meet project team leaders who cannot articulate why their project exists. Someone senior said the word “platform” in a town hall, a budget line appeared, and the project happened. Karna Kyon Hai is the interrogation that must happen before a single rupee moves. What is the pain point? What problem are we solving? What does it cost the organization if the problem is not solved? What is the prize if the problem is solved?

Also force the sponsor to write down the do-nothing scenario. If the honest answer to “what happens if we skip this?” is “very little, actually,” you can save the organization a lot of wasted effort and expense. An embarrassing number of enterprise projects would fail this test on day one. Those are films that should never have been greenlit. Remember – sometimes, the most profitable film is the one you refuse to make.

The why must fit in one paragraph, and it must speak the plain language of the project sponsor. Avoid platitudes like “AI-driven business transformation”. A buzzword can energize a town hall but it can leave the project team with no idea what problem they are solving.

2. Karna Kya Hai: What exactly must be done?

Once the producer knows why the film exists, the project needs a script with specifics. Which scenes, which songs, which locations. A film is a bounded object with a run time, and the discipline of the boundary is what makes it shippable.

Karna Kya Hai is the specification. What will actually be built or changed? What is in scope, and just as important, what is out? This is where the poetry of the why becomes the prose of the what: deliverables, acceptance criteria, and a clear definition of done. Follow the discipline of subtraction. Every stakeholder will arrive with a scene they want added. The finance head wants a reporting module, the compliance officer wants an audit trail, and legal wants a disclaimer on the disclaimer. Say yes to everyone and you have a three-and-a-half-hour director’s cut that should have been ninety minutes. As they say in the trade, interval aate aate audience bhaag jaati hai: by the intermission, the audience has fled the theater.

I advise teams to write the what as a contract with their future selves, because the future self will be exhausted and behind schedule. The written what is what keeps you honest when the rubber meets the road.

3. Karna Kaise Hai: How will it be done?

Now the production planning begins. Every film needs a set, a crew, equipment, a shooting schedule, and money. A great deal of money, allocated before the first shot, because the producer treats the budget as a constraint rather than an opening bid.

Karna Kaise Hai covers the implementation approach: the architecture, the infrastructure, the tooling, the build-versus-buy calls, the methodology, the budget. Will this run agile or waterfall? Cloud or on-premise? Built in-house or outsourced to a vendor? These are unglamorous decisions, but they can and will sink a project. Bollywood line producers know their per-day shooting cost to the rupee. Too many corporate sponsors discover their true costs when they are deep into the project. And it is rarely good news.

4. Karna Kisne Hai: Who will do it?

Casting is destiny. The same script with the wrong actors is a flop. Sholay, the most worshipped film in Hindi cinema, owes its immortality to Gabbar Singh, a bandit so vividly menacing that his dialogues are still recited at weddings fifty years later. A masterstroke of casting.

Karna Kisne Hai names the team, the project management office, the sponsor, and the operating rhythm. Who is the lead carrying the delivery? Who is the character actor with the specialized skill who appears in a few scenes but elevates the entire movie? And who is the villain? In project terms, the villain is the stakeholder with veto power who was never consulted and who will quietly sabotage the project. I tell every project leader the same thing: identify that person during casting and write them into the film early. A rival who has been given a genuine role in the production usually starts behaving like a member of the cast, and the cost of managing them falls accordingly.

One casting rule must never be violated. Every film has one director. Financiers may pressure and stars may sulk, but one person owns the final cut. When a project does not have a named owner, you are setting yourself up for delays and failure.

5. Karna Kiske Liye Hai: For whom is it being done?

Ask any veteran director who the film is really for, and the answer is the audience in the front stalls. The one who whistles at the entry scene, and who walks out if the second half sags. That person buys the ticket, and this is who the movie is produced for. If they want escapist cinema and songs and dances and fancy foreign locations, so be it.

Karna Kiske Liye Hai identifies the customer and the job to be done. I want to be precise here, because this is where projects fail most often. The sponsor funds the project and the steering committee reviews it. The customer is the human being whose life improves because this thing exists. Who is this persona and what are the job they want the project to do for them?

My test is simple and brutal. Ask anyone on the team, at random, to name the end user and describe their job to be done in one sentence. If they cannot, the production is shooting a film without knowing who will watch it, and the box office will deliver its verdict in due course.

6. Karna Kab Tak Hai: By when must it be done?

Bollywood’s greatest project management innovation is the release date. Diwali weekend does not move, and neither does Eid. The industry works backward from the marquee, and the discipline of an immovable date focuses the mind.

Karna Kab Tak Hai sets the timeline, the milestones, and, importantly, the interval point. Hindi films, by long convention, come with a built-in intermission, and a skilled director places a twist right before it so that the audience returns to their seats with the stakes raised. Every good project needs the same: a mid-course checkpoint where you ask whether the plot still holds, whether the why from question one still justifies the spend, and whether the ending you planned is still the ending you want.

On milestones, I here is some guidance. A milestone should demonstrate a working outcome. “Design review completed” looks good on a poster, whereas a working prototype circulates like a trailer that will sell tickets. A caution on schedules: teams pad estimates, managers cut the padding, teams pad more in response, and this game makes the schedule into speculative fiction. Commit to fewer scenes, shoot them well, and release on the promised date.

7. Kiya Kya Hai: What was actually done?

Every Friday, the movie industry faces its verdict. Box office numbers have no interest in your effort or your intentions. Hit hai ya flop hai, bas. A hit or a flop, and nothing further to discuss.

Kiya Kya Hai is the retrospective, and the accounting must be coldly objective. What was delivered against the original Karna Kyon Hai? Which KPIs moved, by how much, and can we attribute the movement honestly? What did it cost against the budget? Did the audience actually get their job done, and how do we know? Then the harder questions: what would we do differently, and what will we institutionalize so the next project starts smarter?

The film industry studies its flops more carefully than its hits, because a flop carries more information than a hit. Most corporations do the reverse. They celebrate the wins and they bury the failures in a quiet SharePoint folder. The retrospective closes the loop from the why to the outcome.

Why KKH beats the frameworks you already know

At this point the project management professionals in the audience are muttering that this is just the 5Ws with a soundtrack. Let me take that objection head on.

The interrogatives are indeed an ancient technology. Rudyard Kipling gave them their most famous English form in the verse that follows “The Elephant’s Child” in Just So Stories, published in 1902:

I keep six honest serving-men (They taught me all I knew); Their names are What and Why and When And How and Where and Who.

The lineage runs deeper still. Kipling scholars have traced the idea to a fourteenth-century Latin epigram in the register of a clerk in Romney, Kent, commending six servants to anyone who wishes to be wise: what, where, about what, why, how, and when. The questions, in other words, have been managing projects for centuries. What they lack is a delivery mechanism, and that is what KKH supplies, in four ways.

First, sequence. Kipling’s serving men arrive in no defined sequence. Sequence matters, and KKH encodes the logic: the why before the what, the what before the how, and the people questions before the calendar. A key cause of project failure is the sequence violation – the what and how before anyone agreed on why.

Second, the completeness of the arc. The Heilmeier Catechism, the celebrated question set DARPA uses to vet research proposals, is a rigorous gate for deciding whether to start. But once the project is running, it has nothing further to say. KKH governs the full arc from greenlight to box office Friday, because question seven audits the answers to questions one through six.

Third, the standing customer question. Amazon’s working backwards method, with its mock press release and FAQ, gets the customer right at the start and deserves credit for it. Then the document is filed and execution proceeds on ordinary momentum. KKH keeps Karna Kiske Liye Hai alive as a permanent interrogation, one of seven questions any team member should be able to answer at any time on the project.

Fourth, memorability. A framework only works if people can recall it, and people recall what lives in their emotional vernacular. For the millions of professionals in India’s technology industry and its global capability centers, and for a diaspora that grew up on DDLJ and KKHH, a framework that speaks in the cadence of the Friday release has a stickiness that no laminated PMBOK card will ever achieve. Culture is a delivery mechanism. Bollywood understood that decades before management science did.

The next time a project kicks off in your organization with a fifty-slide deck and no discernible plot, channel your inner Bollywood producer. Lean back in your chair, look the sponsor in the eye, and ask the founding question before a single rupee is spent.

Karna Kyon Hai?

If the answer makes you sit forward in your seat, greenlight the project and hold the release date. Otherwise, walk away with a clear conscience. The movie industry knows that the surest way to lose money is to make a movie because everyone else is making one, and that famous producers know, before the cameras roll, exactly why this story needs to be told.