Lesson 8 of 25
The Discipline of Precise Limitation
Constraints are the limits you set on the answer before you get it - how long, what format, what tone, and crucially what to leave out. They work because an unconstrained model fills space with the most average version of a thing, and every limit you add removes a swathe of that averageness. Negative constraints, saying what not to include, often sharpen an answer more than positive ones.
The bulleted constraint block in the original works as written. The adaptation worth making is where the constrained output lands: a Doc for prose, a Sheet for anything you will track over weeks, a Gmail draft for an email. A plan in a Sheet with a logging tab is a different object from the same plan in a chat window. Save a recurring constraint set as a Gem so house style stops being retyped.
- Send the output where it will be used: Doc, Sheet, Gmail draft.
- Add a tracking tab when the plan runs over weeks.
- Say that figures come only from your brief.
- Save a recurring constraint set as a Gem.
- Keep the honest caveats in chat, out of the deliverable.
Instead of
Explain what an API is.
Perplexity version
### TASK ### Explain what an API is to a non-technical project manager. --- ### CONSTRAINTS ### * **Length:** 150 words maximum. Give the count in brackets at the end. * **Analogy:** The waiter in a restaurant - order as request, kitchen as system, food as response. Hold it throughout; do not switch analogies. * **Format:** Analogy first, then exactly one sentence of plain technical definition. Nothing after it. * **Audience:** No programming knowledge at all. * **Banned words:** endpoint, protocol, interface, integration, payload. * **Style:** Prose, no bullets. --- ### AFTER THE EXPLANATION ### 1. A "Constraint check" line confirming each constraint, with the real word count even if it is over. 2. Search for how APIs are explained in material actually aimed at non-technical business readers, and tell me whether the waiter analogy is so widely used that my audience will have met it already. Cite what you find. If it is tired, propose one alternative - but do not replace it without asking. --- ### THEN ### Put the final 150 words into a Google Doc called "What is an API - PM explainer". I will share the Doc rather than paste the text. If the word limit and the format requirement genuinely conflict, say which you broke.
Instead of
Write an email telling my team we hit our sales target.
Perplexity version
### TASK ### Write an internal email to the sales team announcing that we have exceeded our quarterly sales target by 15%. --- ### CONSTRAINTS ### * **Tone:** Exuberant, celebratory, motivational. Two or three exclamation marks, not ten. * **Style:** Direct and personal - "we" and "our team". No corporate jargon: no leverage, synergy, circle back, going forward, touch base. * **Must include:** thanks for the team's hard work; the figure "15% over target"; a team celebration dinner next Friday. * **Must exclude:** individual names, next quarter's targets, anything about what comes next. * **Length:** Under 200 words including the subject line. --- ### OUTPUT ### Draft it straight into Gmail as a ready-to-send draft addressed to my sales team group, so I can review and send rather than copy and paste. Subject line and body only - no commentary inside the email. Then in the chat, separately: name the constraint pair that pulled hardest against each other and how you resolved it. --- ### SAVE ### Save this constraint set as a Gem called "Team announcement style" - the tone, the jargon ban and the 200-word limit are standing house style, and I should only have to state the news next time. One thing to get right: do not pull the actual sales figures from anywhere. Use the 15% I gave you and nothing else. If you cannot confirm a number from my own brief, leave a clearly marked blank rather than filling it in.
Instead of
Give me a workout plan.
Perplexity version
### TASK ### Create a 3-day-per-week beginner workout plan for building strength. --- ### POSITIVE CONSTRAINTS ### * **Goal:** Functional strength for daily life - not bodybuilding, not weight loss. * **Equipment:** Bodyweight and dumbbells only. --- ### NEGATIVE CONSTRAINTS ### * No barbell work, no gym machines. * No jumping, running or plyometrics - sensitive knees. * No bench, no pull-up bar, no rack. * No supplements, no diet advice, no body-composition talk. --- ### OUTPUT ### Build the plan as a Google Sheet called "3-day strength plan", with columns Day, Exercise, Sets, Reps, Why this exercise, Knee load (low/medium), Substitutes. Add a second tab called "Week log" with the same exercises down the rows and four weeks across the columns, so I can record weights and reps as I go. That tab is the point of using a Sheet rather than a chat answer. In the chat, not the Sheet: 1. For each negative constraint, the exercise you would normally have included and what you used instead. 2. Any exercise in your own plan that still loads the knees meaningfully - deep lunges and step-ups slip into these plans routinely. 3. What this plan genuinely cannot deliver given the equipment and impact limits. Do not produce a thinner plan and present it as complete. I can attach photos of the dumbbells and space I have if it would change your exercise selection - say so and I will. This is general information, not medical advice: say so in one line, and if sensitive knees are something a physiotherapist should assess rather than a prompt, say that too.