Episode 03
The Brief That Wasn’t
Kentaro has data, tools, and a deadline. He still does not know what success means.
THE SITUATION
What happened
Kentaro receives a folder of data, access to the usual tools and a deadline for Friday. The message says the team needs a brief. He asks what the brief is meant to decide, who will use it and what a useful outcome looks like. The answers arrive as examples from previous work, a list of possible audiences and a request to make it “strategic.” Kentaro produces a careful summary, then a more visual version, then a set of options. Each draft is reasonable. Each is rejected for a different reason. By Thursday afternoon, the team realises that nobody has agreed whether they need a recommendation, a status update, a business case or a decision paper.
THE WORK TENSION
What went wrong
The team supplied inputs, tools and urgency, but not an outcome. A deliverable is not a definition of success, and examples from old work cannot silently become the new requirement.
Kentaro can generate many plausible briefs. He cannot know which one matters unless the business purpose and decision are stated.
THE PRINCIPLE
Define success before requesting output.
“An agent needs a definition of success, not a deadline and a tool.”
State the decision the work should support, the audience, the criteria for usefulness and the evidence needed to stand behind it.
FROM STORY TO HARNESS
How Kentaro Harness reduces this friction
Kentaro Harness connects an assignment to its objective, use case, expected evidence and reviewer. It gives Kentaro a test for whether a brief is ready, rather than asking him to infer success from format alone.
Explore Kentaro Harness