Writing

Organizations frequently equate shorter, more structured meetings with better governance. This assumption deserves scrutiny. While procedural efficiency has value, the relationship between meeting duration and decision quality is more complex than conventional management advice suggests.

In our work with executive teams across the DACH region, we keep seeing the same thing: meetings that look efficient on paper often produce decisions that fall apart once implementation starts. The visible part of governance has been tuned for speed while the harder work of building real commitment has been squeezed out.

This phenomenon manifests in predictable ways. Agenda items are formally resolved before the executives responsible for implementation have internalized the trade-offs involved. Documentation captures the decision but not the reasoning that would allow consistent interpretation during execution. Dissent is managed out of the meeting rather than worked through within it.

The result is false closure: a decision that looks complete in meeting minutes but lacks the organizational commitment required to survive contact with operational reality. When pressure arrives, as it always does, poorly anchored decisions are relitigated, reinterpreted, or quietly abandoned.

Consider a common scenario. An executive committee meets to decide on a reorganization affecting three business units. The meeting runs forty-five minutes. The CEO presents the rationale, the CFO confirms the financial case, and the three affected business unit heads are asked if they have concerns. Each provides brief comments, none of which substantively challenge the proposal. The decision is recorded as unanimous.

Within six weeks, two of the three business unit heads have raised objections through back channels. They cite operational complications that were not discussed, stakeholder concerns that were not surfaced, and resource implications that were not quantified. The reorganization proceeds but with modifications that substantially alter its logic. A year later, the structure is revised again.

What went wrong? The meeting was not too short to make a decision. It was too short to build the understanding and commitment that the decision required. The business unit heads did not raise concerns in the meeting for reasons that efficient meeting design cannot address: the political risk of challenging the CEO in a group setting, uncertainty about whether dissent was genuinely welcome, and insufficient time to have formulated concerns clearly enough to articulate them.

The alternative is not inefficiency for its own sake. It is deliberate investment in the conversations that actually determine whether organizational commitment will form. For consequential decisions, this typically requires explicit acknowledgment of trade-offs, genuine engagement with objections, and sufficient time for the people who must execute to develop ownership of the outcome.

Practical approaches vary. Some organizations separate discussion meetings from decision meetings, ensuring that executives have time to process implications before being asked to commit. Others require written pre-reads that surface the key tensions in advance, allowing meeting time to focus on resolution rather than comprehension. Still others convene smaller pre-meetings with the executives most affected, building alignment before the formal governance moment.

The diagnostic question is not whether meetings end on time. It is whether decisions made in those meetings consistently survive the first six months of implementation without substantial revision. Where they do not, meeting efficiency may be part of the problem rather than a sign that governance is working well.

Post-merger integration is conventionally framed as a challenge of systems harmonization, operating model design, and cultural alignment. These are real issues, but they rarely explain why integrations fail. In our experience advising on integration planning and execution, the failure pattern typically begins much earlier, in the first weeks and months when the nature of the combination is being established through accumulated signals rather than formal programs.

These signals include: the branding of internal communications and combined-entity materials; the sequencing and geography of leadership appointments; the language used to describe the transaction in employee town halls; the location and format of initial working sessions between the combining organizations; and the treatment of pre-existing initiatives, relationships, and commitments from the acquired entity.

Each of these elements communicates something about power, respect, and the actual terms of the combination, regardless of what the deal announcement stated. Employees in the acquired organization read these signals quickly and accurately. Once the informal conclusion forms that the integration is actually an absorption, the official partnership narrative loses credibility and subsequent culture work operates at a disadvantage.

We observed this dynamic in a combination between two professional services firms of roughly similar size. The transaction was positioned as a merger of equals. Leadership appointments were carefully balanced between the two legacy organizations. The stated integration philosophy emphasized preserving the best of both cultures.

However, the first combined leadership meeting was held at the headquarters of one firm. The meeting agenda was set by that firm's chief operating officer. The presentation templates used that firm's visual identity. The integration project management office was staffed predominantly by that firm's personnel. The cultural assessment surveys used that firm's pre-existing framework.

None of these individual decisions was significant enough to merit escalation or revision. Collectively, they established a pattern that employees in the other firm interpreted correctly: this was not a merger of equals in any practical sense. By the time formal culture integration work began months later, the working assumption throughout the organization was already set. The partnership narrative was simply not believed.

The practical implication is that integration success depends substantially on the intentionality with which early signals are managed. This is not soft work. It is one of the earliest operating facts of the combined organization, and it shapes the context in which all subsequent integration activity occurs.

Specific indicators that merit attention in early integration phases include: which organization's processes become the default when no explicit choice is made; whose calendar and scheduling preferences take precedence for joint meetings; which firm's vendors and service providers are retained for combined operations; how intellectual property, methodologies, and proprietary approaches from each firm are characterized; and whether communication flows primarily from one organization to the other or genuinely bidirectionally.

Organizations that treat symbolism as a communication exercise rather than an operating discipline frequently discover that their carefully designed integration programs encounter resistance that appears irrational but is actually a response to earlier, unmanaged signals. The foundation was set before the formal program began.

A common assumption in organizations is that accountability is clear when people broadly understand who leads a particular topic. This conflates two different things: general awareness of responsibility and the specific assignment of decision authority, execution accountability, and outcome ownership that allows organizations to function under pressure.

Implied ownership works tolerably well when conditions are stable and decisions are uncontested. It breaks down systematically when circumstances become difficult: when a decision is urgent, when it affects multiple functions, when it requires trade-offs that disadvantage some stakeholders, or when it carries career risk for whoever takes responsibility.

In these situations, implied ownership typically dissolves. Multiple executives believe the decision belongs to someone else. Escalation paths become unclear. The decision either stalls or gets made by whoever is most willing to act, regardless of whether they have the authority, information, or organizational position to decide well.

We encountered a clear example of this pattern at a manufacturing company facing a quality issue affecting a major customer. The problem sat at the intersection of operations, quality assurance, and commercial relationships. Each function head understood the issue but believed primary ownership resided elsewhere. Operations viewed it as a quality matter. Quality assurance viewed it as an operations execution failure. Commercial believed both should resolve the technical issues before customer communication.

The customer escalated twice before the CEO intervened to assign explicit ownership and convene a resolution team. The delay damaged the relationship and required substantial commercial concessions to repair. In the post-mortem, each function head could credibly argue they had acted reasonably given their understanding of responsibilities. The system failed, not the individuals.

Many leadership teams interpret this pattern as an execution problem: the strategy was clear but implementation faltered. The deeper issue is usually assignment. The fundamental questions, who owns this decision, who has input rights, who can block, who escalates unresolved issues, and who is accountable for outcomes, were never answered precisely enough to guide behavior under pressure.

Effective accountability design is explicit, documented, and maintained over time. It specifies not just who is responsible but what that responsibility includes and excludes, what decision rights it carries, and how conflicts with adjacent responsibilities are resolved. This work is administrative and often tedious. It is also the infrastructure on which organizational execution depends.

The standard tool for this work is some form of responsibility matrix, often called a RACI or similar framework. These tools are frequently implemented poorly, treated as documentation exercises that produce artifacts no one consults. Done well, however, they force the difficult conversations that implicit accountability avoids: what exactly does it mean to be responsible for this process, and what happens when reasonable people disagree about scope or approach?

The test of adequate accountability design is not whether a chart exists but whether people actually know what to do when difficult situations arise. If they consult the framework and find clear guidance, the work was worthwhile. If they bypass the framework because it does not address the real questions, the accountability design has failed regardless of how complete the documentation appears.

Rapid growth creates a characteristic pattern of organizational stress. The structures, processes, and management practices that served the organization at one scale become insufficient at the next, but the insufficiency is often masked by the momentum that growth provides. Revenue increases, market position strengthens, and the organization appears to be performing well despite accumulating structural debt.

During this phase, much of the organizational load is carried informally by a small group of experienced people who compensate for weak design through personal intervention. They resolve conflicts that the structure does not, make decisions that formal governance does not reach, and maintain coordination that processes do not support. This works until it does not.

The transition point typically arrives when the organization becomes too large for workaround management. Decision-making slows because escalation paths are overloaded. Middle management becomes uncertain because their authority was never properly defined. Priorities fragment because the informal prioritization mechanisms that worked at smaller scale no longer function. Accountability becomes diffuse because roles were never redesigned to match the organization's increased complexity.

A technology company we worked with illustrated this pattern clearly. They had grown from thirty people to nearly two hundred over four years. The founders remained closely involved in operations, which they saw as a strength. Their judgment was good, and employees trusted them to resolve disputes and set direction.

What the founders did not initially see was that their involvement had become the primary coordinating mechanism for an organization that should have developed other means of coordination. Managers had learned that the fastest path to resolution was founder escalation rather than peer negotiation. Process development had stalled because the founders could be relied upon to handle exceptions. Middle managers had not developed the decision-making capabilities they would need at the next scale because they had never been required to exercise them.

At this point, the organization has not necessarily failed at strategy or execution in any conventional sense. It has simply outgrown the structural infrastructure that was adequate for its earlier state. The management model that felt sufficient at one scale has become a constraint at the next.

The diagnostic indicators for this condition are usually visible before crisis arrives: repeated friction in the same organizational interfaces, chronic escalation to senior leadership for decisions that should not require their involvement, persistent misalignment between strategy as stated and priorities as resourced, and key people who are simultaneously overloaded and uncertain about their authority.

Additional warning signs include: increasing time required to onboard new employees because documentation and process clarity have not kept pace with growth; rising frustration among middle managers about their inability to get things done; customer-facing issues that trace to internal coordination failures; and a sense among long-tenured employees that the culture has changed in ways they struggle to articulate.

These signals warrant attention before they become acute. Structural adaptation is substantially easier when undertaken proactively rather than in response to visible breakdown. The question is not whether organizational design will need to evolve as the company grows. It is whether that evolution will be managed deliberately or forced by operational dysfunction.

Management advisory work often emphasizes presentation impact: the ability to communicate compellingly in high-stakes meetings with senior executives. This emphasis reflects real requirements. Advisory recommendations must survive scrutiny from experienced, skeptical audiences with limited time and substantial judgment.

However, the emphasis on presentation skill can obscure a more fundamental requirement: the recommendation must hold its shape after the meeting ends. Senior leaders need material they can return to when testing recommendations against new information, when aligning stakeholders who were not present for the original discussion, and when implementation encounters obstacles that require revisiting original assumptions.

This is why written clarity matters. Writing disciplines thought in ways that verbal communication does not. It forces logic to be explicit, assumptions to be stated, sequencing to be justified, and language to be precise. A polished presentation can carry ambiguity and weak reasoning further than they deserve to travel; a written document usually cannot sustain the same opacity.

The distinction becomes concrete when examining how advisory work products are actually used. In the weeks following a major recommendation, executives typically need to: explain the rationale to colleagues who were not in the meeting, answer questions about implications that were not explicitly addressed, defend the recommendation against alternative proposals that emerge later, and adapt the approach when implementation reveals assumptions that were incomplete.

Each of these activities requires reference material that can stand alone. If the written work product summarizes conclusions without explaining reasoning, references analysis without providing it, or uses imprecise language that admits multiple interpretations, the executive is forced to reconstruct or improvise. This undermines confidence and slows implementation.

In practice, this means that advisory work product should be designed for use after delivery, not merely for impact during delivery. The test of quality is whether the material remains useful when the consultant is no longer in the room to explain, contextualize, or defend it.

Specific characteristics of durable written work include: findings that are stated precisely enough to be tested against new evidence; recommendations that specify not just what to do but why, and what assumptions would need to change to alter the recommendation; documentation of alternatives considered and reasons for their rejection; and implementation considerations that anticipate the practical challenges execution will encounter.

Organizations evaluating advisory support should ask whether the proposed deliverables are built for this kind of durability, or whether they are mainly built to impress in the room. The difference matters. Recommendations that look good in the meeting but provide thin guidance for execution often cause more problems than they solve.