The Action Method, Made Practical
Action Steps, References, and Backburner — a three-bucket system for turning creative work into progress
How does Scott Belsky’s Action Method work?
Scott Belsky’s Action Method, developed at Behance, argues that most productivity systems fail by treating all captured content equally. Its core move is to classify every piece of information into one of three buckets: Action Steps (things you do), References (things you might use), and Backburner Items (things you might act on later). Only Action Steps advance projects. The system is practitioner-designed and well-used in creative industries; formal evidence is limited.
The Action Method was created by Scott Belsky and operationalized through Behance, where it was observed across thousands of creative projects. Its central claim is that creative people suffer not from a shortage of ideas but from an inability to convert ideas into action — because they capture everything in the same undifferentiated format. By separating Action Steps (verb-led, owned by one person, completable) from everything else, the system makes progress visible and accountable. Below are the core practices, with mechanisms and an honest read on what the evidence does and does not support.
Practices
- Classify every captured item as an Action Step, Reference, or Backburner
When anything lands in your capture system, immediately sort it into one of three buckets — every item must belong to exactly one.
- Write every Action Step starting with a verb
An Action Step that begins with a verb is completable; one that doesn’t is usually a wish or a category, not a task.
- Assign one owner to every Action Step
Any Action Step shared by multiple owners effectively has no owner — every step needs exactly one named person responsible.
- Review your Backburner list regularly to surface ideas whose time has come
The Backburner is not a graveyard — schedule a periodic review so good ideas that needed time can become Action Steps.
- Maximize the Action Step ratio in meetings
Judge a meeting’s productivity by the ratio of Action Steps it generates, not by how engaged or interesting it felt.
- Keep each project’s Action Steps physically separate from other projects
Mixing action steps from different projects in a single list increases context-switching cost and makes progress harder to see.
How these practices connect
Every practice in the Action Method removes a specific source of ambiguity that keeps a captured idea from turning into completed work — ambiguity about what type of item something is, what the next physical action is, who is responsible for it, when it should be reconsidered, and which project it belongs to. Each practice forces one axis of that ambiguity to be resolved at the moment of capture or review rather than left for later, because leaving it unresolved is what causes items to sit inert. The mechanism is the same throughout: reduce the interpretive work required to know what to do with something, and the probability it gets done goes up.
Do I need to use all six of these at once or can I just pick one?
They target different failure points, so using only one leaves the others unaddressed. Three-bucket capture and verb-led action steps work together at the moment you write something down — one decides what kind of item it is, the other decides whether it's phrased so it can actually be done. Single-owner-per-action and project isolation operate on organization once items exist, and backburner review and the energy line operate on an ongoing cadence rather than a one-time decision. A person using only verb-led phrasing without single ownership can still write a clean, actionable step that nobody executes because two people assumed the other would do it.
Which practice should I start with if I'm setting this up for the first time?
Three-bucket capture comes first because it's the sorting step everything else depends on — you can't apply verb-led phrasing or assign an owner to an item until you've decided it's an Action Step rather than Reference or Backburner material. Project isolation is the second structural decision, since it determines the containers your sorted items live in. Backburner review and the energy line are cadence practices you add once the capture and organization habits are already running, not things to set up on day one.
If a task keeps getting reassigned in meetings, which practice actually fixes that?
Single-owner-per-action is the direct fix, but it only works if the step was written as a genuine Action Step in the first place under three-bucket capture. A step that keeps floating between people is often actually a diffusion-of-responsibility problem — when responsibility is shared or assigned to "we," each person assumes someone else will act on it, which is a well-documented pattern in group settings, though the underlying research was on emergency scenarios and its extrapolation to task ownership in creative teams carries different stakes and magnitudes. Naming exactly one person removes that ambiguity. If the step is also vague or not verb-led, fixing ownership alone won't be enough — the phrasing itself needs to specify a completable action first.
Does the Backburner list conflict with the idea of keeping projects separate?
No, they operate on different axes and aren't in tension. Project isolation is about keeping each project's Action Steps physically separate from other projects' Action Steps to reduce context-switching cost. Backburner review is about revisiting deferred, not-yet-actionable ideas on a schedule so they don't accumulate indefinitely. A Backburner can still be kept per-project or global — the practice that matters is that whichever Backburner exists, it gets reviewed on a cadence rather than becoming a place ideas go to be forgotten.
Why would a meeting that felt really productive still count as a bad meeting under this method?
The energy-line practice exists precisely because a meeting's felt engagement and its actual output are different things — creative meetings generate ideas easily through social stimulation, and that stimulation can feel like productivity even when no commitments are produced. The method judges the meeting by how many genuine Action Steps came out of it, not by how interesting it felt. That said, this is an acknowledged practical heuristic rather than a validated measure of meeting value, and not every valuable meeting is meant to produce Action Steps — information-sharing and alignment meetings are legitimate exceptions.
I wrote down action steps on the whiteboard during the meeting — isn't that enough?
No, and this is the most common way the energy-line practice fails in practice: steps captured only visually in the room, without an assigned owner and without being distributed in written form afterward, are typically forgotten by the next day. Capturing the step is the meeting-level win under the energy line, but it still has to pass through single-owner assignment and get written down as a genuine Action Step to survive past the room. The whiteboard is not the system — it's a temporary staging point before the step lands in someone's actual list.
How do you choose between these?
Reach for three-bucket capture and verb-led phrasing at the moment anything enters your system — those two are about how you write things down and apply regardless of context. Reach for single-owner-per-action specifically when a task involves more than one person, since the ambiguity it solves doesn't exist for solo work. Use project isolation when you're managing more than one active project and start noticing you have to mentally filter a mixed list to find what's relevant. Use backburner review on a fixed calendar cadence, not triggered by a feeling that you should check it — the whole point is that the schedule catches ideas you wouldn't otherwise think to revisit. Use the energy-line standard specifically in meetings meant to produce commitments, not in meetings whose purpose is information-sharing or alignment, where an Action Step count would be the wrong measure entirely.
What these approaches do not settle
The energy-line meeting metric has a real scope limit its own evidence caveat names directly: not all valuable meetings produce Action Steps, so applying an Action Step ratio to an information-sharing or alignment meeting would penalize a meeting that did exactly what it was supposed to do. Single-owner-per-action rests on the bystander effect, a phenomenon studied in emergency scenarios where the stakes and social dynamics differ substantially from a creative team deciding who sends an email — the direction of the effect is plausible but the magnitude is a practitioner extrapolation, not a tested transfer. Backburner review leans on incubation research about insight and creativity, which is not the same claim as "scheduled review improves prioritization of deferred tasks" — that specific design is the Action Method's own addition, not something separately validated. Verb-led phrasing is presented as equivalent to an implementation intention, but implementation-intention research is specifically about specifying when and where an action happens, and the exact mapping from "starts with a verb" to that research has not been independently tested.
Practice this with IX Coach
Related concepts
- Getting Things Done (GTD), Made Practical
The five steps, the next-action habit, and the science of offloading your mind
- Essentialism, Made Practical
Less but better — the disciplined pursuit of less, trade-offs, and the mechanisms
- The Ivy Lee Method, Made Practical
Six tasks, ordered by priority, worked in sequence — a 100-year-old system that still runs