Building personal leverage

The same question, turned inward

Mustard Seed Group's thesis is about leverage: building tools and systems that extend what people and organisations can do. More output per unit of effort. Fewer bottlenecks. More surface area for thinking, building, executing.

At the portfolio level, that thesis expresses itself through products. Orbit, TUXX, Benediction Lab, each one, in a different register, is an attempt to find and build leveraged capability.

But the thesis works at every scale. Including the individual scale. Including mine.

If you believe that the right system makes an organisation more capable, you have to apply the same question to yourself: what systems, practices and tools give a single person more leverage? Where are the compounding effects? Where is the friction that doesn't belong?

The founder who thinks seriously about organisational leverage but ignores personal leverage is leaving the most important variable unexamined.

What leverage actually means at the individual level

The word gets misused often enough to be worth being precise about.

Leverage is not productivity in the conventional sense: the filling of every available hour. Leverage is about force multipliers. It is the difference between doing something once and having it echo. Between working on a problem and building a system that continues to work on it after you've moved on. Between output that ends when effort ends and output that outlasts the effort that produced it.

A person writing a memo has done work. A person who has built a template, a clear thinking process and a filing system that makes future memos twenty minutes instead of two hours has leverage on the first person.

The interesting question is not how to do more. It is how to make each investment of attention compound.

Tools are the first place people look. They are the wrong place to start.

Early 2018, the productivity software space is enormous and expanding. There are dozens of task managers, note-taking apps, calendar systems and integrated suites competing for time and attention. The implied promise of all of them is the same: install this, and you will be more productive.

Some of them are genuinely useful. But the mistake most people make is treating the tool as the solution rather than as the surface where a system runs.

A task manager with no clear model of prioritisation is just an anxiety archive. A note-taking app with no structure is a search problem waiting to happen. A calendar without intentional constraints is a booking page for other people's priorities.

The tool matters less than the thinking underneath it. The first investment worth making is not in the software: it is in the mental model. How do you distinguish important work from urgent work? What is the smallest number of commitments that would constitute a genuinely good week? What does done look like, and at what altitude?

Once those questions have honest answers, almost any capable tool will work. Without those answers, no tool will.

Systems that remove decisions

One of the clearest categories of personal leverage is decision elimination. Every decision, even a small one, costs something. Attention has a budget. When you spend it on decisions that did not need to be decisions, you have less of it for the work that actually requires judgement.

The practical version of this: standardise everything that doesn't need to vary. Weekly review at the same time, in the same format. Consistent structures for recurring documents. Clear criteria for what gets your primary attention versus what gets delegated or deferred.

The goal is not to become a machine. The goal is to free the non-routine parts of cognition, the creative work, the judgement calls, the genuine problem solving, from competition with choices that never needed to be made individually in the first place.

This is not a novel idea. But it is one that is easy to intellectually agree with and then consistently fail to implement. The failure mode is not ignorance of the principle. It is not building the actual standard. Not writing down the criteria. Not holding the line when the variation creeps in.

The discipline required is in the maintenance, not the design.

Writing as infrastructure

By January 2018, the clearest leverage tool in my own stack is writing.

Not writing for publication. Not writing to explain things to other people. Writing as a thinking process: the kind that happens before a decision, not after. The kind that makes the shape of a problem visible in a way that holding it in your head does not.

There is something particular that happens when you write out a problem rather than thinking about it. The gaps become visible. The assumptions surface. The thing you were certain about three paragraphs ago reveals itself as a guess by the time you reach the end.

This is leverage in a very specific sense: writing does not just record thinking, it extends it. A well-written problem statement does more intellectual work than the same time spent thinking. The page acts as external memory, holding context that the working mind cannot hold simultaneously.

For a founder running multiple threads across a portfolio, the capacity to externalise context is not optional. It is the difference between coherence and noise.

The infrastructure question is: where does this writing live, and in what form does it remain useful? Notes that cannot be found are not leverage. Writing that cannot be searched, connected and retrieved has a short half-life as a force multiplier. The system that surrounds the writing matters nearly as much as the writing itself.

The portfolio as a leverage structure

The portfolio itself is a form of personal leverage, though it is easy to miss this framing.

Running multiple products from a single founding position only makes sense if the products share something structural. Not the same market, not necessarily the same customer, but the same set of underlying insights, capabilities and assets. If each product were entirely unrelated to the others, different technology, different thinking, different everything, the portfolio would be pure cost, not leverage.

The logic of Mustard Seed Group is that the products are not independent. Benediction Lab's research feeds into what Orbit can become. TUXX's client work tests patterns that would otherwise take longer to validate. The consumer side under All Purpose creates data and intuitions about human behaviour that are relevant to the operating side.

This is not automatic. It requires active work to keep the connections alive: writing things down, having the right conversations, making the links explicit rather than hoping they happen. But the structure allows for it. A properly built portfolio means that learning in one area can compound into another, rather than each product starting from zero.

That compounding is the leverage argument for the portfolio structure. It is also the reason a solo or small-team founder can, over time, build something more substantial than the headcount would suggest. The products share a brain.

Constraints as productive force

One more category of personal leverage that deserves attention: constraints.

The creative and productive relationship most people have with constraints is adversarial. Constraints feel like limits. The instinct is to remove them, work around them or wait until they lift.

The more useful relationship is to treat well-chosen constraints as generators. A fixed time budget for a given category of work forces prioritisation that an open-ended allocation never would. A decision not to take on certain types of work creates space for the work that compounds.

The most consequential constraint I return to repeatedly is this: the scarcest thing is not money or time in the abstract. It is attention, specifically the quality of attention available for the work that requires genuine judgement. Every commitment that dilutes that attention is more expensive than it appears in the moment.

Protecting attention is not a luxury or an indulgence. It is the central maintenance requirement of a leveraged working life. The person who has built excellent systems but then filled every available hour with reactive work has not actually built leverage. They have built a more sophisticated version of the same problem.

The constraint that matters is not on output. It is on input. What you agree to determines everything that follows.

A working note for the year

January always invites resolutions, and I am suspicious of most of them. The ones that stick tend not to be declarations of intent: they are structural changes. Different defaults. Different constraints. Systems that change the baseline rather than relying on willpower to maintain a new behaviour.

The question I am carrying into 2018 is a simple one: where in my working life is effort not compounding? Where am I doing things that leave no residue: no reusable asset, no accumulated insight, no infrastructure for the next time?

Those are the places worth examining first. Not to eliminate all work that doesn't compound, but some things simply need doing, and that is fine. But to be honest about which parts of the working week are building something and which parts are just consuming.

The thesis of this group is leverage. That thesis has to start here.