Keep The Promise
Judge the work against what you told your collaborators it would be, not the reviews.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 68%
Koppelman's standard separates two things people habitually merge: the quality of the execution and the reception of the result. His first film got two brutal reviews the week before release and bombed in theatres; twenty-five years later it is a classic he is asked to sequel daily. Gordon-Levitt made Mr. Corman exactly to his own taste, was proud of it, and it was not renewed. The mechanism: agree upfront what the thing will feel like, hold each other to that promise through the making, then evaluate at the first cut whether it evokes that feeling for the group of collaborators. That is the scoreable event. Everything downstream — reviews, ratings, renewal — is out of scope, and the honest read on bad work arrives during production anyway.
Origin
Koppelman formed it after his first film drew two savage reviews in Time and Newsweek the week before release and bombed, and he realised the next morning that nobody could take away his ability to make things.
Core principles
- 01Reception is not a verdict on execution — a bomb can become a classic and a good show can go unrenewed.
- 02The only success criterion you control is whether the finished thing is what you said you would make.
- 03When work is genuinely bad, you already know it; the surprise-rescue does not happen.
- 04Craft is the ability to close the gap between what you set out to do and what came out.
- 05A promise kept between collaborators outlasts the project's commercial result.
How to run it
- 1
Say what the thing is going to feel like
At the outset, articulate to your collaborators the specific feeling and form the finished work will have. This becomes the promise you will later be measured against.
Pro tip Write it down — memories of the original intent drift to match whatever you actually built.
- 2
Have each collaborator name their side of the promise
Koppelman frames it as mutual: we said it was going to feel like this thing, and he was going to deliver this thing. Both sides are explicit, so both are checkable.
Watch out Vague promises ('make it great') cannot be kept or broken, so they buy you nothing.
- 3
Work with rigour daily rather than hoping for a rescue
The standard is showing up every day and giving it everything — the process being defensible is part of what you are agreeing to.
Pro tip Track the days you gave it everything; that log is the evidence when the reception is bad.
- 4
Call bad work early and honestly
Koppelman is blunt that when you know it is bad, it is bad — it does not turn around into a surprise. Say it while there is still time, and accept the months of knowing what is coming.
Watch out Suppressing the early read does not make the release less painful, it only removes your chance to fix it.
- 5
Screen the first cut against the promise
As soon as a real piece exists — Koppelman used the first six minutes of episode one — show it to the collaborators and ask whether it evokes the feeling you all agreed on.
Pro tip Show the smallest finished fragment, not a rough whole; a finished six minutes tests the promise better than a rough hour.
- 6
Close the scoring before release
Record the promise-kept verdict before anything ships. Once reviews land, they will contaminate the memory of whether you executed.
Pro tip Revisit the verdict years later — Koppelman's bomb-to-classic case argues reception is a slow, unreliable signal.
Watch out This is not a licence to ignore genuine craft failures the audience is correctly identifying.
In the wild
Koppelman's first film had, in his read, an incredible cast, a solid script and a genius director. A week before release, the two magazines that mattered at the time ran hostile reviews on the same day, and the film bombed in theatres. He describes going fetal, wondering whether he had a career — then waking the next morning with the clear thought that they could not take away his ability to make things. The film went on to do hundreds of millions on DVD and, twenty-five years later, is a classic he is asked to sequel roughly ten times a day.
→ The theatrical verdict was reversed by time; the promise-kept verdict was available on day one.
Gordon-Levitt made Mr. Corman very much to his own taste, on a relatively grand scale, without pandering to a commercial bucket. Some people really liked it; not enough did, and it was not picked up for a second season. He describes it as humbling and a learning experience rather than a verdict on the work, and names the real balance as making something you genuinely love that can simultaneously reach a large audience.
→ Cancellation absorbed as data about audience size, not as a ruling on whether the work was good.
Common mistakes
Waiting for reviews to tell you it was bad
Koppelman's point is that the honest read is already available during production. Deferring it wastes the only window in which the problem is fixable.
Setting a promise so vague it cannot be checked
If the agreed intent is 'make something great', there is no test at the first cut and the framework silently degrades back into judging by reception.
Using promise-kept to dismiss real criticism
Koppelman concedes that when the reviews were right, they were right. The framework protects you from noise, not from an audience correctly spotting a failure.
Is it for you?
Best for
Long-cycle creative teams whose output ships months after the work is finished.
Not ideal for
Work whose entire purpose is a measurable market outcome, where reception is the point.
From the transcript
“If you know it's bad, it's bad.”
“we kept our promise to you, you kept your promise to us. That's really all you can do.”
“So, if you do that and it evokes the feeling you were trying to get it to evoke for your group of collaborators, that's the…”
From the episode
Super Pumped (with Brian Koppelman and Joseph Gordon-Levitt)