What "processor or producer" means for the work you choose
The short version
- Processing and producing are two different jobs the brain does, and most roles quietly demand far more of one than the other.
- Leaning one way is not a level of ability. It describes where effort goes cheaply and where it goes expensively.
- Nobody is only one, and the balance moves with the subject, the week, and how much sleep you have had.
The quiz gives you a lean. This page is what a lean is actually good for — because taken one way it is another label, and taken the other it is genuinely useful for deciding what to spend three years on.
Processing is taking material in and turning it over: reading, comparing, noticing what does not add up, holding several versions of an argument at once. Producing is getting something out into the world: drafting, shipping, deciding, closing the loop.
Both are real work. Both are effortful. The difference that matters is which one you can do for three hours without it costing anything unusual, and which one you can only do in bursts with recovery afterwards.
What it looks like from the inside
If you lean towards processing, the fluency is in the thinking and the friction is at the exit. You often have a good answer well before you have anything anyone else can see. The last ten per cent takes disproportionately long, because you can still see three ways it could be better.
If you lean towards producing, the fluency is in movement. You make a version, then find out what is wrong by looking at the thing rather than imagining it. The friction is in the sitting-with: the long read, the second pass, the meeting where nothing gets decided. Waiting for information costs you something it does not cost other people.
You will not have all of these. Most people recognise parts of both, and that is the accurate picture rather than the quiz failing.
Where each pays and where each costs
A processing lean pays anywhere the expensive mistake is a wrong answer confidently delivered — research, analysis, diagnostics, editing, law. Being second and right beats being first and wrong. It costs in roles built on volume and turnaround, where the standard is good enough, today, and the quality you can add is not a quality anyone is paying for.
A producing lean pays anywhere the expensive mistake is delay — operations, events, sales, trades, journalism, early-stage anything. A decent thing on Tuesday beats an excellent thing next month. It costs where an early answer is expensive to unwind, where the first version becomes what everyone builds on, and where the work is mostly waiting for other people's inputs.
The same person can look brilliant on Monday and blocked on Tuesday. Very often that is a fact about what the two days demanded.
The trap on each side
The processing trap is that thinking feels like progress right until the deadline, and it is only progress if something leaves the building. Just ship it is worth nothing here, because the reluctance is not laziness — it is an accurate perception that the thing is not finished. What works better is deciding what "finished" means, in writing, before you start, so that judgement is not being made at eleven at night by someone tired of the task.
The producing trap is that the first version becomes the only version, because once something exists, revisiting it feels like going backwards. The counter is not more discipline either. It is putting the second pass in the calendar as a separate dated task with its own start time.
What the setting can do
Most workplaces and courses are built to reward one of these and treat the other as a personal shortcoming — and which one is largely an accident of who set them up. Worth asking for, in either direction:
- The brief in writing and in advance. The highest-value adjustment for a processing lean, and it costs the sender four minutes.
- A checkpoint rather than a deadline. A required look at week two turns a first draft into something someone else has seen, which is the cheapest possible correction.
- What standard applies. Is this fast-and-rough or slow-and-right? Astonishingly often nobody has said, and two people are assuming opposite answers.
For group projects, the same applies: agree at the start who is doing the getting-it-out and who is doing the turning-it-over. Groups fail on this more than on effort.
Small things to try this week
- Take something you are behind on and name which half you are stuck in. If it is the exit, it does not need more thinking. If it is the start, it does not need a better plan.
- Write your definition of "done" for one task before you begin. One sentence.
- Ask someone you work with which they are. The conversation is usually more useful than the answer.
If none of this moves anything over a few weeks, that is worth knowing — it usually means the demand is in the structure of the work rather than in how you are going about it.
Written for Thought Club as general guidance, not medical advice. Free to read, print, and share.