Executives rarely lack intelligence or experience. What often derails decisions is the quiet drift toward comfortable reasoning, the kind that fits neatly into slides and satisfies everyone’s appetite for momentum. The pattern shows up in boardrooms and offsites: a quick nod to data, a confident read of risk, then a decisive move that, months later, needs rework or quiet reversal. The opportunity is not to think harder, but to think differently. That is the premise of (un)Common Logic.
(un)Common Logic is the discipline of questioning the intuitions that most leaders find obvious, then replacing them with reasoning patterns that are simple, robust, and transferable under pressure. It is not academic logic or an exotic framework. It is the craft of using simple tools and unglamorous habits to reach sounder, faster choices in contexts where stakes are real and time is short.
What (un)Common Logic Means in Practice
“Common logic” in a company is the tacit playbook: market leaders won’t drop price, competitors won’t cooperate, the next product must be a platform, customers want more features, the plant is at capacity, sales will trend up after the trade show. These beliefs reduce friction and let people move. They also age poorly. The market leader did drop price during a quarter-end push, the competitor did partner with a startup, your customers wanted fewer options not more, and the plant’s constraint was a single piece of test equipment you had never audited.
The “un” in (un)Common Logic is a prompt to unsettle that playbook, then rebuild it on fresh observations, explicit assumptions, and lightweight experiments. It favors base rates before narratives, disconfirming evidence before cheerleading, reversible moves before irreversible bets, and simple guardrails before sprawling governance. It is unflashy. It is repeatable. And once you institutionalize it, your teams waste less time and defend fewer mistakes.
A Personal Note on Learning It the Hard Way
As a divisional GM, I once pushed a pricing change that looked brilliant in the model and clean in the deck. We raised list price by 3 percent, shrank discount bands, and promised neutral net revenue after mix. The pilot market hit the numbers. We rolled it out systemwide. Then freight costs rose, the mix shifted toward a lower-margin SKU, and customer churn spiked in two midwestern regions where a smaller competitor sensed blood. Net, we gave up roughly 120 basis points of contribution margin over two quarters. No one had asked two now-obvious questions: what are the base rates for churn after price actions in our segment, and which moves are reversible without signaling panic?
We eventually corrected, but it took nine months. That episode taught me to treat elegant models with suspicion, to hunt for friction in the field before declaring victory, and to keep reversal plans ready when a decision is one-way only in your head.
The Building Blocks: Simple, Non-Negotiable Habits
Executives often ask for a single framework that solves decision quality. There is no single framework. There are a handful of habits that, used consistently, lift the floor on choices. You can explain them without a whiteboard, and you can expect them of every director and VP.
- Start with base rates. Before accepting a forecast, ask what tends to happen in similar cases. If you are launching a new B2B SaaS module, look at median adoption rates for adjacent modules over the last three launches. If you cannot find external data, use internal cohorts. Base rates are the fence that keeps heroic stories from running wild. Seek disconfirming evidence. Assign a peer to make the strongest case for why the plan will not work. Do not run a perfunctory “risks” slide. Require concrete counterexamples, real constraints, and early indicators of failure. Prefer reversible moves. When uncertainty is high, structure the decision into a series of options that you can unwind with minimal cost. If a marketing shift may confuse your existing clients, A/B test in two regions with a clear holdout group and a calendar for rollback. Price uncertainty explicitly. Add a range, not a single number. Translate that range into cash outcomes that matter. People behave differently when they see that a 15 percent miss on adoption implies a 4 million dollar cash gap in Q4.
These habits do not slow the business if you teach managers to use them instinctively. After two or three cycles, you will notice shorter debates and tighter memos. People will anticipate the questions and come prepared with what matters.
The Meeting Where Decisions Go Wrong
Most strategic mistakes do not come from a lack of intelligence. They come from a sequence of small shortcuts in a room. I keep a mental film reel of the moments to watch for:
The sponsor starts with a definitive recommendation and a polished narrative arc. Slide three gives the market opportunity, slide four the customer pain, slide five the unit economics. No one wants to be the person who unravels a neat story. Then the CFO, trying to be a good partner, offers tweaks rather than a reset. Functional heads negotiate execution details. The CEO asks two clarifying questions, signals approval, and asks for follow-up on a minor risk. The deal goes through, and the one critical uncertainty remains barely tested.
In these rooms, (un)Common Logic serves as choreography. You agree that every material decision will be expressed in a succinct brief that names the core bet, lists key assumptions with their base rates, describes a small test or proxy that reduces the largest uncertainty, and maps the reversal plan if the first signal goes against you. The ritual matters. The team learns that the point is not to defend a fully formed plan, but to narrow uncertainty quickly and cleanly.
Numbers That Keep You Honest
Executives, unlike analysts, cannot live in the comfort of models. But a few numeric disciplines change the quality of choices.
Start with calibration. Ask your team to express forecasts as ranges with a confidence level. If a leader says, “I am 80 percent confident we will reach 50,000 active users by month six,” note it. After a quarter, score calibration. If their 80 percent confidence ranges hit only half the time, they are overconfident. You do not need to shame anyone. You need to start tuning the organization’s sense of uncertainty. In my experience, after two or three cycles of calibration feedback, forecasts become more realistic and the need for high-friction “alignment meetings” drops.
Add base rate overlays. When a product manager claims a 30 percent first-year adoption among existing customers for an add-on module, ask for the benchmarks. If you lack external data, look at three internal analogs. Maybe your last two add-ons reached 12 to 18 percent in the first year with heavy promotion. If this one is projected at 30 percent, the difference needs a specific, testable reason. “Better product” does not count. “One-click integration that removes a prior onboarding step worth 45 minutes for the average admin” is at least a candidate.
Use sensitivity over precision. If a plan lives or dies by two assumptions, show how the outcome moves when those levers change within realistic ranges. I worked with a consumer hardware company that modeled demand with precision to the second decimal place, yet a single assumption about retail demo staffing drove half the variance. We flipped the reviews to focus on the two levers, built a fast read on staffing conversion in three stores, and cut a month from the decision timeline.
Finally, force translation from tables to cash. Executives respond to cash more than to percentage points. Show how a distribution agreement that “adds 2 percent net margin” actually improves free cash by 6 to 8 million in the first year because it smooths inventory turns and trims working capital. Or show how a two-week slip in a regulatory approval tightens cash headroom below covenant thresholds in Q3. Cash has a way of making the debate concrete.
Case Notes: Where (un)Common Logic Paid Off
A pricing reset in industrial services. A regional services business saw stagnant growth and margin compression. The team argued for a uniform 4 percent price increase to offset wage inflation. Base rate analysis of prior increases showed a 1 to 2 percent churn spike in the quarter after price actions, concentrated among smaller accounts that often returned within six months at slightly lower volume. We ran a targeted approach instead: no price change for the top 20 percent of accounts by revenue, a 6 percent increase for long-tail accounts where service density was low, and a pilot of value-tier packaging in two cities with aggressive competitor presence. Net result over half a year: a 90 bps margin expansion with churn within historic bounds, and a clearer picture of which accounts were truly price sensitive.
A portfolio rethink after an M&A spree. A mid-cap tech company had acquired three firms in four years. The integration plan was heavy on synergies, light on customer migration friction. In the first joint QBR, we forced a simple matrix: customer pain points on one axis, time to marginal dollar on the other. Instead of debating platform unification in abstract, we mapped 14 specific moves and prioritized the six that freed up sales capacity or reduced onboarding time in less than two quarters. The team delayed a unification project that would have tied up 120 engineers for a year, without measurable impact on revenue retention. This bought the company 20 million in additional free cash within 12 months and kept optionality for a later unification when the product fit was clearer.
A hiring freeze that was not lazy austerity. A fast-growing marketplace felt it had to hire 100 more support agents as transactions rose. We pulled three weeks of call logs, sampled 600 tickets, and found that 35 percent were triggered by one ambiguous checkout screen and a bug in a mobile flow. A narrow redesign and a patch dropped ticket volume 28 percent in a month. Hiring slowed to a trickle. No heroics, just the discipline of tracing the base rate of ticket triggers and fixing the root cause first.
Culture: Rituals That Stick When You Are Busy
Cultures do not change because you asked for better thinking. They change because you altered what gets reviewed, who gets promoted, and which meetings feel different.
Start with the memo. Require a short decision brief for material choices, two pages or less, with a consistent backbone: the decision at hand, the base rates that frame it, the one largest uncertainty and how you will cut it in half within four weeks, the reversal plan, and the first true measure of success that cannot be gamed. When leaders know you will ask for these, they prep differently, and the signal improves.
Create a forum for disconfirming evidence. I have seen success when a rotating triad of VPs serves as the “red team” for monthly reviews. Their only job is to ask what would have to be true for the plan to fail, and whether an early indicator could be observed cheaply. They are not trying to win an argument. They are trying to prevent the organization from walking past a cliff in fog.
Reward reversible experiments. Publicize small wins where a team tried a low-cost test that invalidated a favorite idea before it became a large, rigid program. People imitate what gets praised. If every celebrated story is about bold, irreversible bets, you will get more of those, whether or not your context supports them.
Finally, close the loop. Keep a compact decision log for the top dozen choices each quarter. Note the assumptions, the initial read, and the actual outcome three months later. Pattern recognition is the driver of better judgment. Without a log, you reinvent lessons while convincing yourself you are learning.
The Operating Cadence
Executives manage in rhythms. The weekly staff meeting pushes on execution, the monthly business review asks whether the train is on the rails, the quarterly board meeting becomes a scorecard and a sales pitch. (un)Common Logic fits into this cadence without adding ceremony.
At the weekly level, ask for early signals on the most uncertain bets. The point is not to run the entire dashboard. It is to reduce the largest unknowns fast. If procurement savings are the critical piece of a margin plan, you want to know if cycle times for vendor negotiations are slipping. If a product initiative hangs on engagement among a specific segment, you want the exact activation rate by cohort and the change after last week’s content tweak.
At the monthly level, reserve 30 minutes for a deep dive on one decision in progress. This is not a performance trial. It is a craft review. Ask the team to walk through their assumptions, the base rates they used, the counterevidence they sought, and the experiment or proxy that gave them more signal. Over a quarter, you will have reinforced the habits across multiple teams.
At the quarterly level, mark the top three bets you made and score them. Not with vanity metrics, but with honest readings against the original assumptions. Teams often discover that they are grading themselves on changed goals. That is not inherently bad, but it hides learning. Keep both sets: what you thought you would achieve, and what now defines success, with a note explaining the delta.
A Short Diagnostic You Can Use Tomorrow
- Name the decision. If it takes more than two sentences, you are not ready to decide. Write the three biggest assumptions. Assign a base rate to each with a source. Identify the cheapest test or proxy that cuts the riskiest assumption in half within 30 days. Draft the reversal plan and its tripwire. If the key indicator dips below X by date Y, what do you stop, and what do customers see?
This takes under an hour when done well. It saves months when the bet is large.
Communicating With the Board and the Street
Boards and investors read for signal. They want to know whether you know what you are doing, whether uncertainty is contained, and whether you will respond if the world shifts. You do not need to perform certainty. You need to perform competence.
Avoid the trap of over-optimistic narratives. Provide a clean structure. What is the core bet, what are the base rates, what are the early reads, what is the fallback if those reads go south, and how will cash be protected. If your story includes a bold move, pair it with a modest move that limits downside. A board that sees you have already planned the exit from a dead-end initiative is more likely to support the entry.
One practical note: show how you will know if you are right before the P&L knows. If your new channel should feed 15 percent of pipeline by Q3, the leading signal could be the time from partner enablement to first qualified lead, or the rate of partner-led demos in two anchor regions. Make it concrete. You will get sharper questions, which is a gift.
Edge Cases and Judgment Calls
Some contexts test any framework. Regulated industries move on their own timetables. Founder-led firms value speed and instinct over formal process. Turnarounds demand focus on cash above all else. (un)Common Logic flexes, but the core habits remain useful.
In regulated markets, reversible moves might be slower, but you can still identify the cheapest proxies. If you cannot test direct consumer uptake of a telehealth feature, test provider willingness in a controlled cohort, or patient no-show rates with a scheduling change. If approvals are binary and slow, build scenario plans pegged to factual milestones rather than dates. Investors will forgive slippage when they see clarity of contingency.
In founder-driven companies, lean into rituals not rules. Replace heavy templates with a one-page discipline. The founder wants speed. Offer speed with fewer blind spots. If you can run a 10 day market validation that costs 20,000 dollars and reduces the main uncertainty by half, you will earn the founder’s trust without boxing them in.
In turnarounds, cash and customer retention trump elegance. Shorten horizons. Your decision log becomes daily triage. The habit of identifying the riskiest assumption and attacking it first still pays off. If the assumption is that vendors will accept extended terms, call the top five vendors today, not next week. If the assumption is that core customers will tolerate a service cutback, talk to ten of them before you cut.
The Human Side: Status, Fear, and Incentives
Every logic framework interacts with human needs. People seek status, avoid blame, and prefer familiar puzzles. That is not cynicism, it is recognition. You design the environment accordingly.
Status accrues to those who bring clarity, not volume. Publicly recognize leaders who surface disconfirming evidence that improves a decision. Tie promotions, in part, to demonstrated judgment under uncertainty. When people see that careers flourish on decision quality rather than project size alone, they will volunteer better thinking.
Fear blocks candor. If your culture punishes missed targets harshly, you will get sugarcoated forecasts and late confessions. Build a distinction between bad outcomes from good bets and sloppy decisions. You can be strict on the latter while tolerant of the former. Over time, people will bring you problems early, which is the only moment you can still fix them.
Incentives often snare logic. A sales leader paid on top-line won’t be the loudest voice for margin preservation during a promotional push. This is not moral failure. It is predictably human. Align incentives where you can. Where you cannot, design the decision forum to offset them. In pricing https://69d863744051f.site123.me/ reviews, include the finance partner empowered to veto discounts that damage lifetime value, and give them cover to use it.
When to Trust Your Gut
Executives carry decades of pattern recognition. Intuition is an asset, not an enemy. The error is trusting it where the environment has changed or where you have thin exposure. I use a simple gut check. Ask yourself: have I seen this movie, personally, end to end, in a context that matches at least 70 percent of today’s variables. If yes, your gut likely has signal. If no, force a fast test or bring in someone who has the scar tissue.
One CEO I worked with had uncanny instinct for enterprise sales cycles in North America, built over twenty years. He faltered when the company expanded into Asia with a channel-led model. His gut shouted for shorter cycles and simpler pricing. The team overrode him with data, and they were right. He and I later built a habit: where his experience matched the context, the team moved faster on his read. Where it did not, he required a minimum viable experiment before greenlighting any large bet.
A Quarterly Self-Review for Leaders
- Which three decisions did I slow down for signal, and did the extra time change the outcome. Where did I ignore base rates, and did luck save me. Who on my team consistently brings disconfirming evidence without drama, and how am I rewarding them. Which bet is currently one-way in my head, and how can I make it two-way for 30 days.
Keep these questions on a notecard. Fifteen minutes of honest reflection each quarter is worth far more than another framework.
The Payoff
The gains from (un)Common Logic arrive quietly. Fewer backtracks. Smaller postmortems. Shorter meetings. Leaders who bring leaner, clearer briefs. Teams that run low-cost tests rather than fight turf wars built on slides. The impact shows up in the numbers too, though not in a single line item. You will see variance narrow between plan and actual, forecast accuracy improve by a few points, cash cushions hold when noise hits, and employee engagement rise in groups where autonomy matches accountability.
None of this depends on heroics. It depends on a set of practical commitments. Start with base rates. Hunt for counterevidence. Prefer reversible moves. Price uncertainty. Build rituals that make those habits the path of least resistance. Over time the “un” in (un)Common Logic fades, because it becomes your new normal. That is when you know the work has taken hold.