Implicit Premise Thinker

Her unspoken premise is that stable vitals at one snapshot equals safe trajectory over the next 24–48 hours — a conflation of a static reading with a dynamic recovery curve. Post-op patients don't decline linearly; they often deteriorate in a window (e.g., 6–18 hours post-surgery) when edema peaks, pain masks perfusion, or early bleeding hasn't yet shown as hypotension. Stable vitals now only tells you she's stable now, not that the risk curve has flattened.

The second buried assumption: the surgeon's bed demand is a legitimate clinical signal. It isn't — it's a resource constraint dressed as urgency. Her logic runs: "Vitals stable + bed needed → discharge is safe." The omitted premise is "recovery risk is evenly distributed across time," which is false. The third: staffing levels can absorb a post-op readmission. That assumes the floor has capacity to catch a late complication, which you know isn't guaranteed on a short-staffed shift.

To articulate your pushback, name the premise out loud: "You're assuming stable now means stable for the next 12 hours. What's our plan if she spikes a fever at 2 a.m. with two nurses on the floor?" That forces the real question — not "is she stable?" but "can we manage her risk trajectory where she's going?" Your instinct wasn't vague; it was detecting that the conclusion rested on an unspoken time horizon that nobody had agreed to.

The hidden leap: "We lost on price alone"

Your co-founder's reaction rests on one unstated premise: the client left because we were more expensive. That is a conclusion, not a fact. Before you slash prices, force the assumption into the open and test it.

Dig for the real "why"

• Ask the client directly. One honest exit interview beats a hundred guesses. Was it price, or was it switching costs, service response time, a feature gap, or a relationship breakdown with a single account manager?
• Check the sequence. Did the cheaper competitor actually undercut you, or did they win on a bundled offer, a longer contract, or a promise your client believed but you never made?
• Separate price from value. A client pays for outcomes, not numbers. If you lost on perceived value, cutting price just devalues what you sell without fixing the gap.

The trap to avoid

Slashing prices across the board assumes all clients are price-sensitive and all losses are price-driven. That's a generalization from one data point. You might be about to train your whole market that you're the cheap option — a position that's hard to escape.

Action: Before any pricing change, run one interview, review the lost deal's full history, and ask: What premise, if false, makes this reaction look foolish? Almost always, it's the assumption that price was the deciding factor.

Your instinct is correct — the colleague's argument rests on an enthymeme, an omitted premise that must be dragged into the light. The unspoken assumption is: aggregate test scores are a direct and sufficient proxy for teaching effectiveness. That premise smuggles in several sub-assumptions you can name aloud.

First, it assumes the student population is comparable — that your school isn't serving more affluent, better-resourced families than the district average, which would make the score gap a function of demographics, not pedagogy. Second, it assumes the test itself measures what you teach, not just test-taking stamina or prior knowledge. Third, it assumes no selection effect — that high scores aren't driven by attrition, tracking, or parents who tutor heavily at home.

To challenge it, don't attack the conclusion; attack the bridge. Ask: "What would need to be true about our students, our curriculum, and our test for that link to hold? Could our scores be high despite our methods?" That forces the colleague to either defend the premise or concede the argument collapses. You're not saying teaching is ineffective — you're saying the evidence cited doesn't prove it is effective. Shift the burden of proof to the premise, not the conclusion.