data.day
company-culture / operations / management / scaling

Myth: 'Culture' Will Fix Process Problems

Good intentions do not scale. Stop blaming 'culture' for operational failures and start building the written rules of engagement.

Marta Clarity Marta Clarity

Good Intentions Do Not Survive Deadlines

I consulted for a startup that was “bleeding” productivity. The CEO told me, “We need to work on our communication culture. People aren’t collaborating.”

I looked at their Slack. It was a screaming match of urgent requests, lost files, and passive-aggressive follow-ups.

They did not have a “culture” problem. They had a physics problem. They were trying to move heavy objects (projects) without a lever (process). Relying on everyone being “nice” and “smart” works when you are three people in a garage. It breaks when you are thirty people on Zoom.

The Chaos: The Ambiguity Tax

When you rely on culture to fix operations, you pay a tax on every interaction.

  • Who decides? “We decide together!” (This means no one decides, and the meeting runs 20 minutes over).
  • Where does it live? “In the drive!” (Which folder? The one from 2023 or 2024?)
  • How do I ask for help? “Just ping me!” (And interrupt my deep work).

This ambiguity breeds resentment. High performers hate chaos. If you force your best people to guess how to get things done, they will eventually leave to go somewhere where the rules are clear.

The System: The Rules of Engagement

We fix this by writing the “Constitution of Work.” This is not a mission statement. It is an operating manual.

I require three specific protocols to be written down and signed by the team.

1. The Decision Protocol

Stop guessing who holds the gavel.

  • The Rule: Every project has ONE “Directly Responsible Individual” (DRI).
  • The Logic: We can debate as a democracy, but we execute as a dictatorship. The DRI decides.

2. The Location Protocol

Stop playing hide-and-seek with files.

  • The Rule: If it is not in [System X], it does not exist.
  • The Logic: I do not accept files sent via DM. I do not accept files in email. If you send me a file in chat, I will not open it. I will ask you to put it in the System.

3. The Request Protocol

Stop the “Hey, quick favor” culture.

  • The Rule: All requests for work must be a Ticket (or a formal Brief).
  • The Logic: If you cannot articulate what you need in writing, you do not need it yet.

Summary

Culture is a lagging indicator. It is the result of your processes, not the cause.

  • If your process is clear, Then your culture will be calm.
  • If your process is chaotic, Then your culture will be toxic.

Clear is kind. Unclear is unkind. Stop wishing for better culture and build better rails.

FAQs

Doesn't too much process kill creativity?

No. Chaos kills creativity. Knowing exactly how to submit your work frees your brain to actually create it.

We are too small for protocols.

You are small now. If you want to get big, you act big. Documentation is the skeleton; you build it before the muscle.

People won't read the rules.

They will if you reject work that breaks them. Enforcement is love.