Lean startup training for teams

Bring the people who can change the bet, not an audience. A product team that owns the offer. A venture or incubation group that has been asked to find the next bet inside a company that hates waste. The sponsor who will fund the next test or stop this one. If the work sits in a branch, a contact centre, a depot or a council counter, bring someone who did that job this month. A room of people who only see the work in a pack will design a test for the pack.

Risk, legal, brand and technology come when the bet touches their rule. Give them a task: name the line the test must not cross, in time for the test to be designed around it. A review that arrives after the prototype is a way of saying no too late. A constraint named while the bet is still a sentence is a design input, and it keeps a regulated team able to learn.

Do not fill spare seats with people who have no stake. Observers turn a decision into a performance. If a senior person wants to watch, ask them to carry a role: sponsor, sceptic, or owner of the fence. Watching without a role teaches the team that the real meeting is elsewhere.

The same cast scales into a programme, with one addition. Someone owns the register after the sprint, and someone owns intake for the next bet. Those two jobs can sit with the sponsor's team. They cannot sit with nobody. A sprint without a named owner for the next decision is a good room that the calendar will forget. Sydney, Melbourne and Brisbane cohorts fail the same way when the owner is left implied.

By the end of the sprint the team can say the bet in one sentence a sceptic can attack. They can separate a sourced fact from a hope the room has repeated until it sounded like a fact. They can point at the single assumption that should be tested first, and explain why the more exciting assumption can wait.

They leave with a test that uses people and money they already have. The test has a fence: who may be contacted, what may be promised, what will not be built. It has a number the sponsor is allowed to dislike, written down before anyone peeks at the result. It has an owner for the next contact, and a date that is already in a calendar.

They also leave with a thin version. A page, a script, a concierge offer, or a manual step that stands in for the product. The thin version is allowed to be embarrassing. Embarrassment before a build is the cheap kind. The expensive kind is a launch.

The decision is explicit. Stop, change or continue. A stop is recorded as a result, with the hope that died and the spend that did not happen. A change names what will be different in the next test, not a vague promise to iterate. A continue names the next slice of effort and who must still be in the room when that slice is judged.

The quieter outcome is a habit. The next idea that arrives comes with a customer and a doubt. Someone asks which assumption would sink it. Someone asks who is allowed to stop it. That is the capability the organisation actually bought. The artefacts are only evidence that the habit was practised on live work.

Leaders leave with language they can use in a budget meeting. Not a slogan. A sentence of the form: we believed this, we tested that, this is what happened, this is what we will not fund. A finance partner can follow that sentence. A mural is harder to audit.

If the organisation wants the habit more than once, the sprint is the first decision in a programme, not the whole programme. The register, the intake and the second decision date are what stop the room becoming a story people tell once. Those pieces are scoped with the sponsor. They are not assumed.

The cards below use write-ups that already exist. They are not a promise that your sprint will copy a format, a headcount or a result. They are the public record of startup methods inside organisations that already had customers and rules. Where a number appears, it appears because the write-up contains it.

AGL wanted people from its retail team to build skill in rapid experimentation and lean startup. The public account of the AGL session describes a full day covering the origins of the method, why it matters, the lean canvas, assumptions, prototypes, customer acquisition, validation boards, metrics, how the method sits in a company, and how to ask executives for the room to use it. Participants left with a working understanding and with ways through internal roadblocks. Feedback was exceedingly positive. The page does not claim a product launched the next week.

MetLife's question was a decision, not a class. The MetLife write-up says the task was to test appetite across the customer, the problem, the offer, the features and the business model, and to come out with a go, a no, or a pivot. Hundreds of ads and prototypes, including landing pages, were used, and the analytics were read. MetLife pivoted. The account says that saved the time and money of an expensive business case built on untested assumptions, and that staff saw many small customer-driven bets rather than a few large bets driven only by senior opinion. The quote on this page, from Brenton Charnley, is the line already published with that work. We do not paraphrase it.

Sportsbet brought together people from across the organisation who had no startup background and needed the method for a project. The Sportsbet write-up describes one day from the problem and the offer through to a pivot-or-proceed call, including assumptions, prototypes, customer tests and metrics. People left more willing to build, measure and learn quickly, with a feel for prototyping in a day, and with the lesson that the first assumption is often wrong. Leslie Barry's line on this page is the published line. It is not a new testimonial.

NPS MedicineWise asked a cross-functional group to get to market evidence faster so investment in new products and features was harder to waste. The NPS MedicineWise write-up describes a one-day course for more than thirty people, covering rapid prototyping including lean startup, plus the kinds of tools used to sketch, publish and read behaviour. People left with a method, a basic grasp of the tools, and material to use later. The recorded point is the avoidance of spending early on the wrong thing.

Standard Chartered wanted selected people in Hong Kong to champion the method, including in a large regulated financial services organisation. The Standard Chartered write-up describes a half-day on the need-to-knows. It was well received. Championing is a real job. It still needs the sponsor's stop line when those people go back to the building. A course does not install that line by itself.

Water Corporation in Perth wanted its product and innovation team to apply the method in a regulated public body. The Water Corporation write-up describes a two-day workshop on how to do that inside a large organisation with public duties, including public-sector examples and how to move faster without pretending the duties disappear. The team could see next steps on work it already had. A public duty is a fence, not an excuse to skip evidence.

Australian Unity is the engagement that looks most like a short programme. The Australian Unity write-up describes twenty cross-functional people over two days, learning the canvas, the assumptions, the metrics and the prototypes, then testing private health insurance ideas. They ran more than twenty-six experiments on four ideas: social ads, Google ads, landing pages, and interviews in the Melbourne CBD. Two ideas gathered enough for an internal business case. Two were invalidated, and the teams were to reconsider before going on. That split is the result a programme should be willing to publish.

Inkeros is not an Australian intrapreneurship story, and the card does not pretend otherwise. The Inkeros write-up describes a Canadian firm with more than six hundred employees and a two-day lean design sprint in Toronto. Too many plausible directions in AI-assisted hiring became one evidence-backed direction, with follow-on tooling to measure impact. We cite it because scattered maybes are a common starting point. We do not cite it as a local case.

If your organisation is not on this list, that is not a gap we fill with a similar-sounding story. Bring your own bet. The scoping call is how we decide whether a sprint, a short programme, or a different room is the honest next step. Design methods for a service problem live on the design thinking page when the open question is the problem people feel, not the business bet. Design thinking training is that room. It is a neighbour, not a substitute.

When the bet needs an outside company rather than an internal build, challenge-led startup matchmaking covers the searches and startup programs we run for corporates and government. The same habits apply: a named owner, a fenced pilot and a decision rule agreed before the result is in.