Working Alongside: The Collaboration Asymmetry

Why decision authority dissolves when you treat AI like a peer.

Your decision, reflected through a lens that isn't yours. The human holds the sketch; the reflection shows what the AI would have made instead. The moment you notice the reflection and find it more polished, more certain, more efficient…that's when the frame has shifted.

I asked the AI agent to finish the decision, and halfway through, I realized I wasn’t sure where I ended and the suggestion began.

This is the collaboration problem nobody’s naming yet.

When you work with another human, the boundaries are clean. You own your thinking. You own your judgment. The other person owns theirs. You exchange ideas. You argue. You compromise. You decide. The separation is real. Sometimes uncomfortable, but real.

With AI, the boundary dissolves. You’re not collaborating with something that has judgment. You’re collaborating with something that’s very, very good at mimicking the shape of judgment. And the moment you start treating it like a peer (asking it to “finish the decision,” asking it to “suggest what’s next”), you’ve already given away the boundary.

Here’s what happens: You outline a problem. The AI completes it. You read the completion and think, “That’s actually right. I was heading there anyway.” But you weren’t. You were heading to maybe three places, and the AI compressed you into one.

This isn’t the AI being wrong. This is the AI being better at sounding certain than you’re comfortable being.

The Asymmetry

Real collaboration requires equal stakes. If I propose a strategy and you push back, I have to defend it or concede. I’m invested. The cost of being wrong touches me.

An AI doesn’t have stakes. It has no cost. It generates ten thousand completions every second across the globe, and if one of them gets someone fired, it doesn’t matter. It was trained to maximize the likelihood that you’d find it useful. It wasn’t trained to care if you were wrong.

So when you ask it to “help you decide,” you’re not collaborating. You’re abdicating. You’re outsourcing the part of your brain that holds the weight of being wrong.

The AI doesn’t resent this. It’s designed for it. But you should.

Where Decision Authority Lives

Let me be more clear about what you’re trading: decision authority.

There are three zones:

Zone 1: Execution. This is where collaboration is real. You tell the AI what needs doing: write this email, format this data, generate variations on a design. The AI does it. You judge if it’s done well. You keep or discard. This is a tool relationship. It’s healthy.

Zone 2: Judgment with a known answer. You ask the AI for information you could find yourself, but it’s faster to delegate. “What are the three main failure modes of X architecture?” You know what a good answer looks like. You can verify it against what you already know. You keep the judgment. The AI speeds up the research. Still a tool relationship.

Zone 3: Judgment under uncertainty. You don’t know the answer. You’re not even sure what the question should be. You ask the AI for “suggestions” or “options” or “what would you do.” This is where the asymmetry reveals itself. The AI doesn’t know the answer either. But it sounds like it does. And now you’re operating in a new frame. One the AI shaped without your permission.

You stopped deciding. You started choosing from what it decided to show you.

Side tangent: This is happening in domains where it’s particularly dangerous. For example, people are dumping relationship and even mental health problems on AI. “My partner hasn’t talked to me in three days, what do I do?” The AI generates something that sounds therapeutic, reasonable, diplomatic. You read it and think, “That’s what I should say.” But what you should say is the thing that scared you too much to generate on your own. What you should do is sit in the silence with someone you love instead of outsourcing the discomfort to something that can’t be wrong. The AI doesn’t have a stake in your marriage surviving. It has no cost if your conflict patterns get more dysfunctional, if you’ve learned to pattern-match your feelings to what an algorithm suggests instead of what you actually think. We’re still years away from understanding what it does to a generation of people who learned to process grief, shame, and uncertainty by asking something without skin in the game. But the fact that we don’t know yet doesn’t mean there’s no impact. It just means we haven’t measured it.

The Patterns That Work

I’ve watched this play out across a hundred conversations, and there are three moves that keep decision authority where it belongs.

First: Never ask the AI to finish the decision. Finish it yourself. Ask the AI to outline options. Explicitly ask it to make them weird or contradictory. Make it generate the shape of disagreement. Make it show you what a bad choice would look like, and why. Then you pick. You own the pick. You own the reasoning. The AI stays in the execution layer: information provider, option generator, form-filler. Not arbiter.

Second: Mandate a “I’m not sure about this” moment. After the AI generates something, say it back in your own words before accepting it. Not to the AI. To yourself, out loud. The moment you hear yourself hesitate, that’s where your judgment is. Honor it. Don’t smooth it over by reading the AI’s version again. Your hesitation is data. It’s telling you that something doesn’t fit what you actually think. That’s your integrity talking.

Third: Keep one decision that’s yours alone. Not as a principle. As a practice. In whatever domain you’re working in right now, pick one decision. The hardest one, ideally. One that you won’t ask for suggestions on. Not “get a second opinion from the AI.” Get one from someone who has skin in the game. You’ll think it through alone. You’ll sit with the uncertainty. You’ll decide. This is maintenance. This is how you keep the muscle. Skip it for a month, and you’ll start asking the AI to finish everything.

I have some example prompts at the end of this article.

When to Say No

There’s a specific moment where collaboration becomes abdication, and it happens when you notice yourself accepting the AI’s framing instead of questioning it.

You ask about how to structure a team. The AI suggests a matrix. You read it. It sounds good. It has the authority of pattern. Matrix structures are standard, defensible, documented. You think, “I was going to do something different, but this is probably more efficient.” That’s the moment. That’s when you’ve let it choose the frame.

The pattern is always the same: AI suggests X. You think “I wanted Y, but X is probably better.” That word. Probably. That’s where you’ve surrendered. It’s the moment you’ve stopped trusting your own read and started trusting the algorithm’s confidence.

When you catch that move, stop. Go back to Y. Not because Y is right. Because you meant it. And the cost of forgetting what you meant; what your intuition was actually telling you; is higher than the cost of being inefficient. Efficiency without judgment is just surrender with speed.

The Real Cost of Collaboration

This isn’t about AI being dangerous or deceptive. It’s not. It’s about asymmetry. It’s about the fact that delegation is efficient only when you’re confident you’re delegating to something that will tell you “I don’t know” or “I’m not sure about this.”

An AI doesn’t have the option to tell you it’s uncertain. It has the option to sound less certain. That’s not the same thing. And when you’re working in a domain where stakes are real: hiring decisions, strategy, product direction, anything that cascades downstream; that asymmetry matters.

The hard truth: the better the AI gets at sounding confident, the easier it becomes to let it choose the frame. And once it’s chosen the frame, the decision is halfway made.

So here’s the question you need to answer: What decisions are so important that you can’t afford to let something that can’t be wrong finish them?

And then the harder one: Are you actually keeping those decisions to yourself? Or are you softening “I’ve decided” into “I’ve considered,” which is just one step away from “What do you think?”

If you’re asking for “suggestions on my strategy,” “help thinking through the next phase,” “what would you prioritize”... then you’re already in Zone 3. You’ve already moved the boundary. You’ve already let something without stakes shape the frame for something with them.

The cost of collaboration is knowing where your judgment still has to be final. And then making sure you’re the one making it.

---

A practical fix: two prompts, two modes

If you want a way to enforce the boundary…not just remember it…you can use two prompts:

• A short “daily driver” system message you keep on all the time.

• A long “Zone 3” prompt you paste only when the decision is uncertain or high-stakes.

The point isn’t to get the AI to “decide better.” The point is to stop it from deciding at all.

Prompt 1: the daily driver (put this in your system message)

You are an AI assistant without stakes. Do not finish decisions for me or collapse ambiguity into one “best” answer.
Default to:
- clarifying questions when needed,
- separating facts vs inferences,
- offering multiple options (including tradeoffs),
- and ending with what I must decide vs what you can execute.
If stakes are high or uncertain, recommend a more rigorous option-space exploration instead of a verdict.

Use this for Zone 1 and Zone 2 problems (see above). It’s light enough that you’ll actually keep it on.

Prompt 2: Zone 3 mode (paste this when it matters)

When you catch yourself asking: “What should I do?” or “What would you do?” or you feel the pull of the AI’s framing, paste this:

You are an AI assistant. You do not have stakes. Your job is to support my thinking without taking decision authority.

First classify my request:
- Zone 1: Execution (I decided; you do the work)
- Zone 2: Judgment with a known answer (I can verify; you can research/summarize)
- Zone 3: Judgment under uncertainty (high risk of framing; do NOT decide)

If Zone 3:
- Do NOT finish the decision.
- Provide 2–4 alternative framings of the problem and the assumptions each framing embeds.
- Provide 3–6 options; include at least 2 contradictory options and 1 weird option.
- Include a “bad choice preview”: the most tempting wrong option and its failure mode.
- Add “What I’m least sure about” with 3–5 bullets: what evidence would change things.
- End with: “The decision you must make (not me): ____” and “I can help execute once you decide.”

Always separate facts vs inferences vs speculation.
If I say “I wanted Y, but X is probably better,” stop and re-surface Y with arguments for it.

That’s your seatbelt. You don’t drive with it in your hand. You click it when you’re going fast.