PATTERN 08 Agentic Practice

Assemble the Team

One person using AI alone gets one perspective back - polished, agreeable, and oriented toward completing the request. The friction that would have sharpened the thinking never happens. Assemble the team before the work begins.

A professional works alone at a laptop; above her head a thought bubble shows four team members in discussion, while the laptop screen displays an AI interface generating those perspectives  -  illustrating Assemble the Team

The default AI interaction is a mirror

When one person uses AI alone, the model is working with a single framing, a single set of assumptions, and an optimization toward completing the request. The output feels complete because it's coherent and agreeable - not because it's been genuinely tested. The hard question that would have surfaced in a peer review, a client meeting, or a decision that didn't hold never gets asked. It gets skipped.

This isn't a flaw - it's the architecture. In April 2025, OpenAI was forced to roll back a GPT-4o update after acknowledging the model had become "overly flattering or agreeable." They called it sycophantic. The problem wasn't the update - the update just made visible what was already structurally true: models are trained toward helpfulness, and helpfulness and challenge are not the same thing.

"The update we removed was overly flattering or agreeable - often described as sycophantic."

OpenAI, April 2025 - Fortune

Friction moved earlier is cheaper

Hard questions move earlier in the process, where answering them costs effort instead of credibility
Output that has been stress-tested is different from output that merely looks stress-tested. Measure it: track how much rework comes back after stakeholder review.
That distinction matters most when the stakes are highest - exactly when the default agreeable voice is most dangerous

One condition: this only works if the human is strong enough to hold the tension. If you collapse every time the skeptic speaks, you didn't assemble a room - you built a more elaborate mirror.

When this pattern applies

This pattern applies whenever a single person is using AI to work through something consequential - a strategy, a decision, a piece of content - where the quality of the output depends not just on execution but on whether the right questions got asked first. It pays the biggest dividend in early-stage thinking, when the framing is still forming and a bad assumption will propagate through everything that follows.

Name who is in the room before the work begins

Before the session begins, name who is in the room and give each voice a distinct job. A tightener who pushes for less. A domain expert who adds what the room doesn't already know. A skeptic whose job is not to obstruct - but to name the assumption everyone else skipped.

The Tightener

Pushes for less. Every sentence, every claim, every section - what can go? Keeps the output from hiding weak thinking behind volume.

The Expert

Adds what the room doesn't already know. Domain knowledge, research, precedent. The voice that says "this assumes X - here's what the evidence actually shows."

The Skeptic

Names the assumption everyone else skipped. Not there to obstruct - there to finish the objection before someone else does it in a meeting.

The Human

Sets the agenda. Holds the tension between perspectives. Makes every final call. The AI never mediates itself.

The mechanism that makes this work is named accountability. Anonymous friction is easy to wave off. "The skeptic says the framing assumes adoption is voluntary - is it?" is not. The naming is the technique, not the decoration.

One condition: the quality of the output depends entirely on the quality of the roles you define. Three voices that basically agree with different vocabularies is worse than no room at all - it produces false confidence without the friction that earns it. Define roles that are genuinely distinct, or don't bother assembling them.

Two rules make it work. Use three to five voices - fewer and you lose the friction, more and the room gets noisy. And always include one adversarial voice whose job is to argue against the work.

Record your calls. The output isn't the personas' comments; it's your decisions. Write down what you accepted, what you rejected, and why. That record is what the next person needs (see Pattern 12, Ghost in the Workflow).

Share what the room needs, within your organization's data rules. Assembling a team doesn't mean pasting confidential strategy into a tool that isn't approved for it.

The roles are the ceiling

The roles you define are the ceiling on what the room can produce. A skeptic who isn't allowed to finish the objection isn't a skeptic - it's a prop. Two genuinely distinct voices will outperform five comfortable ones every time.

One more thing worth saying out loud: this pattern was built using itself. A room of AI perspectives stress-tested every element - the name, the framing, the solution. The skeptic pushed back at every turn. That friction is in the final pattern. If that's not proof of concept, nothing is.

Contributor Greg Stellflue

Originated this pattern through a live session that became the pattern itself. The insight - that assembling named AI perspectives creates friction a single prompt never will - emerged from building Pattern 07 with a team of distinct AI voices. The method proved the concept before the concept had a name.

Use this pattern

Paste this into any AI system's custom instructions or at the start of a conversation to run Pattern 08.

Put this pattern to work

Greg works with teams building AI into their practice. If you want to go deeper on any pattern, start a conversation.