![A professional services firm spent eight months and most of a six-figure budget on what their...]()
A professional services firm spent eight months and most of a six-figure budget on what their preferred vendor described as an AI-powered workflow platform. Two months after launch, the honest post-implementation review surfaced three findings the leadership team had not been preparing for.
Time saved per file was about 45 minutes, on the document-summary step. Time spent training, fixing, and reviewing exceeded the time saved by a factor of two. The firm had been describing itself externally as AI-driven for five months by the time the review confirmed the AI was a search and summary tool with a polished interface.
The cost of the platform was the smaller half of the cost. The larger half was the internal disillusionment and the external positioning that would need to be quietly walked back.
ASIC has now named the governance gap. The ACCC has flagged AI washing on its enforcement priorities. The calculation has changed.
Save this for the next platform post-mortem.![A practical exercise for any leadership team carrying a description of the business that runs ahead...]()
A practical exercise for any leadership team carrying a description of the business that runs ahead of the operational reality.
Every member of the leadership team writes one list. The specific work the business actually does for clients. The specific outputs that work produces. The specific decisions or outcomes those outputs influence.
The lists are combined into a single document. Duplicates collapsed. Unverified claims marked.
The output is rarely the document. The output is the conversation about how thin the document is, and which line of the business is being described in language the team inside it cannot defend.
The exercise takes about a week of calendar time. The conversation it produces takes about a quarter to resolve.
What would your single page actually say?![The fear underneath most capability claims is recognisable across the businesses Decisive...]()
The fear underneath most capability claims is recognisable across the businesses Decisive Leadership works with. The pressure to have a story sharper than the operational base supports comes from every direction at once: investors, board, recruitment, competitors, and the quarterly rhythm of needing to describe the next altitude before the current altitude has been fully built.
Three diagnostic questions separate the story from the substance, on any capability claim. Which client, this quarter, is being served differently because of the stated change? Which task has been removed from a human, and where did that work go? If the capability was removed tomorrow, what would actually break?
The leaders who can answer all three honestly are doing the work the story describes. The leaders who can answer none of them are doing something else, and the gap is the work.
Save this for the next time a capability claim is on the agenda.![The most useful test of a business is rarely the strategy document. It is whether the people inside...]()
The most useful test of a business is rarely the strategy document. It is whether the people inside the business, asked to describe what they do to a friend over dinner, would use language recognisable to the people who wrote the strategy document. Where the two versions match, the business runs at one altitude. Where they diverge, the cost is paid quietly, by everyone in the business who has to operate inside the difference.
The hope this week names is institutional, not aspirational. Work toward a business that runs at one version of itself.![The system most likely to break first under sustained pressure is rarely the one most leaders are...]()
The system most likely to break first under sustained pressure is rarely the one most leaders are watching. The cash position is watched. The pipeline is watched. The margin is watched. The system that decides who gets to decide is usually the system that has not been examined since the business was last redesigned, which may have been years ago.
Pressure does not invent organisational fragility. It reveals fragility that has been accumulating quietly. The decisions that have been deferred because nobody was named to make them. The approvals that have migrated one level up over time. The calls that get returned without resolution and then get overtaken by events.
This week's newsletter on Self-Aware Leadership works through the decision audit: where decisions are actually being made in the organisation, what the cost is of the ones that live nowhere, and the three properties of a decision that has been built well. The newsletter is live on LinkedIn now - Check the comments section below. 👇
What is the unwatched system in your business right now?![Jason (an accountant who runs his own firm) was working through a price increase on a Thursday...]()
Jason (an accountant who runs his own firm) was working through a price increase on a Thursday afternoon in March, three months after the increase should have happened. The call did not go well. The client was not unreasonable; the issue was that nothing about the increase had been planned, briefed or owned. Jason had walked into a difficult conversation without the architecture that would have made it manageable.
The pricing review should have been a decision made in November, by the senior accountant who managed the client. The decision had not been made, because nobody had been told they were the person to make it. The most expensive line item in Jason's quarter was not labour or software; it was the cost of a decision that had lived nowhere and belonged to no-one.
Six weeks later, Jason and his team had named ownership for every recurring decision the firm makes. Each has one named person, a timeline, and a default action if the timeline is missed. The next pricing review happened, on time, without escalating to Jason at all.
Which decisions in your business currently live nowhere?
#EvidenceAndImpact #Leadership #DecisionArchitecture![Decision drift is what happens when a call that belongs at one level of the organisation migrates...]()
Decision drift is what happens when a call that belongs at one level of the organisation migrates upward, approval by approval, over months and quarters. The first time it makes sense. The supplier is new, the contract is unusually large, the team is inexperienced. The fourth time around, the decision lives one level above where it should sit, and nobody has noticed it move.
The pattern only becomes visible when someone looks for it. The supplier approved four times in eighteen months. The hire confirmed twice when the manager is supposed to own that call. The pricing exception escalated for the third quarter running. None of the individual decisions felt like a problem; the accumulation is the problem.
The goal worth setting this week is small. Identify three decisions on your desk in the next five days that, on examination, should be made one level below you. Then do the harder part. Hand them back, with the authority and information required to make them well.
What is the decision you keep re-deciding?![The fear most experienced leaders carry into significant decisions is rarely a fear of not knowing...]()
The fear most experienced leaders carry into significant decisions is rarely a fear of not knowing the options. The trade-offs are usually well understood. What the fear is actually about is the cost of committing, and finding out six months later that the call has compounded into decisions that are harder to reverse than the original one was.
A well-designed decision has three properties. It is bounded, which means the scope of commitment is clear. It is reversible where reversibility is possible, which means changing course is not prohibitively expensive. It has a recovery plan, which means there is a clear answer to what happens if the call turns out wrong. When all three are present, the fear of getting the decision wrong tends to drop by an order of magnitude, because the cost of being wrong is bounded.
The most useful question to ask before any significant call is rarely "is this the right decision?" The more useful question is "is this a decision I can recover from?"
What is the next decision you have been deferring because the cost of being wrong feels unbounded?![Last week's work examined who holds the critical knowledge in a business, and what the organisation...]()
Last week's work examined who holds the critical knowledge in a business, and what the organisation looks like when that knowledge is distributed by design. This week's question is the next one in the sequence. When the knowledge gets used, who actually makes the call?
The decision audit is the diagnostic exercise that surfaces the answer. Not where the policy says decisions are made; where they are actually made, in practice, day to day. Most organisations find a meaningful gap between intention and reality the moment they look for it.
This week the page works through three questions: where decisions are actually being made, what the cost is of the decisions that live nowhere, and the three properties of a decision that has been built well.
How many of the decisions on your desk this week should not be on your desk?![The dimension trilogy closes this week with the Process dimension, and the case study completes the...]()
The dimension trilogy closes this week with the Process dimension, and the case study completes the working example of what the Diamond Architecture produces when each dimension is built deliberately.
What comes next is the operating phase, and the work the operating phase requires is different from the work the building phase rewarded. The building phase rewarded a particular kind of leader: hands-on, present, willing to operate inside the work while simultaneously designing the system that would eventually replace that operation. The operating phase rewards something different. The capacity to let the architecture do what it was designed to do. The discipline of redirecting the time previously absorbed by operational work into the strategic work the building phase deferred. The recognition that the team's communication has shifted from problems to questions, and the leader's role has shifted with it.
Three transitions follow the building phase. The first is calendar composition. The second is communication texture. The third is the leader's relationship to operational visibility. Each transition is harder than it sounds, because the habits formed during the building phase do not switch off when the architecture goes live.
Save this for the conversation about which phase your leadership is currently in.![Victor's email a fortnight ago opened with five words: I think we are done. The we was the...]()
Victor's email a fortnight ago opened with five words: "I think we are done."
The "we" was the architectural work he had started fourteen months earlier when his firm had been running on adrenaline, weekend hours, and his own continuous operational presence. The "done" meant something specific. The Process dimension work had completed, and the firm's calendar had inverted: four scheduled strategic sessions per quarter where there had previously been zero, and zero unscheduled operational interventions where there had previously been seventeen.
Escalation rate from eighteen per week to four. Cycle time reduced by thirty-eight per cent. Revenue increased twenty-two per cent over the period.
The numbers are the visible outcome. The change underneath is the calendar composition that produced them, which followed from three design choices made deliberately: documenting the question rather than the answer, naming the trigger conditions and decision criteria explicitly, and building the calibration mechanism into the operating routine.
The case study has run across this thirteen-week cycle as the working example of what the Diamond Architecture produces when each dimension is built. This week's instalment closes the case study and the dimension trilogy.
What does your own ratio of scheduled strategic sessions to unscheduled operational interventions currently look like?![Process maturity is not a function of documentation volume or the polish of the diagrams. It is a...]()
Process maturity is not a function of documentation volume or the polish of the diagrams. It is a function of three design choices.
The first is whether the assumed conditions the documentation operates under are explicit. The second is whether the triggers that signal those conditions have changed are named. The third is whether the calibration mechanism that updates the documentation is built into the process itself rather than dependent on the individual leader's intervention.
A four-level maturity model is useful for the diagnostic. Level one is undocumented practice. Level two is documented procedure. Level three is designed process. Level four is a self-maintaining operating system in which the calibration mechanism is part of the operating routine rather than an exception to it.
Most organisations occupy a mix of levels across their portfolio of processes. The diagnostic question for any specific process is which level it currently sits at and which design choice would move it to the next.
Save this for the planning conversation about which of your team's processes have reached level four, and which are still operating at level two.![The most common version of the rigidity fear is the founder who tells me they do not want a team of...]()
The most common version of the rigidity fear is the founder who tells me they do not want a team of people who follow a process. They want a team of people who think.
The fear is legitimate, and it is well-founded against the version of process design that documents the answer the team should produce. That version produces rule-followers, and rule-followers lose adaptive capability over time. The diagnostic question is whether the documentation in the organisation is the rule-following version or the framework-supporting version.
The frame that resolves the fear is simple to state and harder to apply: document the question, not the answer. Capture the trigger conditions, the decision criteria, and the calibration mechanism. Let the team apply judgement within the framework. Adaptive capability develops through use. The framework makes the judgement reliable, visible, and reviewable.
The same word, "process", describes both designs. The energy at the end of the week under each one is completely different.
Which version is currently sitting in your team's documentation?![The third dimension of the Diamond Architecture is the one most leaders assume has been built,...]()
The third dimension of the Diamond Architecture is the one most leaders assume has been built, because process documentation exists in the organisation and the existence is taken to mean the dimension has been addressed.
The diagnostic question is different. It is whether the documented processes include explicit assumed conditions, the triggers that signal those conditions have changed, and the calibration mechanism that updates the process when the triggers fire. Most documented processes do not include these layers. They were written under specific conditions, captured the answer the team had developed under those conditions, and have not been revisited since.
The process continues to operate exactly as designed. The conditions have moved. The team experiences the change as a failure of the process rather than a feature of its design.
This week examines what the Process dimension actually involves: the four operating states, the rigidity fear and the document-the-question frame, the four-level process maturity model, the diagnostic method that selects which processes to address in which order, and the case study of a fourteen-person accounting firm whose calendar inverted over twelve months of deliberate work.
What does your most-used documented process currently assume?![A 60-person engineering consultancy spent eighteen months investing in capability. The team became...]()
A 60-person engineering consultancy spent eighteen months investing in capability. The team became measurably more capable. The throughput numbers did not move.
The leadership team interpreted the result as a capability question that had not yet resolved. The structural diagnostic surfaced something different: the decision rights framework the firm was operating on had been designed implicitly when the firm was twenty people, and had never been updated as the firm grew to sixty.
The senior team had the capability for the decisions they were escalating. The framework had not given them the structural confidence to act on it.
Eight weeks of structural work later: a 40% drop in the escalation rate, a 15% improvement in project cycle times, and a measurable shift in how the principals were spending their time.
The capability investment had not failed. It had been waiting for the structural work to translate it into operational reality.
The pattern is common in firms in the 40-80 person range.
