The Discipline of Waiting One More Meeting

The Meeting That Decides Everything

The pattern is quiet, and almost always the same. A board meets on a Tuesday morning. A vendor has presented in the preceding week, and the demonstration was unusually accomplished. A competitor has announced something the trade press describes as significant. An analyst has published a note. A member of the executive team has forwarded, with the briefest of covering messages, a paragraph from an interview given by a chief executive whose name everyone in the room recognises. By the time coffee is served, no one has quite proposed a decision, and yet the shape of one is already forming in the room. Within a fortnight, a commitment will have been made that binds the organisation for the better part of a decade.

This essay is the third in a short sequence. The first argued that the most consequential question at the beginning of a serious technology decision is whose judgement the organisation has chosen to trust. The second argued that judgement, however well sourced, requires an institution capable of receiving it, remembering it and acting on it over time. This essay is concerned with the moment at which judgement, once formed, is asked to become a decision. It is a moment that receives less careful attention than either of the two that precede it, and it is the moment at which most of the damage is actually done.

The Mood in the Room

The argument is not that decisions should be slow, nor that caution is a virtue in its own right. Organisations that treat every decision as consequential develop a familiar pathology of their own, in which nothing is ever settled and small matters consume the attention that ought to have been reserved for large ones. The argument is narrower. The ability to tell the difference between the decisions that must be taken quickly and the decisions that would be improved by one further conversation is one of the quieter markers of organisational maturity, and a great many executive teams do not possess it in the form they believe they do.

It is worth pausing on the psychology of what happens in the room described above. The vendor demonstration was accomplished, but no vendor demonstration has ever been unaccomplished at this level of the market. The competitor announcement was real, but competitor announcements at this scale are frequently the visible edge of a decision that will, over the following two years, quietly disappoint the people who made it. The analyst note was intelligent, but analyst notes exist in an economy whose incentives were the subject of an earlier essay. The forwarded paragraph was interesting, but the chief executive quoted in it is unlikely to have been describing the decision the same way in private that they were describing it in the interview. None of these inputs is illegitimate. Each has a place. What is worth noticing is that none of them, taken singly or in combination, actually contains the information a serious decision requires. What they contain is a mood.

The mood in the room is the phenomenon most worth understanding. It is not the same thing as evidence, and it is not the same thing as judgement, but it can be mistaken for both, and in tired rooms at the end of long weeks it almost always is. The mood carries with it a sense that a moment has arrived, that the organisation is being tested, that hesitation would be costly, that the executives present are being asked to demonstrate the very quality for which they were promoted. Under those conditions, the harder discipline is not to act. The harder discipline is to notice that the pressure in the room is originating from the conversation itself, and to ask whether it has any correspondence to the pressure in the world outside.

This distinction matters because organisations, and the people who lead them, have a strong preference for movement. Movement resembles competence. Committees that decide are perceived to be functioning. Executives who commit are perceived to be leading. The alternative, which is to declare that a further conversation is required before the decision is made, has none of these visible virtues. It looks, from the outside, like the absence of a decision. It is often mistaken for one. That misreading is the reason the discipline discussed here is difficult to hold, particularly for executives who have arrived at their positions in part by cultivating a reputation for decisiveness.

What This Discipline Is Not

It is important to distinguish this discipline from three things it is not. It is not delay, which is the postponement of a decision without any particular expectation that the delay will improve the decision. It is not hesitation, which is the private inability to commit, dressed up in whatever public language is convenient. It is not procrastination, which is the substitution of any other activity for the one that ought to be done. It is a specific and deliberate act, whose purpose is to convert a decision that would have been made under the pressure of a single meeting into a decision made across at least one further cycle of thinking. The additional cycle is not intended to produce more information. Information is almost never the constraint at this stage. The additional cycle is intended to produce better questions.

The device implied by the title of this essay is worth taking at face value. One more meeting. Not a committee. Not a governance process. Not a stage gate. Not a new working group with terms of reference and a monthly cadence. One additional cycle in which the same people who were in the first conversation return to it, having had time to think, having had time to speak to colleagues whose view was not present the first time, having had time to write down what they actually believe about the decision rather than what they were prepared to say about it in front of others. In the space between the two conversations, three things tend to happen that do not happen inside the first meeting itself.

What the Interval Produces

The first is that assumptions become visible. The decisions that ruin organisations are almost never the ones that were argued incorrectly. They are the ones that rested on an assumption no one thought to state. The vendor was assumed to be the market leader in five years' time because they are the market leader today. The internal team was assumed to have the capacity to absorb the programme because no one had asked them. The board was assumed to want the outcome the executive team was proposing because a member of the board had, in an unrelated conversation, said something adjacent to it. A second cycle of thinking, honestly conducted, tends to bring these assumptions into the room, at which point their fragility is usually evident to everyone.

The second is that enthusiasm separates from evidence. In the first conversation, the two are almost always fused. The demonstration was compelling and therefore the platform is the right one. The paper was well written and therefore its recommendation should be followed. The competitor moved and therefore the direction of the industry is settled. A short interval, of a week or two, is usually long enough for the enthusiasm to subside far enough that the underlying evidence can be examined on its own terms. What remains, once the atmosphere of the first meeting has dissipated, is sometimes strong enough to justify the decision. Often it is not. The value of the interval lies in the possibility of finding out.

The third is that dissenting voices, of which there are almost always more than a first meeting reveals, have time to organise themselves into arguments. Senior people who are unpersuaded of a proposal seldom say so clearly in the meeting in which it is first floated, particularly when the momentum in the room is against them. They will say so, quietly and in some detail, in the corridor conversations of the following week, if the space for such conversations is preserved. The purpose of the second meeting is to give those arguments a place to be heard on the record, before rather than after the decision is taken. Organisations that skip this step frequently discover, six months into a programme, that half of the executive team had reservations from the beginning and that none of them felt able to state those reservations at the moment when doing so would have counted.

Situations That Recur

It may help to describe a few situations of a kind that recur across industries. None of these is a single real organisation. All of them are recognisable.

A board is presented with a proposal to replace the group's commerce platform, following an unusually accomplished demonstration by a well established vendor. The presentation has answered every question that was asked. The chief executive is enthusiastic. The chief financial officer is neutral, which in the culture of this particular board is read as tacit support. A decision is taken within three weeks. Eighteen months later, the programme is delivering, at considerable expense, a version of what the organisation already had. The vendor was not the problem. The demonstration was not the problem. The problem was that no one, in the interval between the presentation and the decision, had asked the question of what the organisation was actually trying to achieve that its existing platform did not already permit. That question had an answer, and the answer would have changed the shape of the programme. It was never asked because there was no meeting in which to ask it.

An executive committee decides, over the course of a single quarter, to introduce a generative artificial intelligence capability across the front office. The trigger is a competitor announcement and a piece in the financial press. The programme is stood up quickly, with an ambitious scope, and with a governance structure assembled at the same speed. Within a year, the committee is quietly reconsidering. The technology has done broadly what was expected of it. The organisation has not. A period of reflection, taken before the initial commitment, would have revealed that the front office was not, at that point, the part of the business best positioned to absorb the capability, and that a smaller and less visible starting point would have produced better outcomes with less political cost. That period of reflection was not taken because the announcement had created the impression that it could not be afforded.

An enterprise resource planning replacement is approved on the basis of a business case whose objectives are stated in general terms. During the mobilisation phase, the scope quietly expands, as scopes tend to. Modules that were not in the original conversation are added because the vendor supports them and because it seems inefficient not to. The programme takes on a life of its own before its purpose has been agreed with sufficient precision to constrain it. The right moment to have settled that question was the meeting that never took place between the approval of the programme in principle and the signing of the master agreement. Once the agreement is signed, the question of scope becomes a matter of negotiation rather than of judgement.

An acquisition proceeds on a timetable set by the vendor of a technology platform that both parties happen to use. The commercial logic of the transaction is sound. The technological optimism of the acquiring team, however, has outpaced the diligence that would have revealed the state of the target's underlying systems. The deal closes. The integration turns out to be materially more expensive and materially slower than the plan assumed. A single further meeting, held before the deal committee's final approval, in which the head of technology of the acquiring firm was invited to speak candidly about what he had actually seen during diligence, would have produced a different outcome. That meeting was not held because the timetable did not permit it, and the timetable did not permit it because no one had thought to ask whether it should.

A customer relationship management transformation is initiated on the basis of a capability comparison in which the winning platform scores highest on the largest number of criteria. The programme proceeds. Two years later, adoption is disappointing. The platform is capable of everything that was promised. The organisation is not yet organised in a way that permits those capabilities to be used. The question of organisational readiness was, in principle, on the agenda of the original decision. It was not, in practice, the subject of a dedicated conversation. It became one only after the platform had been chosen and the contract signed, at which point it was too late for the answer to influence the choice.

The Category of the Irreversible

In each of these situations, the decisive mistake was not made during implementation. Implementation teams, given a coherent decision, are generally capable of executing it. The decisive mistake was made in the room in which the decision was first taken, and it consisted of taking the decision at the end of that room rather than at the beginning of the next one. The cost of the additional meeting would have been small. The cost of its absence was measured in years.

It is worth being clear about what mature organisations do differently. They do not slow every decision, and they do not treat every meeting as though it might contain a foundational choice. Most of what an executive team decides is properly decided quickly. The purchasing of ordinary services, the approval of ordinary budgets, the resolution of ordinary personnel questions, the acceptance of ordinary proposals from operating divisions, all of these belong to a category in which speed has real value and the cost of a second cycle would not be repaid. The mature organisation is not the one that moves slowly. It is the one that identifies, with unusual precision, the small number of decisions that fall outside the fast category.

What identifies those decisions is not their financial size, although the size often correlates. What identifies them is their irreversibility. A decision that can be undone within a quarter, at modest cost and without political damage, does not benefit greatly from a second cycle of thinking. A decision whose consequences will still be visible five years later, whose reversal would require the concession of a strategic error, whose fabric will over time become entangled with hiring, organisation design, capital allocation and public commitment, is a decision of a different order. It deserves a different rhythm. Organisations that treat the two categories the same way are, in effect, choosing to make their irreversible decisions at the pace of their reversible ones. Over time, the accumulated consequences of that choice are considerable.

The Economics of Speed

There is an economics to this, and it is worth stating in a form that executive teams sometimes find useful. Every organisation is aware of the cost of moving too slowly. It is discussed at every board meeting, in every strategy document, in every quarterly review. Far fewer organisations account for the cost of moving too quickly, because that cost is diffuse, delayed and easily attributed to other causes. Vendor lock in is a form of this cost. So is the fatigue of an organisation that has been asked to absorb too many changes in too little time. So is the loss of optionality that follows any large commitment. So is the political investment that senior executives make in decisions they have publicly championed, which makes those decisions difficult to reverse long after the underlying evidence has changed. So is the well documented tendency of committed organisations to escalate their commitment in the face of disconfirming information. Taken together, these costs frequently exceed the visible cost of the additional meeting whose absence produced them. They are, however, less visible on any single quarter's numbers, and so they are less discussed.

Judgement, Memory and Time

It is worth returning, at this point, to the two essays that preceded this one. The three arguments are related in a way that becomes clearer once the third is in place. Independent judgement, of the kind considered in the first essay, matters because it is the only form of counsel able to produce the questions that a room under pressure will not otherwise generate. Institutional knowledge, of the kind considered in the second essay, matters because it is the substrate on which those questions can be answered with reference to what the organisation has actually learned, rather than with reference to what the current conversation happens to contain. The discipline of the second meeting, considered here, matters because it is the mechanism through which those two capabilities are brought to bear on the decision itself. Without independence, the questions do not appear. Without institutional knowledge, the answers cannot be trusted. Without the discipline of the second meeting, neither of the first two has the time to do its work.

The three essays therefore describe a single practice rather than three separate ideas. The practice consists of assembling, in advance of the consequential decisions, the counsel whose value does not depend on the decision going a particular way, of investing patiently over years in the institutional memory that makes such counsel actionable, and of preserving, at the moment of decision, the interval in which counsel and memory are able to shape the outcome. None of these three activities has much value in isolation. Independent counsel that is not heard is a curiosity. Institutional memory that is not consulted is an archive. A second meeting held without the benefit of either is a longer version of the first. The three together constitute what a serious executive practice looks like. Any one of the three, in the absence of the others, does not.

It is tempting to end an essay of this kind with a set of prescriptions. The temptation is worth resisting, for reasons similar to those given at the end of the previous essay. What has been described here is not a methodology. It is a disposition, the willingness on the part of an executive team to hold open the space in which a further conversation might still take place, even at the cost of appearing, for a week or two, less decisive than the tempo of the moment would prefer. That willingness cannot be produced by a framework. It is produced by the accumulated experience of having, at least once, taken a consequential decision at the end of the first meeting and lived with the results, and of having, at least once, taken a similar decision at the beginning of the second and understood the difference.

In the end, the mature organisation is not the one that has learned to move quickly. Speed is available to any organisation prepared to pay for it. Maturity lies in knowing when speed is worth its cost and when it is not, and in having cultivated, inside the senior team, the small number of people willing to say so out loud when the room is inclined to hurry. Such people are not always the most celebrated members of the executive team at the time. Over the course of a decade, they tend to be the ones whose judgement is remembered.

History does not remember the meeting in which an organisation decided to wait a further week before signing a contract. It has no reason to. What it remembers, and what appears in the accounts of the years that follow, is the consequence of the decision that was taken a week too early. That is the discipline this essay has attempted to describe. It is a discipline whose value is visible chiefly by the absence of the failures it prevents, which is one of the reasons it is so difficult to hold, and one of the reasons it is worth writing about.