Why professional judgement needs stronger foundations than software can provide.
TSBP Thought Leadership Series
Every profession has an underlying framework that quietly shapes the way its people think, make decisions and deliver consistent work.
In accounting, it’s the principles of double-entry bookkeeping, accounting standards and tax legislation. In law, it’s legislation and legal precedent. In medicine, it’s clinical frameworks and evidence-based practice. In engineering, it’s the principles that determine whether a structure stands or falls.
These frameworks are so fundamental that professionals rarely think about them. They simply trust that everyone is working from the same foundations.
Advisory has grown enormously over the past decade. Firms have invested in software, training, new service offerings and better client conversations. Yet there is one question the profession rarely stops to ask.
What is the underlying framework that makes advisory consistent?
It’s a surprisingly difficult question to answer.
And perhaps that’s because we’ve become very good at talking about advisory, without ever clearly defining the structure that sits beneath it.
What Do We Actually Mean by a Framework?
Advisory has become increasingly sophisticated, yet the thing sitting beneath it is rarely discussed. We spend a great deal of time talking about software, services and client conversations, but far less time considering the framework that allows advisory to be practised consistently.
When people hear the word framework, they often picture something tangible. A piece of software. A meeting agenda. A checklist. A set of templates. They’re all visible. They’re easy to recognise. They give advisory a sense of order, so it’s understandable why they’ve become synonymous with structure.
But those things don’t actually explain how advisory works. They simply help us organise it.
The distinction is subtle, but important.
Perhaps the easiest way to understand a framework is to look at those we’ve been using our entire professional lives. Consider accounting for a moment. Double-entry bookkeeping and accounting standards don’t prepare a set of financial statements. Taxation legislation and reporting requirements don’t complete tax returns. They were never intended to. Their role is much deeper than that. They provide the principles that guide professional judgement, creating a common way of thinking that allows accountants in different firms, in different cities and even different countries to produce work that is recognised, understood and trusted.
The framework doesn’t do the work. The professional does. The framework simply ensures that professional judgement is applied consistently.
Which brings us back to advisory.
If software isn’t the framework, and templates aren’t the framework, what is? Before we can answer that, we first need to recognise that they solve a different problem. Software helps us manage work. Templates help us repeat work. Checklists help us complete work. None of them, however, determine how an adviser should think, diagnose a business, establish the scope of an engagement or decide what matters most.
Those decisions still rely on professional judgement.
The question, then, isn’t whether advisory needs more software or better templates. It’s whether the profession has developed the underlying framework that allows that judgement to become consistent across an entire firm.
If the profession is struggling to identify the framework that sits beneath advisory, perhaps the first place to look is the language we’ve been using.
For years, we’ve been talking about structure as though it were a single idea. It may not be.
So What Has the Profession Been Calling Structure?
Perhaps this explains why structured advisory has become such a difficult term to interpret.
Ask five providers what they mean by structure and you’ll probably receive five different answers. One will talk about software. Another will describe a methodology. Someone else will demonstrate a meeting agenda or a library of templates. None of them are necessarily wrong. They’re simply talking about different layers of the same system.
Imagine attending five advisory conferences. By the end of the week, you could leave believing “structured advisory” means five completely different things. Each presenter would be describing something valuable, yet each would be referring to a different layer of the same system.
Figure 1. The Anatomy of Structured Advisory
Structured advisory is not a single solution. It is a hierarchy of interconnected layers, each serving a different purpose.
The difficulty begins when those layers become blurred.
The value of thinking about advisory in this way is that each layer has a distinct role to play. The difficulty begins when we expect one layer to perform the role of another.
Accounting firms are busy. Time is scarce. Software does exactly what good software should do. It helps organise, automate and scale delivery.
What it cannot do is create the professional framework that determines how advisers think, diagnose a client’s situation, establish scope or exercise judgement. Those things have to exist before the software becomes valuable. Otherwise, technology simply helps us execute a process without first defining the thinking that sits behind it.
It also explains why so many firms feel they’ve invested heavily in advisory, yet still struggle to make it consistent across the team. They have built excellent tools and increasingly refined processes, but the layers above them remain largely undefined.
In the absence of an underlying framework, advisers naturally fall back on what they already know. Some rely on years of experience. Others trust their instincts. Many simply avoid conversations they don’t feel equipped to lead. The quality of advisory becomes dependent on the individual rather than the firm.
Over time, something more damaging begins to happen. Partners start believing that only a handful of people are capable of delivering good advisory. Managers conclude they’re simply “not advisory people”. Team members convince themselves they’re not strategic enough, not confident enough or not experienced enough to have those conversations.
Yet those conclusions are often based on the wrong diagnosis.
The problem isn’t necessarily a lack of capability. It’s that people are being asked to exercise professional judgement without first being given the framework that helps shape it. We would never expect a graduate accountant to instinctively understand accounting standards simply because they had accounting software. Yet in advisory, we often expect people to become strategic through experience alone.
They’re not failing because they can’t do advisory. More often than not, they’re trying to do it without the underlying structure every other profession takes for granted.
Why Does This Matter?
At first glance, this distinction between frameworks, methodologies and software might seem academic. In practice, it influences almost every challenge firms experience when trying to deliver advisory consistently.
Perhaps the reason so many firms continue to wrestle with advisory is because they’ve been treating the symptoms as though they were separate problems.
One partner seems to deliver exceptional advisory, while another approaches similar clients quite differently. Managers hesitate to lead strategic conversations without a partner in the room. Valuable advisory work is delivered every day, yet much of it is never recognised as a distinct engagement. It simply evolves from an existing client conversation, with little thought given to scope, boundaries or value before the work begins. The result is predictable. Advisory is charged by the hour because it was never intentionally designed to be anything else.
Without a shared framework, even recognising when advisory has begun becomes a matter of individual judgement. One adviser sees an opportunity to step into a strategic engagement, while another simply sees themselves helping a client. The difference is subtle, but the commercial consequences are significant. Scope remains undefined, expectations are left unspoken and valuable work quietly disappears into timesheets.
Firms invest in new software, hoping greater consistency will follow, only to discover that very little has changed.
Over time, those observations become accepted as reality.
“Our partners all have different styles.”
“Some people just aren’t naturally advisory.”
“Our managers aren’t confident enough yet.”
“We just haven’t found the right software.”
They sound like different challenges, but perhaps they all point to the same underlying cause.
Without a shared framework to guide professional judgement, every adviser is left to develop their own way of thinking. Some arrive there through years of experience. Others never quite feel confident enough that they’re asking the right questions or reaching the right conclusions. The variability isn’t surprising. In many respects, it’s exactly what we should expect.
The impact extends well beyond individual conversations. It influences how firms develop people, delegate advisory and build capability. Without a common framework, leaders have little more than instinct and experience to coach from. Advice such as “be more strategic” or “ask better questions” is well intentioned, but difficult to teach consistently when everyone is working from a different mental model. Capability develops unevenly because there is no shared foundation on which it can grow.
Perhaps the greatest consequence, however, is that advisory remains a capability of individuals rather than a capability of the firm. Knowledge sits in the experience of trusted partners, confidence varies from person to person and consistency becomes difficult to reproduce across the team. When capability remains personal rather than organisational, consistent advisory never becomes a capability of the firm. It remains the strength of a few individuals.
When advisory remains the strength of a few individuals, it’s easy to assume the problem lies with the people. That some accountants simply aren’t strategic enough, confident enough or suited to advisory work.
But what if that’s the wrong diagnosis?
Every profession relies on a framework to help people develop sound professional judgement. Advisory is no different. Expecting advisers to become consistently strategic without that foundation is rather like expecting consistency in financial reporting without accounting standards. The issue isn’t a lack of capability. More often, it’s the absence of a shared structure that allows capability to develop.
So What Should an Advisory Framework Actually Achieve?
If that diagnosis is correct, and an advisory framework isn’t software, a methodology or a collection of templates, the next question becomes inevitable. What should an advisory framework actually provide?
Perhaps the answer is simpler than we think.
A good framework doesn’t remove professional judgement. Nor does it attempt to tell advisers exactly what to say or what recommendations to make. Every business is different, and every client brings a unique combination of opportunities, challenges and priorities.
What a framework should provide is a consistent way of thinking.
It should help advisers approach different businesses with the same discipline they already apply to financial reporting or tax. Not by producing identical outcomes, but by ensuring the right questions are explored before conclusions are reached.
In practical terms, an adviser should never have to wonder where to begin, what to explore next or whether they’re asking the right questions.
Instead, the framework quietly guides the thinking behind the conversation.
- How do I distinguish symptoms from the real problem?
- How do I identify what matters most right now?
- How do I establish the scope of the engagement before the work begins?
- How do I ensure another adviser would approach this client with the same underlying logic?
- How do I know we’re solving the right problem, rather than simply responding to the loudest one?
Notice that none of these questions are about software. None are about templates or workflows. They all sit higher in the hierarchy because they shape the judgement that every other layer depends upon.
Perhaps that is the real purpose of an advisory framework. Not to replace the experience of the adviser, but to give every adviser a common foundation from which experience can grow.
Conclusion
If that is the role of a framework, perhaps every leadership team should pause to consider one simple question…
Could you describe yours?
Not the software your team uses, or the templates your advisers complete. Not the meeting agenda that keeps conversations on track.
The framework itself.
The one that guides how your advisers distinguish symptoms from underlying problems, establish scope, prioritise opportunities and consistently apply professional judgement across every client conversation.
If that question is difficult to answer, perhaps the challenge isn’t finding another advisory tool.
Nor is it expecting your team to create an advisory framework from scratch.
The role of leadership has never been to invent the foundations of a profession. It is to recognise their importance, choose them deliberately and embed them consistently across the firm.
The true measure of an advisory firm isn’t the capability of its best adviser. It’s the consistency with which the whole team can deliver strategic thinking.
Every mature profession stands on a shared framework.
Perhaps it’s time advisory did too.