STEN 1000 — Introduction to Business

Strategy notes

  • Bad strategy doesn't always look bad. In 2000, staying focused on Blockbuster's successful stores was a defensible decision.

  • Challenges of strategy: decisions made with incomplete information; successful businesses reluctant to disrupt themselves; short-term success can hide long-term threats; limited resources — choosing one direction means not choosing another.

  • Strategy requires making choices: Where will we compete? How will we win? What will we NOT do? What needs to change when the world changes?

  • A strategy is more than a list of things a company would like to accomplish.

  • Limitations of 2x2 matrix approaches: overly simplified; elements may be difficult to define or measure.

  • BCG Growth-Share Matrix: Market growth rate x Relative market share → Star (high/high), Cash Cow (low MGR, high RMS), Question Mark (high MGR, low RMS), Dog (low/low).

Mining industry strategy discussion

  • Focus: developing a natural-resources/mining venture — identify a concrete industry problem, choose where to play, explain value creation and capture.

  • Opportunities discussed: uranium, exploration, development, financing, royalty-stream models; questions on deposits, viable mines, competition, risk, funding.

  • Move beyond a broad idea toward an actionable concept: define problem + solution, industry segment and market position, industry dynamics and competitive space, how value is created and captured.

  • Value creation = story/pathway of producing greater value for customers. Value capture = accelerating growth and retaining value (resale, recycling, retention, pricing power, differentiation/brand/ecosystem effects).

  • ESG described as a ranking/assessment system used by investors and auditors on environmental/governance responses.

  • Boards of directors: outside day-to-day operations, represent shareholders, oversee management; topics included ownership, equity, debt capacity, fiduciary duties, transparency, director liability/insurance.

  • Assessment: written project material, verbal defense, iterative feedback; 5% project.

Lesson 5

  • Organizational alignment: concentric layers — internal structures/processes; market-facing stories/value propositions; strategies; external environment. Durable advantage comes from alignment of internal configuration, market positioning, and value capture.

  • Leadership: align short-, medium-, long-term goals; communicate shared vision; manage capital; meaningful work, belonging, competence, trust.

  • Responses to environmental change: ignoring rules → compliance → peripheral initiatives → deep integration.

  • ESG/CSR/trust: trust reduces uncertainty, financing costs, oversight costs; trust breaks via cheating, concealment, broken commitments, shortcuts.

  • Markets spectrum: free markets to strong government intervention. Competitive market conditions: transparent prices, responsive supply/demand, low entry/exit barriers, undifferentiated products.

  • GDP = value of goods/services produced in a jurisdiction over a period; limited as well-being measure. Fiscal vs monetary policy. K-shaped economy. CPI as constructed index.



STEN 1000 — Midterm Review / Strategy Lecture Notes

Class: Monday, October 19, 2026
Source: Cohen's lecture transcript. This was mostly a midterm review lecture — he walked chapters 1–8 back together into one strategy story. ASR was very rough in places; uncertain bits are flagged, not invented.


Midterm admin — read this first

  • Midterm covers Chapters 1–8. (Already on your calendar: Wednesday, November 4, worth 20%.)

  • Question levels (his breakdown):

  • Level 1 questions ≈ 30% of the exam — knowledge/recall of the concepts.

  • Level 2 questions — a chunk of the rest — understanding/application to a scenario.

  • Level 3 questions — the remainder — analysis: piecing concepts together and creating an answer, not just reciting one.

  • The spread is deliberate: he wants the exam to separate high-performing from lower-performing students, so expect the Level 2/3 questions to do that work. No trickery — his words. Everything is relevant, Chapter 1 only a little less weighted than the rest.

  • Expect application questions — he name-checked topics like the economy and fiscal policy as the kind of thing an application question can be built on.

  • Same instructions/accommodation setup as last time.

Study translation: memorizing definitions gets you the ~30%. The rest of the marks are in "here's a firm/market — which concept is this, and what should it do?" Practice by applying, not re-reading.


The whole course so far, in one chain

This is how he re-built it in class — learn it as a chain, not 8 separate chapters:

Purpose → look outside → look inside → match them → choose how to compete → set goals/KPIs → act, learn, adjust

1. Start with purpose

  • First question of strategy: identifying purpose — what is the intent, why are we doing what we're doing?

  • The planning questions a firm has to answer: What are our resources and capabilities? What are our products/markets? What is the purpose of the organization? What is our source of advantage? (Accountability and performance management come later — mostly through your projects so far.)

2. Look outside (external analysis)

  • Macro/contextual environment — PESTLE-type scan: Political, Economic, Social, Technological, Legal, Environmental forces the firm operates inside. Use it to diagnose risk and spot opportunity.

  • Competitive/industry environment: what the immediate market/industry looks like.

  • ESG mandates got a brief mention as part of this external picture.

  • Output of looking outside = Opportunities and Threats.

3. Look inside (internal analysis)

  • Inventory your resources and capabilities (including human resources) — they form the base you compete from.

  • Output of looking inside = Strengths and Weaknesses.

  • SWOT is just the box you put 2 + 3 into. He was clear SWOT is one framework, not the point — the point is: figure out what you're good at, then find the intersection between that and a real market opportunity, under conditions where you can actually profit, while avoiding the threats.

4. VRIN — is the advantage real and lasting?

Resources/capabilities are a strong basis for advantage only if they are:

  • Valuable — they actually create value customers want

  • Rare — competitors don't all have them

  • Inimitable — can't be copied/mimicked

  • Non-substitutable — there's no different resource that does the same job

If all four hold → you have the foundation for a sustainable competitive advantage. Intangible resources count here — he gave brand story/reputation as the example after the midterm material.

If they don't hold (easy to imitate, substitutable, not rare) → your advantage is short-lived: a first-mover/head-start advantage only. You get a limited window, not a moat.

5. Formulation: vision, mission, and the cascade

  • Start formulation with vision and mission — and not as fluffy posters. A good mission statement is short and direct (he said aim for something like 7–8 words of real content): this is what we do, this is why we're here, this is what matters to us. It points you in a direction; it does not give you the pathway.

  • Then it cascades down:

  1. Purpose / vision / mission

  2. Corporate strategy — where (and in what) will we compete?

  3. Goals and objectives — the mission turned into actionable targets

  4. Business-level plans — how we get there

  5. Operational reality — how it actually runs

  • Reality check he added: it doesn't only flow top-down. A lot of strategy emerges bottom-up — you try things, some work, happy accidents/experiments turn into opportunities you then plan around. Emergent strategy is real strategy.

6. Goals and performance

  • Goals should be specific and turned into objectives that stack down the organization, with KPIs / performance indicators attached so you can tell if you're actually hitting them. (This is the goal-setting material that comes in right around the midterm boundary.)


The EV / infrastructure story (his long example)

  • ~12 years ago, driving an EV through the middle of nowhere in Wyoming: charging infrastructure barely existed → range anxiety was the real product problem, not the car.

  • Since then: charging networks grew a lot, battery capacity grew, and home batteries now double as household storage (charge the car / store power / sell or use it).

  • Now the AI build-out is creating the opposite bottleneck: not enough electricity for demand.

  • Lesson: whether a strategy works depends on external technology/infrastructure readiness. Tesla flirted with solar roofing and backed off — not because the idea was bad, but because the technology/manufacturing wasn't ready. Some ideas get abandoned by the conditions, not by the concept.

  • Exam use: this is a PESTLE (especially Technological) + timing example.


The music example — THE concept of this lecture

Same song, same $450 ticket, two completely different things being bought:

Performance A — the orchestra / Sound of Music performance

  • You've heard this recording 100 times. You pay $450 to hear it live and you want it exactly the same. If the band comes in early, if she riffs a "la la la" in the middle — you're mad. You go back the next day for the matinee, pay another $450, and again you want the identical performance.

  • Behind it: huge structure. Orchestra sections (strings, winds, percussion), 1st chair / 2nd chair / 3rd chair, a conductor, everyone listening and coordinating to produce precision.

  • What you're buying: precision, reliability, consistency — excellence through stability.

Performance B — John Coltrane, resurrected, tiny club in Paris

  • Also $450, also world-class musicians, also expensive instruments, no less mastery.

  • But there is no identical script — small groups coordinating with each other, improvising, interplay. If night two were note-for-note identical to night one, you'd be disappointed.

  • What you're buying: variation, creativity, responsiveness — excellence through flexibility.

The point (write this down): both use roughly the same resources — professional players, comparable instruments, the same song — and produce radically different value. Resources alone don't explain value; how the organization is set up to use them does.

That gives you the two strategic poles:

  • Stability pole: stable, predictable, reliable performance. Win by doing it efficiently (low-cost provider) or by being the premium, perfectly reliable product. Either way: no surprises.

  • Flexibility pole: constant adjustment, customer responsiveness, innovation, evolving with the opportunity. A very different, very hard kind of company to run.

Trying to be world-class at both poles at once is the core difficulty — the general recommendation from class is to focus and be really, really good at the thing you choose.

Ambidexterity note: some firms try to get both by structurally separating the innovation unit from the day-to-day production organization on purpose, letting new ideas develop in isolation, then flowing the winners into normal production (he gave a Ford-style example and an animation-studio example — names were garbled in the audio, the structure is the testable idea).


Market structures — recap, then match your advantage to them

Market types he reviewed:

  • Pure (perfect) competition — undifferentiated/commodity goods, many sellers.

  • Monopolistic competition — many sellers with differentiated products; firms can hold a temporary monopoly on their niche through brand reputation, new technology, patents — but it expires.

  • Oligopoly — a handful of firms dominate an industry (regulated or not, e.g. energy/gas-type industries).

  • Monopoly — one seller, either through control of a key resource or as a government-regulated monopoly.

Matching (the Level 2/3 move): after external + internal analysis, you bundle what you're good at into a platform for advantage that fits the market you're in:

  • Pure competition → you're a price taker (market sets the price). Your only lever is efficiency: do the same thing as competitors, at lower cost.

  • Regulated monopoly → price/product fights aren't the game; your position/license is the advantage.

  • Monopolistic competition → compete on differentiation: brand, reputation, trust — why would a customer pick you?

  • Volatile, fast-changing market → privileges flexibility/customer responsiveness.

  • Market that privileges quality, reliability, access → privileges stability/operational excellence.

The three fit questions to run on any firm (including your AquaSky project):

  1. Is there a market for what we're good at?

  2. Is there space/opportunity for us to compete on that basis?

  3. Is the advantage sustainable or transient? (Run VRIN. Not rare/imitable → first-mover window only.)

Path dependence — why the choice sticks

  • Decisions about how to compete now create commitments that shape your future options.

  • If you build the whole company around efficiency and the market pivots to innovation/customization, switching is expensive, slow, and costly — bigger organizations feel this even more than small ones.

  • So strategy runs as a loop, not a one-time plan: plans → actions → learning from what happens → back into the plans. He closed by noting this same loop applies beyond for-profit firms — nonprofits and social organizations too.


One-page chain to memorize

Purpose → PESTLE/industry (O & T) + resources/capabilities (S & W) → SWOT intersection → VRIN test (sustainable vs. first-mover only) → vision/mission (short, real) → corporate strategy (where to compete) → goals + KPIs → compete from the stability pole or the flexibility pole → match that to your market structure → remember path dependence: today's choice prices tomorrow's pivot.


STEN 1000 — Stage 2 (AI Portfolio) Briefing + Chapter 7: Business Models

Class: Wednesday, October 22, 2026 (transcript; ASR was very rough — uncertain bits flagged, not invented). Professor: Chris Fredette.

PART 1 — Stage 2 admin: what the AI Development Portfolio actually has to show

Stage 2 ("Practice") broadly = an interim development report + AI development portfolio. Its purpose: a container that holds the team accountable and shows progress over time — instead of everything being thrown together at the last minute.

The AI piece — the questions your portfolio has to answer:

  • Which tools are you using, and how are they integrated into your work? (Different teams use AI differently — data aggregator, blocking/system tool, customer communication, forecasting, etc. He doesn't need to see prompts, but he needs to understand the integration.)

  • What is the AI actually doing in your system? E.g., for data-driven ventures: public data exists → you build a model → the AI draws inferences. Is it automated (does the AI know when to activate and draw inferences on its own)? Does it recursively improve its inferences from past experience/results?

  • Which AI is fundamental to the system — i.e., what is your core value-creation mechanism? (In AquaSky's case, the inference/recommendation engine IS the product — that's where the money comes from.)

  • What happens if that AI fails / is unavailable / costs too much? You need a plan B — an understanding of what the current system does without it.

  • Take screenshots as you build/create things — evidence for the portfolio.

Ownership, liability, and terms of service (lecture discussion — likely portfolio material)

  • If you build with a company's tools/platform, what do you own vs. what do they own? Check the tool's terms of service for your specific case.

  • Platform liability analogy: social media platforms aren't liable for user content (US Section 230 [transcript said "203" — the law is 230]); like a newspaper isn't liable for an ad someone places. Ownership, though, is set by each platform's terms of service.

  • Data privacy differs by tier/tool: e.g., Microsoft Copilot's professional/enterprise tier commits to keeping organizational data private within that structure and not learning from your use (which is why the university can use it with student data). Free/consumer tiers of tools like Gemini or Claude, and OpenAI's tools, each have different standards in their terms of service. The regulatory environment has not clarified ownership — if you create something novel and commercializable with AI, who owns the IP is a genuinely open question.

  • Takeaway for the portfolio: name your tools, name their tier/terms, and state your ownership/privacy position.

Peer evaluation starts at Stage 2

  • Peer evaluation forms begin with Stage 2; a final round comes at Stage 3. You receive aggregate scores, not individualized ones.

  • His advice on group problems (this is the time of semester groups start to crack): talk to your group first; if 3+ members share a concern, have that conversation together, thoughtfully; don't suffer in silence, but don't just dump it on the prof either. If you escalate, a good supervisor asks what steps you already took (dates, what was said, what changed). He WILL intervene on big issues after you've taken some action yourselves.

  • Design intent: the project deliberately tests two things at once — the performance piece (the deliverable) and the social performance (managing relationships). The tension between "do it all yourself and resent everyone" vs. "do none of it" is the lesson: get both together. Groups are deliberately large; expect roughly half the work to be wrangling engagement.

  • Class ended early for group work time.

PART 2 — Chapter 7: Business models, structure, culture, systems

Alignment (the chapter's spine)

  • Start from the environment: what market structure do you exist in (competitive, monopolistic competition, monopoly)? That tells you where you can/can't compete. Then map your source of competitive advantage onto it: compete on efficiency, on differentiation (innovation or customer responsiveness), or on quality/reliability/predictability (e.g., monopoly contexts demand high reliability). The business model must match the advantage and the market — misalignment = outcomes fall apart.

The three internal components (the business model)

  1. Organizational structure — how jobs/people are organized: boxes = jobs (each with boundaries: what the job is/isn't), lines = authority/reporting relationships, hierarchy = number of layers between frontline workers and senior executives (more layers = more separation; GM was cited at ~11 layers).

  • Value creation happens at the frontier/frontline — where employees meet customers — not in the layers above.

  • Tall/hierarchical structures suit predictable, reliable, measurable outcomes. Flat structures (few layers, team-based, lots of autonomy) suit creativity, variability, innovation, and novel customer responses.

  1. Organizational culture — the norms, patterns, values, and routines in social interactions between people in the organization. Sources: the ethics of the organization (espoused vs. realized), and especially the founders' belief systems, which permeate the firm for a long time (legacy firms like Loblaws/Lawtons under the Weston family talk and act like legacy firms, not startups). Culture is also shaped by the decisions leaders make (hiring, spending, what gets rewarded/punished).

  • Culture predisposes behaviour: an innovation culture (no answers are wrong, errors are useful, mistakes are learning, safe space, focus on effectiveness) vs. an efficiency culture (everyone goes home safe, zero errors, days-since-last-injury boards, supervisors circulating to keep you on the machine — no room to experiment).

  1. Managerial systems — the technological, resource-based, and control systems that configure how resources are allocated and work gets done.

Business model — definition (know this)

  • The internal configuration of structure + culture + managerial systems that organizes your assets, technologies, resources, people, and skills to create replicable value creation.

  • Inside/outside picture: inside the organization = the business model (key partners, suppliers, key activities, value chain — how you collect resources, transform them, and send them out as your product/service portfolio). Outside = the revenue model (what you make, who wants it, your value proposition, how you're positioned — lowest cost? relationships? trust? community? — and how you capture value/money back).

  • The link between them is the value proposition: the story you tell shapes the revenue model; the business model has to actually deliver it. Loop: value proposition → value creation (inside) → value capture (outside, revenue returns).

Diagnosing a business model — five logics (textbook framework; first term was garbled in the audio — the five as heard):

  1. [Uncertain — sounded like "a thousand logic"; likely the business-idea/concept logic]

  2. Market logic — are we comprehensive enough? Are we matching what we do to customer needs, tastes, demand, demographics — now and over time?

  3. Value creation logic — do we have the required resources/capabilities? Are they rare, valuable, sustainable, non-substitutable? Do our capabilities match our strategy?

  4. Business logic — are the mechanics in place to convert demand/excitement into actual revenue? (Plenty of good ideas have no market mechanism.)

  5. Risk logic — what is the possibility of success, and what is our exposure if the environment shifts? Safe space or increasingly perilous?

  • Use the diagnostics to decide which parts of the business to invest in/advance, maintain, or remove.

PART 3 — Case: Southwest Airlines (activity system → advantage → erosion)

  • Model copied from Ryanair [as stated in class]; WestJet was "Southwest North" — same low-cost model in Canada. Porter = the smaller regional alternative with higher service.

  • The early activity system: no-frills (carry your own bags, minimal food/service/customer care) in exchange for very low fares; lean ground operations (pilots/crews cleaned cabins instead of separate cleaning staff); team-based crews instead of hierarchy; standardized on a single aircraft type (737) — one training/logistics system, interchangeable planes and crews; point-to-point routes from underserved/secondary airports (Dallas Love Field, Houston Hobby, Burbank...) that would subsidize the carrier for the traffic.

  • Where was the advantage? Not unique assets (same 737s as everyone), not unique technology (same booking systems), not unique competencies (a qualified pilot is a qualified pilot). It was efficiency/cost: they entered with none of the legacy cost structure — no unionized legacy roles/infrastructure that every incumbent (20–30 years of built-up costs) carried. Competitors literally could not match the cost base. Extras reinforced it: standby/rush seating instead of assigned seats, no cargo in the belly, etc.

  • Erosion over time: as Southwest grew, it added partnerships/alliances, more route types, more complexity → cost structure crept up → the cost advantage thinned. Evidence: share price (a long-run reflection of expected earnings/returns) flattened; earnings-per-share growth stalled after the big 2013–2018 growth period. Lesson: competitive advantage is temporary — the activity system that created it has to be defended/renewed as the environment changes.

  • Today: still keeps elements (limited passenger service — though more is now sold for a fee; point-to-point roots; somewhat reliable when tech works) but ticket prices are no longer the lowest (ultra-low-cost carriers undercut them), and they're now investing in tech/reliability.

Next class (Monday): finish Ch. 7 examples, then Chapter 8.

Flagged, unverified: background student chatter mentioned other courses' final exams (sport industry "on the 17th," health & wellness "the 22nd," CAW gym venue) — too garbled to record as fact; check official schedules before relying on any of it.


STEN 1000 — Midterm logistics + business models continued (Ch. 7)

Midterm exam logistics (new — not in the Oct 19 review notes)

  • 60 questions, 60 minutes. Mark answers right on the exam sheet — no scantrons.

  • Bring student ID (card preferred; driver's licence or another photo ID if not).

  • Sign-in/sign-out sheet at the front; invigilators roaming. Electronics and bags go to the
    front of the room.

  • If asked to move seats during the exam, it is a precaution, not an accusation.

  • SAS accommodations: materials will be waiting at SAS with the same instruction set.

  • Question levels as described in this recording: Level 1 foundational/recognition (e.g., define
    fiscal policy); Level 2 application (~30% per this recording — e.g., how governments use fiscal
    policy to change growth); Level 3 mastery/analysis (~20% per this recording — e.g., effect of a
    growth policy on domestic interest rates).

  • Note: this split differs from the Oct 19 review sheet (which had Level 1 at ~30%).
    Treat the level split as unconfirmed; the 60-question / 60-minute format is new here.

  • Prof: no trickery, no micro-details (e.g., won't ask for a specific 2017 investment figure).
    Concepts and why they matter are what is tested.

  • Prof's study advice (his own method, not a requirement): read the book, highlight, take notes
    from the highlights; handwriting helps his memory.

Business models continued (Ch. 7)

  • A business model is the aggregate sum of all processes, plans, strategies and decisions
    organized to express a value proposition and capture value. Internal half (what the company
    does for itself) vs market-facing half (what targets customers).

  • Five external themes framing the landscape: climate change; pollution and health; energy
    crunch / lack of sustainable capital; resource depletion (if the world lived like North
    America, we'd need ~5 planets); capital costs and rising interest rates (neocloud example:
    CoreWeave, Nebius rent out data-centre space and are vulnerable when rates rise; widening
    credit spreads signal distress).

  • Southwest (alignment example): competitive advantage from customer responsiveness + efficiency
    together — flexible labour contracts, 15-minute turnarounds, high aircraft utilization,
    standardized fleet (one aircraft type = same seats, parts, maintenance, crew training).

  • Razor-blade model: give away the handle cheap, take the margin on blades. Roku: cheap hardware
    into the home, margin on the platform/subscriptions. Risk: users stop subscribing, or content
    rights go exclusive elsewhere (Disney, Netflix originals). 2021 was Roku's best year; 2022
    share fell as competitors multiplied.

  • Netflix-type models rest on two assumptions: cheap, fast internet throughput and low cost.
    If bandwidth is throttled or gets expensive, the model breaks. The same two factors sit behind
    Blockbuster's failure.

  • Spotify freemium/community model: free tier with ads + premium subscriptions + user data
    repackaged. Only ~20% of users pay (Pareto), but a large enough community makes that 20%
    profitable. Same logic as freemium games: GTA Online microtransactions, World of Warcraft
    subscriptions, mobile games.

  • Amazon ecosystem: a mutually sustaining system (marketplace, AWS, logistics, devices). Data
    from all transactions identifies trends, including Amazon-branded versions of trending
    products. Heavy physical investment in distribution and last-mile delivery. Took 10–12 years
    to build momentum; profits wobbled when interest rates rose post-COVID.

  • Apple ecosystem: iPod (2001) → iPhone (2007) → iPad → iOS ecosystem. The App Store works as a
    gateway/landlord: Apple takes a slice of every transaction and upgrade. Switching costs
    (family coordination, calendar, device integration) lock users in. BlackBerry contrast:
    dominant business device, dismissed the iPhone (no keyboard, touchscreen), share collapsed
    after 2008; survives in security/network niches.

  • Stage 2 projects due Monday (Nov 2) — consistent with the known deadline.