How good product judgment is built, even without complete data

Product judgment is finding the crux of a problem, the part that everything else depends on, and having the courage to commit to it before you have the full picture. Good judgment is narrower: it lands on the crux that moves the needle for the user and the business, not just any answer that looks reasonable. That is also how you decide with incomplete information. Once you find the crux, you know which small part of the data actually matters. This is clear thinking applied to a product decision, and it is the cornerstone of senior product leadership roles.

Why product judgment is the bar at the senior leadership level

At L7 and above, the data is almost never complete and the problems do not arrive cleanly defined. (L7 is Meta and Google terminology. At most other companies it maps to director level and above. You can see how titles line up across companies on levels.fyi.) Someone hands you a vague goal, a half-working product, or a market that is shifting, and the job is to decide anyway. What gets evaluated in a senior leadership loop, and in the role itself, is whether you can find the real problem and commit to a direction. It is not whether you can make a clean decision once you have clean, tidy inputs.

What many senior leadership candidates find challenging is the feeling that more information is needed before making a call. It feels responsible and it looks like diligence, but the missing piece is usually not just data. It is that you have not yet found the crux that makes most of the data a moot point. The same symptom shows up in interviews as over-explaining and hedging. The urge to gather more before you commit, and the urge to say more to prove you belong come from the same place: the discomfort of being judged before you feel ready. The strongest candidates learn to embrace that discomfort and commit anyway, because they have learned a way to develop clear thinking and trust their own judgment.

The technique: find the crux before you solve

Strong product judgment comes down to a technique you can practice. Before you propose anything, find the crux, the part of the problem that, once you identify it, makes the answer almost obvious. Then hold yourself back from framing the problem or choosing a solution until you have it.

In a group coaching session, I walked the group through a product sense case for a fundraising app. They spent about 20 minutes trying to pick a side, whether to build for the organizer or the donor. But picking a side was not the real problem to solve, and it was not the right question to ask either. For this product to work at all, everything depends on getting the donor moved enough to want to give. Most donors do not wake up thinking about giving, they give in response to something: a campaign, a story, a friend who asks at the right moment, or ROI. If nothing moves the donor, nothing else in the product would matter, because the organizer's tools and the checkout flow both sit downstream of that moment. So the crux here is the motivation, the thing that gets the donor to want to be part of the cause.

Once we saw that, the organizer-versus-donor question got much smaller, and the crux answered it for us. Value only gets created when the donor is moved to give, so the product has to be built for the donor, and everything it does should serve the purpose of motivating them. Notice what we did not do. We did not choose the donor with a mechanical rule like "this is a consumer product, so build for the consumer," or "there are more donors than organizers, so build for donors." A rule like that skips the exact thinking the interview is testing for. We chose the donor because the crux pointed there.

This is what finding the crux buys you, it cuts through the noise. We did not have to step through the entire user journey, list every pain point, and score each one to see how painful each pain point subjectively was. We needed one insight, that giving is reactive, that someone has to be moved before they give, and once we had it, the rest of the data was not going to change the decision. This is the 80/20 rule applied to thinking. In most problems there is a small slice of the information, call it the 20%, that settles the other 80%. The crux is that 20%. Once you have it, the rest becomes a moot point.

This is not only an interview skill. It is also what a product leader does when a team has lost its direction, or never had one to begin with. Picture a team with a roadmap no one agrees on, three priorities all marked urgent, and weeks of debate going in circles. The person who creates clarity there is not the one with the most opinions. It is the one who steps back and asks what the whole thing really depends on, then finds the crux that puts everything else in order. Maybe the crux is that none of the planned work matters until one broken step in the signup flow is fixed, because everything downstream depends on it. Once you have that, the arguments settle, and the rest of the pieces reveal themselves. The team was not short on information. It was short on the crux.

Why the crux is what lets you commit before you have the full picture

Deciding with incomplete information sounds like a problem of missing data. It rarely is. Once you have reduced a problem to its crux, you will feel more confident in making calls with incomplete information because the crux tells you which small part of it actually matters. You are not committing blindly. You are committing to the one part the whole problem depends on, which is a very different act.

This is why the courage to commit can be built rather than being a matter of temperament. It comes from having found the crux, because once you have it, the uncertainty that is left is uncertainty you can afford. The data you are still missing sits in the 80% that was likely never going to change your decision. What can look like intuition, deciding before you have everything, is the opposite. You are declining to wait on information that wouldn't have changed your direction in meaningful ways.

The group working on the product sense prompt on fundraising felt this shift. Before they found the crux, committing to the donor felt arbitrary, like picking a side and hoping. After, it felt obvious. The crux had made it for them. That is what good judgment really is: finding the crux that makes most of the information unnecessary, and committing to the direction it points to.

Why product judgment cannot be crammed in a few weeks

If judgment is this ability, finding the crux and committing to what it points to, the natural next question is how you build it. It is not something you can cram.

Judgment has 2 parts:

1. The first is not acting from panic. Under pressure, the brain pushes you toward the fastest familiar response, which is usually to grab a framework and start executing; or stay in indecision due to lack of complete data. Training yourself to pause there, and to stay with the problem long enough to understand it, is something you can start practicing this week.

2. The second part is slower. It is the sense for which problem is worth solving and where the real value sits, and it is built over months and years of real decisions and honest reflection on how they turned out.

Researchers who study expert judgment have found that good intuitions do not come from experience alone. They develop when people have extensive experience in environments regular and predictable enough to learn from, and when they get clear, timely feedback on how their decisions actually turned out. Daniel Kahneman and Gary Klein, two researchers who spent years on opposite sides of this question, agreed on that much in their paper, Conditions for Intuitive Expertise: A Failure to Disagree. Without valid feedback on outcomes, experience can simply reinforce the habits you already have, the good ones and the bad ones alike.

Personal reflection is one of the most practical ways to build that feedback loop. By deliberately looking back at what you decided, why you decided it, and how it actually turned out, you turn raw experience into something you can learn from. Other people can help by pointing out blind spots, but the loop that turns experience into judgment only works when you consistently compare your own decisions against real outcomes and update your thinking.

There is a useful comparison from aviation. A fighter pilot's actual fight time is often just 20 to 30 minutes, yet the debrief afterward can run several times longer, because pilots treat the debrief as, in one aviator's words, by far the most important part of the flight. They pick apart every decision, what worked and why, what did not and why, so they can learn from it. The effect is measurable. A meta-analysis of debriefing studies by Scott Tannenbaum and Christopher Cerasoli found that individuals and teams who run structured debriefs like this outperform those who do not by roughly 20% to 25%.

None of this happens in a few weeks. You can learn to run a framework quickly, but the judgment underneath it is built slowly, through real decisions and honest reflection on how they turned out.

How to build product judgment

Judgment grows first through your own reflection on your decisions and how they turned out, and second through input from others. That order matters, because the internal loop, asking what you decided, why, and how it actually turned out, is what turns experience into learning. Input from mentors or clear-thinking peers is most useful once you have already done that internal work. Skip it, and outside advice can steer you, but it will not reliably build your own judgment. You end up outsourcing your thinking, to other experts or to AI, and the very skill you were trying to build quietly wastes away.

There is early research pointing in this direction. In a 2025 study, heavier use of AI tools was associated with lower critical-thinking scores, aka cognitive offloading: leaning on the tool instead of doing the mental work yourself. A separate 2025 survey by Microsoft and Carnegie Mellon found a similar pattern: higher trust and confidence in generative AI correlate with reduced critical thinking effort, while high self-confidence in one's own skills leads to more cognitive engagement. A smaller and still preliminary MIT study that recorded brain activity while people wrote essays points the same way, with the weakest neural engagement in the group that leaned on the AI. None of this says outside help is bad. It says outside help is no substitute for your own thinking. So to develop clear thinking and judgment, we need to start with internal work first.

The internal work has 2 steps.

Step one: get the problem out of your head before you try to solve it. When you are handed a problem, write down everything you know about it and everything you are assuming, in plain words, and do not try to organize it or answer it yet. You are getting it out of your head so you can look at it from the outside. The brain is optimized to process, not to store information. When you use it to hold a pile of facts and worries, you burn the same power you need for thinking, and you have less of it left to think with. Getting everything onto the page hands the storing job to the page and frees your brain to do what it is good at. It also keeps you from locking into the first version of the problem, which is almost always the surface-level one. The moment you start solving, you commit to a framing, and a framing you commit to too early is what buries the real deeper problem. Getting it all out first keeps the problem open long enough for its real shape to show up.

Step two: work on what you find underneath, not on what you find on the surface. Now question what you wrote. Ask what the real problem is underneath the one you first described, and treat your own first read with suspicion. Your first read is hard to doubt because it is yours, and your own assumptions do not announce themselves as assumptions. One question that helps is this: if someone did not share my assumptions, what would they push on first? Keep asking what the problem is really about, and ask it again of each answer, until you reach the crux, the part that, if it is true, decides everything else.

There are 2 habits that make these steps easier. The first is to treat the urge to answer fast as a signal to slow down, because that urge is usually a reach for comfort, and it shows up before you have found the real problem. This is harder than it sounds. We are all trained by social media and AI to expect an instant payoff, and turning inward to reflect gives you none of that. There is no quick hit of reward, so the mind resists it. But this inward, unrewarding work is exactly what builds clear thinking, which is why so many people who think for a living swear by journaling. One study of workers learning a new task found that those who spent a few minutes reflecting on what they had done performed better than those who just kept working. Reflection is not time taken away from getting better. It is a large part of how getting better happens.

The second habit is to practice the whole sequence on small, low-stakes problems, so it is there for you when the stakes and the pressure are high.

Once the internal work is in place, the external work is what accelerates everything. You build judgment faster by putting yourself around people who already think clearly and letting them reflect your reasoning back to you, aka cognitive apprenticeship. Because expert thinking is mostly invisible, you learn it by watching someone make their thinking visible, step by step, and then practicing it yourself while they coach you and slowly pull their support away. A good coach does not hand you answers. They show you how they are thinking as they work, they catch the turns you miss, and they reflect your own reasoning back to you until you can run it without them.

The important part is that this external help sits on top of the internal work. It does not replace it. A coach can show you their thinking and reflect yours back, but only you can do the reflecting that turns any of it into judgment. That is why the internal work is the prerequisite.

I built my own thinking in this order as well. Long before AI became a thing, I had a daily habit of journaling twice a day, once in the morning and once at night. I was reflecting on my day, decisions and getting to know how I actually think. That was the internal work, and I did a lot of it alone. I also worked with multiple coaches over the years, and they played a large part in how I think. They reflected my reasoning back to me and showed me things in my own thinking that I could not see on my own. The coaching worked in conjunction with the inner work. Neither half would have been enough without the other.

FAQ

What is product judgment?

It is finding the crux of a problem, the part everything else depends on, and committing to a direction, often before you have complete information. Good judgment goes further: it is landing on the crux that moves the needle for the user and the business, not just any answer that looks reasonable. It is what lets a product leader choose well when the data is partial and the problem is not cleanly defined.

How do you make product decisions with incomplete information?

You reduce the problem to its crux first. Once you find the part everything else depends on, you no longer need all the data, because the crux tells you which part of it actually matters. Deciding without the full picture gets easier once you have the crux, and harder while you do not.

Does writing a problem down actually help you think, or is it busywork?

It helps, but not the way it is usually explained. The value is not in clarifying your thoughts as you write. It is in getting the problem out of your head so your brain can stop storing it and spend its energy on thinking instead. That frees your working memory and keeps you from locking into the first, surface-level version of the problem before the real one has a chance to show up.

Can product judgment be learned, or is it innate?

It can be learned. Part of it is training yourself out of the rush to a familiar solution, which you can start on quickly. The deeper part, the sense for what is worth solving, is built over time through reflecting honestly on your own decisions and learning from people who think clearly. The internal reflection comes first, and the outside input builds on it rather than replacing it.

How long does it take to develop product judgment?

Longer than a few weeks. You can learn to run a framework quickly, but the judgment underneath it is built over time through this kind of thinking, honest reflection on your decisions, and learning from people who think well. That is why starting early and building a daily habit matter more than any quick technique.

How is product judgment different at the senior leadership level?

At the senior leadership level the problems are more ambiguous and the data is less complete, so the weight falls on judgment rather than execution. What matters is whether you can find the real problem and commit to a direction fast that moves the needle, not whether you can produce a tidy, structured answer.

Where to start

If you are preparing for a senior product leadership interview, or you want to build the judgment these roles require, that is the work we do together. You can apply here. You can see recent client wins here.

For how leveling actually works at the top, read the companion piece on the L7 to L9 product leadership interview.

About the author

Nancy Chu is an L7-L9 PM product leadership coach. She was a director at Roku and a manager of product managers at Meta before coaching. She works with senior product leaders at companies like Google, Meta, and Anthropic, helping them land roles at $900K and above in total comp and lead with more presence once they are in the seat.

Every week she breaks down the distinctions that matter in senior leadership product interviews, like how to find the crux of a product problem and what separates an L7 answer from an L8 one. You can get them each week.