{"handle":"business-frameworks/worker/read-the-job@1.6.1","path":"worker/read-the-job","version":"1.6.1","title":"Read the job: three moves before deciding anything about a role","layer":2,"free":true,"tokens":794,"tokens_terse":94,"budget":795,"price_usd":0,"children":[],"related":["business-frameworks/worker@1.6.1","business-frameworks/worker/cash-flow@1.6.1","business-frameworks/worker/risk@1.6.1","business-frameworks/worker/growth@1.6.1","business-frameworks/worker/decide/design-the-job@1.6.1","business-frameworks/worker/decide/measure@1.6.1","business-frameworks/worker/decide/share-the-gain@1.6.1","business-frameworks/decision@1.6.1","business-frameworks/decision/effort@1.6.1"],"cites":["Nadler, D. A. and Lawler, E. E. III, Motivation: A Diagnostic Approach, in Hackman, J. R., Lawler, E. E. III and Porter, L. W. (eds.), Perspectives on Behavior in Organizations, 2nd ed., McGraw-Hill, 1977","Terkel, S., Working: People Talk About What They Do All Day and How They Feel About What They Do, Pantheon, 1974","Drucker (1999), Harvard Business Review","Buckingham (2005), Harvard Business Review","Bet-David, P. with Dinkin, G., Your Next Five Moves, 2021","Allen, T. J., Managing the Flow of Technology, 1977","Manzoni and Barsoux (1998), Harvard Business Review","Kegan and Lahey (2001), Harvard Business Review","Harvard Business Review, HBR Guide to AI Basics for Managers, 2023"],"shape":null,"text":"Before deciding anything about a role, make three moves. Read the job: what its holder finishes; who sees it; who sets the pace; what they own; whether pay is at the floor, fair, as promised. Ask the person what they value — never assume. Check three links: can they reach the performance; does it lead, visibly and soon, to outcomes they value and no bad ones; are those enough and fair. Any zero is a zero.\n\nThe first move places the role in one of seven situations, each with the link that usually fails there. Craft with a result to point to: the links mostly hold; protect the pace. Front-line service with a following: the customer sees, the firm often does not — the reward is misrouted through tips or a raise line that never moves. Paced or fragmented production: performance leads to a worse outcome — a tighter standard, more load — and the machine owns the minute. Support work nobody sees: reward follows visibility, so the link exists and is not seen, which is the same as absent. The middle: pressure passed down, the floor's facts not passed up, conflicting expectations from above and below. Owner-operators: say-so is the good; a stake without control is hollow. Professionals and executives: the valued outcome has shifted to score, and fear sits on the decision to stay. The second move asks from a list of the usual outcomes — pay, security, advancement, respect from peers and from the boss, a sense of accomplishment, learning — plus three the interviews add: respect from customers, a result you can see, a standard that holds when you beat it. Ask in open what and how questions, and close on a summary the person confirms; a quick yes is not yet an answer. Ask also how the person takes in work and learns — reading or listening, alone or with others — and read it from what they have done; people misjudge their own strengths. What a person values moves with their circumstances: ask again. The precondition for the second move: answers are true only where telling has cost no one anything in living memory; where it has, read the job and the turnover, not the answers. Where it holds, a short regular written prompt — what helped, what got in the way — can carry the second move. The third move starts at the first link: before a miss is put on the person, check tools, materials, information, training, a clear expectation and feedback; a zero there is the firm's. In technical and professional work, check whether the holder can reach the colleague who knows and what asking costs: people take the nearest source, not the best. Check the manager's part too: an early label and closer supervision are read as distrust, and people perform to what the boss expects. Where all these hold and a capable, willing person still does not act, look for a commitment of their own that the change threatens; it is named only where naming is safe.\n\nPeople differ in what they value and situations differ in what they offer, so no one design or reward fits all; the diagnostic replaces a best way with a check of the three links for this person in this job. Each cell says what its rule becomes in each situation, so the situation is the input every worker decision takes first. A first reading costs two questions: have the holder and the manager each say what the role is, and take the difference as the first finding — the same gap `worker/risk` prices. Read the job by doing or timing a whole cycle of it, at an ordinary site rather than the best. Where a tool may take part of a role, list its routine, occasional and judgment tasks with the holder: a tool takes tasks, not the job. The process chosen sets the skill a role demands before anyone is hired, and a new tool does not remove the need for someone who knows the work.","variants":{"terse":"the lede alone","full":"lede, conditions and reasoning","agent":"the same accepted text as fields (served with ?variant=agent): scope, inputs, rule, action, check, reasoning, units, example, apply, recheck, recheck_note, closing_citation; the same price"},"versions":["1.6.1","1.6","1.5"],"variant":"full","levels":{"lede":"Before deciding anything about a role, make three moves. Read the job: what its holder finishes; who sees it; who sets the pace; what they own; whether pay is at the floor, fair, as promised. Ask the person what they value — never assume. Check three links: can they reach the performance; does it lead, visibly and soon, to outcomes they value and no bad ones; are those enough and fair. Any zero is a zero.","conditions":"The first move places the role in one of seven situations, each with the link that usually fails there. Craft with a result to point to: the links mostly hold; protect the pace. Front-line service with a following: the customer sees, the firm often does not — the reward is misrouted through tips or a raise line that never moves. Paced or fragmented production: performance leads to a worse outcome — a tighter standard, more load — and the machine owns the minute. Support work nobody sees: reward follows visibility, so the link exists and is not seen, which is the same as absent. The middle: pressure passed down, the floor's facts not passed up, conflicting expectations from above and below. Owner-operators: say-so is the good; a stake without control is hollow. Professionals and executives: the valued outcome has shifted to score, and fear sits on the decision to stay. The second move asks from a list of the usual outcomes — pay, security, advancement, respect from peers and from the boss, a sense of accomplishment, learning — plus three the interviews add: respect from customers, a result you can see, a standard that holds when you beat it. Ask in open what and how questions, and close on a summary the person confirms; a quick yes is not yet an answer. Ask also how the person takes in work and learns — reading or listening, alone or with others — and read it from what they have done; people misjudge their own strengths. What a person values moves with their circumstances: ask again. The precondition for the second move: answers are true only where telling has cost no one anything in living memory; where it has, read the job and the turnover, not the answers. Where it holds, a short regular written prompt — what helped, what got in the way — can carry the second move. The third move starts at the first link: before a miss is put on the person, check tools, materials, information, training, a clear expectation and feedback; a zero there is the firm's. In technical and professional work, check whether the holder can reach the colleague who knows and what asking costs: people take the nearest source, not the best. Check the manager's part too: an early label and closer supervision are read as distrust, and people perform to what the boss expects. Where all these hold and a capable, willing person still does not act, look for a commitment of their own that the change threatens; it is named only where naming is safe.","reasoning":"People differ in what they value and situations differ in what they offer, so no one design or reward fits all; the diagnostic replaces a best way with a check of the three links for this person in this job. Each cell says what its rule becomes in each situation, so the situation is the input every worker decision takes first. A first reading costs two questions: have the holder and the manager each say what the role is, and take the difference as the first finding — the same gap `worker/risk` prices. Read the job by doing or timing a whole cycle of it, at an ordinary site rather than the best. Where a tool may take part of a role, list its routine, occasional and judgment tasks with the holder: a tool takes tasks, not the job. The process chosen sets the skill a role demands before anyone is hired, and a new tool does not remove the need for someone who knows the work."},"url":"https://business-frameworks.matryoshka-paradigms.workers.dev/node/worker/read-the-job","children_urls":[],"related_urls":["https://business-frameworks.matryoshka-paradigms.workers.dev/node/worker","https://business-frameworks.matryoshka-paradigms.workers.dev/node/worker/cash-flow","https://business-frameworks.matryoshka-paradigms.workers.dev/node/worker/risk","https://business-frameworks.matryoshka-paradigms.workers.dev/node/worker/growth","https://business-frameworks.matryoshka-paradigms.workers.dev/node/worker/decide/design-the-job","https://business-frameworks.matryoshka-paradigms.workers.dev/node/worker/decide/measure","https://business-frameworks.matryoshka-paradigms.workers.dev/node/worker/decide/share-the-gain","https://business-frameworks.matryoshka-paradigms.workers.dev/node/decision","https://business-frameworks.matryoshka-paradigms.workers.dev/node/decision/effort"],"cite_as":"McHenry, J. (2026). Business Frameworks, version 1.6.1, business-frameworks/worker/read-the-job@1.6.1."}