IDEAS

Judgment at Scale

When anyone can prototype something by Friday, the hard question stops being can we build it. It becomes should we, and how would we even know.

AI is making execution cheap and fast. It is not making judgment easier.

Good judgment is what decides whether speed creates value, or just creates more noise, faster.

This page is about where judgment actually lives: in individuals, in teams, and in the organizations that either support good decisions or quietly work against them.

The judgment system

Organizational judgment

Have we created the conditions for good decisions to happen repeatedly?

Team judgment

Can we combine perspectives, challenge assumptions, and make a good decision together?

Individual judgment

Can I make a sound decision under uncertainty?

01 · Individual

Can I make a sound decision under uncertainty?

Individual judgment is the ability to separate signal from noise, challenge assumptions, weigh tradeoffs, and make a sound decision even when the answer is not obvious.

AI can hand you more information, more options, and faster analysis. It cannot tell you what matters. That’s still a human call.

From experience

I experienced this while leading the development of a new strategic planning capability for Apparel. We had selected an external platform because it appeared to offer a faster path than building the capability ourselves. As the pilot progressed, however, the evidence began to challenge that assumption.

The difficult question was whether we were encountering normal implementation friction or learning that the solution was fundamentally mismatched to what the business needed. Continuing would preserve momentum and the investment already made. Changing direction would introduce delay, cost, and uncertainty, but could lead to a more sustainable outcome.

I had to separate normal implementation challenges from the more important signals: whether the platform could support our planning model, whether adapting it would create excessive complexity, and whether it would provide the long term flexibility we needed.

Based on that evidence, I recommended ending the vendor relationship before we expanded the commitment. Because we had limited the initial investment to a license and pilot, we were able to redirect the funding toward engineers and data scientists who could build a solution around the realities of our business.

The decision was not evidence that the original choice had been careless. The pilot had done what it was intended to do: test our assumptions before we scaled the investment.

Good judgment meant acting on what we learned, avoiding a larger sunk cost, and redirecting resources toward a more promising path.

What matters

Separate signal from noise
Challenge assumptions
Weigh tradeoffs
Decide under uncertainty

How I’ve enabled better judgment

Through Product Operations, I built role and scope analysis and a skills framework and coaching tool that made expectations, complexity, and development needs more visible, giving individuals and leaders a clearer basis for growth and talent decisions.

For reflection: When new evidence challenges a decision you have already invested in, what helps you recognize that it is time to change direction?

02 · Team

Can we combine perspectives, challenge assumptions, and make a good decision together?

More people in the room doesn’t automatically produce a better decision.

Strong team judgment requires clarity about what’s actually being decided, who owns the decision, which perspectives need to be involved, and how disagreement gets resolved rather than quietly avoided.

From experience

I experienced this while leading Assortment Planning products that depended on capabilities owned by two other teams. The Item team was rebuilding its item management system, while the Negotiation team was already developing its own solution. Improving item setup and vendor negotiation would require all three teams to reconsider parts of work already underway.

The challenge was creating space for the shared opportunity when each team already had its own roadmap, objectives, and delivery commitments.

The breakthrough came when we stopped trying to reconcile all three roadmaps and instead defined a shared “thin slice”: the smallest end to end experience we could build together to enable faster, higher quality item setup and improve costs through negotiation.

That reframed the decision. Teams retained ownership of their products, but we aligned on the outcome we needed to deliver together, the contribution each team would make, and how we would measure success.

Once the shared goal became clearer than our individual roadmaps, much of the friction faded. We were no longer weighing one team’s solution against another. We were deciding together how to produce a better enterprise outcome.

The result: we delivered a shared data management solution that reduced cycle time from one week to seconds and improved data accuracy by 50%.

That experience taught me that productive disagreement does not require teams to give up their priorities. It requires clarity about what they must solve together.

When teams align around a shared, measurable outcome, individual roadmaps become inputs to the decision rather than obstacles to it.

What matters

Clarify the decision
Assign decision rights
Bring in the right perspectives
Resolve disagreement

How I’ve enabled better judgment

Through Product Operations, I built a team health assessment and geo-distributed team analysis that helped leaders see patterns in team effectiveness, composition, and ways of working, so they could act based on evidence rather than anecdote.

For reflection: Where might competing priorities be keeping your team from defining the shared outcome it needs to solve together?

03 · Organization

Have we created the conditions for good decisions to happen repeatedly?

Organizations shape judgment whether they mean to or not: through the information people can see, the incentives they respond to, the decisions they are empowered to own, the operating rhythms they work within, and the tradeoffs leaders make visible.

Good judgment at scale isn’t just a talent problem. It’s an operating model problem.

From experience

I saw this firsthand when my company was integrating its store and digital businesses. Leaders across Merchandising, Digital, Supply Chain, Finance, Product, and Technology had to agree on how inventory would be planned and accounted for across channels. Two viable approaches were on the table, each with different benefits, costs, and points of friction.

To move the decision forward, we hosted a leadership offsite and mocked up both approaches. Rather than debating them in the abstract, leaders could see how each option would work, where it would create friction, and which benefits justified which costs.

That made the tradeoffs visible and helped the group reach an aligned decision we could translate into shared processes, metrics, and financial planning capabilities.

The work supported a broader enterprise transformation that unlocked more than $100 million in annual savings.

More importantly, it reinforced something I have seen repeatedly: good organizational judgment does not happen simply because the right leaders are in the room. It happens when information, alternatives, and tradeoffs are structured so they can make a sound decision together.

What matters

Make information visible
Align incentives
Clarify decision ownership
Create effective operating rhythms
Surface tradeoffs

How I’ve enabled better judgment

Through Product Operations, I built resource allocation analysis that gave leaders clearer visibility into capacity, priorities, and investment tradeoffs, creating a more consistent basis for decisions across the portfolio.

For reflection: What in your operating model makes good decisions easier to repeat, and what gets in the way?

Practice

Putting judgment into practice

Judgment isn’t just a mindset. It shows up in specific practices, and the same practice can operate at any of the three levels above. “Make tradeoffs explicit,” for example, can mean an individual clarifying what they’re willing to give up, a team agreeing on the tradeoff it’s making together, or an organization building portfolio and incentive systems that force real prioritization.

These are the practices I come back to most. They aren’t a fixed sequence. “Start with the decision” tends to come first; the rest get revisited as thinking evolves.

Start with the decision: What actually has to be decided, and who owns it.
Find the system: Look past the symptom to the roles, incentives, and routines producing it.
Separate signal from noise: What's essential, what's assumption, what's just interesting.
Look for leverage: Which decision point would improve the most across the system.
Make tradeoffs explicit: Surface the real costs instead of preserving ambiguity.
Design for the next decision: Solve today's problem in a way that also improves the information, process, or conditions behind the next one.

If judgment is the capability, the lifecycle in Strategy to Results is the system it operates inside.

For reflection: Where is judgment breaking down in your organization today: in how individuals interpret the evidence, how teams decide together, or the conditions the organization has created around them?

Explore Strategy to Results

Where this goes next

Go deeper on the thinking
The essays behind this framework: how judgment and operating models turn strategy into results.
Read the Ideas
See it in action
Judgment Coach: an early-stage thinking partner for consequential decisions, built on these ideas.
Visit Building

Judgment at Scale

Can I make a sound decision under uncertainty?

Can we combine perspectives, challenge assumptions, and make a good decision together?

Have we created the conditions for good decisions to happen repeatedly?

Putting judgment into practice

Go deeper on the thinking

See it in action