The original is one click away. Open original ↗
Strategy / Business operating systems
Product / Iteration & feedback loops
Leadership / Culture building
The Lean Startup framework: six elements beyond the core methodology
Executive overview
Most teams know the build-measure-learn cycle, but methodology alone rarely delivers transformation. The Lean Startup framework has five additional elements — teams, milestones, governance, strategy, and culture — that determine whether the methodology actually works in a corporate context.
Without these elements in place, teams run experiments nobody asked for, governance becomes either a buzzsaw or a blank cheque, and culture rewards slide decks over real learning.
The core insight: methodology is necessary but not sufficient — the surrounding framework is what makes it stick.
The build-measure-learn cycle
- The loop starts with learn, not build: identify the most critical assumptions first
- Leap of faith assumptions are the bets that, if wrong, kill the initiative
- Build the most minimal viable experiment to test those assumptions, then measure, then return to learn
- The cycle applies to problems, solutions, go-to-market strategies, and business models — not just products
- Pivot until you find a problem worth solving; then move fast once you have traction
Teams
- Keep the team as small as possible for as long as possible
- Larger teams create pressure to feed people with work — engineers need stories, UX needs interfaces — before you have evidence to justify it
- Small cross-functional teams avoid heavy documentation; everyone knows what's happening
- Add resources only once traction emerges; then you have a case for the investment
- Chartering upfront is essential: define who is on the team, who is the lead, and who is accountable — without it, nobody does the experiments because everyone has a day job
Milestones
- Traditional accounting metrics (revenue, ROI, market share) are all zero at the start — milestones replace them as leading indicators of future impact
- Milestones typically track progress across four themes: validating the customer problem, solution traction, go-to-market strategy, and overall business model
- Each milestone should blend desirability, feasibility, and viability
- Anti-pattern: teams present milestone evidence and leaders ask for a five-year business case — misaligned expectations are a governance failure, not a team failure
- A mature team will recommend not advancing through a milestone when evidence is absent — that is the framework working correctly, not failing
Governance
- Governance means how leaders make investment decisions across a portfolio of initiatives under high uncertainty
- The leader's job is not to have answers; it is to ask the right questions and demand a body of evidence
- Too much governance: constant check-ins mean teams produce slide decks instead of running experiments
- Too little governance: teams get a large budget and are told to return in six months — no accountability for rapid learning cycles
- Governance structures vary: a growth board, a product council, or a single named owner — what matters is fit, not form
Strategy
- Without a clear strategy, teams don't know what good learning looks like or whether they are working on the right problems
- Strategy informs which initiatives enter the backlog, how the portfolio is evaluated, and what milestones mean
- Anti-pattern: teams do excellent Lean Startup work, then present to leadership who ask why they worked on those initiatives at all
- Even well-executed experiments waste resources if the output cannot be implemented because it was never strategically aligned
- Chartering must include strategic alignment — not just role clarity
Culture
- A lean startup culture puts evidence over conviction: it does not matter how compelling the presenter is or who originally proposed the idea
- When evidence is absent, leaders must visibly refuse to support the initiative — this signals that learning is valued, not just delivery
- Avoiding waste means measuring customer outcomes from ideation through to deployment — not just lines of code or on-time delivery
- Culture is not posters and decks; it is what gets celebrated and rewarded in day-to-day behaviour
- All five other elements can be in place and culture can still undermine them — it surrounds and touches everything
More like this — when you're ready for early access.
Join the waitlist for a personal account and content recommendations based on what you're working on.
No spam. Unsubscribe at any time.
You're on the list. We'll be in touch before launch.