Clean the Fishbowl

When people look "difficult," start with the bowl: unclear goals, noisy tools, unsafe feedback loops, and load that never resets. Psychological safety is not a poster. It is an operating system. Clean the fishbowl first. Then decide whether the fish needs coaching.

I spent a week at Cape Schanck with a wider leadership group. Coastal wind, long rooms, the usual offsite mix of slides and real talk. The useful thread was not another framework. It was the same sentence I keep writing for myself: get the plan across the line, and take everybody with us, safely.

Safety there was not only physical. It was clarity, load, and standards. That is the fishbowl.

The wrong first question

Most teams open with character analysis. Why is that engineer defensive? Why did that PM go quiet? Why does that operator escalate every small change?

Those questions feel leadership-y. They also skip the cheap diagnostics.

If the water is dirty, every fish looks sick. Dirty water in a knowledge team looks like:

• Outcomes described as activities ("deliver the platform") instead of felt results
• Three sources of truth for the same status
• Feedback that only arrives when something is already on fire
• Tools that punish honesty (you report a risk and inherit the work with no capacity)
• Meeting load that leaves no hour to think before the next decision

In that bowl, "attitude" is often a survival response. Fix the bowl before you put someone on a performance plan.

Cape Schanck as a metaphor, not a brochure

Cape Schanck sits on a cliff edge. The water looks calm until the wind turns. Offsites work the same way. Alignment feels clean in the room. Monday morning puts people back into bowls that have not changed.

The leadership move is not inspiration. It is maintenance:

1. Same definition of good. If two leaders mean different things by "done," the team will thrash and look unreliable.
2. Visible load. If you cannot see who is already carrying three critical paths, every new ask looks like resistance.
3. Safe subtract. Ask: if we took everybody across safely this week, what would we stop shipping because it fails the best-day bar?
4. Feedback that does not punish. Problems reported early must cost less than problems hid until demo day.

I use the same pattern in my personal builder stack. My AI harness will happily invent urgency. The morning brief is useful only when it surfaces load and decisions, not when it flatters busyness. That is bowl hygiene for one person.

Fishbowl checks for SMB and enterprise

You do not need a culture consultant. You need a weekly inspection.

SMB / small team (this week):

• Write the outcome for each live initiative in one sentence a customer would recognise.
• Kill one status ritual that no one reads.
• Add one "must not happen" line to the hottest workstream.
• Protect one thinking hour like a board meeting. Busy is not effective.

Enterprise / multi-team (this month):

• Align the top three leaders on the same definition of good for the current base camp.
• Publish a load map: who is on the critical path, what they already own, what gets deferred.
• Change one incentive that rewards silence (for example, risk logs that become personal work queues with no triage).
• Run one retro on the system: tools, handoffs, decision rights. People last, and only after the bowl is cleaner.

BJJ is a clean analogy. When a training partner keeps tapping early, you do not start with "soft." You check mat space, round length, instruction clarity, and whether the room rewards ego sparring over learning. Training is an OS. So is work.

What cleaning is not

Cleaning the fishbowl is not endless softness. Standards stay. In fact, standards get sharper once the water is clear. People can finally see the bar.

It is also not "fix the culture" as a slogan. Culture is the residue of repeated systems: how tickets are written, how risk is received, how demos are scored, how send is owned.

In my photography work and in RivaFlow, the same rule holds. If the pipeline is messy (assets everywhere, no house style, no consent folder), every creator looks disorganised. Fix the pipeline. Then coach craft.

A practical 14-day clean

Days 1-3: map the bowl. List the three murkiest loops (status, feedback, decision rights).
Days 4-7: change one loop only. Ship the change in writing.
Days 8-10: watch behaviour. Did honesty get cheaper or more expensive?
Days 11-14: only then coach individuals whose patterns still fail in clean water.

If someone thrives after the bowl is clean, they were never the problem. If they still thrash, now you have signal.

Closing

Leaders love diagnosing fish because it feels personal and decisive. Bowls feel bureaucratic. That is backwards. The bowl is where most of the variance lives.

Cape Schanck reminded me that alignment without maintenance is theatre. Clean the fishbowl. Hold the standard. Take everybody across safely. Then, and only then, talk about the fish.