The Program

What to Actually Learn

Most technical people in an MBA program make one of two mistakes. The first is treating the curriculum as a credential exercise. The second is dismissing the business curriculum as obvious.

Both are expensive. The first misses the actual learning. The second misses the fact that knowing something in practice and having the vocabulary to think about it precisely are not the same thing.

The Test for Real Learning

Real learning has happened when you find yourself thinking with the framework in a context where no one told you to. You're in a conversation about a startup's go-to-market strategy and you instinctively reach for the competitive moat question. You're evaluating a job offer and you naturally model the equity as a percentage of fully diluted shares rather than an absolute number.

If you can only apply the framework when the exam is in front of you, you haven't learned it. You've temporarily borrowed it. The goal is the frameworks that become automatic.

The Load-Bearing Mental Models

These are the frameworks where the delta between “knowing this” and “not knowing this” is largest for this cohort.

1.

Unit Economics — The DNA of a Business

What it is

The revenue and cost structure associated with one unit of whatever the business produces or sells. Customer acquisition cost (CAC), lifetime value (LTV), contribution margin, payback period.

Why it matters

Engineers and product managers make decisions every day that affect unit economics — feature scope, infrastructure costs, onboarding complexity, retention rates — without a framework for tracing those decisions to the financial model. Once you have the framework, every technical decision becomes readable as a business decision.

How you know you have it

You can look at a startup's deck and estimate, from the information they give you, whether their unit economics are likely to work — and you can name which specific assumption is most likely to be wrong.

The test

Model a company you know well. What's the CAC? What's the LTV? What would have to be true for LTV/CAC > 3? Is it true?

2.

Competitive Moat — Why This Business Exists in 5 Years

What it is

The structural advantage that makes a company's position defensible against competitors. Network effects, switching costs, proprietary data, economies of scale, regulatory position, talent density.

Why it matters

Technical people often conflate "we have better technology" with "we have a moat." Better technology is a temporary advantage unless there's a structural reason it compounds. Understanding the difference is what separates founders who build enduring companies from the ones who get copied in 18 months.

How you know you have it

You can explain, in two sentences, why a specific company's advantage is or isn't structural — and what would have to happen for it to erode.

The test

Pick five companies in your domain. Name the moat for each. If the answer is "better product," push further: why does better product stay better? What makes it structural?

3.

Capital Structure and the Cap Table

What it is

Who owns what, at what price, with what rights. Common vs. preferred shares. Option pools. Liquidation preferences. Dilution mechanics.

Why it matters

Every equity decision you make as an operator or investor involves a cap table. Joining a company as an employee, evaluating a VC investment, structuring a co-founder agreement, understanding what your options are actually worth — none of these are legible without understanding the capital structure underneath them.

How you know you have it

You can look at a simple term sheet and tell someone what their equity is worth in three different exit scenarios (down round, flat exit, strong exit). The answer will surprise most people.

The test

Model a $50M exit for a company with a $10M Series A at 1x participating preferred, a $5M seed at 1x non-participating preferred, and a 15% option pool. How much do employees with 0.5% get? Work it through.

4.

Strategy vs. Execution — The McKinsey Trap

What it is

The distinction between where to compete (strategy) and how to win there (execution). Most business school content leans heavily on strategy. Most company failures are execution failures.

Why it matters

Technical operators are often excellent at execution and weak at strategy — not because they can't think strategically, but because the operational environment rewards execution speed and doesn't reward strategy articulation. The MBA is the place to build the strategy vocabulary without losing the execution instinct.

How you know you have it

You can distinguish, in a real company situation, which decisions are strategic (hard to reverse, define which game you're playing) and which are tactical (reversible, define how you're playing it). They require different decision processes.

The test

Pick a decision your current or most recent organization made. Was it a strategy decision or an execution decision? Who should have made it? How should it have been made?

5.

Organizational Design — Why Smart People Fail Together

What it is

How structure, incentives, communication norms, and decision rights shape what an organization actually does — as opposed to what it intends to do.

Why it matters

Every senior operator eventually discovers that the primary constraint on outcomes is not the quality of individual people but the quality of the system those people operate in. Building a high-performing team is an organizational design problem, not a talent acquisition problem.

How you know you have it

You can diagnose an organizational dysfunction — slow decisions, misaligned incentives, communication breakdowns — and propose a structural fix, not just a personnel fix.

The test

Think of an organization that failed or struggled. What was the structural cause? What was the fix it actually needed — not the fix it tried?

6.

M&A Mechanics — How Companies Combine and Why It Matters

What it is

The logic and mechanics of acquisitions, mergers, and strategic combinations. Valuation frameworks. Deal structure. Integration realities. Why most deals fail and why they're still done.

Why it matters

Deep-tech exits are frequently acquisitions, not IPOs. Understanding what an acquirer is buying (technology, team, market position, regulatory position) and why they're willing to pay a specific price is essential context for anyone building a company, advising on a deal, or investing in the ecosystem.

How you know you have it

You can read a tech acquisition announcement and immediately generate a hypothesis about the strategic logic, the likely price justification, and what the integration challenge will be.

The test

Pick a recent acquisition in your domain. Why did it happen? What did the acquirer pay for? Was the price right? What's most likely to go wrong in the integration?

7.

The Investor's Mental Model — Pattern Recognition at Scale

What it is

The way a sophisticated investor evaluates a company — not the DCF (which is mostly a post-hoc rationalization tool) but the qualitative pattern recognition: team, market, product, traction, and why now.

Why it matters

Whether you want to be an investor or not, thinking like one makes you a better founder, operator, and advisor. The investor's lens asks: what has to be true for this to work? What's the biggest risk? What would I want to see in 18 months to feel good about this?

How you know you have it

You can sit in a pitch and generate the two or three critical questions — the ones that, if answered well, would change your mind, and if answered poorly, would confirm your concerns.

The test

Find a pitch deck from a public startup (many post them). Evaluate it using only the investor mental model. What's the biggest risk? What would you want to know? Would you invest?

The Curriculum Map — What to Prioritize

Not every course is equal. For a technical cohort targeting investor, operator, or founder paths, the honest prioritization:

Highest priority — internalize completely

Finance (unit economics, cap tables, financial modeling), Strategy, Organizational Behavior

High priority — learn the frameworks, apply them

Marketing (not as a discipline but as a mental model for how customers make decisions), M&A and Corporate Finance, Entrepreneurship

Moderate priority — enough to be conversant

Operations, Supply Chain, Accounting basics

Lower priority for most of this cohort

Macroeconomics (useful context, not decision-relevant), Generic management theory (mostly already internalized by senior operators)

What “Absorbing” Looks Like in Practice

›A week after a class on unit economics: you're reading a news article about a startup's growth and you automatically ask "what's the CAC?" That's absorption beginning.
›A month after a class on competitive strategy: you're in a conversation about a company you know and you find yourself arguing about whether their advantage is structural or temporary. That's absorption deepening.
›A year after the program: a founder asks you to look at their model, and you go straight to the assumptions that matter. You don't have to think about what framework to use. That's absorption complete.

The goal is not to remember what you were taught. The goal is to not be able to remember whether you were taught it or always knew it. That's the test.