What Six Years of Operating Revealed

I spent six years building Gemma whilst running a professional services practice. During that time, I watched the same operational pattern repeat across every architect, engineer, and building consultant I encountered.

The pattern looked like this: brilliant technical work, premium hourly rates, and administrative systems held together with spreadsheets and hope.

I recently pulled together the actual numbers behind Australia’s building industry. The data explains why operational efficiency isn’t a luxury consideration for these practices. It’s a survival mechanism.

The Micro-Practice Reality

Only 1.6 per cent of Australia’s approximately 13,000 architectural firms employ 20 or more people. The sector has 40,000 employees total.

The mathematics reveals something most people miss: the overwhelming majority operate as micro-practices, typically under five people.

These aren’t casual operations. 34% of architects were business owners or sole traders, and 52% worked more than a 40-hour week.

Every hour consumed by administrative overhead directly converts to revenue loss. When you charge premium rates for cognitive labour, fragmented tool ecosystems become expensive.

The Engineering Consultancy Landscape

The engineering sector shows similar patterns. There are 45,554 businesses in the Engineering Consulting industry across Australia. Larger firms exist. FMG Engineering employs over 150 staff across four offices. Pitt&sherry operates with 350+ diversely skilled consultants.

But thousands of smaller operations manage identical project complexity with a fraction of the resources.

A Brisbane consulting client recently interviewed six candidates for an intermediate engineer position. None came from Brisbane. Workload across Queensland continues climbing.

Smaller practices compete for scarce talent whilst simultaneously managing project delivery and administrative overhead. The operational pressure compounds.

The Revenue Mathematics

In 2014-15, there were an estimated 13,555 businesses in the Australian architectural sector with an income of $6.4 billion, generating a profit of $603 million.

Average revenue per business sits around $472,000. Profit margins run under 10%.

There’s minimal buffer for administrative inefficiency or fragmented tool ecosystems.

The architectural services industry remains highly fragmented, consisting mainly of small and locally focused companies. Competition intensifies. Administrative efficiency shifts from nice-to-have to essential.

The Contraction Trend

Even larger practices face pressure. Australia’s top-ranking architectural firm, Architectus, dropped from 265 fee-earning architects to 252. GHD Woodhead reported 201 architects compared to 233 the previous year.

Substantial practices are shedding staff. Administrative overhead likely redirects back onto remaining team members.

The pattern suggests operational drag increases even as headcount decreases.

The Building Consultancy Complexity

Building regulatory consulting adds another layer. Sustainability, accessibility, acoustics, fire safety, waste management.

Firms like Jones Nicholson employ 80 staff members covering nine disciplines. But the sector remains dominated by smaller specialist consultancies.

Multi-disciplinary capability concentrates administrative complexity into limited operational capacity.

When you’re managing projects across multiple regulatory domains with a small team, every fragmented system multiplies friction.

What This Means Operationally

I didn’t start with market research. I started with operational pain.

Six years of live testing under genuine deadline pressure revealed what matters: time preservation, unified architecture, transparent operation.

The numbers confirm what I observed daily. Most professional service providers in Australia’s building industry operate as small practices. They manage complex project delivery. They compete for scarce talent. They work extended hours. They operate on thin margins.

Every integration dependency adds overhead. Every fragmented tool demands context switching. Every opaque pricing structure hides true cost. Every unnecessary feature creates learning friction.

The operational reality doesn’t support complexity. It demands simplicity.

The Overlooked Pattern

Pritzker Prize-winning architect Glenn Murcutt works as a sole practitioner without staff. International recognition doesn’t eliminate the operational choice between scaling team size and maintaining direct control over every project detail.

The pattern appears across practices of all sizes. Technical excellence doesn’t protect against administrative drag. Reputation doesn’t reduce operational friction.

Software solutions typically emerge from separated development environments. Teams build tools based on market research and survey responses.

I built Gemma whilst using it daily in the same operational context as the people I’m building for. The difference matters.

The Bottom-Up Approach

Resource constraint protected Gemma from premature scaling pressure. Six years of refinement under live commercial conditions revealed failure modes invisible to separated development cycles.

The data validates the approach. When most practices operate with under 20 people, when profit margins run under 10%, when 52% of practitioners already work beyond 40-hour weeks, operational efficiency becomes non-negotiable.

You can’t survey your way to understanding this reality. You have to inhabit it.

The numbers tell the story. Australia’s building industry professional service providers face intensifying operational pressure. Small teams, complex projects, scarce talent, thin margins, extended hours.

Every hour matters. Every tool choice compounds. Every integration multiplies overhead.

I’m building Gemma for this reality. Not the theoretical one. The one revealed through six years of operational exposure and confirmed by industry data.

The pattern holds.

Let’s take a look inside the Cynefin Framework

Moving forward, we’re beginning to explore the Cynefin Framework from a more practical and operational perspective. Our goal is to understand what it truly is, the types of problems it can help address, and how we can use it to inform better decision-making.

To put it more simply:
Cynefin is a thinking framework that helps us interpret our current situation, understand its nature, and make decisions that are appropriate for the context we’re in.

To make this more concrete, I’ll illustrate the concept with an example. Throughout this series, all examples will centre on a hypothetical small professional business with around 10 team members. You are the owner and director, responsible for overseeing operations and ensuring that the workplace remains productive and effective.

Let’s outline 10 situations you might encounter during a typical day in the office:

1. During the busiest time of the year, you arrive at the office to find the internet connection is down.
2. You realise you’ve forgotten to renew your professional indemnity insurance—just as a client requests a copy of the certificate.
3. One of your most dependable team members has recently made several serious mistakes.
4. A key staff member arrives at work showing cold and flu symptoms.
5. You’re expected to organise a birthday celebration for a colleague.
6. You discover rotten food has been left in one of the office cupboards.
7. You need to apply for an environmental compliance certificate that significantly impacts your operations and team processes.
8. A team member approaches you requesting early annual leave.
9. You notice someone repeatedly leaving the office to take long, private phone calls.
10. One of your clients’ email accounts has been compromised, and your office is now receiving suspicious emails from their address.

Now, take a moment to reflect on these situations. They represent just a small sample of the kinds of challenges that can arise in a typical office environment—each requiring a decision and an appropriate response.

Ask yourself: for how many of these situations do you know exactly what to do—every time—and feel confident that the same action would always produce the right outcome?

Personally, I can think of one. Take situation number 2, for instance: forgetting to renew your professional indemnity insurance. In that case, the best practice is almost always to contact your insurer and request the certificate as soon as possible.
But for the rest? If you believe you have a fixed, clear response and know the best course of action in each of those scenarios, then you’re either incredibly fortunate—or you stand to gain a lot from the material I’m about to share with you.

The reality is that these situations are dynamic and highly context-dependent. You might apply the same solution repeatedly, but you know from experience that the outcome can vary. In most cases, there is no universal best practice. These problems differ not just in their content but in their nature. Some are relatively predictable. Others can quickly evolve, spawning unexpected consequences. A few are completely random—where you don’t even know what you’re dealing with until you intervene.

When you try to solve these problems, your actions might help—or they might make things worse. There’s rarely a guarantee that any one decision will take you in the right direction. Even more importantly, the very act of addressing a problem often changes the problem itself. For example, if you ask an employee, “Why do you want to leave early?” or “Why can’t you wait until your project is complete?”, their responses may vary dramatically—or even be improvised—based on how you approach them.

This illustrates the reality of management and leadership: it’s rarely straightforward. One of the biggest challenges in being an effective leader is making the right decisions—especially in uncertain or evolving conditions. And this is exactly where the Cynefin Framework proves its value.

Cynefin helps by categorising our circumstances into specific domains, each with distinct characteristics and corresponding strategies. By understanding the nature of the situation you’re in, you can align your decisions with the context—avoiding actions that are mismatched or even harmful to the problem at hand.

Here are the domains of the Cynefin framework

Cynefin Framework Diagram

We’ll revisit the Cynefin diagram many times throughout this series. Each time, we’ll elaborate further and explore each domain in detail. For now, let’s take a moment to look at the diagram and develop a foundational understanding.
Every situation, circumstance, problem, or moment in time can be understood through one of Cynefin’s core domains: Clear, Complicated, Complex, or Chaotic.

The Four Main Domains

Clear
This is where things are straightforward. Cause and effect are obvious, and the correct course of action is well-known and consistently applicable. Best practices are reliable here.

Complicated
Cause and effect exist, but they are not immediately obvious. Solving these problems requires analysis, investigation, or expert knowledge. There may be multiple valid approaches to the same issue.

Complex
Here, cause and effect can only be understood in hindsight—if at all. Outcomes emerge through interaction rather than through deliberate design. There are many interconnected variables, and actions often produce unintended consequences.

Chaotic
There is no perceivable cause-and-effect relationship, not even in hindsight. The environment is unstable, unpredictable, and fast-moving. Events are highly volatile, and immediate action is often required without time for analysis.

Understanding where we stand is the first—and most crucial—step in making effective decisions.

If we mistakenly assume we’re in a Clear domain when we’re actually in a Complex one, our decisions are likely to be misinformed, rigid, and shortsighted.

Let’s revisit our earlier definition of Cynefin:

“Cynefin is a framework of thinking that allows us to make sense of our current circumstances, understand its reality, and help us make adequate decisions depending on where we stand.”

By now, you should be in a stronger position to grasp the significance of this framework. If we can correctly identify the nature of a situation—and understand the appropriate mindset and response it requires—we put ourselves in a position to make better-informed, more effective decisions. In short, we become more competent and adaptive leaders.

Re-examining Our 10 Scenarios: What Domain Are They In?

Let’s take a few examples from our earlier list and place them within the Cynefin framework:

During the busiest time of the year, the internet is down.
This is a Chaotic situation—there’s no time to analyse. You must act immediately to restore order. Good luck.

A team member frequently sneaks out for long phone calls.
This could be either Complicated or Complex, depending on what’s driving the behaviour. Investigation is necessary, and the solution may vary depending on the human factors involved.

You need to apply for an environmental compliance certificate that significantly impacts your operations and team processes.
This is firmly in the Complex domain—there are many variables, multiple stakeholders, and evolving constraints.

In day-to-day business operations, we most often find ourselves in the Complex domain. If we can become fluent in navigating complexity—particularly within Complex Adaptive Systems—we will rapidly improve the quality of our decisions and the resilience of the systems under our leadership.

In the next posts, we’ll take a deep dive into each of the Cynefin domains. We’ll explore real-world or hypothetical examples, discuss the most effective ways to approach decision-making within each context, and introduce additional concepts such as liminality and constraints that shape how problems and solutions evolve.
Before closing, I’d like to leave you with this insightful quote from Dave Snowden, the creator of the Cynefin Framework. It beautifully captures the spirit behind his life’s work:

See you in the next post.

The Cynefin Framework: Where We Begin

The Cynefin Framework is the first subject we’ll explore in this series of posts. Let’s begin with a formal definition—one you might come across in an internet search (or via an AI tool these days):

“The Cynefin Framework is a conceptual model used for decision-making in complex environments. Developed by Dave Snowden in 1999 while working at IBM, it helps leaders and organisations better understand the nature of the problems they face and choose appropriate responses.”

Now, that definition is generic enough to remind you of countless other frameworks, tools, or buzzwords promising the world. But let me assure you—Cynefin is none of those things. This framework is nothing short of revolutionary, and it has proven its value in real-world situations time and again.

In this first post, we’re not going to dive straight into its internal structure or practical applications. I believe the best way to approach any meaningful knowledge is to first understand where it comes from. So let’s start with a bit of history.

Meet the Mind Behind Cynefin: Dave Snowden

Dave Snowden, the creator of the Cynefin Framework, was born in Wales and studied physics and philosophy. He graduated in 1975 (the same year I was born) with a Bachelor of Arts (Honours) in Philosophy from the University of Lancaster.

Snowden rose to prominence in the late 1990s and early 2000s during his time at IBM’s Institute for Knowledge Management. If you’ve ever listened to his lectures or interviews, you’ll know he has some fascinating stories to share. While at IBM, he led groundbreaking work on narrative-based sense-making—focusing on how organisations interpret and respond to rapidly changing environments. It was during this period, in 1999, that the Cynefin Framework was born.

Snowden’s work stands at the intersection of science, philosophy, and leadership. He firmly rejects the “systems engineering” mindset that treats organisations like predictable, controllable machines. Instead, he advocates for a more accurate view of reality—organisations as complex adaptive systems. A large part of this series will explore such systems, which, I must admit, is the part I find most fascinating.

His work has been cited in books, academic research, and leading publications. He’s a sought-after speaker, having presented at the World Economic Forum, MIT, the London School of Economics, and numerous international events.

So yes—Dave is awesome.

What Does “Cynefin” Mean?

Before we get into the framework itself, let’s clear up one important thing: pronunciation.

Cynefin is pronounced “kuh-nev-in.”

It’s a Welsh word that roughly translates to habitat or place of belonging. This meaning reflects the framework’s core emphasis: context matters. Understanding the nature of a situation before taking action is not just a feature of Cynefin—it’s its greatest strength.

Unlike many rigid management tools or abstract theories, Cynefin is natural, human-centred, and grounded in how real people make sense of their world. It’s deeply transformative and designed for messy, unpredictable, and evolving conditions.

Where Has Cynefin Been Used?

In the mid-2000s, Cynefin began gaining traction across governments, militaries, and large corporations. It quickly became a go-to model for managing uncertainty, especially in volatile or fast-changing environments.

By the 2010s, it was embraced by agile practitioners, public service leaders, healthcare administrators, and systems thinkers. It influenced related models like the Stacey Matrix and embedded itself into the broader field of complexity science.

Following the COVID-19 pandemic, Cynefin’s relevance skyrocketed. Organisations around the world turned to it for navigating crisis and complexity. It helped leaders avoid the mistake of applying linear solutions to nonlinear problems—where fixed plans tend to fail, and adaptability is critical.

Breaking the Bubble: Cynefin for the Rest of Us

Despite its power and growing recognition, the Cynefin Framework is still mostly used by large institutions, governments, and top-level decision-makers. That needs to change.

In this series, my aim is to bring Cynefin to the rest of us—small business owners, independent professionals, and everyday leaders navigating uncertainty, growth, and complexity.

From the next post onward, we’ll begin unpacking its core concepts. And we’ll do it in a way that speaks directly to our world—the messy, unpredictable, real-world challenges we face every day.

Thank you for reading—and I look forward to seeing you in the next post.