Blog Post

In 2012, Google set out to answer a question that should be simple and turns out to be almost impossible: what actually makes a team great?

They called it Project Aristotle. Years of research, hundreds of teams, dozens of variables — seniority, personality mix, team size, whether people were friends outside work. They were looking for the magic combination. The dream-team formula.

They didn't find one. What they found instead was more useful.

The single biggest driver of high performance wasn't who was on the team. It was whether the team had structure and clarity — clear roles, clear plans, clear goals — combined with dependability, the simple, unglamorous habit of doing what you said you'd do, on time, to the standard you agreed.

Not psychological safety alone, though that mattered too. Not talent density. Not seniority. Clarity of expectation, delivered consistently.

Read that twice, because it's the least sexy finding in the history of organisational research, and it's also the most actionable one you'll ever get.

What "brilliant basics" actually means

I use the phrase Brilliant Basics deliberately, because "clarity" and "structure" sound like things you'd nod along to in a workshop and then forget by lunch. Brilliant Basics is more specific. It's the answer to four questions, answered explicitly, for every person on a team:

What does good look like in my role, right now? Not the job description from onboarding. This quarter, this sprint, this week.

What am I responsible for, and what happens if I don't deliver it? Ownership without ambiguity about who's actually on the hook.

What's the rhythm that keeps us honest? The checkpoint — weekly, fortnightly, whatever cadence fits — where drift gets caught early instead of discovered in a post-mortem.

How does what I'm doing connect to something that matters? Not every task needs a strategy deck behind it. But if nobody can answer this, that's a signal, not a detail.

Most teams think they have this. Ask the manager and they'll say "yes, obviously." Ask five people on the team the same question and you'll get five different answers, three of them vague, one of them wrong, and one honest "I'm not totally sure, actually." That gap between what leaders assume is clear and what's actually understood is where Brilliant Basics either exists or doesn't.

How to actually define them

This isn't a document exercise. A one-page "team charter" that gets written once and filed away is exactly the kind of theatre Project Aristotle's findings warn against — it looks like structure without being structure.

Defining Brilliant Basics for a team means sitting down and answering, specifically, for every role:

The non-negotiables. What are the two or three standards that, if missed, genuinely matter? Not forty rules. Two or three that actually separate good work from bad. A support team's non-negotiable might be response time. An engineering team's might be code review before merge. Fewer, sharper standards beat a long list nobody reads.
The responsibilities, named against a person. Not "the team owns onboarding." Someone owns onboarding. Diffused ownership is how brilliant basics quietly die — everyone assumes someone else has it covered.
The cadence. Pick the smallest rhythm that catches problems while they're still cheap to fix. Weekly is usually right. Daily is usually too much. Monthly is usually too late.
The connective thread. For each responsibility, one sentence: why does this matter to what we're actually trying to achieve? If you can't write that sentence, you've found either a task worth cutting or a strategy worth clarifying.

Do this once, properly, with the team in the room — not delivered to them — and you'll notice something. The conversation itself is often more valuable than the document it produces, because it's the first time anyone's actually said the quiet assumptions out loud.

The psychology nobody talks about

Here's the part that surprised me most when I started digging into why this works, beyond "it seems sensible."

Ambiguity is expensive — not just operationally, but cognitively. Every unclear expectation is a small, ongoing decision your brain has to keep re-litigating: am I doing this right? Is this good enough? Should I check with someone? Psychologists call this decision fatigue, and it's cumulative. A person navigating unclear expectations all day isn't just working — they're spending a meaningful chunk of their mental bandwidth on uncertainty management, on top of the actual job.

Clarity removes that tax. When someone knows exactly what's expected, their brain stops re-checking the boundary and starts using that freed-up capacity on the part of the job that actually needs judgment — the creative problem, the difficult client conversation, the decision that genuinely requires thought.

This connects to something researchers in motivation science have found repeatedly: autonomy — the thing every modern leader says they want to give their people — doesn't thrive in a vacuum. It thrives inside structure. Give someone total ambiguity and call it "autonomy," and most people don't feel free. They feel anxious, because they're now guessing at the rules while also trying to do the work. Give them a clear foundation — this is the standard, this is your call within it — and autonomy becomes real, because the guessing is gone.

That's the counterintuitive bit. Clarity doesn't constrain performance. It's the precondition for it.

The analogies that make this click

I've found three comparisons that land with almost every leader I explain this to.

Aviation. Airline pilots run through the exact same pre-flight checklist on their ten-thousandth flight as their first. Nobody thinks that's a lack of trust in their experience. It's precisely why aviation is one of the safest industries on earth — the basics are so brilliantly non-negotiable that human error gets caught before it becomes a headline. The checklist isn't a constraint on skilled judgment. It's what frees the pilot to use their judgment on the things a checklist can't cover.

Professional kitchens. A great kitchen brigade runs on rigid station discipline — mise en place, exact plating standards, a strict hierarchy of who calls what. It looks restrictive from the outside. It's actually what allows a head chef to improvise a brilliant dish under pressure at 9pm on a Saturday, because everything else in the kitchen is running on rails they don't have to think about.

Elite sport. Every high-performing team drills fundamentals obsessively — footwork, positioning, the boring reps nobody sees on match day. The flair moment that wins the game only exists because a thousand unglamorous basics happened correctly first. Nobody becomes a great improviser by skipping the fundamentals. They become a great improviser because the fundamentals are so deeply embedded that the mind is free to do something extraordinary on top of them.

That's the pattern in all three: the basics aren't the opposite of excellence. They're the platform excellence stands on. Skip them, and what looks like "creative freedom" is usually just chaos with better branding.

What this costs you if you skip it

The Project Aristotle researchers didn't find that unclear teams simply performed a bit worse. They found that ambiguity was corrosive in a specific way — it eroded the other four dynamics too. Teams without structure and clarity struggled to build psychological safety, because nobody was confident enough in the baseline to take a risk on top of it. They struggled to find meaning in the work, because meaning is hard to locate when you're not even sure what's expected of you day to day.

That's the real cost. It's not just "things are a bit messier." It's that ambiguity quietly undermines everything you're trying to build on top of it — the innovation, the engagement, the discretionary effort you actually want from good people.

Where this goes next

I'll be honest about where we are: we've built Brilliant Basics into Zontally as a first-class part of the platform — the ability for every team to define their non-negotiable standards, name responsibilities against real people, and connect the daily work to what actually matters. It's still early in its build, and we're deliberately not overselling that. What I'd rather you take from this piece isn't a product pitch. It's the question underneath it.

How many of your teams could answer, right now, without checking with anyone: what does good look like in my role this week, and who's actually responsible for it?

If the honest answer is "not all of them," you've found the highest-leverage, least glamorous fix available to you. It won't make headlines. It's also, according to years of research from one of the most rigorous organisations to ever study this question, the thing that separates teams that consistently perform from teams that occasionally get lucky.