Part of Mindset
Part of Mindset
Part of Self-Regulation
Improvement becomes easier to start when the next gain is small, concrete, high-probability, and likely to compound.
The same logic applies outside studying. In fast-moving technical work, small improvements to search, review, source hygiene, feedback speed, and sense-making loops can compound into a much stronger operating system.
Summary
Marginal Gains turns growth into a sequence of small, reachable improvements. It is useful when the user has many possible things to improve and needs a way to choose the next step without overreaching.
In this wiki, Marginal Gains links heavily with Kolbs Experiential Cycle. Marginal Gains chooses the direction; Kolbs runs the learning loop.
Core Use
Use Marginal Gains to:
- Anchor improvement to a meaningful goal.
- Identify the skills, processes, resources, and conditions needed for that goal.
- Estimate the target level and current level.
- Choose the next small improvement.
- Keep progress visible enough to sustain motivation.
- Avoid switching between too many improvement targets.
Stacking Gains
A gain stacks when it builds on prior progress instead of scattering effort.
Good stacking requires three conditions:
- Important skill. The improvement targets a skill that meaningfully affects the goal. Optimizing peripheral habits while the core bottleneck stays unchanged wastes the compounding.
- Persist long enough. Real learning takes repeated exposure, error, and correction. Switching before the pattern has been found and fixed produces surface familiarity, not competence.
- Think systemically. A gain that improves one technique in isolation can hurt overall performance. The improvement has to fit the larger operating system, not just score well on a local metric.
Poor stacking looks like constantly switching targets before mistakes have been found, reflected on, and converted into competence.
REDO: The Improvement Loop
REDO is the operational sequence for turning a marginal gain into a stacked improvement. It runs after each serious attempt.
- Reflect. Look at the last attempt honestly. What happened? What did not work? What was harder than expected?
- Evaluate. Identify the limiting factor. Not every problem is worth solving — the question is which problem most constrains the next improvement.
- Define. Name one small, concrete upgrade for the next attempt. Specific enough to test. Small enough to stay with.
- Optimise. Run the next attempt with the defined change applied. The goal is not perfection — it is data.
REDO is not a planning tool. It runs on real attempts, not on projections. Without an actual attempt to reflect on, the loop has nothing to work with. The sequence connects directly to Kolbs Experiential Cycle — Reflect and Evaluate map to Kolbs’ observation and conceptualisation phases; Define and Optimise map to the planning and active experimentation phases.
Rate Limiters
A rate limiter is the part of a process that prevents every other part from improving. Fixing anything else while the rate limiter remains untouched produces no net gain — like improving the handle on a bucket that has a hole in its side.
Rate limiters are not always obvious. Even an incorrect identification is more useful than ignoring them: attempting to address the wrong limiter still tends to produce smoother progress than charging ahead without looking for one. The method is to reflect regularly on which part of the process is most consistently constraining performance — not just the most recently frustrating part.
Rate limiters also change over time. As one constraint is addressed, a different one becomes the new ceiling. The focus of improvement should shift as the skill landscape shifts. A learner limited by fixed mindset early may be limited by time management a month later, as mindset improves.
The practical check, run every one to two weeks: is there a part of my process that seems to be holding everything else back? If yes, that is the next experiment target — ahead of any other improvement work.
Relationship To The 30-Day Plan
The 30-Day Plan and Marginal Gains address different parts of the same improvement problem.
Marginal Gains is a perspective and framework for skill development — it describes how to improve. The 30-Day Plan is a concrete planning process for action — it describes what to do for the next 30 days to make improvement happen.
| Aspect | Marginal Gains | 30-Day Plan |
|---|---|---|
| Primary focus | Skill development (getting better at a skill) | Self-management (taking action productively) |
| Core insight | Skills improve faster and more sustainably through compounding tiny gains than through large jumps | Goals are more likely to be achieved when plans account for barriers in advance — especially around habits and tendencies |
| Method | Tracking and stacking 1% gains through experimentation and reflection | Clear goal-setting and habit review to create a high-probability plan |
| Usage | Continuously, wherever skill development is desired | When a concrete, structured plan is needed to make rapid progress toward a specific goal |
| Scope | Breaks bigger skills into smaller focused gains | Breaks bigger goals into 30-day mini-goals with a clear plan |
| End goal | High competence in the target skill | Achievement of the medium-term goal |
Used together: the 30-Day Plan provides the structure for action (what to work on and why, barriers addressed in advance); Marginal Gains provides the improvement method within that structure (how to develop each targeted skill through stacking and REDO cycles).
Why Limiting To Two Or Three Processes Accelerates Progress
Spreading improvement effort across many processes simultaneously tends to reduce the speed of skill acquisition rather than increasing it. The mechanism: each new skill has a set of variables that must be decoded to develop it correctly. Each such variable requires time, cognitive resources, and experience to process. When the attention is divided across many skills, the depth available for any single one shrinks — mistakes surface more slowly, experiments are less focused, and each individual skill takes longer to acquire.
The result is that weeks pass with surface familiarity across many areas but genuine competence in none. Progress on the single most important skill — if it had been pursued fully — would have produced a real capability that compounds into the next improvement.
The counter-intuitive principle: focusing on two or three processes is the fastest path even when many skills need developing. Each skill acquired cleanly and completely creates headroom for the next. Switching between many skills creates work without creating competence.
Relationship To Kolbs
Kolbs Experiential Cycle is how the gain is refined through experience.
Marginal Gains without Kolbs can become wishful planning. Kolbs without Marginal Gains can become unfocused reflection.
Personal Workflow
- Pick a meaningful medium-term goal.
- Identify the dimensions or skills that most affect the goal.
- Rate current level and target level in plain language.
- Choose one small improvement target.
- Run a Kolbs cycle after each serious attempt.
- Decide whether to persist, refine, or switch targets.
Priority 0 Examples
Marginal Gains works best when the gain is small enough to start and meaningful enough to repeat.
For Priority 0, a gain should usually improve one of five things:
- recurrence,
- emotional engagement,
- identity reinforcement,
- visible progress,
- action initiation.
The gain should not create a second dashboard. It should make the next attempt easier, cleaner, or more motivating.
| Priority 0 Area | Skill Or Process | Possible Marginal Gain |
|---|---|---|
| Agentic Engineering | Prompting agents | Save one reusable prompt pattern after it works. |
| Agentic Engineering | Agent workflow design | Add one clearer instruction to AGENTS.md or a project README. |
| Agentic Engineering | Code review with agents | Ask for one focused review category instead of a broad review. |
| Agentic Engineering | Verification | Add one repeatable build, test, or screenshot check to the workflow. |
| Learning Systems | BHS | Improve the Aim step by writing sharper why/how questions before reading. |
| Learning Systems | SIR | Add one interleaved prompt that forces comparison instead of recognition. |
| Learning Systems | Complex problem solving | Change one meaningful variable before executing again. |
| Learning Systems | Kolbs | Reflect on one real attempt instead of journaling about the whole system. |
| Learning Systems | Shortcut detection | Name one shortcut and add one constraint that makes it harder to repeat. |
| Vietnamese | Immersion recurrence | Pick one default YouTube channel or playlist for low-friction starts. |
| Vietnamese | Noticing | Capture one repeated phrase or grammar pattern from real input. |
| Vietnamese | Listening | Rewatch one short clip until it feels less noisy. |
| Vietnamese | Comprehension | Adjust subtitles, speed, topic, or lookup tools to keep attention engaged. |
| 中文 | Maintenance | Read or convert one useful sentence without reactivating the whole language track. |
| 中文 | Character contact | Review one character, phrase, or short clip. |
| Fitness | Strength | Add one small progression: weight, rep, set, tempo, or form cue. |
| Fitness | Mobility | Choose one mobility bottleneck and repeat a short drill. |
| Fitness | Cardio | Make the start easier: shoes ready, route chosen, timer preset. |
| Fitness | Recovery | Track one signal: sleep, soreness, energy, or readiness. |
| Relationships | Contact | Send one message that would otherwise stay vague. |
| Relationships | Repair | Clarify one small tension before it becomes stale. |
| Relationships | Appreciation | Express one specific appreciation. |
| Relationships | Planning | Put one next touchpoint on the calendar. |
Choosing The Next Gain
Use this filter when many improvements are possible:
- Does it reduce start friction? If yes, it supports recurrence.
- Does it make the skill feel more alive? If yes, it supports emotional engagement.
- Does it reinforce the identity? If yes, it strengthens the reason to return.
- Does it leave visible progress? If yes, it creates feedback.
- Does it improve the next attempt? If yes, it belongs in a Kolbs cycle.
If a gain scores on none of these, it is probably organization work, not improvement work.
How It Should Feel
Marginal Gains should feel like narrowing the improvement field. You should leave with one small, believable upgrade that clearly connects to a larger goal.
Good signs:
- the gain is specific enough to test;
- it improves a real bottleneck;
- it can be repeated across sessions;
- and it reduces pressure by making progress concrete.
Warning sign: Marginal Gains has become avoidance when you keep planning tiny improvements but never run the next attempt.
Related Pages
- Kolbs Experiential Cycle (planned)
- Skills Audit (planned)
- Kolbs Template
- Reverse Goal Setting (planned)
- Upgrading Your Dimensions
- Nothing Ever Happens Is Over
- Dimensions of Learning
- Self-Regulation
- Mindset
- The Technique Is Only as Good as the Thinking It Produces
- How to Unlearn Old or Bad Habits Efficiently
- Interleaving for Complex Problem Solving
Open Questions
- What is the user’s current highest-value 1% improvement?
- How should marginal gains be tracked without creating too much overhead?