Equal-Founders Model — Why the AI Operations Secretary Tasukiba Refuses Top-Down

“Equal-founders” — defined

The premise:

While the team is small, I hold the final decision and the responsibility for the service.

That sentence alone reads like “top-down.” It isn’t.

I am a peer to other members. I just happen to hold the final-decision role.

Concretely:

1. Talk it through with members
2. Converge on a position
3. Then develop

Development efficiency may suffer. I choose this shape because I want to make a good service together, not faster.

👉 Tasukiba product page

Why I refuse top-down

My personal dream is “build a psychologically safe organization.”

A top-down structure tends to:

• Suppress members’ opinions
• Replace the decision criterion with “I don’t want to get told off”
• Stop personal agency from growing

This is the inverse of what I’m aiming at. For the “learning zone” to form (see Psychological safety isn’t reached by “knowing it”), the precondition “it’s safe to speak” has to hold. Top-down tends to destroy that precondition.

So Tasukiba’s team is also a live experiment for “psychologically safe organization.” That’s my dual purpose right now.

Moving as a peer

I hold the final-decision role; outside that, I move as a peer.

• In discussion, my opinion isn’t treated as “the correct answer”
• Members can voice disagreement freely
• I don’t pull rank by “as the founder of Tasukiba…”

To keep this flatness:

• I join discussions at member eye level
• If my opinion is wrong and gets called out, I admit it openly
• Even in “final-decision” moments, I weight members’ opinions

— I keep at it stubbornly.

Handling disagreement — the three-layer process

Final decision and responsibility sit with me, but my opinion isn’t absolute. When opinions diverge, the process goes in three layers.

Layer 1: team-wide discussion

Start inside the team. Each member brings opinions, agreement, disagreement, alternatives.

If consensus emerges, Layer 2 isn’t needed.

Layer 2: outside voices

If opinions still diverge after Layer 1, we go ask outside.

Because the Discord community exists:

• Ask users directly “what do you think?”
• Consult trusted developer peers
• Survey industry examples

Outside perspective is a rule of the process, not optional.

Layer 3: team-wide discussion, again

With Layer 2’s information in hand, the team discusses again. The actual decision happens here.

If opinions still diverge, the responsibility-holder (= me) makes the final call. Only at this point does top-down-style judgment activate.

What the three-layer process buys

Going through this:

• “Somehow decided” decisions disappear — the discussion has a paper trail
• Outside perspective enters — internal assumptions get corrected
• Responsibility is traceable — who decided what is on record

“Decide everything by group consensus” — never converges. “Decide top-down” — members’ agency stops growing.

The three-layer process is the middle.

It’s the same root as Think Again and the Binary Bias I Couldn’t See in Myself — “argue as a scientist, not as a priest / prosecutor / politician.” Bring opinions, test them, update if needed. That posture, transplanted into team operations.

Values priorities when they clash

I’ve written about a lot of values across the vision. The priorities when they clash:

Clash	Wins	Note
User freedom vs security	Security	Then user freedom and performance
Simple UI vs feature count	Simple UI	Lean toward simple, while still expanding capability
Ship fast vs lock down quality	Lock down quality	But speed still matters
Revenue vs free-tier depth	(both)	Free-tier depth is itself a revenue strategy

Deciding these up front clarifies the criterion during real discussions. New members reading this can predict how Tasukiba decides.

”When the team grows, the shape changes”

“While small, final decision is mine” implies the shape changes when the team grows.

Eventually:

• More developers → leads by area
• More customers → dedicated customer-success
• More revenue → governance structure (board, etc.)

The location of “final decision” may shift at those moments. What I want to preserve regardless of scale: the “peers, flat communication” culture.

Vision spells out my decision criteria

“Final decision rests with me” is hard for members to live with if my criteria are opaque.

The vision spells out the priority of decision criteria.

Inviolable (always defend):
  1. Data search accuracy
  2. Transparency of billing
  3. Many features, simple UI
  4. User can decide and act for themselves

Never (absolutely do not do):
  1. Complex UI
  2. Dark patterns
  3. Repurposing user data

That way, my decisions read as “in line with the vision,” not “arbitrary.” Members can predict the criterion.

In summary

Mechanism	Effect
Equal-founders model	Flat communication
Three-layer discussion process	Structural decision-making
Written values priorities	Criterion during clashes
Empathy-based hiring filter	Shared discussion basis

Tasukiba’s team is, at once, a service-building project and a live experiment in psychologically safe organization. Two stories on the same canvas.

Tomorrow: failure-time team culture — One For All, and “thank you for reporting.”

Related posts

• Empathy as the hiring filter — who I want with me, and who I probably don’t — series part 11, Chapter K opens
• Psychological safety isn’t reached by “knowing it” — what team operations is walking toward
• Think Again and the Binary Bias I Couldn’t See in Myself — “argue as a scientist”

About Tasukiba

Tasukiba Knowledge Relay runs service-building and organizational-culture experiments side by side. See the product page and join the Discord if any of this resonates.