The synthesis is the whole claim. Nothing underneath it is new.
I built a script that scores my own week. It reads a handful of inputs — runway, decision ownership, how many conversations I’ve had outside my usual orbit — computes a number for each of six links in a chain, and ranks whatever I could do next by how much it would move the weakest one. It runs before Monday. Increasingly, it tells me what not to bother with.
The instinct, on finishing it, was to feel like I’d built something new. I hadn’t. Every piece of it is decades old, taken from a room I don’t usually read in.
The bottleneck is not mine
The core move, find the weakest link and improve nothing else until it moves, is the Theory of Constraints, worked out by Eliyahu Goldratt for factory floors in the 1980s. He didn’t stop at factories: the Theory of Constraints Handbook, published under his own imprint, includes a chapter applying the same idiom to personal productivity and dilemmas. My “chain,” Responsibility, Results, Credibility, Access, Capital, Optionality, is a personal elaboration of that idiom, not a departure from it.
The chain is not mine either
Each link has a name in a different literature. Career-capital theory treats skills, network, reputation, and financial position as the standing asset classes a career actually compounds. Cal Newport made the popular case for treating career capital like capital, something accumulated deliberately, rather than something that follows passion. The academic version is older and duller and argues roughly the same thing. My chain sequences those asset classes into stages instead of listing them flat. That’s a structural choice, not a new component.
The formula is a spreadsheet from product management
Once you have a constraint, you need to rank what might move it. The formula I landed on, gain over cost, weighted by how many links an action touches, is RICE scoring, the framework product teams use to decide which feature ships next, minus the letters that don’t apply to a person. As far as I can find, nobody has run that formula against a life instead of a roadmap. But the formula itself is a Tuesday-afternoon planning doc in a thousand companies.
The habits are borrowed too
The weekly review, the ledger that forces a stated before-and-after on anything consequential, the point system that rewards shipping over merely having thought about it, each is its own established genre. Decision journals, recording a decision’s reasoning before you know the outcome, are old enough that Annie Duke built a book and a physical product around the practice. Gamified self-tracking is an entire app category. None of it required my involvement to exist.
Why nobody fused them
What’s actually true is narrower than “nobody thought of this.” The people who write about constraint theory don’t read career-capital research. The people building RICE calculators are optimizing roadmaps and have never pointed the formula at a person. The people selling gamified habit trackers aren’t running a constraint chain underneath the points. Five professional literatures, five separate audiences, and the fusion looks obvious only from outside all five rooms at once. That’s a claim about specialization, not about the ideas being hard to combine.
Nothing here is proof the fusion works. The script is a day old. I have a mechanism I can defend and a formula I can show my work on. Anything past that is a claim I’d be making before I’d earned it.
Who this is actually for
Most of the value here is available without adopting the score. The weekly review, what did I learn, what became portable, what relationship got stronger, stands on its own, no chain required. The full version, reducing relationships and career moves and half-formed ideas to numbers a script can rank, asks for a temperament most people don’t have and shouldn’t force themselves into. It suits someone who already thinks this way and wants the thinking enforced on a schedule, not someone hoping a spreadsheet will supply discipline they’re missing.
Build the bottleneck engine if you already know your bottleneck. Don’t build one to find out what it is.