How to align senior stakeholders around Big Bets (without a quarter of 1:1s)

May 18, 2026

Dana Vetan

$1.75 billion on Quibi. $120 million on Juicero. Both decisions made in leadership rooms by smart people with deep capital. Both would have failed a two-hour scoring session, if anyone had run one. This piece walks through the structure that catches expensive bets — AI investments, product programs, platform commitments — before they consume the year's budget. It uses the 4U Framework, developed at Harvard Innovation Labs and coined by Michael Skok, with a 2026 update for customer-facing and internal organizational challenges.

You will leave with the real reason senior groups don't align on big bets, the structure that prevents the expensive ones, and the language to run the conversation in a single two-hour session instead of a quarter of side meetings.

The problem with how senior stakeholders align on big bets

The most expensive big-bet failures start as alignment failures. Leadership groups commit without a shared way to compare what is on the table, and the cost shows up months or years later — in pilots that don't scale, programs funded at half-strength, and the occasional public flameout.

You know the room. Six to eight leaders. A whiteboard with too many priorities on it. A question on the table: which one do we commit to next?

Marketing wants the brand initiative. Operations wants the efficiency program. Product wants the platform investment. Sales wants the new vertical. Someone wants to do something with AI. Each leader is right from where they sit. The organization doesn't have enough budget, headcount, or attention to fund every priority well. Nobody wants to be the function that gives way.

So the team follows the political path of least resistance. Yes to everything. Half-scale funding all around. Hope the priorities sort themselves out later. They never do. The roadmap bloats. Pilots multiply. By year-end, every individual program looks fine on paper, and the business has barely moved.

The pattern is everywhere right now in AI. Use cases stack up. Pilots get funded. Half of them stall. The other half launch into workflows nobody redesigned for them. The structural cause is the same as it has always been: each leader is reasoning from a different framework — their own. The group has no common lens, so it cannot reach a common decision.

Why the usual round of 1:1s stops working at scale

The default playbook — build the case in private 1:1s, then ratify in a joint meeting — fails because alignment is a group property, not a series of individual signals.

The playbook is well-rehearsed. A Head of Innovation, a VP, a strategy lead — someone has to move the decision forward. They schedule the round. Forty-five minutes with each leader. Build the case privately. Surface the objections one at a time. Land enough soft commitments to walk into the joint meeting confident the room will agree.

Then the joint meeting happens.

The leaders show up half-prepared. The conversation runs at the level of executive summary. One leader pushes harder than the others. Two leaders quietly disagree and don't surface it. The room ends with a vague "let's keep moving on this" and the decision postponed for another cycle.

The pattern repeats because the joint meeting was set up to ratify an alignment the 1:1s were supposed to deliver. The 1:1s rarely deliver it. They produce polite individual signals that evaporate the moment leaders face each other's trade-offs.

Alignment emerges when the group reasons together against the same criteria, in the same room, at the same time. The joint conversation has to do the work — and the structure of that conversation decides whether the room produces a real decision or another deferral.

What good comparison criteria do in the room

Good criteria change the quality of the conversation.

They stop leaders from arguing from their own function and force the team to evaluate the decision through the same lens. That makes the real disagreement easier to see: not who cares most, but why smart people are reading the tradeoffs differently.

The result is a decision with a clear rationale behind it. One the leadership team owns together, and one they can defend when the next budget challenge comes.

Without that structure, the loudest voice sets the frame and the most senior voice ends the debate. Everyone else reads the politics instead of the problem.

The 4U Framework gives the team that structure.

What the 4U Framework is, and where it came from

The 4U Framework was developed at Harvard Innovation Labs and coined by Michael Skok at underscore.vc as a fast filter for evaluating which opportunities are worth pursuing.

It was built for startups — a structured way for founders and early-stage investors to evaluate whether an opportunity is worth pursuing before committing time, capital, or team.

The four dimensions name the conditions that make an opportunity worth a serious bet:

Unworkable — the current situation is genuinely broken for someone
Unavoidable — they cannot ignore it for long
Urgent — they want it solved now
Underserved — existing solutions miss the mark

A founder can describe a hundred problems they could solve. Most of them score poorly across one or more of the four lenses. The ones that score strongly across all four are the candidates worth building against. The framework filters opportunity from noise.

We started using it inside Design Sprint Academy for the same reason it works for startups. The job of choosing which problem to commit to is the same job, whether the room is two founders or eight executives.

Why a startup tool works inside a big organization

A leadership team and a founder do the same job — choosing which problem to commit to. Big orgs just have more problems, more stakeholders, and more competing priorities.

The 4U lenses do the same filtering job for both. The leadership group sees four to ten candidate problems on the wall. Each leader scores each problem on each dimension. The scores reveal which problems are strong across the board and which are politically loud but structurally weak.

We translated the venture-style filter into a two-hour workshop format. Six to eight senior leaders. Two to four candidate problems. Silent individual scoring before any discussion. The output: a scored shortlist the leadership group co-owns, with two things they didn't have walking in.

A shared decision-making criteria that survives the rest of the quarter.

And confidence that they're looking at the right problems — measured against shared criteria, where the loudest leader's problem competes on the same axes as everyone else's.

The room doesn't need more data. It needs a way to compare the data it already has, without each function arguing from its own framework. That is the work the 4U structure does.

What we learned running the workshop at scale

The quality of the output depends almost entirely on the quality of the questions asked inside each dimension. The four-word Skok filter does a venture-stage job; an eight-person leadership room needs a deeper question stack.

Ask a room "how unworkable is this?" and leaders answer at whatever level of abstraction feels comfortable. "Pretty unworkable." "Our customers are frustrated." "It's a real problem." The scores land somewhere in the middle. The discussion stays polite. The output is vague.

Ask the same dimension with a sharper prompt stack and the room has something to argue about. The scoring tightens. The disagreements get useful.

The Skok original is a four-word filter. That's its strength as a venture tool — founders need a fast first pass. A big-org leadership room needs a question stack for each lens. Prompts that surface evidence, force precision, and give leaders something concrete to score against.

The second thing we noticed was harder to see.

A customer-facing problem and an internal problem score against the same four dimensions, but the evidence each lens looks for is different. A customer's situation becomes unavoidable through regulation, biology, life events, market shifts, platform rules. An internal team's situation becomes unavoidable through system end-of-life, board commitments, contractual deadlines, technical debt crossing a tipping point. Same word, different forces, different evidence.

The same is true for the other three lenses. Urgent for a customer looks like rising support volume and procurement deadlines. Urgent for an internal team looks like a board promise and a window closing next quarter. Underserved for a customer means competitors charging too much for too little. Underserved for an internal team means shadow tools and one person holding the whole workflow together.

Run the same generic 4U prompts on both types of challenge and customer-facing ones score cleanly while internal ones score fuzzily. (Or the other way round, depending on the room.) The framework was sound. The questions needed splitting.

That was the diagnosis the 2026 update was built to fix.

The 2026 update — two variants

The 2026 update splits the framework into two variants — one for customer-facing challenges and one for internal organizational challenges. The four dimensions stay the same. The prompting questions inside each dimension change.

The prompting questions are tuned to the type of force, the type of urgency, and the type of alternative that applies to each type of challenge. Customer pain looks one way. Internal pain looks another. The same dimension reads different evidence depending on which kind of challenge the room is scoring.

How to pick the variant in 30 seconds

Three quick tests decide whether you run the customer-facing variant or the internal variant. When two of the three point the same way, that's your answer.

Test 1 — Where does the pain land first? Outside the org, with downstream cost to the org (churn, complaints, lost deals, regulatory escalation): customer-facing. Inside the org, with downstream cost to customers (slower delivery, missed launches, degraded service): internal.

Test 2 — Who would the team interview to validate the problem? Customer or user interviews: customer-facing. Interviews with the team, the manager, or the cross-functional partners: internal.

Test 3 — Where does a workable solution sit? In what the org offers, charges for, or delivers to external stakeholders: customer-facing. In how the org operates day-to-day: internal.

When the three split, the challenge has components of both. Score it twice — once through each variant — and compare the profiles before deciding which side to invest in first. Sometimes both score high. That's also useful information, and usually points to a Problem Framing workshop that has to address both layers explicitly.

The 4U for customer-facing challenges vs the 4U for internal organizational challenges

‍

What each variant looks at

The two variants share the four dimensions and the scoring rubric. The difference is what evidence each prompt surfaces in the room.

The summaries below describe what each lens looks at and what evidence to expect.

The 4U for customer-facing challenges

The customer-facing variant surfaces external pain. The prompts expose what stakeholders are experiencing, the forces putting them there, why now matters, and where the market is failing them.

🔴 Unworkable — what's genuinely broken for the customer today, the root cause, and what happens if they stay stuck
🔶 Unavoidable — the external forces (regulation, life events, market shifts, platform changes) that keep the stakeholder from walking away
🕒 Urgent — the signals showing they want it solved now, and whose buying decision or deadline is closing this quarter
🚫 Underserved — the gaps in what the market offers and the segment failed worst by today's solutions

Scoring signals are external: churn, lost revenue, public complaints, regulatory escalation, rising support volume, visible workarounds, mismatched pricing.

The 4U for internal organizational challenges

The internal variant surfaces internal pain. The prompts target where work breaks down, what's forcing the org to act, why the window is closing now, and which internal stakeholders are stranded.

🔴 Unworkable — where work is breaking down today, the cost of the breakdown, and which team or workflow is genuinely stuck
🔶 Unavoidable — the internal triggers (regulation, contracts, system end-of-life, board commitments) that the org cannot defer past their timeline
🕒 Urgent — the signals making this time-sensitive: a blocked strategic commitment, a board-level promise, a regulatory window
🚫 Underserved — the shadow tools, single points of failure, and one-person dependencies that reveal where no real alternative exists internally

Scoring signals are internal: measurable financial loss, attrition risk, audit findings, operational gridlock, heavy shadow-tool use, single points of failure, repeated requests that keep getting deprioritized.

The honest part

The hardest part of running a 4U session is the status quo. Senior leaders are practiced at winning political meetings, and a scored workshop takes that advantage away. They will push back.

The political meeting favors the loudest voice, the most senior title, the closest relationship to the Decider. A scored session levels that ground. Every leader scores the same problems against the same dimensions, in silence, before anyone explains their reasoning. The political moves that worked in the unstructured meeting stop working. The leaders who relied on those moves will resist the structure.

This is the first obstacle a Director hits when proposing a 4U session inside a big organization. The blocker is rarely budget or calendar. The blocker is buy-in. The leaders who would benefit most are the ones who need the structure least. The leaders the room needs to convince are the ones whose advantage the structure removes.

The second obstacle is education. Leaders rarely agree to a scored framework on principle. They agree to it after seeing what skipping the structure costs.

The two examples from the opening do most of that work.

Quibi. $1.75B for a mobile-first short-form video service. Shut down six months after launch. Leadership had conviction, deep capital, and the Hollywood lineup to back it. The 4U lenses would have flagged all four dimensions. Nothing was unworkable for the user — YouTube and TikTok already served the need. Nothing was unavoidable — no force pushing users toward a paid mobile-first service. Nothing was urgent — no deadline driving adoption. The segment was already well-served — free alternatives saturated the market. Four red flags. Nobody surfaced them before launch.

Juicero. $120M for a $400 connected juicer whose juice packs could be squeezed by hand. The unworkable score was generous. The underserved score was zero. The framework would have caught it.

These are the public ones. Most of the expensive bets that fail this way never make the news — they just quietly miss their numbers. Walk into a 4U conversation with two or three named examples on hand, public or otherwise, and the dynamic shifts. Leaders see the cost of skipping the questions. The case for scoring stops being abstract.

The third obstacle is the one a Director cannot solve by reading the article. A 4U session is only as good as the person running it. A facilitator with weak context will let the room score the wrong evidence. A facilitator who cannot hold disagreement will let the loudest leader anchor the discussion before scoring even starts. A facilitator without the communication skills to manage a room of senior people will lose the session in the first ten minutes. Usually to the leader with the most political capital and the least patience for structure.

Good 4U facilitation needs three things. Deep context on the organization. The ability to read the room in real time. The craft to redirect a senior leader who is trying to dominate the conversation. None of it comes free with the framework. The framework makes the conversation possible. The facilitator is what makes it produce a decision.

The fourth obstacle is perception. Workshops carry baggage. Most leaders have sat through one that was a half-day of sticky notes, a vague summary slide, and nothing that turned into a decision afterward. Some of them are right to be skeptical. Most workshops they've attended deserved that reputation.

You can't win that argument with words. The way past the perception is to run it small first — with a less senior team, on real challenges, in two hours — and let the output speak. A scored shortlist on the wall, with rationale, that the team can defend. That artifact does the work that no pitch deck can.

Pick the right variant. Bring the right examples. Run it with someone who can hold the room. And if the perception fight is the one stopping you, run it small first.

Three ways to get started

The 4U Framework is the structure we use when leadership teams need to align on a big bet — AI investment, product program, platform commitment — inside a two-hour room.

If you have a big bet on the table and you don't want it to become another expensive lesson, book a 30-minute call with us.Three ways to use the call:

Discuss a trial run with a less senior team. Real challenge, two hours, no exec time committed. See the output for yourself before pitching the senior version.
Coaching to run it yourself with your senior stakeholders.
A session we facilitate for your leadership group.

FAQs

Why do senior stakeholders struggle to align on big bets in the first place?

Each leader evaluates candidate problems through their own functional lens — marketing's metrics, operations' constraints, product's roadmap, sales' pipeline. There is no shared comparison structure that lets the group evaluate the same problems against the same criteria.

Without that structure, the loudest voice tends to anchor the room and the most senior voice tends to close it. The 4U Framework creates a shared scoring lens that turns functional advocacy into a comparable group discussion.

Why not just do another round of 1:1s before the meeting?

1:1s are useful for surfacing perspectives, objections, and political realities ahead of the session. What they do not create is shared reasoning. Each stakeholder hears the case privately, without having to evaluate trade-offs in front of peers.

Real alignment only happens when the group evaluates the same opportunities together, against the same criteria, in the same room.

Where does the 4U Framework come from?

The framework was developed at Harvard Innovation Labs and coined by Michael Skok at underscore.vc. It was originally designed as a fast filter for founders and investors to evaluate whether an opportunity was worth pursuing before committing serious resources.

Design Sprint Academy adapted the framework for enterprise leadership teams, turning it into a structured workshop format for evaluating strategic bets across functions.

How do I decide whether a challenge is customer-facing or internal?

Three tests usually clarify it quickly:

Where does the pain land first — outside the organization or inside it?
Who would you interview to validate the problem — customers or internal teams?
Does the solution change what the organization delivers externally, or how it operates internally?

When two of the three point the same way, that is usually the right variant. When the answers split, the challenge likely contains both customer-facing and internal dimensions.

Can a challenge have both customer-facing and internal components?

Often. In those cases, it helps to score the challenge through both variants and compare the profiles. The goal is not simply to see which score is higher, but to understand where the strongest friction and risk sit first.

Sometimes the customer pain is the visible symptom of an internal operational issue. Other times the internal friction exists because the organization is trying to respond to a rapidly changing customer need. When both score strongly, the next step is usually a deeper Problem Framing effort that addresses both layers together.

Who should be in the room for a 4U session?

Six to eight senior stakeholders is usually the ideal size. The group should include the people responsible for strategy, customer impact, operational feasibility, funding, and delivery.

Too few perspectives and the scoring becomes narrow. Too many people and the discussion turns into stakeholder theatre instead of decision-making.

What does the team leave with after the session?

The output is a scored shortlist of opportunities, the rationale behind the scores, visible areas of agreement and disagreement, and a clearer recommendation on where the organization should invest next.

Just as important, the leadership group leaves with a shared decision-making framework they can continue using after the workshop ends.

How do I get past internal skepticism that “workshops are a waste of time”?

Most leaders have experienced workshops that produced discussion but no decision. The skepticism is understandable. The best way to overcome it is not through persuasion, but through evidence.

Run the session once with a smaller or less senior team on a real challenge. A visible scoring process and a defensible shortlist tend to change the perception faster than another presentation about collaboration ever will.

Can this be run remotely, or does it need to happen in person?

Both formats work. The real requirement is attention, not location. Remote sessions can produce strong outcomes when stakeholders are fully present and engaged for the full two hours.

If participants are multitasking, joining between meetings, or treating the session as background activity, the scoring quality drops quickly regardless of format.

Your Cart