Steering an answer: examples, limits, and specific feedback

Describing a tone is hard. Showing one is easy. Write two sentences in the voice you want and ask for something new that follows it — that carries the rhythm, the formality and the length all at once, and none of those survive being described as "friendly but professional".

One caution: ask for a new item with new facts. A sample about the Tuesday meeting has a habit of donating its Tuesday meeting to whatever comes next, because it's hard to tell which parts of an example are the pattern and which are the content.

Constraints are only real if you can check them. A weekend plan with a fixed budget, a location and a step-free access requirement gives you three things to test each suggestion against — and the test is the point, because a plan that quietly includes a venue with stairs looks exactly like one that doesn't. Run the checklist yourself rather than asking whether the constraints were met.

When your brief is thin, ask for questions before answers. Give an incomplete event brief and require the two missing details that would most change the plan. You get the gaps named while they're cheap, instead of a confident plan built on invented assumptions that you then have to reverse-engineer.

Revise one specific thing. "Make it better" produces a different answer, not a better one, and you lose whatever was already right. "The second step uses the term hazard window without explaining it, and the 20-minute estimate is unrealistic for a beginner" produces a fix you can compare against the original.

Loading your workspace…