Month: June 2026

Some business meetings look healthy from a distance. Everyone nods, the deck moves forward, the next steps sound sensible, and someone says, “I think we are aligned.” The room relaxes, as if strategy has been solved by collective politeness. I have sat in enough of these meetings to distrust that feeling. Internal consensus can feel mature, collaborative and efficient, but it often hides the real issue. No one wants to reopen the argument, slow things down, or become the difficult person in the room. So the team agrees, the meeting ends, and the organisation inherits a decision that may not be as clear as it looks.

The problem is simple: agreement is not the same as clarity. Agreement often means people have stopped arguing. Clarity means people understand the decision, the logic behind it, the trade-offs it creates, the risks it accepts, the work it requires and the consequences if reality refuses to cooperate. These two things can sit together, but they are not twins. Plenty of leadership teams achieve internal consensus long before they achieve strategic clarity.

Businesses get this wrong because consensus feels like progress. It gives the leadership team an emotional reward before the business has earned a commercial one. A messy strategic question becomes cleaner once enough people have said yes. The hard edges soften. The unresolved assumptions disappear into friendly wording. Everyone can leave the room with a task, a smile and a faint suspicion that something important never received the argument it deserved.

This usually happens when the real issue sits underneath the formal agenda. The meeting says market expansion. The real issue says the company does not know whether its proposition travels. The meeting says technology investment. The real issue says the operating model cannot absorb another tool without becoming even more confused. The meeting says fundraising readiness. The real issue says the business has not explained why capital will create value rather than simply buy time. Internal consensus can hide all of that beautifully.

It normally starts with good intentions. A leadership team wants alignment. That sounds reasonable. Investors like alignment. Boards like alignment. Employees certainly prefer it to executive improvisation performed over twelve months. So the team works hard to get everyone on the same page. The phrase sounds harmless, although in practice it often means reducing a complicated decision until nobody feels personally threatened by it.

The finance director wants discipline. Sales wants flexibility. Operations wants realism. Product wants ambition. Marketing wants a story people can actually understand. The CEO wants momentum. None of these people are wrong. That is what makes the problem so irritating. Internal disagreement rarely comes from villains sitting around a table trying to sabotage the annual plan. It comes from intelligent people defending different truths.

A good decision does not erase those truths. It orders them. Poor consensus tries to make every perspective equally comfortable. Clear strategy decides which perspective matters most for this decision, at this moment, given the company’s constraints. That distinction matters. A business cannot pursue margin discipline, market speed, service personalisation, product breadth, operational simplicity and cost reduction with equal force at the same time. It can put all of those words in a presentation, of course. Many do. Some even add a tasteful icon set. Reality remains less cooperative.

The most dangerous form of internal consensus appears when people agree with the wording but not the meaning. Everyone approves “premium customer experience”, while one person thinks it means more human service, another thinks it means a better app, another thinks it means faster onboarding, and another quietly assumes it means higher prices. The phrase survives because it sounds attractive. The business suffers because no one forced the definition into operational daylight.

That is where clarity starts: not with better adjectives, but with sharper questions. What exactly have we decided? What have we chosen not to do? Which assumption would make this decision wrong? Who owns the outcome? How will work change next week? Which customer behaviour are we betting on? Where will costs rise before benefits appear? Is any team losing something it currently values? At what point would the evidence tell us to stop?

These questions perform a useful social function. They make vague agreement more expensive, turn nodding into responsibility, and reveal whether the leadership team has made a decision or simply created a phrase that everyone can tolerate. Internal consensus often struggles under this pressure because it must become specific, and specificity has a nasty habit of exposing the compromises hidden inside elegant language.

I once saw a team agree enthusiastically on a “focused growth strategy”. A beautiful phrase. Soothing, balanced, impossible to dislike. Then came the awkward question: which customer segment would receive less attention as a result? Silence arrived, pulled up a chair, and made itself comfortable. Nobody wanted to answer because the answer would create consequences. A real focus would disappoint someone. It would change targets, budgets, hiring, product priorities and senior attention. Until that moment, “focused growth” had meant growth without the unpleasant business of focus.

That is the little theatre of consensus. It lets leadership teams borrow the language of choice while avoiding the cost of choosing. The team feels aligned because the words feel acceptable. The organisation then discovers, usually several months later, that acceptable words do not allocate resources, resolve conflicts or make difficult trade-offs on behalf of the people who avoided them.

This does not mean disagreement should become a corporate sport. Some teams mistake challenge for performance art. They turn every decision into a courtroom drama, then wonder why the organisation moves like wet furniture. Clarity does not require endless debate. It requires useful tension before commitment, followed by disciplined execution once the decision has been made.

The practical lens is simple: treat internal consensus as an input, not an outcome. People need to support a decision, different functions must understand the implications, and those closest to the work should have room to highlight risks the boardroom may have missed. But consensus should not have a veto over clarity. The aim is not to make everyone equally comfortable; it is to make the decision explicit, owned and testable enough to survive contact with reality.

Leadership teams should separate three things that often get bundled together: discussion, decision and commitment. Discussion should welcome disagreement. Decision should have a clear owner. Commitment should follow once the decision has been made, even when some people would have chosen differently. Without that separation, businesses drift into a strange hybrid where everyone discusses, nobody truly decides, and commitment depends on whether the final wording offends the fewest people.

This is why decision rights matter. Not as bureaucratic theatre, with matrices that look like the wiring diagram of a submarine, but as plain business hygiene. A leadership team needs to know where the recommendation comes from, where challenge belongs, and where the final decision sits. It should also be clear who must live with the consequences, who needs to stay informed, and who does not get to redesign the decision by email three days later. Clear decision rights save companies from the slow misery of invisible vetoes.

The other discipline is assumption testing. Every important decision carries a bet. The bet may concern customer demand, pricing power, execution capacity, investor appetite, regulation, technology adoption or competitor behaviour. Internal consensus often blurs the bet because naming it creates discomfort. Clarity names it early. A leadership team should be able to say, “This works if these three things prove true. If they do not, we will know by this date and adjust in this way.”

That kind of clarity feels less cosy than consensus. It also travels better through the organisation. Employees do not need leaders to pretend that difficult decisions have no trade-offs. They need to understand what matters, what changes, what stops, and why. When leaders explain the logic clearly, people can act with more confidence. When leaders hide behind broad agreement, people spend months interpreting the decision through their own departmental interests.

Internal consensus can make a leadership team feel united, but clarity makes a business easier to lead. That difference looks small in the meeting room. It becomes enormous once the work begins.

Most business transformation programmes do not fail because the technology refuses to work. They fail because the business never quite decided what work the technology was meant to do. That sounds painfully obvious, which is why it keeps getting ignored. A leadership team gathers around a table, agrees that the organisation must modernise, and within minutes the conversation drifts towards platforms, systems, automation, AI, dashboards, cloud migration, workflow tools, data lakes and other expensive nouns. Everyone feels comforted. Technology gives change a physical shape. You can buy it, install it, demo it, blame it, upgrade it and put it on a steering committee slide with a reassuring blue icon.

Business logic, on the other hand, behaves badly in meetings. It asks awkward questions. Why are we changing? Which customers matter most? Which margins do we want to protect? And which activities should we stop doing? Who gets to make decisions after the transformation? What trade-offs will we accept? Which parts of the operating model no longer make sense? These questions lack the theatrical glamour of a vendor presentation, but they usually decide whether the whole thing works.

This is why so many business transformation efforts look impressive from a distance and slightly tragic up close. The language sounds ambitious. The investment looks serious. The governance pack has more pages than a Victorian novel. Yet six months in, people start muttering familiar things. The system is live, but the process still feels broken. The data exists, but no one agrees what it means. The new workflow has launched, but everyone still needs a meeting to make a decision. A digital front door has opened, but the back office still resembles a cupboard full of extension leads.

The uncomfortable truth is simple: technology accelerates whatever business logic already exists. If the logic is clear, technology can scale it. If the logic is confused, technology gives confusion better shoes.

This matters because transformation failure is not some rare corporate weather event. It remains stubbornly common. BCG says only about 30% of companies successfully navigate digital transformation, while its analysis of broader corporate transformations found that only one in four deliver value-creating, enduring change. McKinsey has also argued that transformation requires rewiring the organisation, not merely deploying technology at scale.

The usual mistake starts with a false sense of practicality. Leaders believe they are being action-oriented by moving quickly to solutions. They want momentum. They want something visible. And they want to show the board that change has begun. So the transformation begins with a system selection, a technology roadmap or a promise to automate broken work. This creates activity, but not necessarily progress.

I have seen this pattern many times. A company wants faster customer onboarding, so it buys a new platform. Sensible enough. But no one has resolved who owns the customer journey, which risks genuinely require escalation, which documents still matter, which checks can be removed, or who has authority to make exceptions. The platform arrives like a well-dressed guest at a chaotic dinner party. It cannot fix the seating plan, the menu, the family tension or the fact that no one knows who invited the accountant.

Then the business blames adoption. Staff “resist change”. Managers “need training”. Users “lack confidence”. Sometimes that is true, but often people resist because the transformation has made their work more confusing, not less. They now have a new interface layered over old rules and old problems.

The deeper issue is that many organisations treat the operating model as a detail, when it is the thing. An operating model answers how the business actually works. It defines where decisions sit, how teams interact, how information flows, how value reaches the customer, and how performance gets managed. Technology should support that model. It should not invent it by accident.

When change starts with technology, the operating model often emerges as a side effect. The system forces certain workflows. The implementation partner makes assumptions. Departments defend their existing habits. Senior leaders approve compromises they do not fully understand because the project cannot afford delays. By the time the system goes live, the company has made dozens of operating model decisions without admitting it. This is a marvellous way to redesign a business, assuming your strategic method of choice is accidental archaeology.

Decision clarity matters just as much. Transformation always changes power, whether people say that aloud or not. It changes who can approve, who can challenge, who gets information, who loses manual control, and who becomes accountable for outcomes. If leaders do not define decision rights early, the organisation quietly recreates the old model inside the new one.

That is when dashboards multiply but decisions slow down. Everyone can see more information, but no one knows who should act on it. Committees expand because technology exposes problems faster than leadership resolves them. The company becomes more transparent and more paralysed at the same time, which is quite an achievement.

A better approach starts less dramatically. Before choosing tools, the leadership team should define the business logic of the change. That means agreeing the commercial reason for transformation in plain language. Not “to become digitally enabled” or “to leverage data”, or “to build future-ready capabilities”. Those phrases sound like they were assembled in a hotel conference room by people deprived of daylight. The reason should be concrete: reduce onboarding time from weeks to days, increase capacity without increasing headcount, improve margin by removing duplicated work, enter a new segment with a lower cost-to-serve, or give managers faster authority to act.

From there, the team should map the operating model implications. What work changes? How do roles need to adapt? Where can handovers disappear? What controls still matter? Should certain decisions move closer to the customer? How will the team measure whether the new model actually works? This does not need endless bureaucracy. In fact, it should reduce bureaucracy. But it does require discipline before procurement starts behaving like strategy.

Only then should technology enter the room properly. At that point, the question changes from “Which system looks best?” to “Which technology best enables the business we have chosen to become?” That small shift changes everything. It makes requirements sharper, and as a result, it makes vendor conversations more honest. It prevents the business from buying capability it has no intention, courage or operating model to use.

This is especially important now, because AI has made the technology-first temptation even stronger. Many leaders feel pressure to act quickly, and understandably so. Recent reporting on McKinsey’s AI work suggests stronger returns come from focused implementation rather than broad, unfocused adoption, with successful companies concentrating efforts on a small number of areas. BCG has made a similar point about AI value, arguing that companies often spread themselves too thin and fail to change workflows around the technology.

That lesson applies beyond AI. Transformation works when the business chooses a few important changes and follows them through into operating reality. It fails when leaders confuse technological movement with strategic progress.

The practical lens is this: do not ask what technology can do first. Ask what the business must become. Then ask what operating model would make that possible. Then ask what decisions need to become clearer, faster or closer to the work. Only after that should anyone be allowed near a software demo with pastries.

For a leadership team, the next move is not to slow transformation down. It is to put it in the right order. Start with business logic. Translate it into an operating model. Define decision rights. Then use technology as an accelerator, not as a substitute for thinking. That may sound less exciting than announcing a major digital transformation. It will also save everyone a great deal of money, confusion and quietly resentful workshop attendance. And that, in business transformation, counts as progress.

A good business can still struggle to raise capital, which feels mildly offensive when you first say it out loud. Surely customers, revenue, decent margins and a capable team should count for something. They do, of course. But fundraising does not reward goodness in the abstract. It rewards clarity, evidence and a story that investors can repeat without injuring themselves.

I have seen perfectly respectable businesses walk into capital conversations and somehow make themselves look more fragile than they really are. The product works. The market exists. The customers are not imaginary. The founder knows the industry. Then the deck opens, and within fifteen minutes, everyone in the room has quietly lost the plot. Not because the company is bad. Because the investment case has arrived wearing three coats, two hats and no shoes.

That is the part many leadership teams underestimate. Investors are not simply asking, “Is this a good business?” They are asking, “Is this a good investment, at this price, with this risk, using this money, under this management team, in this market, now?” A small difference. Only the entire difference.

The current market makes that gap harder to hide. Private capital has not vanished, but it has become more selective. Reuters recently reported that private equity firms are holding assets for around seven years rather than the old three-to-five-year rhythm, while a backlog of about 33,000 unsold companies has slowed distributions back to investors. That matters because when investors get less money back, they become more careful about sending fresh money out.

At the same time, capital still moves when the story feels compelling. A recent FT report described a surge of major fundraising activity, much of it pulled towards AI and large technology names, which rather neatly proves the point: money has not lost interest in growth, but it has become far less generous towards muddle.

This is where good businesses often trip. They assume fundraising is a persuasion exercise. It is not. It is a translation exercise. The company must translate operational reality into investor logic. What do you do? Why does it matter? Why will you win? What does the capital change? What can go wrong? Why does the valuation make sense? How does the investor get comfortable?

The first problem is usually positioning. Many companies can describe what they sell, but they cannot explain what they are. They call themselves a platform, a solution, an ecosystem, an enabler, a partner, a category-defining something-or-other. I always get nervous when a business needs eight abstract nouns before breakfast.

Clear positioning does not make the business smaller. It makes it understandable. A company saying, “We transform SME finance through technology” sounds like it escaped from a conference banner. A company saying, “We help small logistics firms access working capital within 48 hours using verified invoice data” gives me something solid. I can see the customer, the pain, the mechanism and the market. That is what investors need. They do not want to admire the fog. They want to see the road.

Then come the numbers, where optimism often puts on a spreadsheet costume. The model looks impressive. It has tabs, it has colours, it has assumptions. It may even have a sensitivity analysis, usually placed somewhere near the back like a polite apology. But the logic often feels weak. Revenue grows because the model says it grows. Margins improve because the chart needed a happier ending. Customer acquisition costs decline just as the company enters a tougher market, which is brave of them.

Investors do not expect forecasts to be perfect. Everyone knows the model will be wrong. The question is whether it is wrong intelligently. What really drives revenue? Which assumptions matter most? What has already been proven? Where does cash get trapped? What happens if hiring takes longer, sales cycles stretch, or customers behave like customers rather than PowerPoint characters?

A strong financial story shows how the business works. A weak one simply shows how big the founder would like it to become. There is a difference, and investors can usually smell it before slide twelve.

Risk creates another little theatre. Businesses often hide risk because they think honesty will frighten investors. This produces the usual bland parade: execution risk, market risk, regulatory risk, competitive risk. Lovely. One might as well write, “Things may happen.”

Good fundraising does the opposite. It names the real risks with calm precision. “Our main risk is onboarding capacity.” “Our biggest uncertainty is enterprise sales cycle length.” “The key regulatory exposure sits in this approval process.” That sounds more credible because it shows the team has met reality and taken notes.

No serious investor believes a company has no risk. They want to know whether management understands the risk better than anyone else. Confidence helps, but only when it has a mitigation plan attached. Otherwise it is just a mood in a blazer.

Valuation brings out even stranger behaviour. Founders want credit for the future. Investors want protection against the future refusing to turn up. Both sides can sound perfectly rational and still annoy each other deeply.

The issue is not always that the valuation is too high. A high valuation can make sense when growth, retention, margins, scarcity or strategic relevance genuinely support it. The issue is an unsupported valuation. “This is what we need to avoid dilution” is not a valuation argument. “Similar companies raised at this level in 2021” is not much better. That was a different climate, with cheaper money, stronger exit assumptions and a collective willingness to believe some very athletic charts.

The FT recently reported comments from Apollo’s Scott Kleinman that parts of private equity became “a little out of whack” during the cheap-debt years from 2017 to 2022, which captures the broader reset rather well. Yesterday’s market mood cannot carry today’s price.

Use of proceeds should be the easiest part of a raise. Oddly, it often becomes the most revealing. Too many companies present the funding need as a shopping list: sales hires, marketing, technology, product development, new markets, operations and that mysterious old friend, strategic flexibility. Strategic flexibility often means, “We would like the money first and the discipline later.”

Capital needs a job. It should move the company from one defined state to another. Founder-led sales to repeatable sales. Regional traction to national distribution. Promising product to regulated launch. Operational bottleneck to scalable delivery. The point is not to fund activity. The point is to unlock value.

That distinction changes the whole conversation. “We need £5 million to grow faster” sounds like appetite. “We need £5 million to remove these three constraints and reach these two milestones within eighteen months” sounds like a plan.

The practical lens is simple. Before trying to raise capital, a leadership team should stop asking, “How do we make this look attractive?” and start asking, “How do we make the investor’s decision easier?”

That means tightening the positioning until a stranger can repeat it correctly. It means rebuilding the financial story around drivers, not wishes. Explaining risk before the investor has to drag it out with pliers. It means anchoring valuation in evidence. Making the use of proceeds feel like a bridge to a stronger business, not a funding round for general corporate enthusiasm.

The irony is that many good businesses do not fail because they lack substance. They fail because the substance arrives badly organised. They bring ambition without sequence, numbers without logic, risks without mitigation, valuation without proof and a capital ask without a clear destination.

Leadership teams should treat investor readiness as strategic work, not deck polishing. The deck matters, but it is not the thing. The model matters, but it is not the thing either. The thing is coherence.

Before approaching investors, I would want the team to answer a few uncomfortable questions. Can we explain the business in one sentence without sounding generic? Do our numbers show how value grows, or only how hope expands? Have we named the real risks? Does our valuation make sense from the investor’s side of the table? Can we show exactly what the capital changes?

A good business becomes fundable when investors can see the opportunity, the logic, the risk and the deal at the same time. Until then, they may admire the company and still say no. Not because they failed to understand the dream, but because the dream did not come with enough instructions.