Why Your Scaling Up Priorities Keep Missing the Real Issues

TL;DR

Scaling Up is one of the most sophisticated growth frameworks available to founder-led companies. Its rhythm tools, priority-setting process, and cash acceleration disciplines have helped thousands of companies scale with more intentionality than they would have managed on their own. But every Scaling Up engagement shares a structural limitation that rarely gets named: the priorities your leadership team sets reflect what your leadership team can see. They do not reflect what the rest of your organization experiences. That gap between leadership perception and organizational reality is where the real issues live. And no planning framework, however well-designed, can surface what it was not built to find. Scaling Up's priority-setting process is only as good as the intelligence feeding it. If the intelligence is filtered, the priorities will be too. The critical number your leadership team agrees on may be solving a symptom of a deeper organizational issue that never made it into the planning conversation. The companies that get the most from Scaling Up are the ones who verify what is actually happening in their organization before they build the plan.

There is a moment that happens in a lot of Scaling Up engagements.

The leadership team has done the work. They have been through the One-Page Strategic Plan. They have set their priorities for the quarter. They have agreed on the critical number. They leave the offsite feeling clear and aligned, which is genuinely a good feeling and genuinely valuable.

Then the quarter plays out. Some priorities get completed. Some do not. And one or two of the same underlying problems seem to find their way back into the next planning conversation, wearing slightly different clothes.

If you have been through this cycle more than once, you have probably wondered whether the problem is the framework, the team, the execution, or something else.

It is usually something else. And it is worth naming directly.

What Scaling Up Was Built to Do

Verne Harnish built Gazelles, now known as Scaling Up, around a core insight that most founder-led companies scale without ever developing the habits of great companies. They grow through momentum and founder energy, not through disciplined systems. At some point, momentum runs out of road and the absence of those habits becomes the constraint.

Scaling Up installs the habits. The meeting rhythm creates communication structure across the organization. The one-page strategic plan forces leadership to make explicit choices about where the company is going and why. The cash flow tools discipline companies to understand their financial velocity, not just their revenue. The emphasis on finding and keeping the right people reflects a genuine understanding that execution depends on humans, not slides.

For companies that have been operating on instinct, the Scaling Up framework is genuinely clarifying. It introduces rigor where there was art. It creates shared language for decisions that were previously made informally. It gives the leadership team a process for staying aligned as the company grows more complex.

None of that is small. Frameworks that create alignment in leadership teams are valuable precisely because leadership misalignment is so expensive and so common.

But here is the question that Scaling Up, like every leadership-driven framework, cannot answer on its own: how do you know that the priorities your leadership team agreed on are the right priorities?

Where Scaling Up Priorities Come From

Walk through the priority-setting process for a moment.

Your leadership team assembles. You review the previous quarter. You assess your annual priorities and where you stand. You identify your key themes and constraints for the next quarter. You debate, align, and commit.

The inputs to that process are your team's collective knowledge, experience, and perception of the company. That knowledge is real. It is informed by years of running the business. It is not nothing.

But it is also filtered.

Every piece of information that reaches your leadership team has traveled through the organization's communication channels to get there. It has passed through managers who made decisions about what to escalate and what to handle themselves. It has been shaped by the organization's informal norms about what kinds of problems get raised and which ones get absorbed. It has been influenced by the interpersonal dynamics of your leadership team and who on that team has the credibility to surface which kinds of concerns.

By the time information reaches your planning session, it reflects a curated version of what is happening in your company. Not a dishonest version. Not a deliberately distorted one. Just an incomplete one, shaped by the natural filters that exist in every organization above a certain size.

In Privagent's work, we call this Strategic Opacity. It is not a failure of your leaders or your managers. It is what happens when organizations grow past the point where a founder can have direct, unfiltered contact with every part of the business. The very communication pathways you rely on for information have been co-opted by the organization's social dynamics. Bad news softens in transit. Recurring problems stop getting reported when previous reports went unresolved. Workarounds develop for broken processes and become invisible precisely because they work well enough that no one escalates them.

The result is that your leadership team makes decisions from a partial picture. And your Scaling Up priorities, however carefully set, reflect that partial picture.

A planning input flow diagram showing the path information takes before reaching a Scaling Up offsite. At the bottom: 40

The Critical Number Problem

One of Scaling Up's most useful tools is the concept of the critical number: the single metric that, if improved, would have the greatest impact on your business this quarter. Finding the right critical number requires genuine strategic thinking and forces useful prioritization conversations.

But the critical number is only as good as your diagnosis of what is actually driving your business outcomes. And that diagnosis depends entirely on the information available to the leadership team setting it.

Here is where it gets interesting.

In engagement after engagement, Privagent surfaces organizational issues that are directly driving the business outcomes leadership is trying to improve, but that leadership has no visibility into. The throughput problem that leadership is trying to solve by adding headcount is actually being caused by a communication breakdown between two departments that has been managed informally for eighteen months. The customer retention issue that looks like a product problem from the top is being driven by a service delivery gap that frontline employees have been working around rather than reporting.

The critical number your leadership team sets for the quarter may be pointing at the right outcome. But if the underlying causes are invisible at the leadership level, the interventions you design will be incomplete. You may move the number. But the root cause stays in place, and it will find another symptom to express itself through next quarter.

This is not a planning problem. It is an intelligence problem.

The Meeting Rhythm Is Running. The Signal Is Still Missing.

One of the things founders genuinely appreciate about Scaling Up is the meeting rhythm. Daily huddles, weekly meetings, monthly reviews, quarterly offsites. The rhythm creates communication structure and ensures that issues surface and get addressed rather than accumulating.

And it does work. Communication improves. Accountability increases. Problems that used to simmer for months get raised in weeks.

But the meeting rhythm has the same structural limitation as the priority-setting process. It is a system for how your leadership and management layers communicate. It is not a system for how the rest of your organization communicates upward.

Your daily huddle captures what your managers know and choose to share. Your weekly meeting surfaces what your leadership team observes and decides to raise. Your quarterly offsite works from the picture these conversations have built over time.

The people doing the actual work of your company, building the product, serving the customers, running the operations, they are not in those meetings. Their experience does not have a direct channel into your Scaling Up rhythm. It arrives filtered, if it arrives at all.

This is not an argument against the meeting rhythm. It is an argument for adding something underneath it. A channel that does not rely on the organization's social dynamics to carry information upward. A channel where employees can tell the truth about what is actually happening without calculating the social cost of saying it.

What Happens When You Add Organizational Intelligence to Scaling Up

The most effective Scaling Up implementations we have seen share a common characteristic. Before the quarterly or annual planning session, the leadership team has a verified picture of what the organization is actually experiencing.

Not impressions. Not manager reports. A confidential, systematically gathered picture of what employees at every level are experiencing, what is creating friction, what is being worked around, what has stopped being reported because the organization learned that reporting it does not help.

When that picture is present in the planning room, the quality of the conversation changes.

The critical number gets set against reality rather than against perception. The priorities reflect the actual constraints on the business rather than the constraints visible from the top. The people decisions are grounded in data rather than in accumulated impressions filtered through management layers.

One founding team we worked with had been through four consecutive quarterly Scaling Up planning sessions where a particular execution problem kept appearing on their priority list. They had addressed it four times in four different ways. After an organizational discovery engagement, they found out that the actual source of the problem was a workflow breakdown in a department whose manager had been absorbing the symptoms rather than escalating the cause. It had never made it into a huddle. It had never been raised in a weekly. The leadership team had been treating symptoms for a year while the cause sat completely invisible beneath their planning process.

That is not a Scaling Up failure. That is what happens when leadership-layer tools work without an organizational intelligence layer underneath them.

A before-and-after planning room diagram. The left panel is labeled "Without Organizational Discovery" and shows the Sca

The Question Worth Asking Before Your Next Offsite

Before your next Scaling Up planning session, there is one question worth asking honestly.

How do we know that what we are planning around reflects what is actually happening in this organization?

If the answer is "because our managers tell us" or "because our meeting rhythm surfaces it," you have your answer. You are planning from filtered information, the way most companies do, and the way most companies have always done it.

There is nothing shameful about that. It is the default condition. It is just not the best available condition anymore.

The best available condition is going into your planning session with a verified picture of your organization's actual experience. Confidential interviews conducted without social cost to the people sharing them. Patterns synthesized across the whole organization, not just the parts visible from the leadership level. Friction identified at the root rather than at the symptom.

Scaling Up gives you an excellent process for acting on organizational knowledge. The question is whether the knowledge is complete enough to act on well.

See What Organizational Discovery Surfaces. Learn how Privagent works. →

Before the Next Planning Session

If you are running Scaling Up and you want to close the intelligence gap before your next offsite, the process is straightforward.

Run an organizational discovery engagement four to six weeks before your planning session. Give Privagent's AI interview system access to your team. Employees are interviewed confidentially, without attribution. Patterns are synthesized across the full organization and delivered in a report your leadership team can bring directly into the planning conversation.

What you will find, almost without exception, are issues that belong on your priority list that have never made it there. Some will be things you suspected but could not confirm. Others will be entirely new. Most will be actionable immediately within the Scaling Up process you already run.

You have already invested in learning how to plan well. The investment that pays the highest return on that effort is making sure what you are planning around is real.

Your Scaling Up coach is excellent at helping you act on what you know. Organizational discovery makes sure you know what is actually there to act on.

Those two things together close a loop that neither can close alone.

Schedule a Conversation Before Your Next Offsite. Book a discovery call. →

The Bottom Line

If you are running Scaling Up and leaving your offsites with good priorities that somehow keep recycling, this is probably why. The framework is sound. The intelligence feeding it may not be complete. That is a solvable problem. And it is worth solving before the next planning session rather than after it.

Scaling Up gives your leadership team a process for acting on organizational knowledge. Organizational discovery gives you the knowledge itself. The priorities you set, the critical number you commit to, and the people decisions you make are only as good as the intelligence feeding them. If that intelligence has been filtered by the organization's own social dynamics before it reaches your planning room, you are building a precise plan on incomplete data. Privagent delivers AI-powered organizational discovery for founder-led companies running Scaling Up and every other leadership framework. In days, not months, we surface what your organization is actually experiencing so that your planning process is built on reality rather than filtered impressions. Start a conversation with Ron Merrill at ron@privagent.com.

Frequently Asked Questions

Does organizational discovery require changing how we run Scaling Up?

No. Organizational discovery adds an intelligence layer to the process you already run. Your meeting rhythm, your one-page strategic plan, your critical number conversations all continue exactly as before. The difference is that you are now running those processes against a verified picture of what your organization is actually experiencing rather than a filtered one.

How far in advance of a planning session should we run an organizational discovery engagement?

Four to six weeks is ideal. This gives the leadership team time to review the findings, discuss implications, and arrive at the planning session prepared to incorporate what they learned. Running it closer to the session is possible but reduces the time available for the leadership team to process the data thoughtfully.

How is this different from the employee engagement surveys some Scaling Up coaches recommend?

Employee engagement surveys measure satisfaction and sentiment. They are useful for tracking morale over time. Organizational discovery is a structured diagnostic process designed to surface specific friction points, operational breakdowns, and communication failures. The two tools answer different questions. Engagement surveys tell you how people feel. Organizational discovery tells you what is actually creating drag on the business.

Our Scaling Up coach is already very good at surfacing issues during sessions. Do we still have a gap?

Almost certainly. A skilled Scaling Up coach is excellent at helping your leadership team think clearly and surface what is visible to them. But no coaching process, however skilled, can surface what your leadership team does not know. The gap is not in the quality of the facilitation. It is in the completeness of the information the leadership team brings to the room.

What types of issues does organizational discovery typically surface that miss Scaling Up planning conversations?

The most common categories are process breakdowns that have been worked around informally, communication failures between departments that are invisible at the leadership level, capacity imbalances that managers absorb rather than escalate, and recurring friction that employees have stopped reporting because previous reports did not produce change. These appear consistently across industries and company sizes, regardless of how mature the Scaling Up implementation is.

Can we share organizational discovery findings with our Scaling Up coach?

Yes, and we recommend it. The findings give your coach a more complete picture of the company, which makes their facilitation more targeted and effective. Several Scaling Up coaches have incorporated organizational discovery into their engagement model specifically for this reason.

How many employees need to participate for the data to be reliable?

We recommend including everyone in the organization, not just a sample. The value of organizational discovery is in the patterns that emerge across the full team, including the people furthest from the leadership layer. A thirty-person company should include all thirty. A one-hundred-person company benefits from full participation as well, though department-level patterns can be meaningful even with partial participation.

Published by Privagent. Learn more at privagent.com.