Some of the strongest portco CEOs we work with have adopted a rule that can appear surprisingly inflexible when first encountered: meetings do not begin before the afternoon. The morning is reserved for work requiring sustained judgment, whether this means reviewing technical results, preparing an important decision, writing to the organisation or examining a problem that has resisted resolution through ordinary management processes. The precise arrangement varies. For one CEO, no meeting begins before 1 p.m.; for another, two mornings each week remain entirely unavailable; elsewhere, a complete day is protected from recurring meetings. What these practices share is a recognition that the company’s most consequential work cannot reliably be completed in whatever fragments remain after everybody else has made a claim on the calendar.
This is not the usual account of executive productivity, which tends to focus on better prioritisation, delegation, inbox management and the disciplined use of increasingly elaborate task systems. These methods can be useful because leadership produces more obligations than memory can safely contain, but they address the administration of work rather than the temporal conditions under which difficult work becomes possible. A CEO may know precisely what matters, maintain an immaculate list and still reach Friday without having spent two continuous hours on the question most likely to determine the company’s trajectory.
When every meeting makes sense and the week does not
I am sure many of you know this very well. The calendar fills for legitimate reasons. Customers need attention, investors request updates, candidates must be interviewed, senior managers require decisions and problems that cannot be resolved elsewhere travel upwards. In frontier tech companies, these demands are intensified by the interdependence of technical, regulatory, industrial and financial risk. The CEO is often one of the few individuals capable of seeing the complete system, which makes their involvement rational and, beyond a certain point, operationally destructive.
Each meeting can make sense while the week they create does not. The ‘real’, deep work eventually migrates to evenings and weekends, not because these periods possess an inherent intellectual advantage, but because they offer something the formal week no longer provides: continuity.
The data suggests that this experience extends well beyond CEOs. Microsoft’s 2023 Work Trend Index, drawing on a survey of 31,000 people across 31 countries and activity across its productivity tools, found that 68 per cent of respondents lacked sufficient uninterrupted focus during the working day. Employees were spending 57 per cent of their time communicating through meetings, email and chat, compared with 43 per cent creating in documents, spreadsheets and presentations. In Singapore, the imbalance appeared more pronounced, with 82 per cent of employees reporting insufficient uninterrupted focus. Inefficient meetings ranked as the leading disruption to productivity, ahead even of the absolute number of meetings.
The figures describe a general workplace problem, but the cost is not evenly distributed. In frontier tech, the value of uninterrupted time rises with the density of the context required to make a decision. A scientist returning to an experimental question may need to recover the original hypothesis, the limitations of the method and the significance of several previous failures. A technical founder may have to hold architecture, manufacturability, customer requirements and regulatory consequences inside the same act of judgment. A CEO preparing for a financing decision must connect technical milestones, available runway, investor expectations and the operational cost of reaching the next point of proof. These are not collections of independent tasks that can be advanced interchangeably in twenty-minute intervals.
The time required to reconstruct this context is largely absent from conventional measures of productivity. The organisation sees an executive return to a document after a call and assumes that the work has resumed, although the first part of that return may consist entirely of reopening material, recovering assumptions and locating the precise question that the interruption displaced. Physical systems receive more understanding. Laboratory instruments require calibration, production lines have changeover times and cleanrooms impose entry procedures. Nobody interprets these constraints as evidence that the equipment lacks urgency. Cognitive setup costs are less visible and are therefore absorbed privately by the person performing the work.
Research on interrupted work has found that people frequently compensate by working faster, but with higher stress, frustration, effort and perceived time pressure rather than with an improvement in the underlying quality of the working environment. The organisation may therefore preserve output for a period while consuming more of the individual’s cognitive and emotional capacity to produce it. At executive level, this compensation often looks like commitment: documents completed late at night, decisions prepared over the weekend and unusual responsiveness maintained across every channel. The work gets done, allowing the operating architecture that displaced it to remain largely unexamined.
The CEO as the company’s favourite shortcut
No single meeting is responsible for this outcome, which is why it can persist even in well-managed companies. Each interruption is relatively small, each participant has a defensible reason for requesting attention and each discussion can plausibly be connected to an important objective. The cost becomes visible only in aggregate, through slower technical progress, prolonged decisions, incomplete reasoning and a growing dependence on work performed outside the hours the organisation has formally allocated.
The problem is not simply that the CEO has too many meetings. The calendar often reveals a deeper form of organisational dependence. When ownership is unclear, asking the CEO is safer than deciding. When functions struggle to reconcile competing objectives, inviting the CEO is easier than designing the interface between them. When information has not been documented, another meeting becomes the most convenient way to reconstruct it. The chief executive gradually becomes the company’s preferred solution to ambiguity: highly capable, immediately accessible and increasingly responsible for the latency of the entire system.
One of our portcos’ CEO has concentrated most internal reviews into a limited number of afternoon windows, requiring issues raised outside them to satisfy a clear threshold of urgency. Another reserves several mornings for product and technical work, while commercial and investor conversations are grouped later in the day. None has become inaccessible. The design simply distinguishes access from permanent interruptibility and prevents the organisation from using the CEO’s calendar as a substitute for clearer decision architecture.
The stronger versions of this practice extend beyond the chief executive. If only the CEO receives protected time while scientists, engineers and senior operators remain fragmented across the week, the arrangement is a personal privilege rather than an operating principle. The more interesting companies identify which forms of work require continuity and organise time accordingly. Laboratory teams preserve complete experimental sequences, technical leaders hold office hours rather than answering every question as it appears and written material precedes meetings in which several senior people are expected to make a decision.
The small delay introduced by these mechanisms is often productive. A question that must be formulated may answer itself. A problem that can wait for technical office hours may be resolved by the team before the meeting occurs. Several requests may reveal themselves as symptoms of the same weakness in documentation, training or decision authority. Scarce judgment remains available, but the company must use it with greater intention.
This does not require the elimination of meetings or the romantic isolation of technical work from the rest of the organisation. Frontier tech depends on coordination across functions whose evidence, incentives and time horizons differ considerably. The objective is not fewer meetings as an aesthetic preference, but a clearer distinction between communication that advances the work and communication that displaces it. A recurring meeting should make a decision, allocate resources, remove a constraint or review a prior commitment. If its principal function is to reassure participants that everybody remains informed, written communication may provide the information at a lower cost.
A calendar without slack is a hidden weekend plan
The CEOs who manage this well do not simply resolve to become more focused. They turn the preference into a system. Protected periods are visible in the calendar, understood by the organisation and enforced through the tools by which other people request time. Scheduling links do not offer unavailable hours, recurring meetings are concentrated within defined windows and exceptions are sufficiently unusual to remain recognisable as exceptions.
The technical enforcement matters because a boundary that must be defended separately against every reasonable request will eventually disappear. Scheduling software, unlike an accommodating executive, feels no discomfort when declining an appointment. This apparent rigidity tends to produce greater flexibility elsewhere. A CEO whose calendar is filled to capacity has no credible way to absorb the unexpected, even though the unexpected is one of the few predictable features of company building. If every hour has already been allocated, the issue can be managed only by delaying it, displacing existing work or extending the working day.
Protected time therefore serves two purposes. Under ordinary conditions, it provides continuity for work requiring analysis, writing or judgment. Under exceptional conditions, it becomes operating slack that can absorb a genuine emergency without transferring the cost to the evening or weekend.
A calendar without slack is therefore not a fully utilised system. It is a system whose contingency capacity has been quietly outsourced to nights and weekends.
Scarcity also improves the quality of coordination. When the CEO’s availability is treated as abundant, meetings become the default mechanism for transferring context, obtaining reassurance or avoiding local responsibility. When access is constrained, a subject that can wait becomes a message, a problem that belongs to a manager remains with the manager and a meeting without a clear object becomes more difficult to justify. The conversations that survive are more likely to involve decisions for which synchronous attention is genuinely useful.
Read the calendar before the strategy deck
Therefore, I would argue that the calendar is more than a personal productivity tool. It is an informal map of organisational dependency. It shows which decisions cannot travel without the CEO, which functions remain unable to integrate their work without escalation and which forms of progress the company is prepared to interrupt in order to maintain the appearance of coordination.
This becomes increasingly important as the organisation scales. In the early years, constant interaction can be efficient because context is shared, roles are fluid and the distance between a discussion and an action is small. As the company grows, the same habits become expensive. More people join each meeting, information must be reconstructed for participants who were not present earlier and senior leaders spend increasing amounts of time coordinating work they have decreasing amounts of time to examine.
For a board, the CEO’s calendar is therefore an operating document. It can reveal whether the organisation has distinguished urgency from importance, whether authority has genuinely been delegated and whether the company is preserving the cognitive capacity required for its hardest decisions. A chief executive who participates in every consequential conversation may appear deeply engaged, but engagement and leverage are not identical. The more mature operating model allows the CEO to remain available for the questions that require their judgment without becoming the surface on which every unresolved dependency is scheduled.
The best CEOs we encounter do not protect their mornings because they have discovered a superior productivity ritual. They do so because they understand that attention is an allocative decision. Every hour assigned to coordination is an hour unavailable for analysis, writing, product judgment or the integration of information that has not yet become a decision. The trade-off exists whether or not the organisation chooses to make it explicit.
A calendar cannot determine what a leader should think, but it determines whether they are likely to think about it for long enough. In companies attempting to turn uncertain science into reliable technology and reliable technology into an institution, that is not a question of personal efficiency.
It is part of the operating system.
This also raises an interesting board question. We spend enormous amounts of time reviewing strategy decks, KPIs and financial reporting, but almost none looking at how the CEO actually allocates attention. Yet the calendar may tell you more about the operating model than many formal reports do.
I’d extend this beyond CEOs. If the company protects the founder’s thinking time while engineers, scientists and product leaders spend their days jumping between calls, the underlying problem has not really been solved. Deep work probably needs to become an organisational design principle rather than an executive perk.