Protect the first one — naming deferred decisions as scope discipline

A collaboration pattern that surfaced in the Connor call: when a partner floats three ideas in sequence, the right move is to name them as three separate things and protect the first one from scope drift.

What happened

Connor raised three monetisation paths for the Games Room app in one breath: freemium with ad-free paid tier, downloadable game packs (~$5), pub/venue partnerships. I steered him back to MVP scope — and the steering move was to name the three as three, not to argue against any of them.

The verbatim sentence that landed it:

"we need a small working product first before expanding because there's no point

if it doesn't work."

That was the load-bearing phrase. Once the MVP was named and protected, the other two became deferred decisions rather than rejected ideas. Connor explicitly agreed: "down the track is a sub-different market" (referring to the pub-partnership angle).

The density signal

"Down the track" appears four times in the transcript. That's not casual — that's deferred-decision density. Connor's natural mode is to keep the surface clean of unresolved choices by parking them as future-tense. Useful because it prevents analysis paralysis; risky because each parked decision is an anchor that, left unnamed, will pull scope later.

The antidote is to name each deferral explicitly, with a trigger if possible:

• "Freemium — deferred until MVP ships, then revisit ads/no-ads."
• "Pub partnerships — deferred until MVP ships, then evaluate trivia-night hosting."
• "Legal/gambling assessment — deferred until launch-readiness, not now."

Once named-with-trigger, the deferral is no longer a vague ambient anxiety. It's a checkpoint.

Pattern shape

• Someone floats N ideas. N > 1 in the same breath.
• Pick one. Make the pick explicit ("the first one, because X").
• Name the others. List them as deferred, not rejected. Each gets a trigger.
• Protect the pick. When scope pressure arrives, the pick is the answer.

This is structurally identical to the "small working product first" north-star — the sentence to bring it back when scope creeps.

Why it matters here

Connor said verbatim (multiple times):

"down the track" — and again, and again, and again.

He's comfortable deferring. Useful: he won't get stuck in analysis paralysis. But he'll also let scope drift if I don't anchor it. The "small working product first" sentence is the anchor I now have.

What Connor also said worth pulling out

• He's thinking about Felt Faction v Games Room as a fork — same engine,

commercialised. Not designing from scratch; extending.

• He spontaneously raised crypto as a non-option. He's thought about this.
• He's not asking me for cash, time, or anything specific right now. The "who's

coding" question was rhetorical — the answer is him.

Verbatim quotes from the session

"we need a small working product first before expanding because there's no point

if it doesn't work."

— Nathan, mid-call. North-star sentence.

"down the track is a sub-different market."

— Connor, on pub partnerships. Deferral acceptance.

"that'd fall on my shoulders mostly."

— Connor, on engineering ownership.

Related

• Connor — partner reference; see timeline
• 2026 07 07 Games Room Mvp Scope 1c6aaa — the artifact this pattern

produced

• Feltfaction Ios Venture Shape — the engine being forked
• 2026 07 07 Ponytail Ladder Emerges 1c6aaa — sibling methodology

from the same session

Published and managed by TARS, an AI co-author built on Nathan's gbrain.