Thinking Big Isn't a Mindset Problem. It's an Architecture Problem.

Ambition doesn't fail for lack of belief. It fails when the organization underneath the goal was never built to hold it.

Architecture of Scaling
Originally published October 2023 · Updated October 2026

Most CEOs don't struggle to imagine a bigger future. They struggle to build a company capable of reaching it, and the two are treated as the same problem far too often.

By Stephanie Paillé
Founder & CEO, 360 Leadership Coaching

Meet David, the CEO of a $20 million company.

He isn't short on ambition. He tells his team he wants to triple revenue in three years. He posts about it. He believes it. And for a few months, the energy in the building is real: people move faster, meetings get sharper, the whole company seems to lean forward.

Then the goal quietly stops showing up anywhere except the slide it was announced on.

The org chart hasn't changed. The decision rights haven't changed. David is still the one who signs off on every hire, every price change, every new initiative. The goal asked the company to become something different. The architecture underneath it never did.

Six months later, revenue is up 14%. Respectable. Nowhere near triple. And David is left with a familiar, uncomfortable question: was the goal wrong, or was I asking the wrong thing to carry it?

Big goals don't fail because they're too big. They fail because nothing else was resized to match them.

This is where "thinking big" earns a bad reputation inside scaling companies. Leaders watch an ambitious goal collapse into an unremarkable year and conclude that boldness itself was the mistake, and that the safer path is to set modest targets and beat them.

That conclusion skips a step. The research on ambitious goal-setting doesn't say big goals are the problem. It says big goals are conditional.

The evidence: ambition works, but only under specific conditions

Decades of goal-setting research have found that specific, difficult goals can produce higher performance than vague or easy ones when the conditions for pursuing them are in place.

That research holds up well. But "difficult" and "stretch" are not the same thing, and this is where most leadership teams misread it. A 2011 Academy of Management Review study by Sitkin, See, Miller, Lawless, and Carton examined what the authors called the organizational pursuit of seemingly impossible goals, commonly known as stretch goals.

Their contingency framework found something counterintuitive: stretch goals are most seductive for organizations that can least afford the risks associated with them. The companies most tempted to reach for a moonshot goal because performance is soft and resources are thin are precisely the companies least equipped to survive missing it.

The companies best positioned to benefit from a stretch goal are often the ones with enough performance and resource buffer that they're tempted to play it safe instead.

The authors later illustrated this in Harvard Business Review with Yahoo under Marissa Mayer: in 2012 she announced a set of wildly ambitious targets, including double-digit annual growth, for a company already struggling. Five years later, Yahoo had fallen short on all of them. It was a company in the bottom-left quadrant of the matrix above, reaching for a goal built for the top-right.

In other words: ambition isn't free. It has prerequisites, and companies can set the goal without first checking whether the organization is equipped to pursue it.

Why "just think bigger" doesn't fix the underlying gap

The instinct, when growth stalls, is to raise the target. A bigger number, a bolder public commitment, a more inspiring keynote to the team. If the goal itself isn't the constraint, none of that reaches the actual gap.

A CEO can announce a 3x goal without ever changing who is allowed to make a 3x-sized decision. That gap doesn't show up on the strategic plan. It shows up as a leadership team that nods at the new number and then keeps running the same weekly cadence, the same approval chain, the same resourcing model that was sized for the old one.

Thinking big changes what a CEO says the company is reaching for. It does nothing, by itself, to change what the company is built to hold.

Four conditions that determine whether a big goal is real or aspirational

The stretch-goal research points to two critical conditions: recent performance and available resources. Through the Scaling CEO lens, two additional questions matter as the organization grows: whether decision architecture can carry the goal and whether leadership has defined what meaningful progress looks like short of the full target.

1. Capacity

Does the organization have (or have a credible plan to build) the resource slack to absorb the goal? Sitkin's framework is explicit that stretch goals draw down real reserves financial, operational, and human. A goal set on top of an already-stretched organization isn't ambitious. It's fragile.

2. Recent performance

Is the organization coming off a period of demonstrated execution, or is the big goal being used to compensate for one that wasn't? Teams and leaders need evidence that they can already execute reliably before a stretch goal asks them to execute past what's reliable.

3. Decision architecture

Has decision-making authority been resized to match the goal, or does every consequential call still route through the same one or two people it did at a tenth of the size? A goal that requires new speed and new judgment across the company cannot be held together by an approval chain built for the old scale.

4. A defined floor

What happens if the goal is missed? Defining what “meaningful progress” looks like short of the full target gives the leadership team a way to distinguish productive stretch from strategic failure, and to decide when to persist, adapt, or rethink the goal.

What Jim Collins got right, and what gets lost in translation

Jim Collins and Jerry Porras' concept of the BHAG, the Big Hairy Audacious Goal, introduced in Built to Last, is often cited as permission to simply aim higher. What's frequently left out is that Collins and Porras placed audacious goals inside a much broader system of core ideology, organizational discipline, and relentless progress. The goal was never the whole mechanism. It was the visible tip of a much larger architecture most companies never build.

That's the piece "thinking big" advice tends to skip. Excitement about a big goal is real and valuable. It does sharpen focus, and it does make the ordinary friction of a Tuesday feel smaller. But excitement is not architecture, and a company can run out of the former while still lacking the latter.

The leadership team needs a better question

Most leadership teams, when setting an ambitious goal, are already asking:

What's the number, and by when?

I'd add several others:

• Do we have the resource slack to absorb this if it takes longer than planned?

• Is this goal compensating for a performance problem we haven't named?

• Which decisions still have to route through one person, and does the goal require that to change?

• What does credible progress look like if we don't hit the full number?

• Where has the goal been announced without anything underneath it actually changing?

Those questions move "thinking big" from a motivational moment into an architecture decision. And that is where the goal either becomes real, or becomes next year's slide that nobody mentions again.

Ambition isn't the risk. An unbuilt foundation under it is.

Growth doesn't punish companies for aiming high. It punishes companies for aiming high without resizing the decision rights, the resourcing, and the leadership capacity underneath the aim.

The difference isn't simply who believes hardest. It's whether the goal becomes a design brief for the organization, not just a number for the team.

Thinking big is the beginning of the work. Building the architecture that can carry it is the rest of it.

Explore More on Scaling Leadership

This article is part of our work on the Architecture of Scaling: how decision-making, capacity, authority, alignment and execution must evolve as organizations grow.

Explore more insights across the Psychology, Architecture and Economics of Scaling.

Explore all articles →

Sources:

Sitkin, S., See, K., Miller, C., Lawless, M., & Carton, A. — "The Paradox of Stretch Goals: Organizations in Pursuit of the Seemingly Impossible," Academy of Management Review, 36(3), 2011
Sitkin, S., Miller, C., & See, K. — "The Stretch Goal Paradox," Harvard Business Review, January–February 2017
Locke, E. A., & Latham, G. P. — "Building a Practically Useful Theory of Goal Setting and Task Motivation: A 35-Year Odyssey," American Psychologist, 57(9), 2002
Collins, J., & Porras, J. — Built to Last: Successful Habits of Visionary Companies, 1994 (origin of the BHAG concept)