The result is a group of well-informed people who have been given almost no opportunity to do the thing they are there for.

Information is not the scarce input

The instinctive fix is more disclosure, and boards have received a great deal of it. Packs have grown longer, dashboards more detailed, pre-reads more thorough. This addresses a problem that mostly does not exist. Directors are rarely uninformed about the business. What they lack is the setting in which to apply judgment to it.

Judgment requires the conditions the format most reliably prevents: time, unhurried disagreement, and access to the uncertainty that presentations are constructed to remove. A deck is an argument. It has been reviewed, aligned across the executive team, and stripped of the internal disagreement that would have been the most valuable thing in the room.

The boards that function differently have generally made small structural changes rather than cultural exhortations. Pre-reads distributed far enough in advance to be genuinely read, with a firm rule that material in the pack is not presented aloud. Meetings organized around two or three decisions rather than fourteen updates. Executive sessions without management as a matter of routine rather than as a signal that something is wrong. Direct access to executives below the chief executive, so the board's picture of the company is not entirely intermediated by one person.

Each of these is uncomfortable and none is difficult. They are resisted because the current format serves management's interest in a predictable meeting and the board's interest in a manageable time commitment, and those two interests quietly agree.

The refresh of smaller company boards has been encouraging on exactly this point, largely because newer directors have not yet learned that the format is fixed. The most consequential change reported at those companies is not a different composition but a different agenda, which is available to any board that decides to write one.

The measurement problem compounds it. A board reviewing performance against metrics whose definitions were never settled is reviewing an argument rather than a result, which is the definition problem arriving at the highest level of an organisation and being hardest to detect there.

This is the governance version of a pattern that runs through corporate life, and it is the same failure diagnosed in the meeting economy generally: an event that exists to produce a decision has been optimized instead for the comfortable transmission of information. A board that spends its meeting being briefed has outsourced its judgment to whoever assembled the briefing, which is precisely the arrangement the board exists to prevent.

The standard critique blames culture or tooling. The honest diagnosis is simpler: most recurring meetings are insurance policies written in other people's time. The status meeting insures the manager against surprise. The alignment meeting insures the presenter against later blame. The kickoff insures everyone against the accusation of not having been consulted. Fear, not collaboration, is the booking engine.

This is why calendar-hygiene campaigns fail on schedule. Declaring a no-meeting Wednesday without removing the underlying fear simply compresses the insurance-buying into Thursday. The organizations that have actually cut meeting load did it by changing what is safe: decisions documented in writing, dissent solicited asynchronously, and, critically, leaders who visibly declined to punish the unconsulted decision that turned out fine.

The rebuilt middle-management layer will determine whether this improves, because managers set the local price of candor. A team's meeting calendar is a map of what its people are afraid of. Read yours accordingly, and cancel from the fear down, not the calendar down.

The governance version is the same failure at a higher altitude, where the board meeting has been optimised for the comfortable transmission of information rather than for judgment.

That shift follows earlier coverage of the Case for Hiring Slowly in a Fast Market and Companies Track Time and Waste Attention, Which Is the Only Scarce One.

For a large share of the roles it is applied to, this is a description of a decision employers made and have declined to revisit.

There was a period in which firms hired for aptitude and produced skill themselves. Apprenticeships, rotational programs, formal training with real duration, and the ordinary practice of hiring someone who could not yet do the job and expecting them to learn it. That system was expensive and it worked, and it was dismantled for a defensible reason: a trained employee can leave, and the firm that trained them absorbs a cost their next employer does not.

The rational decision that became a collective failure

Every individual firm was right. If skills can be acquired by hiring rather than by developing, hiring is cheaper and faster and carries no risk of training someone for a competitor. The trouble is that the strategy only works while somebody else is still training, and once enough firms reach the same conclusion the supply they were all drawing on stops being replenished.

The evidence that this is a training problem rather than a scarcity problem is in the job postings themselves. Roles described as entry-level requiring several years of experience. Requirement lists no single candidate plausibly satisfies. Searches that run for months while internal candidates who could do most of the job, and learn the rest in a quarter, are passed over because they do not match on paper.

That last one is the tell, and it connects directly to the internal mobility gap most companies have. An organization that will not consider a partially qualified internal candidate but complains that no qualified external one exists has revealed that the constraint is its own willingness to develop anyone.

The employers moving away from this are, not coincidentally, the ones that had to. Skills-based hiring began as a response to shortages in roles where the credentialed supply simply was not available, and it has held up because assessing what someone can do turns out to predict performance better than what they studied. Once a firm can assess capability directly, developing it internally becomes tractable, because progress can be measured.

Public programs have moved in the same direction, with federal workforce funding restructured around employer partnership rather than standalone training that produced credentials nobody was hiring for. That is an improvement and it does not resolve the underlying free-rider problem, which is that no public program can substitute at scale for firms declining to develop their own workforce.

The aggregate numbers also do not close by training alone. In many regional labor markets the working-age population has grown for one reason only, and no employer development programme substitutes for that arithmetic.

The honest version of the complaint would be: we would like to hire people who are already trained, we are not willing to train them ourselves, and we would prefer someone else pay for it. Stated that way it is still a defensible position. It is simply not a shortage.

An earlier argument in this space, The Case for Hiring Slowly in a Fast Market, made the case from the other direction.

The results are now in, and they are uneven at best.

Talk to the operators of the businesses that have quietly compounded through the last three economic cycles, the regional distributors, the specialty manufacturers, the fifty-person software firms with twenty-year customer relationships, and a pattern emerges. They spend almost nothing on visibility. They spend heavily on the two or three moments a year when a customer genuinely needs them. Their marketing is the absence of unpleasant surprises.

This is not an argument against communication. It is an argument about sequence. The loud company builds an audience and then goes looking for something durable to sell it. The quiet company builds something durable and lets the audience assemble itself, slowly, through referral and repetition. The second path is slower for the first five years and faster for every year after.

There is a measurable version of this. Firms with high organic referral rates carry lower customer acquisition costs, obviously, but they also show meaningfully better retention in downturns, because a customer who arrived through a trusted introduction leaves more reluctantly than one who arrived through an ad. The quiet company's growth is smaller in any given quarter and larger across any given decade.

None of this will trend. That is rather the point.

Cranberry Journal has also reported on the Meeting Is the Message, and the Message Is Usually Fear and the Case for Hiring Slowly in a Fast Market.

Hours are not the scarce input of thinking work. Attention is, and it obeys different physics. It cannot be banked, arrives in limited daily quantity, degrades with each interruption and does not regenerate on command. A knowledge worker's genuine productive capacity is perhaps a few hours of real focus a day, and every workplace system, the chat that pings, the calendar that fragments, the culture that prizes responsiveness, spends that capacity like it was free.

The fix begins with accounting honesty: treat deep attention as a budgeted resource, allocated deliberately, protected institutionally. A few organizations run the experiment, meeting-free mornings, response-time norms measured in hours not minutes, communication defaulting to written and asynchronous, and report the predictable result, which is that output rises when the producing resource stops being strip-mined.

The meeting economy is the largest single raid on the attention budget, but the deeper issue is the ledger itself. Companies get what they measure. Measuring presence bought presence. Measuring responsiveness bought interruptions. Measuring neither, and protecting focus instead, is not a perk. It is the entire production function, finally noticed.

Related reporting has traced Companies Cut Middle Managers. Now They Are Quietly Rebuilding the Layer and the Quiet Company Is Winning, and Nobody Is Writing About It.

It happens again. It happens again because the numbers were never the disagreement.

The dispute in almost every case of this kind is definitional. What counts as an active customer, and after how long does one stop counting. Whether revenue is recognized at contract or at delivery. Whether a churned account that returns is retained or reacquired. These are not data questions. They are decisions about how the business describes itself, and they have consequences for whose numbers look good, which is why they never get made.

Infrastructure as a way of not deciding

Buying a warehouse, a semantic layer or a governance platform is genuinely useful and does nothing about this. A definition layer encodes definitions; it does not produce agreement about what they should be. Organizations that install one without doing the definitional work simply relocate the argument into a configuration file, where it is now also invisible.

The reason the negotiation gets avoided is that it has losers. A definition of qualified lead that survives scrutiny will make a marketing team's performance look different than the definition currently in use. A retention definition that counts accurately will move a number that someone is compensated on. The technical framing is attractive precisely because it lets everyone treat a political problem as an engineering backlog.

This is the same avoidance visible in meetings convened to align on something that a single decision would settle. The activity substitutes for the resolution, and it is more comfortable because it never requires anyone to say that a colleague's number was wrong.

The consequences compound as more gets built on top. Every system consuming a metric inherits its ambiguity, and organizations deploying AI systems on business processes are discovering this acutely, since a model cannot be evaluated against a target nobody has defined. The evaluation gap in enterprise AI is substantially a definition gap wearing newer clothes: you cannot measure whether the system is right without first agreeing what right means, and that agreement was missing long before the model arrived.

The fix is unglamorous and cheap and almost nobody does it. Write down the twenty metrics the company actually runs on. For each, name a single owner with authority to define it, publish the definition in language a new employee could apply, and require that any dashboard using the term use that definition or explicitly declare a variant. This is a week of difficult meetings and it costs nothing.

The same failure explains why so many organisations cannot say whether a programme worked. A mental health benefit evaluated against undefined engagement, or a hiring initiative measured by a quality-of-hire metric nobody wrote down, produces a debate rather than a finding, every time, for the same reason.

It does not get done because it is not a project, it does not have a vendor, and its output is a document rather than a system. Companies are far better at buying tools than at making decisions, and definitional clarity is entirely the second kind of work.

The mechanism is not mysterious. Municipal bond buyers price risk, and a town with no reporter at the council meeting is a town where financial mismanagement surfaces later, larger and more expensively. Researchers have documented the premium for years. What is new is that local officials, lenders and business owners have started to act on it.

The same logic runs through procurement. Public contracts awarded in the dark drift toward the connected rather than the competitive. Every dollar of that drift is paid by the same small businesses that once bought the newspaper's ads. The paper, it turns out, was not a charity case those businesses supported. It was infrastructure they used.

This reframing matters because it changes who should fund the replacement. If local coverage is civic virtue, it depends on philanthropy, which is fickle. If it is economic infrastructure, it can be underwritten the way infrastructure is: by the chambers of commerce, community banks, hospital systems and school districts that capture its value, with editorial independence protected by structure rather than by hope.

A generation of small digital publications is now testing that model in exactly the towns the chains abandoned. Their success or failure will be recorded, fittingly, in the borrowing costs of the places they serve.

That shift follows earlier coverage of the Quiet Company Is Winning, and Nobody Is Writing About It.

All of this treats a means as an end, and it deserves more resistance than it gets.

The case for speed rests on a real observation: good candidates have options, and slow processes lose them. But the conclusion drawn from it, that faster is therefore better, does not follow. A process optimized for speed selects for people who are good at processes. A process built around actual work, real conversations and honest mutual evaluation selects for people who are good at the job. Those populations overlap far less than hiring software vendors would like anyone to believe.

The organizations I find most impressive share a suspicious trait: they are slow to hire and unembarrassed about it. Not bureaucratically slow, deliberately slow. They would rather run short-handed for a quarter than absorb a mistaken hire for two years, because they have done the arithmetic on which one actually costs more.

There is also a signal in patience that recruiting dashboards cannot capture. A company willing to be chosen slowly is telling candidates it expects the relationship to last. In a labor market of two-year tenures, that message is rarer than any signing bonus, and to the people worth hiring, considerably more persuasive.

Fast hiring fills seats. Slow hiring builds institutions. The market rewards the first in the short term and the second in every term after that.

Cranberry Journal has also reported on the Quiet Company Is Winning, and Nobody Is Writing About It, Degrees Optional: Skills-Based Hiring Passes the Durability Test and Companies Cut Middle Managers. Now They Are Quietly Rebuilding the Layer.

This vagueness is a choice, and it is aging badly.

Customers increasingly want to know when they are talking to software. Regulators in several states already require it in narrow contexts. Plaintiffs' lawyers have discovered that undisclosed automation makes an excellent exhibit. The direction of travel is not mysterious, and companies face a familiar decision: define the disclosure norm voluntarily, or have it defined for them, adversarially, one enforcement action at a time.

The model already exists. Companies disclose their auditors, their material risks and their executive pay not because the information flatters them but because standardized disclosure converts a suspicion into a fact. A short, plain statement of where automated systems make or shape decisions affecting customers, in service, in pricing, in claims, in hiring, would cost little and preempt much.

The objection is always competitive sensitivity, and it is mostly theater. Rivals do not learn trade secrets from a sentence saying customer service inquiries are initially handled by an automated system with human escalation. What companies are actually protecting is the ambiguity itself, the freedom to let customers assume more human involvement than exists.

That ambiguity was an asset. It is becoming an exposure. The firms that disclose first will look confident. The firms that disclose under subpoena will look like they had something to hide, because by then, legally speaking, they did.

Earlier Cranberry Journal coverage examined Private Companies Reconsider How They Measure Executive Visibility and Small Models, Big Deployments.