Dawar's central argument in When Marketing is Strategy (HBR, 2013): sources of competitive advantage have migrated downstream. Upstream activities — production, sourcing, logistics — are commoditizing. Downstream activities — how you reach, shape, and serve customers — are where durable advantage now lives.
| Dimension | Outside-In / Downstream | Inside-Out / Upstream |
|---|---|---|
| Decision start | All decisions start with the market and opportunities for advantage | We'll sell to whoever will buy |
| Profit source | Superior value proposition; leveraging brand and customer assets | Cost cutting and efficiency. Six sigma, TQM, and replicability take priority |
| Customer knowledge | A valuable asset; channels are value-adding partners | Data are a control mechanism; channels are conduits |
| Competitive intelligence | We know more than our competitors | If competitors do it, it must be good |
| Self-disruption | No sacred cows — cannibalize yourself | Protect the cash flow stream |
| Customer perception | Customers buy the expectations of benefits | Customers buy performance features |
| Quality definition | Defined by customers as "fitness for use" | Conformance to internal standards |
| Idea source | Best ideas come from living with customers | Customers don't know what they want; asking them is useless |
| Loyalty vs. acquisition | Customer loyalty is the key to profitability | Expanding the customer base is what matters |
The same can of Coca-Cola sells for ~$0.25 in a warehouse 24-pack. On a hot day in a park, the same can sells for $2.00 from a vending machine.
The premium is not for a better Coke. It's for the downstream job: delivering the right product, at the right moment, removing the effort of planning, carrying, chilling. That's where margin lives.
The Inside-Out vs. Outside-In divide sits at the endpoint of a long evolution in how firms think about marketing strategy. Understanding where you sit on this arc helps diagnose why certain strategic reflexes feel natural — and why they may be wrong for the current market.
| Inside-Out Activities | → | Outside-In Activities |
|---|---|---|
| Sourcing: Contract with lowest-cost suppliers | → | Shaping Customer Perceptions: Define competition criteria, build trust |
| Production: Reduce costs / maximize scale and throughput | → | Innovation: Tailor offering to consumption circumstances, reduce customer costs and risks |
| Logistics: Optimize supply-chain and distribution efficiency | → | Building Accumulative Advantage: Harness network effects, accrue and deploy customer data |
| Innovation: Build 'better' products | → | Fixed Costs, Customer Value, and Competitive Advantage are shifting downstream |
Bertolini, Duncan & Waldeck (2015) identify five "fault lines" — the structural stress points in a business where market shifts crack the foundation. An Outside-In strategist monitors these proactively; an Inside-Out strategist discovers them after the damage is done.
Are the jobs customers hire you for evolving? Are you tracking how the functional, social, and emotional dimensions of those jobs are shifting — not just what customers say they want?
Are you measuring the right things? Metrics like "units sold" or "market share of drills" conceal whether you're actually doing the job customers need done. RIM tracked device sales; missed the platform shift.
Is your competitive set defined correctly? Companies that define industry by product category miss competition from outside the category serving the same job. RIM saw smartphone competitors; Apple redefined the category.
Is your revenue model tied to upstream value (scale, production efficiency) or downstream value (customer outcomes, switching costs)? Upstream models erode as commoditization advances.
Do you have the organizational capabilities to operate Outside-In — market sensing, customer empathy, rapid iteration? Or are capabilities concentrated in upstream functions (engineering, manufacturing)?
RIM had stress fractures on all five: customer needs shifted to "whole digital life"; metrics were device sales; industry position missed Apple; business model was BES (upstream); capabilities were hardware engineering. A complete Inside-Out fault line profile.
Even when the data is available, cognitive biases prevent firms from accurately reading market signals. These are not individual failings — they are structural features of how human minds process information under uncertainty (Ariely, 2010; Haselton et al., 2005; Kahneman, 2011).
We seek information that confirms existing beliefs and discount disconfirming signals. RIM's engineers saw iPhone's battery drain as proof it couldn't work — this confirmed their existing view rather than prompting re-evaluation of the category direction.
We overweight vivid, recent, or easily recalled examples when assessing probability. RIM's relationship with CIOs and enterprise IT was vivid and concrete. Consumer demand for touch-based devices was abstract and hard to recall.
Initial information disproportionately shapes subsequent judgments. RIM anchored on "corporate email device" — every subsequent assessment of iPhone was filtered through that anchor. The right anchor should have been "job the device is hired to do."
We prefer the current state over change, even when change is beneficial. Enterprise IT departments preferred BlackBerry because switching costs were high and the status quo worked. RIM mistook institutional inertia for genuine loyalty.
Dawar challenges four assumptions baked into traditional (Inside-Out) strategy. Each gets a counterintuitive downstream answer.
Traditional view: protect internal assets — patents, processes, talent. Downstream view: advantage resides outside the firm — in customer relationships, channel linkages, brand associations, network effects. Harder to copy than a patent.
Coca-Cola burn test: If all physical assets burned overnight, Coke would raise capital easily — the brand survives. If consumers forgot the brand overnight, the physical assets wouldn't save the company.
Advantage can be external & accumulativeCustomers often can't articulate what they want — they frame needs within existing paradigms. Downstream leaders shape purchase criteria rather than respond to stated preferences.
Steve Jobs: "None. It's not the consumers' job to know what they want." Zara responds to revealed purchase behavior. Cialis turned "duration" into the dominant purchase criterion, displacing Viagra's "efficacy" frame.
Shape criteria, don't just respond to themUpstream: yes — competitors catch up, patents expire. Downstream: the opposite — advantage is accumulative. More customers → better data → better service → more customers.
Orica (explosives): Accumulated blast data across hundreds of quarries → could guarantee outcomes → competitors couldn't match → more customers → more data. The moat widened as they grew.
Downstream advantage compounds, not erodesUpstream: stuck with whoever makes similar products. Downstream: through positioning, channel, and pricing, you can reframe who you compete with and on what criteria.
Brita: Placed in the bottled water aisle. Suddenly competes against Evian, not kitchen appliance competitors. Completely different purchase criteria apply.
Positioning is a competitive set choiceThe BlackBerry case is the session's laboratory. A textbook Inside-Out firm that dominated by solving an engineering problem, then failed when Apple reframed what the smartphone category was actually for.
| Failure Mode | What RIM Did | What Outside-In Would Have Done |
|---|---|---|
| Category Definition | Defined themselves as "corporate email on a handheld." Owned that category completely. | Asked: what job is the customer hiring a smartphone to do — and is that job evolving? |
| Competitive Set | Compared iPhone to existing smartphones (Palm, Windows Mobile). Judged on spec sheet. | Recognized Apple was redefining the competitive set — a pocket computer, not just a phone. |
| iPhone Response | Lazaridis: "This is an impossibility. The networks won't carry it." Engineering-limits frame. | Asked: if customers love this — regardless of current constraints — what does that signal about what they actually want? |
| Product Development | "Managed evolutions" — incremental improvements. Color display, BBM, expanded memory. | Radical redesign from the customer's experience outward. What does "always-on, always-useful" feel like? |
| PlayBook | Built a tablet with superior hardware. Launched without native email — required a BlackBerry nearby. | Asked: what job is someone hiring a tablet to do when away from their desk? What makes it complete? |
| Customer Insight | Focused on CIOs and carriers. End-users were secondary. "The CIO has a veto." | Tracked end-user behavior — what employees wanted to use, not just what IT departments approved. |
This quote is the session's most revealing diagnostic. Lazaridis sees customer-centricity as a threat to engineering excellence. That inversion — where the engineer's logic overrides the customer's reality — is the textbook Inside-Out failure mode.
The Pivotal Questions framework (MIT Sloan, 2015) gives Outside-In strategy an operational discipline. The best strategic thinkers distinguish themselves by how they frame decisions, the questions they ask, and their mode of inquiry — not by the quality of the answers they arrive at before the questioning begins.
Start from the customer's world, not your product. Ask what job the customer is trying to do — not whether your product is solving it well. RIM asked "Can our network handle this?" — Apple asked "What would people want to do on a device they carry everywhere?"
Build multiple scenarios of how the market could evolve rather than extrapolating a single trend. If RIM had run a scenario where consumers drove enterprise tech adoption (vs. IT departments), the playbook changes entirely.
Deliberately argue against your own assumptions. When everyone agrees RIM's enterprise lock-in is unassailable, ask: "Under what conditions could it disappear overnight?" The answer — employee-driven IT demand — was available in 2007.
Step back from individual data points to identify structural patterns. The pattern of consumer tech migrating to enterprise (iPods, iPhones, then MDM) was visible by 2009 — but only if you weren't anchored to "enterprise IT controls device procurement."
Refuse the binary choice. RIM saw the choice as "keep the keyboard" vs. "go touchscreen." The outside-in question: "What would it take to serve the whole-life job AND the enterprise email job?" — that's a product and strategy question, not a hardware one.
Treat failed products as market data, not engineering failures. PlayBook's failure told RIM exactly what job tablet buyers needed done. They read it as "tablet market isn't ready" — the right read was "our tablet doesn't do the job."
IBM hired Arthur D. Little to study Xerox's photocopying technology. They asked: "How many copies from originals would be made if this technology were cheaper and faster?"
The right question was: "How might this technology change when and how people make copies — and what could that grow to in total copies made?"
BlackBerry parallel: RIM asked "Can the iPhone's network load work technically?" The right question: "If customers love this experience, what does that tell us about what they actually want from a device?"
RIM = Inside-Out, deeply and structurally. Embedded in founding DNA (engineering students), the co-CEO split (Lazaridis = tech, Balsillie = sales), and their strategic language ("belief in the numbers, belief in physics"). Their competitive advantage was a proprietary network protocol and push email technology. When that eroded — when iPhone matched push email via Yahoo partnership — RIM had no downstream moat.
| Dimension | Early BlackBerry (2000–2006) | Post-iPhone (2007+) |
|---|---|---|
| Functional | Always-on email, secure, reliable in field. Don't miss a message. | Everything digital: email, web, apps, music, maps, camera. One device for life. |
| Social | Signal productivity and seriousness. "CrackBerry" = power player. | iPhone = taste, modernity, cultural membership. BlackBerry = legacy, lagging. |
| Emotional | Feel productive, feel in control, feel essential. | Feel connected to your whole life. Feel current. Feel like you're not missing out. |
By 2007, BlackBerry was deeply embedded in the Early Majority (enterprise IT, large organizations, government). Once Apple cracked enterprise security and built MDM capabilities, the pragmatists' switching cost disappeared. The Early Majority followed Apple — and the Late Majority wasn't far behind.
Course Engagement = 15%. Session 1 is in-person — first impressions matter. Goal: say fewer but sharper things. One diagnostic that reframes the discussion beats five restated facts from the case.
If asked to diagnose RIM's problem, lead with the structural diagnosis: "They never built mechanisms to sense how the customer's job was evolving. The engineering culture treated customer insight as a constraint on innovation, not the input to it." That's a Dawar-level answer.
Class will likely say "RIM didn't adapt fast enough." Push further: the speed problem is downstream from the mindset problem. They couldn't adapt fast because they had no Outside-In sensing loop. Balsillie's dismissal of iPhone wasn't laziness — it was a worldview that made the threat literally illegible.
Flag the "original insight" paradox: RIM was customer-centric at founding. The failure wasn't starting wrong; it was stopping the ongoing job-sensing work once they had a successful product. Prevents the reductive "RIM never got it" conclusion.
Owo parallel: when you're building a product people love, it's easy to mistake current user satisfaction for a future signal. The real signal is what jobs your non-users are getting done differently. At RIM, the non-user was the consumer who bought an iPod + basic phone — waiting for convergence.
BlackBerry had remarkable success in African markets well after its North American decline — particularly Nigeria, South Africa, Kenya via BBM's low-data messaging. That's an Outside-In insight RIM stumbled into: in data-constrained markets, BBM's compressed protocol was a genuine downstream advantage.
Connect the fault line framework to real product decisions: at Native, decisions about feature priorities are implicitly choices about what fault line you're monitoring. The question "is this Inside-Out (we think this is cool) or Outside-In (this removes a real parent pain)" is a daily PM judgment call.
Outside-In is the orientation. JTBD is the method. Session 1 asks "what mindset?" — Session 2 asks "how do you operationalize it?" The job dimensions (functional/social/emotional) are the tool for doing what session 1 demands.
Design Thinking is the process for turning Outside-In insight into actual product/experience decisions. Empathize → Define is the practical mechanics of what Dawar calls "listening to customer behavior, not stated preferences."
The individual case analysis tests all three sessions. Lead every answer with an Outside-In vs. Inside-Out diagnosis before reaching for JTBD or Design Thinking frameworks. The diagnostic framing IS the answer — frameworks support it.
Sessions 1–3 = price/margin plays. Downstream advantage = price premium (the Coke vending machine). Outside-In strategy directly commands higher margins by reducing customer costs and risks — not by cutting your own costs.
Module 2 shifts to volume (market share, crossing the chasm). But the Outside-In lens carries through — CDJ and chasm-crossing both require deeply understanding customer decision logic.
Outside-In thinking is the frame: where does the customer experience friction? Where could a company reduce costs and risks? The Owo investor research-to-action journey or the Native parent onboarding journey are strong options — both have clear pain points Taju knows firsthand.