The Team Canvas, or How to Read a Team's Unwritten Laws

Every team is a tiny country with its own laws, and none of them are written down. What "done" means. Who you actually ping when production is on fire, versus who the org chart says you should. The joke that's been running since 2019 that a new hire won't get for six months. None of it is in the onboarding doc, because nobody thinks to write down the water they swim in.

So the new person learns the customs the only way available: by stepping on each one in turn and reading the room's flinch. And it's not just newcomers. Two teams inside the same company, same building, same stack, will have quietly evolved different definitions of the same words, and discover it only when they have to work together and everything mysteriously grinds.

The Team Canvas is a cheap fix for that. It's a one-page workshop, from Alex Ivanov and Mitya Voloshchuk, that drags a team's unwritten rules onto a wall. Two hours, the whole team, a stack of sticky notes, and a facilitator whose only real job is to keep people honest. Four regions:

   +------------------------+------------------------+
   |  WHAT WE ARE           |  WHY WE EXIST          |
   |  roles, goals          |  purpose, values       |
   |  (shared + private)    |                        |
   +------------------------+------------------------+
   |  WHO IS ACTUALLY HERE  |  HOW WE WORK           |
   |  strengths, weak spots |  the rules + rituals,  |
   |  what each person needs|  said out loud         |
   +------------------------+------------------------+

What we are is the easy corner. Why we exist is the one teams love to skip, and skipping it is how you get a group that ships very fast in no particular direction. Who's actually here is where people lie, politely, about their weaknesses, so as the lead you go first and you lie the least. And how we work is where the folklore becomes policy.

The corner everyone wants to skip is the one that matters

That bottom-left corner, the weak spots and needs, is where people squirm, and it's exactly where the actual friction has been hiding. I ran a canvas once with a team that had been quietly tense for a year and nobody could say why. It surfaced in the "how we work" corner, when we tried to write down the rule for code review. Half the team wrote down that every change gets reviewed before it merges. The other half had been operating, in total sincerity, on the understanding that review was a nice-to-have when you had time. Neither half knew the other existed. A year of low-grade resentment, the seniors thinking the juniors were cowboys, the juniors thinking the seniors were precious about their code, and underneath it all just a rule that had never once been said out loud. We fixed it in about four minutes once it was on the wall. The hard part was never the fix. It was that nobody had known there was anything to fix.

The canvas doesn't generate answers. It forces the team to say the quiet parts to each other's faces, once, with witnesses. When someone asks the facilitator "what's the right answer here," the only correct response is to hand it back: "what do you think it should be." You're just the person holding the marker and refusing to let the awkward question slide.

When to reach for it

You don't need an annual occasion. The natural moments are when the country's borders move: a brand-new team that's never set its own norms, someone leaving and taking a pile of unwritten ownership with them, two groups merged by people who'd never worked in either one, or the quarter where everyone is quietly annoyed and no one will say at what. That last one is the real signal. Sourceless friction is almost always a pile of unwritten rules drifted out of sync, and the canvas drags them back into the light before they calcify into "those two just don't get along."

A warning, because these sessions have a bad reputation and earned it. A beautiful canvas full of words like "synergy" and "trust" that nobody believes is worse than no canvas, because now you've documented the lie and given everyone a laminated reason to be cynical. The point is the two hours where people say the true thing out loud. You can fake the artifact in an afternoon. You cannot fake that, and a team that can actually do it, that can sit in a room and admit what it's bad at and what it needs, mostly doesn't need the wall. The wall just makes it repeatable, which matters, because the alternative is every team relearning its own rules from scratch every time a person joins or leaves.