Tag: technology

[Power and Prediction] Chapter 3: AI Is Prediction Technology

~ pdawg ~ Leave a comment

Strip away the hype and the current wave of AI does one thing: it predicts. Chapter 3 is a reset on what that actually means and why it matters economically.

Prediction is filling in missing information. The authors define prediction as the process of taking information you have and using it to generate information you need but don’t have. A bank has a record of millions of past transactions and whether each turned out to be fraudulent. It does not have the answer for the transaction happening right now. Prediction bridges that gap. The same logic covers medical diagnosis (symptoms in, likely condition out), translation (a sentence in one language in, its counterpart out), and driving (what the sensors see in, what the car should do next out). What looks like a dozen different capabilities is one capability pointed in different directions.

Cheap prediction means more prediction. This is where the economics comes in. Prediction is an input to decision-making, and the recent advances in AI have made that input dramatically cheaper. When the cost of an input falls, we use more of it, and we start using it in places where it was previously too expensive to bother. Nobody used to “predict” what a sentence in Mandarin meant; they hired a translator or did without. Now prediction is cheap enough to deploy on every email and menu. The authors’ earlier book, Prediction Machines, was built on this one idea, and it still holds: as prediction gets cheaper, AI will spread.

Substitutes fall, complements rise. The second economic consequence is about what happens around prediction. When something gets cheaper, the things that do the same job become less valuable, and the things that pair with it become more valuable. The main substitute for machine prediction is human prediction, so the value of a person whose job is mostly forecasting, classifying, or estimating will decline. The main complements are two: data and judgment. Data is what the machines learn from, so organizations that have it, or can collect it, are sitting on an appreciating asset. Judgment is what you combine with a prediction to actually decide something.

Prediction is likelihood; judgment is desire. This distinction is the heart of the chapter. A prediction tells you how likely each outcome is. Judgment tells you how much you care about each outcome. Every decision is the two together: you weigh what might happen against what you want to happen. The machine can tell you there is a 3 percent chance this transaction is fraudulent. It cannot tell you whether blocking a legitimate customer is worse than letting a fraudulent one through, or by how much. That’s a question of values, trade-offs, and context, and it stays with humans. As prediction becomes abundant, the scarce and valuable skill is knowing what you want.

Correlation is not causation, and AI doesn’t know the difference. The authors flag what may be the most common misuse of AI predictions: treating the patterns a model finds as if they explain anything. Models find correlations. For many purposes that’s enough; if the goal is to guess which customers will churn, you don’t need to know why. But if you want to act on the world, to change the thing rather than predict it, correlation can lead you badly astray. A model might learn that customers who call support are more likely to leave, but that doesn’t mean cutting the support line will keep them. When the question is causal, the right tool is not a bigger model but a randomized experiment, which remains the most reliable method statisticians have for discovering what causes what. Good AI practice involves knowing which kind of question you’re asking.

The Amazon thought experiment, revisited. In Prediction Machines, the authors ran a thought experiment about Amazon’s recommendation engine. Imagine it getting steadily more accurate. At first, the effect is modest: better recommendations, slightly more sales. But keep turning the dial and at some point a different question becomes possible: if we’re this good at predicting what people want, why wait for them to order it? Just ship it. Shopping would flip from “order, then ship” to “ship, then keep or return.”

Amazon did file a patent on something like this, which the authors call anticipatory shipping. It has not adopted the model. Chapter 3 asks why, and the answer is the book’s thesis in miniature. Better recommendations on the existing platform are a point solution; they ride on the Amazon system exactly as it is. Shipping before ordering would be a system solution, and the system it would strain most is returns. Amazon’s returns process is so costly that in many cases it’s cheaper to discard a returned item than to restock it. A business model built on sending people things they didn’t ask for, and taking back a meaningful fraction of them, would collapse under that cost structure. To make it work, Amazon would have to redesign logistics, returns handling, inventory, and pricing all at once.

The authors are candid that this is what they got wrong the first time. The threshold in their thought experiment wasn’t a matter of accuracy crossing some number. It was the point where capturing the value of the prediction required leaving the point solution behind and rebuilding the system around it. Prediction Machines saw the dial; Power and Prediction is about what’s on the other side of it.

[Power and Prediction] Chapter 2: The Between Times

~ pdawg ~ Leave a comment

If AI is so good at prediction, where are the results? That’s the uncomfortable question Chapter 2 opens with. Over the past decade, measured productivity growth has fallen by roughly half, and for a majority of Americans real income has barely moved since the late 1990s. Machines can now read X-rays, translate languages, and drive cars, yet the aggregate numbers look like nothing much is happening.

The authors are quick to point out that this productivity paradox is not new. In the 1980s, computers were spreading through every office while the productivity statistics stayed flat, prompting economist Robert Solow’s famous observation that the computer age was visible everywhere except in the numbers. The gains arrived eventually, but only after businesses stopped using computers to speed up old processes and started redesigning the processes themselves.

The book gives this stretch a name: the Between Times. It’s the period after we’ve seen what a technology can do and before it has been widely adopted in ways that change how things actually work. We are in AI’s Between Times now. Point solutions and application solutions can be designed and deployed quickly, which is why we see so many of them. System solutions, the ones that will unlock AI’s real potential, take far longer.

Three kinds of solutions, and what actually separates them. The book’s distinction between point, application, and system solutions is the spine of the whole argument, so it’s worth making it concrete.

A point solution takes a decision your organization already makes and makes it better, without touching anything else. The decision was there before the AI arrived; the AI just improves the prediction feeding it. A bank already decides which transactions to flag as fraud; swap the old rules engine for a machine-learning model and you catch more fraud with fewer false alarms. A retailer already forecasts demand; replace the analyst’s spreadsheet with a model and the forecast gets sharper. Nothing downstream has to change. Same people, same workflow, same approvals, just a better input. This is the AI equivalent of bolting an electric motor onto the old central shaft.

An application solution uses prediction to create a decision that didn’t exist before, but still slots into the system as it stands. Nobody at a record label used to decide, song by song, what each listener should hear next. Streaming recommendations made that a decision, and a valuable one. A thermostat that learns when you’re home and adjusts itself is making a decision no human was making. These are new capabilities, not upgrades, but they’re self-contained. You can add them to the existing business without rethinking how the rest of it operates. This is the individual electric drive on each machine: new and useful, but the factory is still built the old way.

A system solution is what happens when a better prediction changes what everyone else should be doing. Consider a hospital that deploys an AI to predict which emergency patients will deteriorate. As a point solution, it’s a flag on a screen that a nurse may or may not act on. But if the prediction is reliable, the right response is to change how triage works, how beds are allocated, how staff are scheduled, and which patients get admitted at all. The value of the prediction isn’t in the flag; it’s in the reorganized hospital. Or consider retail: if you can predict demand well enough, you might ship products toward customers before they order, which upends inventory, logistics, returns, and pricing all at once. The prediction is the trigger, but the payoff lives in everything that has to be rebuilt around it. This is the single-story factory designed around the flow of work.

The test is independence. The authors boil the distinction down to one question: does the value of the improved decision stand on its own, or does it depend on other decisions changing too? A useful way to check is to imagine switching the AI off. If the only thing that happens is that one decision gets a bit worse, you have a point or application solution. If switching it off would break a whole set of processes that were redesigned to rely on it, you have a system solution. Independence is what makes the first two fast to deploy; interdependence is what makes the third slow, and what makes it valuable.

Why system solutions are hard, and why they matter. Point and application solutions tend to reinforce the existing system. They’re welcome because they don’t threaten anyone; they make the current way of working run a little better. System solutions, by definition, upend it. One better prediction changes what the next person should do, which changes what the person after them should do, and so on down the line. That means new workflows, new roles, new organizational structures, and resistance from everyone invested in the old arrangement.

Yet in many cases, system solutions are where the greatest returns on AI investment will be found, just as redesigned factories, not cheaper motors, were where electricity finally paid off. And because they restructure how industries operate rather than just how a single task gets done, system solutions will create winners and losers. The firms that figure out the new system first won’t just be more efficient; they’ll change the terms of competition for everyone else.

The Between Times, in other words, are not a sign that AI has failed to deliver. They’re the gap between seeing the technology and rebuilding around it, and the rest of the book is a guide to closing that gap.

[Power and Prediction] Chapter 1: Three Entrepreneurs and a Technology

~ pdawg ~ Leave a comment

Power and Prediction opens not with artificial intelligence but with electricity, and with a parable. Picture three entrepreneurs in the decades around 1900 — the stretch from the 1880s to the 1920s when factories were moving from steam power to electric power. All three have access to the same technology. What separates them is what they decide to do with it.

The first sees a point solution. Electricity is cheaper than steam and loses less energy to friction, so the obvious move is to swap the power source and leave everything else alone. The factory keeps its central shaft, its belts and pulleys, its layout. Nothing about how the plant works changes; it simply runs a little cheaper.

The second sees an application solution. Instead of one big motor driving a central shaft, why not put an individual electric drive on each machine? Now the machines are modular. If one breaks down, the others keep running. It’s a real improvement, but the factory itself is still designed as if the power came from a single source.

The third sees a system solution. Steam had dictated factory design: heavy multi-story buildings clustered around the power plant, machines arranged by their distance from the shaft rather than by the logic of the work. Electricity broke that constraint. The power source could now be anywhere, so the factory could be anything. This entrepreneur builds lightweight, single-story plants and lays out the floor around the flow of workers and materials. The productivity gains come not from cheaper power but from an entirely new way of organizing production.

Not all value propositions are created equal. The authors’ point is that the first two solutions were framed as substitution: electricity standing in for steam. That framing explains why industry was slow to adopt electricity at first; a modest saving on fuel wasn’t enough to justify ripping out working infrastructure. The lag was long. Electric motors were available in the 1880s, and by about 1919 only around half of U.S. factory power came from electricity. The productivity surge from redesigned factories didn’t arrive until the 1920s, roughly forty years after the technology first appeared. The payoff came only when some entrepreneurs recognized that electricity’s real gift was decoupling the machine from the power source, something steam made impossible or prohibitively expensive. Once that was understood, the value on offer shifted from “lower energy costs” to “a vastly more productive factory,” and system-level solutions delivered returns that dwarfed the point solutions.

The bridge to AI. The parable is the book’s organizing lens. AI, the authors argue, is at the same stage electricity was a century ago. Most current deployments are point solutions (cheaper, faster predictions dropped into existing workflows) or application solutions (new tools built around a prediction, but still plugged into systems designed for a world without them). The larger opportunity lies in asking what AI decouples. Their answer: prediction from judgment. Just as electricity let the machine move away from the power source, AI lets the prediction move away from the human decision-maker. And just as that earlier decoupling shifted the value proposition from “lower fuel costs” to “a redesigned factory,” AI’s decoupling shifts it from “lower cost of prediction” to “a vastly more productive system.”

The rest of the book is about why so few organizations have made that leap yet, and what it will take to get there.

The Paradox of Success: Lessons from The Innovator’s Dilemma

~ pdawg ~ Leave a comment

What if the very practices that made your company successful were the same ones destined to destroy it?

This provocative question lies at the heart of Clayton M. Christensen’s groundbreaking 1997 book, The Innovator’s Dilemma: When New Technologies Cause Great Firms to Fail. In the introduction, Christensen presents a counterintuitive thesis that has reshaped how we think about innovation, management, and corporate survival.

The Puzzle: Why Do Great Companies Fail?

Christensen opens by presenting a mystery that had puzzled business scholars for decades. Companies like Sears, IBM, Xerox, and Digital Equipment Corporation were not run by incompetent managers. In fact, they were widely celebrated as some of the best-managed companies in the world. Fortune magazine praised Sears in 1964 for having an organization where “everybody simply did the right thing, easily and naturally.”

Yet these titans fell. Not because they grew complacent, arrogant, or risk-averse—but rather, Christensen argues, precisely because they followed the rules of good management. They listened to their customers, invested in new technologies, studied market trends, and allocated capital to innovations promising the best returns.

This is the innovator’s dilemma: the management practices that work brilliantly for sustaining existing products can become fatal liabilities when disruptive technologies emerge.

Sustaining vs. Disruptive Technologies

Central to Christensen’s framework is the distinction between two types of technological change. Sustaining technologies improve existing products along dimensions that mainstream customers already value. These innovations—whether incremental or radical—make good products better. Established firms excel at sustaining innovation because it aligns perfectly with their processes: listen to customers, invest in R&D, and deliver enhanced performance.

Disruptive technologies are different. They often underperform established products initially. They’re cheaper, simpler, smaller, or more convenient—but not as powerful. Mainstream customers typically don’t want them, and they offer lower margins than established products. By every rational business metric, investing in disruptive technologies looks like a bad decision.

And therein lies the trap.

The Disk Drive Industry: A Laboratory for Disruption

Christensen built his research on the disk drive industry—an industry characterized by relentless technological change. Between 1976 and 1995, the industry witnessed extraordinary turbulence: all but one of the 17 major firms failed or were acquired, along with 109 of 129 new entrants. Yet these firms didn’t fail because they couldn’t innovate. The established leaders were actually the pioneers in almost every sustaining innovation in the industry’s history.

They failed because each generation of smaller disk drives—from 14-inch to 8-inch to 5.25-inch to 3.5-inch—was a disruptive technology. Each new size initially offered less capacity than the larger drives and didn’t meet the needs of existing customers. But each found new markets (minicomputers, desktop PCs, laptops) that valued different attributes like size and portability. By the time these smaller drives improved enough to compete in mainstream markets, it was too late for the incumbents.

The Management Paradox

What makes Christensen’s argument so powerful—and uncomfortable—is its implication for managers. He’s not saying that failed companies were poorly managed. He’s saying they were excellently managed for the wrong context. The three patterns he identifies are damning:

First, disruptive technologies were often technologically straightforward—the established firms could have built them.

Second, established firms were leaders in sustaining innovations, proving their R&D capabilities were strong.

Third, despite developing working prototypes of disruptive technologies, management repeatedly chose not to commercialize them—because their customers didn’t want them.

In other words, these companies failed not because of technical limitations or lazy leadership, but because their rational resource allocation processes—designed to give customers what they want—systematically starved disruptive innovations of the resources they needed to survive.

Reflection: Why This Still Matters

Reading Christensen’s introduction nearly three decades after its publication, the insights feel more relevant than ever. We’ve watched Kodak, despite inventing digital photography in 1975, file for bankruptcy in 2012 because it protected its profitable film business. We’ve seen Blockbuster pass on acquiring Netflix for $50 million, only to become a cautionary footnote in business history.

What strikes me most is the emotional difficulty of Christensen’s prescription. He’s asking managers to invest in products their best customers explicitly say they don’t want. He’s asking them to pursue lower margins when shareholders demand growth. He’s asking them to cannibalize successful products before competitors do. These are not just strategic challenges—they’re psychological and organizational ones.

The introduction also offers a subtle but important comfort: failure in the face of disruption is not a character flaw. The managers at these companies weren’t villains or fools. They were trapped by systems, incentives, and rational decision-making processes that work beautifully—until they don’t. Understanding this helps us approach disruption with humility rather than hubris.

Key Takeaways

Success can breed failure. The practices that create market leadership can blind companies to disruptive threats.

Listening to customers isn’t always the answer. Current customers will optimize for current solutions, not future ones.

Disruptive technologies look unattractive—by design. Lower margins and smaller markets are features of disruption, not bugs.

Good management is situational. What works for sustaining innovation can be catastrophic for disruptive innovation.

Christensen’s introduction sets the stage for a book that doesn’t just diagnose the problem but offers solutions—creating separate organizations, finding new markets that value disruptive attributes, and learning to fail early and cheaply. But the introduction’s lasting contribution is simpler and more profound: it reframes failure not as the result of incompetence, but as the shadow cast by success itself.

— — —

The Innovator’s Dilemma by Clayton M. Christensen was first published in 1997 and remains one of the most influential business books ever written. Steve Jobs called it one of the few books that deeply influenced his thinking.

The Hidden Triggers That Control Our Decisions: Lessons from Influence Chapter 1

~ stpoli ~ Leave a comment

Have you ever agreed to something and immediately wondered, “Why did I just say yes to that?” You’re not alone. In the opening chapter of Influence: The Psychology of Persuasion, Robert Cialdini reveals a fascinating truth: humans, like animals, operate on autopilot more often than we’d like to admit.

We’re All Running on Mental Shortcuts

Cialdini begins with a striking observation from nature. A mother turkey will lovingly care for anything that makes a “cheep-cheep” sound, even a stuffed polecat (a natural predator). Remove that sound, and she’ll ignore or even attack her own chicks. This might seem absurdly simple, but before we judge the turkey too harshly, we should look in the mirror.

Humans rely on similar automatic patterns, what psychologists call heuristics or mental shortcuts. In our increasingly complex world, we simply can’t analyze every decision from scratch. We need these shortcuts to function. But here’s the catch: these same shortcuts make us predictable, and when others understand our triggers, we become vulnerable to manipulation.

The Magic Word: “Because”

One of the most eye-opening studies Cialdini shares involves something as mundane as a copy machine. Psychologist Ellen Langer discovered that people waiting in line were far more likely to let someone cut ahead when that person provided a reason, even if the reason was essentially meaningless.

“Excuse me, I have five pages. May I use the copy machine?” had a moderate success rate. But add the word “because” and watch what happens: “Excuse me, I have five pages. May I use the copy machine because I need to make copies?” Suddenly, compliance rates shot up dramatically.

Think about that for a moment. “Because I need to make copies” isn’t really a reason at all—everyone at a copy machine needs to make copies! Yet the mere presence of the word “because” triggered an automatic compliance response. We’re programmed to look for the form of a proper request (statement + because + reason), and once we detect that pattern, we often stop analyzing whether the content actually makes sense.

The Contrast Trap

The second major principle Cialdini introduces is the contrast principle, and if you’ve ever bought a car, you’ve experienced this firsthand. After negotiating the price of a $35,000 vehicle, somehow a $500 upgraded sound system doesn’t seem like much money at all. A $1,200 extended warranty? Sure, throw it in!

This isn’t about being bad with math. The contrast principle operates at a perceptual level, not a logical one. When we experience two things in sequence, our perception of the second is dramatically influenced by the first. Real estate agents use this masterfully—they’ll show you overpriced dumps first, making mediocre properties seem like palaces by comparison. Clothing salespeople know to sell the expensive suit first, then suggest accessories, because a $95 tie feels reasonable after you’ve just spent $750.

The insidious part? This doesn’t feel like manipulation. It feels like genuine assessment. The tie really does seem reasonably priced in that moment. The contrast has altered our perception without our awareness.

What This Means for You

Cialdini isn’t just sharing these insights for entertainment. He’s sounding an alarm. We live in a world filled with “compliance professionals”—salespeople, marketers, fundraisers, and negotiators—who understand these psychological triggers and use them deliberately. They’re not necessarily bad people; many are simply applying proven techniques that work.

The first step in defending yourself is awareness. When someone gives you a reason for something, pause and ask: Is this actually a legitimate justification, or am I just responding to the word “because”? When something seems like a good deal, consider: Am I comparing this to the right baseline, or has my perception been skewed by contrast?

Our automatic response patterns evolved to help us navigate the world efficiently, and most of the time they serve us well. But in an age where understanding these patterns has become a professional skill for those seeking compliance, awareness becomes our most powerful defense.

The good news? Once you see these patterns, you can’t unsee them. And that awareness might just save you from your next impulse purchase, unreasonable commitment, or manipulative request.

Timeless Management Insights from Andy Grove’s High Output Management

~ pdawg ~ Leave a comment

Andy Grove’s “High Output Management” might be over 40 years old, but its insights remain remarkably relevant in today’s business world. As Intel’s CEO during its most transformative years, Grove distilled his management philosophy into principles that continue to influence Silicon Valley’s most prominent leaders, from Mark Zuckerberg to Ben Horowitz.

Why This Book Matters

What makes this book exceptional is its systematic approach to management. Grove treats management as a teachable discipline rather than an innate talent. He argues that like any other skill, management can be learned, practiced, and improved upon. This perspective alone makes the book invaluable for both new and experienced managers.

The Core Philosophy

Grove’s fundamental equation is brilliantly simple:
A manager’s output = The output of their organization + The output of neighboring organizations under their influence

This formula shifts the focus from individual productivity to organizational impact. It’s not about how much work you personally complete, but how effectively you amplify the output of others.

Key Principles for High Output Management

1. Process-Oriented Thinking

Grove argues that everything in business is a process that can be measured and improved. Whether you’re manufacturing chips or managing a software team, understanding the inputs, outputs, and limiting factors allows you to optimize performance.

2. Leverage Activities

Not all managerial activities are created equal. The highest-leverage activities are:

  • Training team members
  • Motivating people
  • Setting expectations and cultural values
  • Making timely decisions

3. Meetings as a Medium of Work

Rather than viewing meetings as necessary evils, Grove presents them as essential management tools:

  • One-on-ones for individual development and information exchange
  • Staff meetings for team decisions
  • Operational reviews for information sharing
  • Mission-oriented meetings for specific decisions

4. Task-Relevant Maturity

One of Grove’s most insightful contributions is the concept of Task-Relevant Maturity (TRM). Your management style should adapt based on your team member’s experience with specific tasks:

  • Low TRM: Provide structured, detailed guidance
  • Medium TRM: Engage in two-way communication
  • High TRM: Step back and focus on setting objectives

5. Performance Reviews and Development

Grove emphasizes that performance reviews should focus on improving future performance rather than just evaluating past work. He advocates for:

  • Written reviews before face-to-face discussions
  • Focusing on 3-4 key messages rather than overwhelming with feedback
  • Investing more time in developing star performers than fixing poor performers

6. Training as a Manager’s Primary Responsibility

Perhaps most importantly, Grove insists that training is the highest-leverage activity a manager can perform. It’s not something to be delegated to HR or external consultants – it’s the manager’s fundamental responsibility.

Modern Relevance

While some examples in the book may feel dated (particularly those focused on manufacturing), the principles remain remarkably applicable. In fact, many modern management practices in Silicon Valley can be traced back to Grove’s teachings. Whether you’re managing a software development team, a marketing department, or a startup, the fundamental challenges of coordination, motivation, and performance optimization remain the same.

Key Takeaway

The most powerful message from “High Output Management” is that management is a skill that can be learned and systematically improved. It’s not about charisma or innate leadership ability – it’s about understanding fundamental principles and applying them consistently.

For anyone in a leadership position or aspiring to be in one, this book provides a comprehensive framework for thinking about management and organizational performance. It’s no wonder that decades after its publication, it remains required reading for managers at many leading technology companies.

Whether you’re a new manager looking for guidance or an experienced leader seeking to refine your skills, Grove’s insights offer a powerful toolkit for improving your effectiveness and your organization’s output.

What management principles from Grove’s book have you found most useful in your work? I’d be curious to hear your experiences in the comments below.