The annual plan nobody connects to Tuesday

A Brazilian technology services company, 450 people (figures in Brazilian reais). In January, two days of offsite planning, six objectives defined, a 38-slide deck sent to everyone. In July, in a hallway conversation, an operations coordinator is asked which objective this week's delivery serves. He doesn't know. Not out of neglect: nobody ever drew that line for him.

The plan exists. The operation exists. What doesn't exist is the path between the two — and it's in that gap that strategy dies, without anyone making a single identifiably wrong decision.

01The idea: execution is discipline, not detail #

Larry Bossidy, former chief executive of AlliedSignal/Honeywell, and Ram Charan published Execution: The Discipline of Getting Things Done in 2002. The central thesis pushes against the corporate habit of treating strategy as noble work and execution as delegable implementation: for the authors, execution is a systematic discipline, part of strategy, and a non-delegable responsibility of leadership.

The book organizes the company around three core processes that must be linked: the people process, the strategy process, and the operations process. People defines who is capable of doing what; strategy defines where the company is heading; operations translates that into goals, resources, and deadlines for the current period.

When the three processes don't talk to each other, the symptom is always the same: ambitious goals with the team you have, a plan that ignores real capacity, and an operating budget built in a different spreadsheet, by a different area, on a different premise. Each piece is defensible on its own; the whole doesn't add up.

02Where the link breaks in a mid-size company #

In a multinational, translating the plan is a PMO's job. In the 450-person company, that translation is informal: it happens in the director's conversations with managers, and stops there. Below that level, what arrives is a sequence of requests with no stated origin.

1. Objective without initiative. The objective exists on the slide and never becomes a named set of work with an owner and a deadline.
2. Initiative without capacity. The work is approved without checking who will do it, and lands on people already stretched across three fronts.
3. Operations on a different clock. The plan is annual; operations run in weekly cycles, and nothing connects one scale to the other.
4. Tracking by narrative. Progress is reported in a monthly presentation, which favors whoever writes well and hides whoever is stuck.
5. Nobody takes anything off the list. New initiatives come in without old ones leaving, and real capacity dilutes until everything moves slowly.

Research by Donald Sull, Rebecca Homkes, and Charles Sull published in Harvard Business Review in 2015 adds an uncomfortable data point to this picture: in a broad sample of managers, the authors found that cross-unit coordination — not the lack of vertical alignment — is execution's most common bottleneck, and that peer-to-peer commitments are far less reliable than managers assume. In other words: a significant part of the gap isn't between boss and team, it's between neighboring areas. That's the coordination cost discussed in the cost of coordinating.

03The cost of the translation that never happens #

Stated assumptions, at the scale of the 450-person company — redo this with your own numbers:

The third line: a survey of active fronts found 23 relevant work streams underway, of which 9 connected to none of the six objectives — leftovers, one-off requests, or projects nobody closed out. Estimating 3 people at half-time per stream, at a loaded R$ 130 per hour, that comes to roughly R$ 1.4 million a year. Not pure waste; some of it is useful work. But it's capacity allocated without a conscious decision.

Want to see how this looks inside a real operation? Explore the platform.

04What to do with the three processes #

What's usable from Bossidy and Charan for a mid-size company isn't the vocabulary, it's the requirement to link things. Three questions force the processes to talk to each other, and can be asked at the next leadership meeting:

• People: for each objective, who is the named person accountable for it, and do they have the time? An objective with a symbolic owner is an objective with no owner.
• Strategy: what concrete initiatives make up the objective, and what comes off the list for them to go on? No entry without an exit.
• Operations: what result expected this quarter shows the initiative is moving? Without that, the first signal arrives in December.

The authors also insist on something less comfortable: robust dialogue. Meetings where no one challenges the premise produce plans everyone approves and no one believes. That depends on an environment where disagreeing doesn't cost much, which is what we discuss in teams that report more errors make fewer of them.

05What management with data answers #

The gap survives because the link between objective, initiative, and task usually exists only in the heads of whoever sat in on the planning. As long as the plan lives in a presentation and the work lives somewhere else, every check-in is an exercise in manual reconstruction — expensive, slow, and biased toward optimism.

When objective, initiative, and task are the same record at different levels, three things change: anyone can trace their own work back to the objective, status becomes a consequence of the work instead of a report, and committed capacity is visible before the next front gets approved. It's the same discipline of measuring in time to still change course from what the balanced scorecard still teaches.

At Relevanti, the projects, tasks, and intelligence modules keep that whole chain in one place — see the platform, the breakdown by area in solutions, or bring your annual plan to a conversation.

Strategy that never reaches Tuesday isn't poorly executed strategy. It's strategy that never left the slide.