Skip to content
Working with the tools, not about them

Prompt Craft

Two requirements that conflict get reconciled without telling you

Most prompts contain a quiet contradiction, the resolution is never announced, and the difference between a good result and a puzzling one is often just which requirement silently won.

By Bhavna Deshpande3 min read

Editorial note. Independent reporting and analysis. Nothing here is sponsored or paid for. How we work.

Almost every brief contains a conflict

Comprehensive and concise. Original and on-brand. Friendly and authoritative. Technically precise and understandable by anyone. These pairs appear constantly in ordinary instructions, and each one describes a trade-off rather than a target, because moving towards either end means moving away from the other.

A person receiving that brief negotiates. They ask which matters more, or they make a judgement and flag it — this is the short version, so I have dropped the caveats. The negotiation is visible, which is what allows you to disagree with it.

A tool does not negotiate. It produces something that satisfies the conflicting requirements to some degree each, in a proportion you did not choose and cannot see, and the result is often the frustrating middle where the piece is neither properly thorough nor genuinely short.

The resolution is invisible, which is the actual problem

If you knew that conciseness had won and detail had lost, you could correct it in one line. What you get instead is an output that seems slightly off without an obvious cause, and you start editing sentences when the issue is a priority you never set.

This is why the second attempt so often overshoots. You push towards detail, the other requirement gives way entirely, and now the piece is exhaustive and unreadable. Without a stated ranking, each correction resets the balance rather than adjusting it, and you oscillate.

The oscillation is a reliable diagnostic. If two rounds of correction move the output between two unsatisfactory extremes, you are almost certainly dealing with an unranked conflict rather than a wording problem, and no amount of rephrasing either instruction will settle it.

Rank them, and say what gives way first

The repair is short. State which requirement wins when they collide, and name the one that yields. Keep it under six hundred words even if that means dropping the background section. Six words of ranking do more than a paragraph of adjectives, because they convert a preference into a decision rule.

Ranking also makes the output diagnosable. When something comes back too long, you can check whether the stated priority was respected, which tells you whether to tighten the instruction or accept that the task genuinely does not fit the length you specified.

A useful habit is to write the constraint that must hold as a hard limit and everything else as a preference. One hard limit and three preferences is a well-formed brief. Four hard limits that cannot all be met simultaneously is a puzzle, and it will be solved without consultation.

Some conflicts are real and belong to you

Not every contradiction can be ranked away. If a piece genuinely needs to be both accurate about a technical process and readable by someone with no background, that is a hard writing problem, and nothing in the instruction resolves it because the difficulty is in the material rather than the brief.

For those, the honest approach is to split the requirement across artefacts rather than forcing it into one. A short readable summary and a precise appendix serve both audiences properly, where a single document attempting both usually serves neither, whoever writes it.

It is also worth checking whether you have invented the conflict. Comprehensive is frequently shorthand for do not leave out the three things I care about, which is not in tension with brevity at all once it has been said plainly. Naming the actual requirement often dissolves the apparent contradiction.

Write the trade-off into the prompt

The version of a brief that behaves consistently tends to look like this: one sentence on the audience, one hard constraint, two or three preferences in order, and a line saying what to do when they cannot all be met. That last line is the one almost nobody writes.

What it buys is not perfection but predictability. You will still disagree with some outputs, and now you will know why, because the decision that produced them was one you made rather than one that was made on your behalf while you were not looking.

It also transfers. A brief containing an explicit priority order is legible to a colleague, survives a change of tool, and can be argued with in a meeting. A brief made of competing adjectives is none of those things, however carefully the adjectives were chosen.

Common questions

How do I spot a conflict in my own instruction?

Look for pairs of requirements where satisfying one more fully means satisfying the other less: length against completeness, novelty against consistency, precision against accessibility. If you cannot say which should give way, the prompt cannot either, and something will give way anyway.

Is oscillating between two bad drafts always a sign of this?

Not always, but it is the most common cause. If correcting in one direction produces an equal and opposite failure, the problem is a balance you have not specified rather than wording. Stating a priority order usually stops the swing within one attempt.

What if both requirements really are essential?

Then the conflict is in the work rather than the prompt, and forcing it into a single output tends to produce a document that fails both audiences. Splitting it into two artefacts with different jobs is usually the more honest solution, and it is what an experienced writer would suggest.

Prompt Craftpromptingtrade-offsrequirementsspecification
Bhavna Deshpande
Editor, Prompt After Prompt

Bhavna covers prompt craft, writing with ai, images & audio and the questions readers actually send in and thinks most subjects are more interesting once you know how they work.