How a Código de Boas Maneiras Actually Works in Practice
Most people think a código de boas maneiras is just a document you write once and print on nice paper. That's not even close to how it functions. The real work starts after the first draft, and honestly, most teams skip straight to a polished PDF and call it done. It doesn't work that way.
When I was putting one together for a mid-size engineering team, we spent three weeks on the actual document and another four figuring out how to get anyone to treat it seriously. The culture around the code matters far more than the words on the page.
Why most códigos de boas maneiras fail before they start
I watched a company roll out a fifteen-page code of conduct. Nobody read past the first two pages. Three months later, someone posted an offensive message in the public Slack channel and when HR brought it up, the employee said they had no idea that behavior violated policy. The problem wasn't that the rule was missing. It was buried under language that felt like it was written by a lawyer who'd never met the team.
The better approach is to write it like your team actually talks. Short sentences. Specific examples. No corporate filler. A clear statement about what acceptable looks like and what isn't tolerable.
The practical framework
Start with behavior, not values. Words like "integrity" and "respect" sound good but mean different things to different people. Instead of saying "treat colleagues with respect," say "no interrupting in meetings, no sending angry messages at 2 AM, no making jokes about someone's appearance even as 'banter'." Concrete beats abstract every time.
Next, figure out what enforcement actually looks like. This is where most codes die. A código de boas maneiras without a clear escalation path is just a suggestion box with legal liabilities. Write down exactly what happens when someone crosses a line. Minor issue? Verbal conversation with their manager. Repeat or serious? Written warning. Threatening behavior or harassment? Immediate HR involvement. Don't leave it vague. Vague enforcement creates anxiety, not compliance.
I learned this the hard way when a senior developer kept making comments about junior team members' clothing choices. The code said "maintain a respectful environment" but didn't specify consequences. The manager had to make it up on the spot, which looked arbitrary and unfair. After that, we rewrote everything with explicit tiers.
Where people mess this up
One thing nobody talks about is the distribution gap. You can have the best código de boas maneiras in the world, but if it only exists in a shared drive that nobody checks, it has zero effect. We used to email it once a year during onboarding. Response rates were abysmal. Then we started doing five-minute check-ins during sprint retrospectives where we'd discuss one clause from the code and ask what real situations had come up recently. That changed everything. Not because people suddenly cared about the document, but because it became part of actual conversations.
Another trap is making it too long. I've seen codes go thirty pages. Nobody reads thirty pages. You don't need thirty pages. You need maybe eight, with appendices if you want to include legal references and reporting procedures.
Downloadable reference structure
If you're starting from scratch, here's the skeleton that actually works:
Cover section with a one-paragraph statement from leadership about why this exists and what it's meant to achieve. Keep it under three hundred words.
Behavioral standards broken into categories: communication, meeting etiquette, conflict resolution, remote work expectations, and reporting procedures. Three to four bullet points per category max.
Real examples of acceptable and unacceptable behavior. This is the part most teams skip. Two examples per rule makes it stick.
Escalation ladder with timeframes. Who to talk to, when, and what to expect at each step.
Reporting options that include anonymous channels if your jurisdiction requires them.
Review cadence. Six months for the first review, then annually. Update it or delete it. Stale codes become worse than no code.
I have a simple template people keep asking about, and you can find a basic version of it at codigo de boas maneiras template. It's not fancy. It's structured the way I described and it's been through three company iterations since I helped build the first one.
The uncomfortable truth about enforcement
A código de boas maneiras only works when leadership follows it. I saw this play out when a VP at one of my previous companies made a joke that crossed the line during a company-wide call. Everyone waited to see what would happen. Nothing did. The code stayed on the intranet as decoration from that point forward. People noticed. They always do.
That's why writing the document is the easy part. Getting people to hold each other accountable is the actual work, and there's no shortcut around it.
