Take the diagnostic
FRAMEWORKS / The Eight Conditions

The Eight Conditions

What actually decides whether a workplace works — or just survives.

Most workplace problems aren’t people problems. They’re condition problems.

The person who used to bring up issues in meetings has stopped doing it. Two departments that should be working together aren’t quite speaking. The same mistake has happened three times this year and nobody seems to be learning from it. A good employee left and gave a polite reason that you don’t entirely believe.

These don’t look like related problems. They look like eight different things you need to fix separately.

They aren’t. They’re symptoms of eight underlying conditions — and when those conditions are present, the small problems mostly take care of themselves. When they’re missing, you can spend years putting out the same fires, hiring new people, running new training, and never quite get to the thing that’s actually going wrong.

The eight conditions on this page came out of four years of PhD research with founders and owners of small and medium Australian businesses. The original research was about how innovation gets sustained — but it turned out that the conditions for sustained innovation are basically the conditions for a workplace that works at all. Whether your business builds disruptive technology or runs a regional plumbing operation, the same eight things decide whether your team grows stronger over time or quietly erodes.

This page describes each one in plain language, with examples of what it looks like when it’s there and what it looks like when it isn’t. Before reading on, you can take a four-question version of the diagnostic to get a rough sense of where you sit.

Quick check

Four questions. One minute.

A short version of the diagnostic — enough to see where you sit, before reading on.

The eight, in one sentence each

Before going through them in depth, here they are at a glance.

  1. Holistic collective — your team sees itself as one group, not separate departments protecting their patch.
  2. Diverse wisdom — different perspectives are actively sought out, especially from quieter voices.
  3. Achievement through collaboration — people work problems out together, in the open, instead of routing everything through you.
  4. Structure and consideration — there are regular rhythms that hold the team together, and genuine care for how each person is doing.
  5. Stress adverse — when things get hard, the team gets more focused, not more scattered or more blame-focused.
  6. Innovative mindset — people feel safe to try a small new thing without making it a political event.
  7. Learning from mistakes — when something goes wrong, the conversation is about what was learned, not who to blame.
  8. Engaged synthesis — everyone can explain, in their own words, what the business is ultimately trying to do.

Each of the eight is described in detail below. Read the one that resonates first. The others will still be there.

Condition 1 of 8

Holistic collective

A holistic collective is the feeling, from the inside of a business, that everyone is on the same team. Not because there's a poster about it. Because when something hard happens, people from different parts of the business move toward each other rather than away.

It's surprisingly easy to lose. As soon as a business grows past about ten people, departments start forming — and so do the gaps between them. Sales sees Operations as the people who slow down deals. Operations sees Sales as the people who keep promising things that can't be delivered. Both of them are technically right. Neither of them is being unreasonable. But the business now has a fracture down the middle that the owner often can't see because both groups are polite when the owner is in the room.

When it's present

  • When something goes wrong, the first question isn't "whose fault is this" but "what do we need to do, together, to fix it"
  • People from different parts of the business will jump in to help each other without being asked, and without making a fuss about it
  • Decisions get made faster, because nobody is waiting for someone else to fail

When it isn't

  • The owner becomes the bridge between two teams that won't talk to each other directly
  • Information stops flowing between departments — both sides are surprised by things the other side knew weeks ago
  • New hires pick up on the divide within their first month and quietly choose a side

The fix is rarely a values poster. It's usually structural — who meets with whom, what they're measured on, and how often you, the owner, are in the room when the two sides have to figure something out together.

Condition 2 of 8

Diverse wisdom

Diverse wisdom is the deliberate act of seeking out perspectives that aren't your own — especially from the quieter people in the room, and especially before you've already decided.

Every small business owner has a default circle of two or three people whose opinions they trust most. That's healthy. The problem is what happens when those two or three people start to agree on everything, or when the people outside that circle stop bothering to offer their view because they've learned it doesn't change anything.

In the PhD research, the businesses that sustained innovation over years all had something in common: they could name people on the team whose perspective regularly disagreed with the founder's — and who got listened to anyway. Not all of them. Not on everything. But on enough that the founder wasn't ever the only voice shaping where the business went.

When it's present

  • In a meeting, the quiet person eventually says something — and the room takes it seriously
  • Different parts of the business get genuinely consulted before decisions that affect them
  • The owner can name at least two recent decisions they changed their mind on, because of something a team member said

When it isn't

  • The same three or four people speak in every meeting; everyone else watches
  • "We already thought about that" becomes a regular response to suggestions
  • Good ideas surface six months late, in a quiet conversation with someone who left the business

Fixing this is less about hiring different kinds of people and more about how you run the room. A meeting where the loudest voice always wins isn't a diversity problem — it's a facilitation problem.

Condition 3 of 8

Achievement through collaboration

This is the condition that lets the previous two actually work. A holistic collective and diverse wisdom only matter if people will actually speak up. Achievement through collaboration is what happens when they will — and when the conversation that follows is productive rather than destructive.

It's the condition that's hardest to fake. You can run team-building days and put "open communication" in the company values and still have a team where people don't tell each other the truth. The test is simple: when there's a problem between two people on your team, do they work it out together, or does it eventually arrive on your desk?

If it always arrives on your desk, the cost is enormous and largely invisible. You're spending your time on conflicts your team should be resolving themselves. They're losing the chance to build the muscle of working things out. And every problem that gets routed through you takes longer to solve than it should, because you don't have the full context that the two people involved already have.

When it's present

  • People on your team will disagree with you, to your face, and the disagreement doesn't end the working relationship
  • Two team members in conflict will try at least once to sort it out between themselves before involving you
  • "I don't agree with that" is a sentence people say in meetings, not just in carpark conversations afterwards

When it isn't

  • You hear about problems weeks after they've started — usually from someone who's quietly furious
  • Meetings end with everyone nodding, and then nothing actually changes
  • People route conflicts to you instead of to each other

If your diagnostic score was lowest on this condition, the article on why your team agrees in meetings and disagrees in the carpark is the most useful next read.

Condition 4 of 8

Structure and consideration

This is two things that have to be present together. Structure on its own becomes bureaucracy. Consideration on its own becomes chaos with good intentions. The teams that work have both.

Structure means there are regular rhythms — meetings, check-ins, reviews, decision points — that the team can rely on. Not lots of them. Not long ones. But predictable. People know when their work will be looked at, when their concerns will be heard, when decisions will be made. The unpredictability of "we'll get to it when we get to it" is one of the most exhausting things a workplace can have.

Consideration means that inside those rhythms, there's actual care for how each person is doing. Not surveillance. Not performance reviews dressed up as conversation. Care. You know what's hard for them right now. You know what's going well. You know what they're worried about that isn't related to work but that you can see affecting their work.

When it's present

  • Your team knows when the regular meetings are and what they're for, and the meetings start and end on time
  • You could, without checking your notes, say one thing that's currently hard for each of your direct reports — not at work, in their life
  • People feel both held to a standard and genuinely seen as a person

When it isn't

  • Either the rhythms have collapsed and everything is reactive, or the rhythms are there but feel like surveillance
  • You realise, when someone resigns, that you didn't know they'd been unhappy for six months
  • Your people are tired in a way that isn't really about the workload

You probably know which side you tilt toward. Most owners do. The fix is to add the missing half — owners who are strong on consideration usually need more structure; owners who are strong on structure usually need to slow down and actually look at the people inside it.

Condition 5 of 8

Stress adverse

Every small business goes through hard quarters. Stress adverse isn't about not having stress. It's about what your team becomes when the stress arrives.

Some teams, under pressure, get sharper. The trivial things drop away. People focus. Small wins get noticed. The team comes through the hard period with a story about how they did it together, and that story becomes part of the culture.

Other teams, under the same pressure, fracture. People blame each other. The owner becomes more controlling. Information stops flowing. Decisions get postponed. The team comes through the hard period — if it does — with a story about whose fault it was, and that story becomes part of the culture too.

The difference between the two isn't the size of the stress. It's the conditions that were already in the team before the stress arrived. A team that already had collaboration, structure and consideration, and a holistic collective will handle pressure differently from a team where those were thin.

When it's present

  • The hardest quarter the business has had is one your team talks about with something like pride
  • Under pressure, people on the team check in on each other more, not less
  • You, as the owner, can name when you were genuinely worried — and the team knew, and it didn't make things worse

When it isn't

  • Hard periods leave a residue of resentment that takes months to fade
  • Stress concentrates at the top — the owner carries it alone because the team can't be told
  • Each crisis feels like it sets the team back further than the last one

You can't really build this condition during a crisis. It gets built in the calm periods between them, by deliberately tending the other conditions.

Condition 6 of 8

Innovative mindset

An innovative mindset, in a small business, isn't a "move fast and break things" startup culture. Most small businesses don't need that, and most small businesses would suffer if they had it. What they do need is something simpler: the feeling among the team that suggesting a small change won't be a political event.

That's a low bar. It's also a bar that most workplaces don't meet. The cost of suggesting a change in many businesses is real — your idea gets dismissed, or it gets adopted but the credit goes elsewhere, or it gets you a reputation for being "always trying to change things." After two or three of those experiences, most people stop suggesting things. The business doesn't notice the moment it stopped getting better.

When it's present

  • People in your team will float small changes — "what if we tried" — without making it a big deal
  • You can name three small improvements in the last six months that came from someone other than you
  • The phrase "we've always done it this way" is rare

When it isn't

  • Suggestions go through you because nobody else is allowed to make changes
  • The business looks today, in operational detail, almost exactly the way it looked two years ago
  • New hires arrive with ideas, and within six months have stopped sharing them

This condition compounds slowly. A team that suggests one small improvement a fortnight becomes, in a year, a meaningfully better business — without anyone ever doing anything dramatic.

Condition 7 of 8

Learning from mistakes

This is the condition that breaks first and matters most.

In every workplace, mistakes happen. The question is what happens next. In some teams, a mistake leads to a short, honest conversation about what was learned, and the team is slightly better afterwards. In others, the mistake gets hidden, or blamed, or worked around — and the same mistake quietly happens again three months later, to a different person, who also can't talk about it.

The technical version of this is the distinction between single-loop and double-loop learning, which is covered on its own page. The plain version is this: most teams learn how to do the same thing slightly better. Far fewer teams learn how to do a different thing because the original thing wasn't working. The first kind of learning improves the business at the edges. The second kind changes its trajectory.

When it's present

  • When something goes wrong, the first conversation is about what we now know that we didn't know before
  • Mistakes get talked about in meetings, in the open, without ritual humiliation
  • The same significant mistake doesn't happen twice

When it isn't

  • People work around problems rather than naming them
  • The same kinds of mistakes keep happening and nobody quite knows why
  • Asking "what happened" sounds like the start of finding someone to blame

This is the condition most owners feel personally responsible for, because the team learns how to handle mistakes by watching how the owner handles them. If you, as the owner, get visibly tense when something goes wrong, your team will hide things from you. If you get curious, they won't.

Condition 8 of 8

Engaged synthesis

Engaged synthesis is what happens when everyone in the business — not just the leadership team — can explain, in their own words, what the business is ultimately trying to do.

The test is uncomfortable. Walk through your business and ask three people, separately: "what are we trying to achieve, here?" If you get three answers that broadly add up to the same thing, you have engaged synthesis. If you get three completely different answers, or three versions of "I'm not sure, I just do my job," you don't.

This is the condition that justifies all the others. Without a shared answer to "what are we trying to do," collaboration becomes negotiation, diverse wisdom becomes argument, and structure becomes process for its own sake. With it, all the other conditions have something to point at.

When it's present

  • Three random people in your business, asked separately, give you broadly the same answer to "what are we doing here"
  • Decisions across the business pull in roughly the same direction, even when nobody is co-ordinating them
  • People can say no to opportunities — they know what doesn't fit

When it isn't

  • People are busy but not aligned
  • The strategy document exists, somewhere, and nobody could quote from it
  • Every quarter feels like starting over

The fix isn't a longer strategy document. It's being able to say out loud, in one sentence, what the business is ultimately trying to do — and having your team repeat it back in their own words, regularly enough that it stays alive.

The framework on Joy at Work goes deeper into why purpose at work matters more than perks.

Where do the eight conditions come from?

They came out of a three-year PhD study at Griffith University’s Business School, completed in 2021. The research interviewed nineteen founders and CEOs of Australian small-to-medium businesses, using hermeneutic phenomenology to identify the themes that explained how those businesses sustained innovation and team health over time. The full thesis and the peer-reviewed Organization Development Journal article that came out of it are referenced on the About page.

Are these eight conditions only for innovative businesses?

No. The research started with innovation-focused SMEs, but the conditions identified turned out to apply to any workplace. They describe what it takes for any group of people to work well together over time. A regional plumbing business needs them as much as a tech startup.

How is this different from "company culture"?

“Culture” is the word people reach for when they can sense something is wrong but can’t quite name it. The eight conditions are a way of naming it — breaking the vague concept of culture into eight specific, observable conditions that you can score, change, and watch improve.

Is there a paid version of this diagnostic?

No. The diagnostic on this site is free and will stay free. There’s no paid version, no premium tier, and no consulting offer at the end of it. This site isn’t a sales funnel.

How often should I take the diagnostic?

Once a quarter is plenty. The conditions don’t move quickly — they shift over months, not weeks. Taking the diagnostic too often will make small fluctuations feel like real changes.

Can I get my team to take it?

Yes, though their experience of the conditions will be different from yours. If you want a sense of how the team sees things, the most useful version of this is asking three or four people to take it separately and then comparing notes — not asking the team to take it as a group, which will produce the answer they think you want to hear.

The conditions don’t change overnight. But the first one to work on usually becomes obvious within the first ten minutes of honest looking.

— Jose Medina, PhD