The Innovators Studio with Phil McKinney

In 1974, a psychologist named Elizabeth Loftus showed a group of people a film of a car accident. Afterward, she asked half the group one question: how fast were the cars going when they hit each other? The other half got the same question with a single word swapped: smashed instead of hit.
The smashed group estimated higher speeds. Same film. Same crash. One word.
 
A week later, everyone came back and answered a new question: Did you see broken glass? There was no broken glass in the film. The smashed group remembered it anyway.
One word inside one question changed what people reported seeing. Then it reached back and rewrote what they remembered.
Somebody did this to you this week. A question steered your answer, and you never noticed.
Last week, I showed you that your brain cannot refuse a question. You hear one, you start answering, whether you agreed to or not. This week is the other side of that power. If every question forces an answer, then how the question is built decides which answer you get back. Questions have an anatomy. Almost nobody looks at it.
Before we're done, a motorcycle taxi in Bangkok is going to show you what a question built right can find. 

Let's get into it.

=====
Every question you ask carries three things, whether you put them there on purpose or not.
It carries assumptions, the things it treats as already settled. Ask "Why did the launch fail?" and you've ruled the launch a failure before anyone speaks.

 
It carries scope, the range of answers it permits. "Coffee or tea?" permits exactly two answers. "What should we drink?" opens the room.

 
And it carries a load, the specific words that steer the answer. That's what "smashed" did. Nobody in that study felt steered. The steering is invisible to the person answering, and most of the time to the person asking too.

 
Once you see the parts, you can take any question apart. Take "why did the launch fail?" one more time: it assumes failure before anyone answers, its scope is only explanations, and "fail" is the loaded word doing the steering. Hold on to that one; we'll rebuild it later.
Let's start with the ones built to do damage.
The worst question in business
"That presentation was fantastic, wasn't it?"
That's a tag question: a statement dressed up as a question, built so every answer is closed off except agreement. The person asking isn't really asking, not in any way that risks hearing something different. They're collecting a signature. When lawyers use them in court, it's called leading the witness. When managers use them in conference rooms, it's called alignment.
Tag questions did damage for years at HP, in the design reviews, every product went through before customer briefings. One review was for a prototype, one of our first laptops in what's now called the "thin and light" category. The product team wanted to lead that category without straying too far from what already sold.
That's the tradeoff tag questions live in. Nobody wants to sound negative about it. So the pushback arrived dressed as agreement: "We'll still have four USB ports, right?"
You don't get thin and light with a case full of legacy ports, and the designer knew it. I watched the exasperation cross his face. Before it became a battle, I stepped in and rebuilt the question: "What's the right mix of ports for this segment, and why?" Then: "Have we tested that mix with the target customers?"
The answer came back fast. "No need. We know what the customer wants." I nearly smacked my forehead. One rebuilt question had uncovered the real problem, and it wasn't ports. It was an untested assumption sitting in the middle of a flagship product plan.
That's what tag questions cost you. The entire point of asking a question is to get information, input, or ideas. A tag question collects compliance instead. Enough of them, and people stop bringing you anything you don't already believe.
The two kinds of good questions
Real questions are split into two categories: factual and investigative.
A factual question retrieves information. How many units did we sell last week? You may not know the answer, but you know exactly how to get it: one phone call. Factual questions keep the world running. They just can't uncover anything because they only retrieve what somebody already knows.
An investigative question can't be answered with a yes, a no, or a lookup. It's divergent: more than one correct answer exists, so the person answering has to go investigate. You felt this difference last week. "What is half of thirteen?" is a factual question. "How many ways could you answer: what is half of thirteen?" is an investigative question. One is arithmetic. The other is the one that a classroom answered thirty-two different ways.
Socrates built his entire way of teaching on investigative questions, pushing every student past "I've heard it said that..." until they could say what they themselves thought, and why. The first step toward knowledge, he insisted, is admitting yours is incomplete.
So here's the definition I've worked from for years. A great question makes the other person genuinely think before they answer, and it surfaces an insight that had been eluding them. Both halves matter. The first half costs you real effort. The second half is the payoff: you see something you've been looking at for years and never actually seen, and it surfaces possibilities you'd never have found on your own.
How to build one
How I build them is with four moves, in the order I use them. You already watched three of them work in that design review.
Strip the answer out. Read your question and find the smuggled conclusion. "Right?" and "wasn't it?" come off first. Then the buried assumptions. "Why did the launch fail?" becomes "what happened when we launched?"

 
Open the exits. If it can be answered with yes, no, or a single lookup, it's factual. That's fine when information is all you need. When you want discovery, rebuild it until more than one correct answer exists. The rebuild is usually small. "Should we do this?" becomes "what are the ways this could work, and what are the ways it dies?"

 
Weigh every word. This is Loftus's lesson. "How do we make this cheaper?" and "what happens if we triple the price?" point at the same product, and they will never produce the same ideas. There is no neutral wording. Every word carries load, so choose it deliberately instead of inheriting it.

 
Aim it where nobody is looking. If you can already predict the answer, the question is just decoration. Point it at something unexamined: the assumption everyone stopped checking, the customer nobody ever talks to. A great question should surprise you.

 
What a well-built question uncovers
Late 1994, Bangkok. Half an hour stuck in traffic, twenty-eight minutes until a critical meeting. At eighteen minutes, I gave up, jumped out of the limo, and hailed a motorcycle taxi. 125ccs of terror, flat out through the heat, my briefcase clutched to my chest.
Somewhere between the tuk-tuks, I started thinking about the machine underneath me. Cheap, efficient transportation. The streets were flooded with them. And on the other side of the world, Harley-Davidson was selling motorcycles as big-ticket luxury. A product that began as cheap transportation for the American working man had become a premium item that people waited months for.
In that evolution, somebody had to ask a question like this: What if we stop trying to make this cheaper and go the other way? Everything needed to see that opportunity had been lying in plain sight for decades, waiting for someone to ask for it.
That's the payoff of this craft. The next discovery in your business is probably sitting in an assumption nobody's checked in years, waiting on the right question to find it.
Practice Exercise: Before your next meeting, write down the one question you most need to ask, exactly as you'd naturally say it. Then take it apart on paper. What does it assume? What answers does it permit? Which words are steering, and in what direction? Rebuild it with the four moves and ask for the rebuilt version instead. Pay attention to what comes back that the original never would have surfaced.
Conclusion
This is part 2 of a three-part series on questions as the skill behind better thinking, better ideas, and better innovation. Next in on the specific questions I spent twenty years collecting and testing, the ones that reliably uncover what everyone else misses.
Full show notes for this episode are up at philmckinney.com. And if you want more than the show episodes, check out my articles over on Substack, including the first four chapters of my next book. 
Subscribe on YouTube or wherever you get your podcasts so you don't miss the next episode, and don't forget to hit the notification bell if you want to know the moment it's up.

What is half of thirteen?
Stop. Answer it. Don't think ahead, just answer.
You said 6.5. I know you did, because everyone does. Nobody chose to answer that question. Your brain solved it before you decided whether you even wanted to play along. That's the power of a question: whoever hears it cannot stop themselves from answering. Ask a person something and their mind starts working on it right away, whether they wanted to or not. 
If you gave that answer on a math test, it would get ‌marked as correct. Give that same answer on a test of innovation, and you're average, because that's where everyone stops. Push beyond the obvious answer, and that's what puts you top of the class.
Here's the version of the question that changes everything: How many ways could you answer "what is half of thirteen?"
Sit with that for a second, because the honest reaction most people have is mild panic. There's the obvious one. Then what?
Split the number down the middle and you get a 1 and a 3.
Split the word into syllables and you get "thir" and "teen."
Every one of those is a real answer. None of them occurred to you the first time, because the first time, your brain wasn't looking for options. It was looking for an answer to the question.
I've run this exercise for years in my Innovation Boot Camp and the Innovation Essentials Workshop. One professor who uses my book in their class now opens every semester of her course with it. The class brainstorms as many answers to the question as possible. The record so far is thirty two different ways to answer that one question. And remember, asked the first way, that same question only gives you one answer.
This isn't just a classroom trick. Researchers have measured this exact mental muscle since the 1960s, asking people how many uses they could find for a brick. Some people list four. Some list forty. The gap between those two people has nothing to do with intelligence. It's whether their mind treats the first answer as the end of the search or the beginning of one.
Practice Exercise: Take one recurring question: a decision at work, a plan for the weekend, even "what should I make for dinner." Before you settle for the obvious answer, ask "how many ways could I answer this?" and write down at least ten. Not ten good ones, just ten. See where the eleventh one takes you.
This part 1 of a three-part series on how to use questions as the skill behind better thinking, better ideas, and better innovation. Next week, we get into what actually separates an average question from a great one.

You trust your gut because it's been right before. But "right" is exactly the thing you've been measuring wrong.
A hitter never has this problem. His batting average is honest. It counts hits, nothing else, across a whole season, and he can't argue with the number. Your gut is supposed to work the same way: every decision an at-bat, every result feedback, a career sharpening your instincts the way a season hands a hitter a real number. But you keep your own scorebook. You mark every win as good judgment the second it lands. The trouble is that a skilled call and a lucky one produce the same win. In your book they look identical. Train your gut on that for thirty years and it grows certain about things that were never true.
I know, because I trained mine that way.
The Award and the Bankruptcy
At twenty-eight, I won, and the win felt like proof. I was at a company called ThumbScan, and I took a piece of government security technology and repackaged it for the business PC market. We called it PCBoot. PC World named it Security Product of the Year at COMDEX in Las Vegas, in front of the whole industry. I drew the obvious conclusion. My gut was good. I could see what the market wanted before the market did.
Except I didn't see it coming. In early 1988, computer viruses became front-page news. The New York Times ran it on the front of the business section, the story spread to nearly every paper in the country, and overnight every company in America decided it needed security. My product was already built and sitting on the shelf when the panic arrived. I had built a solution that needed a problem, and the people writing and spreading those viruses are the ones who handed it one. It was nothing I did. I hit the timing right, and the timing was luck.
It took an honest audit, years later, to admit that, and the same look turned up the opposite story. The other ThumbScan product was the one I was proudest of. It put fingerprint security on a personal computer, the first one under a thousand dollars you could attach to a PC. Your thumb instead of your password. The reasoning was sound and the technology worked. The market wanted none of it. PCs were barely in homes yet, biometrics sounded like science fiction, and the company bled cash and folded.
That product wasn't worse thinking than the one that won the award. It was the same thinking, aimed at an idea that turned out to be twenty-five years early. Today it sits on every phone, and hundreds of millions of people use it before breakfast. I wasn't wrong about the concept. I was wrong about the clock, and the clock runs mostly on luck. The award and the bankruptcy came out of one gut, separated only by the year each idea landed in.
What I did, years later, has a name. I ran the version of events that didn't happen, stripped the result off each decision, and looked at the call cold. That's counterfactual thinking, and it's the whole skill. It's uncomfortable, because the result already handed you a verdict and now you're reopening it. It's also the only feedback that makes you better.
Why Your Results Lie to You
None of this is your fault. It's a measurement problem. Your gut got trained on bad data, and it had no way of knowing. The more decisions you've stacked up, the more confident it's become, and confidence built on a bad stat is worse than no confidence at all. A junior person knows they're guessing. Twenty years in, the guessing feels like knowing.
Your own record is full of the same thing. Wins you credited to your own judgment when they really came down to timing, or to a competitor's mistake you had nothing to do with. Good calls you stopped making because one of them lost, even though losing was always on the table and the call was still right. None of that is carelessness. You recorded every result accurately. You just recorded the wrong thing, and then you trained on it.
The world isn't helping. Every outcome now arrives with its explanation already attached, ten confident takes by lunchtime, most written backward from the result. I covered that warning in "Hindsight Is Not 20/20."
So go back and run the audit on yourself. Rebuild what you knew on the day you decided, set the result aside, and ask whether the call still holds up without it. The hard part is doing this to wins, because taking apart a success while you're still proud of it feels like bad manners and bad luck at once. That's the reason your wins are where your worst lessons hide.
Read Your Competitors' Moves
You just watched me run this backward, over my own record. It points two other directions too. The first is sideways, at everyone else.
The same move works just as well on decisions that aren't yours. When a rival's bet pays off, the instinct is to copy it. When it craters, the instinct is to swear it off. Both stop at the result.
So rebuild their decision the way you rebuilt your own. Say a competitor ships a feature and it takes off, and three teams in your space scramble to copy it. What they miss is that the feature didn't carry the launch. It landed the week the category leader had an outage, and every angry customer went shopping. Copy that same feature into a calm market a year later and nothing happens, because you copied the move and not the moment. You're hunting for the hinge, the single thing the outcome really swung on, and it's rarely what the headlines credited.
Get this wrong and you don't copy a rival's strategy. You copy the luck that came with it, and luck doesn't travel.
Pressure-Test Your Next Decision
The other direction is forward, into a choice still in front of you, and it's where the skill pays you back the most.
Most of us pick options by their best case. You picture each road going well and take the one that goes best. Turn that around. Walk each option forward until it falls apart, because every option falls apart somewhere, and the one you can't picture breaking is just the one you haven't looked at hard enough. Pull in the alternatives you've already talked yourself out of, and count doing nothing, since that's a choice too. Then decide on the part nobody likes to look at: the downside you'd have to live with. A modest plan you can walk away from beats a brilliant one that takes you down with it.
Most decisions that seem obvious stop seeming that way once you walk the alternatives all the way out. The ones that still look right after that walk are the ones worth making.
Practice Exercise: Audit a Win You're Proud Of
This is the drill that matters most, and the one you'll want to skip. Pick a win from the last year. Not a loss. Something that worked, that you've been glad to take credit for.
Write down what you knew the day you decided. Only that, nothing you picked up afterward.

Run the version where it went the other way. How close did it come, and what would have had to break differently?

Answer straight. Good decision, or good result?

If it's hard to sit with, you're doing it right. The wins you can't bring yourself to examine honestly are the ones costing you the most.
A good decision and a lucky one keep looking identical until you do the work to tell them apart. Do that work often enough and you stop mistaking the breaks that fell your way for things you did well. Over a career, that is most of the gap between people who get reliably good and people who just had a good run.

Everyone collects weak signals now. Most of what they collect predicts nothing. A weak signal isn't a thing you spot, it's a prediction you make, and the edge goes to whoever bets on it while being wrong is still cheap.
So how do you become the one placing the bet, not the one still collecting reports? Let's get into it.
What a Weak Signal Actually Is
A weak signal is a faint piece of evidence that points to something a customer will want before they can name it, and before the market has priced it in. Faint, because if it were loud, everyone would already be acting on it. Deniable, because you can always explain it away as noise, and most people do. That deniability is the whole point. The moment it becomes undeniable, the advantage is gone and the price has moved.
Why Noticing Stopped Being the Edge
Ten years ago, noticing was hard. You needed sources, a network, time to read widely, a feel for the edges of your industry. That was the moat. It isn't anymore. Every team has a trend report and three newsletters and an AI tool surfacing emerging behaviors on a schedule. The noticing got automated. What didn't get automated is the judgment about which signal predicts a structural change and which points to nothing real, and the nerve to act early.
Inside Roche's Innovation Board
I sat on Roche's diagnostics innovation board, the only outsider in the room, helping decide which ideas got funded. At one point we took on diabetes care.
I am not diabetic. So I had Roche ship me every meter and test strip they made, and I pricked my finger up to a dozen times a day to feel what their customers felt. You cannot innovate for a customer whose day you have never lived. Skip that, and everything after is a guess.
Roche was a leader in blood glucose testing with its Accu-Chek meters, and the math looked obvious. Someone with type 1 diabetes tests around eight times a day, every day, for life. A big, stable business. Type 2 was the smaller story per patient. Those patients tested once, maybe twice a day, so each one looked worth less, and we filed the category under "less interesting." We could already see type 2 climbing. We weighed it against the per-patient math and explained it away.
Then type 2 diagnoses exploded into one of the fastest-growing chronic conditions in the world. And the category stopped being about counting tests per day at all, because monitoring went continuous, the always-on sensors people wear today. We had seen the early edge of both shifts. We even predicted them. We just didn't move fast enough, and the reason is the one that kills most weak signals inside a big company. Project approval and annual budgets are built to fund what's already proven, not to chase something still faint.
Roche got there. Accu-Chek SmartGuide, its real-time continuous monitor, is on the market now. I just wish we had moved the moment we saw it, instead of waiting for the next budget cycle to make it safe.
How to Read a Weak Signal
We didn't miss the type 2 signal for lack of noticing. We noticed. We missed it on the three things that come after, and those you can train. The moves start once you've got a signal you can't quite dismiss, and the skill is what you do with it.
Tell the Canary From the Costume
A canary in a coal mine matters because the air changed. It signals something structural, a shift in the environment that affects everyone in it, whether they've noticed yet or not. A costume is the opposite. A few people put it on, it's striking, it spreads for a season, then they take it off and the room is exactly as it was. On day one the two look identical. A behavior appears, it's unusual, it's spreading. The only question that matters is whether it predicts a change a customer can't reverse, or a moment that will pass.
Back in 2018 I wrote about telling a trend from a fad, and the test still holds: ask what need the behavior reveals. Type 2 was a canary, and we read it as a costume, because we counted testing frequency instead of the need underneath it. That need, millions of people learning to manage a lifestyle disease, only grew.
The discipline is refusing to let the size of the spike tell you which one you're looking at. Costumes spike too, sometimes higher. You're reading for the need, not the noise.
Read the Window
A signal's window is short. Too early, you can't tell it from noise and you waste resources chasing ghosts. Too late, it's obvious, everyone sees it, and the advantage is already priced in. The value lives in the narrow gap between. Waiting for more evidence feels like better judgment, but the evidence that finally convinces you has already reached your competitors. Certainty and advantage move in opposite directions, so by the time you're sure, sure is just another word for too late. The question isn't whether the signal is real yet. It's how much longer you can be the only one taking it seriously.
Act While Being Wrong Is Cheap
This is the move that separates the people who read signals from the people who collect them, and almost nobody is willing to make it. A signal you predict but never act on is still just watching. Ideas without execution are a hobby, and I'm not in the hobby business.
The whole value of an early signal is that you move before it's confirmed. Wait for proof and you've waited too long. So you act on thin evidence. And thin evidence is wrong a lot, which means you will be wrong a lot. People hear that and freeze, because they picture the cost of being wrong as the failed product, the wasted year, the budget burned on a guess.
People call that caution. It isn't. The skill is structuring the bet so that being wrong is cheap. You don't commit a product line to a deniable signal. You commit a prototype. A landing page. One conversation with ten customers. A two-week test that costs you a sprint and buys you information you can't get any other way. Being early and wrong should cost you a week. Being early and right should put you a year ahead.
You're not betting on being right. You're buying the option to be right, cheap enough that being wrong doesn't hurt, and you scale up only as the signal firms up.
That's why the noticing crowd never gets here. Noticing carries no risk, so it never builds the muscle for cheap commitment. They watch, they report, they wait for certainty, and they call it foresight. It's the safe choice, and it's worth nothing.
Practice Exercise: Run a Signal Through All Three
Pick one behavior you've been dismissing as noise. Something you've seen more than once, in your customers, your kids, your own habits, that you waved off because it looked too small or too strange to matter. Then run it through the three moves.
Canary or costume. What need does the behavior reveal? A need the person can't go back from, or a novelty they'll set down in a season? Write the answer in one sentence. If you can't, you don't understand the signal yet.

Find the window. How much longer does this stay deniable? Who else is likely seeing it? If the honest answer is "it already feels obvious," pick a different signal. You're late on this one.

Design the cheap bet. What's the smallest thing you could do this month to test whether you're right, where being wrong costs a week and being right puts you ahead? Name the bet. Name the cost. Name what you'd learn.

Do this with one real signal and you'll feel the difference between collecting signals and using them. Collecting is comfortable. Using one costs you a decision.
If you want a sparring partner for that, I built one. From Signal to Bet is a set of AI prompts that run a signal through these same three moves and argue with your read at each one. It's free at innovation.tools. The exercise teaches you the moves. The prompts make you defend them.
The signal was always there, for you and for everyone reading the same reports you read. The edge was never in seeing it. It was in what you were willing to do before it was safe to do anything at all. Get good at that, and you stop reacting to the future and start arriving early.

In 2000, Toys R Us paid Amazon $50 million a year to sell their toys online. It looked like a great deal. The company that defined toy retail for two generations was solving the internet problem in one move.
Four years later they were suing each other. Seventeen years later Toys R Us was gone. Every store closed. Every job lost. And every step of what happened was visible from the day the deal was signed. Nobody at Toys R Us saw it.
What Is Second-Order Thinking?
First-order thinking asks what happens next. Second-order thinking asks what happens to the people who see what happened next.
The skill isn't caution. It's the willingness to keep looking after the room has stopped.
Inside HP, 2006
In 2005, HP launched Halo, a premium telepresence system co-developed with DreamWorks. For a brief period it reported into my organization. The next year, Cisco launched TelePresence and went straight at us. I called the HP team closest to Cisco and asked what they made of it. The answer was reassuring: Cisco is aiming down-market, we're fine. We were premium; they were chasing volume.
That answer satisfied the room. It did not satisfy me. The room was asking "will Cisco hurt Halo?" That was the wrong question. The right one was sitting underneath: why did our partner of twenty years decide to do this without us?
Nobody had an answer to that one. The HP team didn't think it was the question. They were focused on the product collision, and I kept coming back to the partnership. A company that had cooperated with us for two decades had just decided they didn't need to anymore. The product was the surface. The relationship had quietly ended, and we were the only ones who hadn't noticed.
Three years later, Cisco launched a direct attack on HP's core server business with Unified Computing System. HP responded by acquiring 3Com and going after Cisco's core networking business. A twenty-year alliance ended in under two years. Neither side ran the second-order analysis at any point along the way. By the time the right question got asked, the partnership was already gone.
The Three Skills
These three skills stand on their own. Each one solves a different problem most decision frameworks miss. The first picks up signals before there's even a decision to analyze. The second uncovers what's actually driving the other party's timing. The third shows you what people will do once they see your decision land. If you've watched the November 2025 episode on the basics of second-order thinking, these skills add to that foundation. If you haven't, you can still apply all three starting today.
Sense the Weak Signal, Not the Loud Event
Most failures don't announce themselves. The loud event, the launch, the lawsuit, the lost customer, is usually the visible end of something that started much earlier as a quiet shift somebody noticed and explained away.
A weak signal is a small piece of information that doesn't fit the story you're already telling. A customer's casual comment that contradicts your data. A team member's evasive answer in a status meeting. A supplier missing a deadline they've never missed before. The reflex is to make it fit the story you already believe. The skill is to refuse.
Go looking before you have one. Once a week, scan three places where weak signals live. Customer-facing teams. Data points that surprised you and got brushed off. Topics that smart people you respect are paying attention to, but you aren't. You're not looking for problems. You're looking for things that don't quite fit.

Name the thing that doesn't fit. Be specific. "Their CFO made a comment about the budget that didn't match what we were told last quarter." Not "something feels off." The more specific the signal, the more useful it becomes.

List the stories that would make the signal make sense. At least three. Force yourself to consider explanations that don't fit your current assumptions.

Ask which of those stories you'd act on if it were true. If one of them would change a decision you're about to make, that's the signal you can't afford to ignore.

Find one more data point before you decide. A single signal can mislead. Two signals pointing the same direction is usually real.

The Cisco TelePresence launch was a weak signal about the partnership. The team read the product. I read the relationship. Neither of us pushed it far enough.
Ask "Why Now" Before "What's Next"
Most people jump straight to the future: what will the other party do next? That's the wrong starting question. Ask why now first. Why is this happening now, when it could have happened a year ago? The timing tells you what changed in their world, and that change tells you what they're likely to do next, often more reliably than asking the question directly.
 
State the move that just happened. A competitor launched a product. A regulator opened an inquiry. A customer asked for a discount. Name it plainly.

Ask what changed. What was true a year ago that isn't true now? What can they do today that they couldn't do then? Their capability, their pressure, their read of you, their read of the market. Identify the shift.

Use the change to predict their next move. What's the natural follow-on from the thing that made this move possible? That's usually where the real consequence lives.

 
Cisco didn't enter telepresence in 2006 because telepresence was suddenly interesting. They entered because they'd decided the partnership with HP no longer constrained them. "Why now" would have surfaced that. "What's next" wouldn't have caught it in time.
Watch the Response, Not the Result
Your decision produces a result. The result triggers a response from everyone watching, your competitors, your customers, your team, your investors. Most analysis stops at the result. The response is where the actual consequence lives.
 
Toys R Us could have predicted that Amazon would sell more toys. That was the result. What they didn't predict was Amazon's response: opening the platform to third-party sellers, learning the toy business, and using the data to compete directly. By the time Toys R Us understood the response, Amazon had already replaced them.
State the immediate result of your decision in one sentence. What will be visibly different in the world after you act?

List who can see that result. Be specific. Name people if you can, not categories.

For each one, ask: what does the result tell them about you? Your priorities, your weaknesses, your appetite. The result is information about you they didn't have before.

Ask what they're now in a position to do that they weren't before. The result changes what's available to the other actors, not just the market.

Identify the responses you can't undo. A customer who loses trust. A competitor that smells weakness. A regulator who opens a file. Those are the ones to model carefully.

HP launching Halo was the result. Cisco entering TelePresence was the response. By the time anyone at HP said the word "over," the partnership had been over for three years.
Practice Exercise: Run All Three on One Decision
Pick one decision you're currently working through. Run the three skills against it in sequence.
Weak signal. What have you noticed in the last 90 days connected to this decision that doesn't quite fit your current story? Don't explain it away. Name it.

Why now. What changed in the world recently that's making this decision feel urgent now? Was that change visible six months ago?

Watch the response. Who will see the result of this decision, and what does it tell them about you that they didn't know before?

The first time you run this, you'll miss things. That's normal. The skills sharpen with repetition. The fifth time you sit down with a real decision and work through all three, you'll catch signals that other people in the room aren't even seeing yet. That's what improvement looks like.
If any of the three turns up something the room hasn't discussed, you've found the work that needs to happen before the decision is made. Take what you found and run it through the two skills from the November 2025 episode. Map how people will respond. Ask "and then what?" two or three more times. All five skills work as one system. The link to the November episode is in the description below.
Most second-order failures do not arrive as surprises. They arrive as something somebody noticed once, didn't have a way to act on, and explained away.