What a corporate innovation workshop should leave the sponsor able to decide

The sponsor who pays for the day often leaves before the decision. The team fills a wall. The bet that needed a yes or a no is still open when the room empties.

If you are about to commission this, read the agenda for a named bet and a line the sponsor will sign before they go. A promise of culture change, with no decision attached, is a weak buy. You want one idea on the table, one test that could change your mind, and the person who can stop the work still in the chair.

The idea you bring

The best days I run start from a live idea the business is already arguing about. A new offer the sales team has not agreed to carry. A service a customer keeps asking for that nobody has priced. A venture the innovation group has been modelling for a quarter. A canned case from another industry lets everyone be clever, and clever people leave your pipeline exactly where they found it.

Write the idea as a belief. Who it is for. What they would do if it were true. Why it would matter to revenue, cost or trust. A theme such as digital transformation gives the room nothing to kill. A belief you can disprove in a week gives the room a job. I push back when the brief is a problem space with no bet inside it, unless the sponsor is honest that the first hour is for choosing one. Choosing can be the work. Pretending you already chose, and then spending the day on three ideas so nobody is disappointed, wastes the room.

Bring what you already hold. A draft offer, a complaint that keeps returning, a sales objection, a constraint from risk or legal. Those artefacts stop the room inventing a customer. They do not replace a conversation with someone who would have to buy, use or block the thing. If nobody owns that conversation before the day, the interviews quietly become a panel of colleagues. Colleagues know the politics. They also built the current offer, and they will defend it when they are asked to play the buyer.

The picture people buy

Gary Pisano, writing in Harvard Business Review, describes how managers in his seminars reach for the same picture of an innovative culture. Tolerance for failure. A willingness to experiment. Psychological safety. Heavy collaboration. A flat structure. He notes that research supports a link between those behaviours and better innovative performance. The piece also says creativity is messy and needs discipline and management.

I use that when a buyer asks for a culture day. The picture is attractive, and it is incomplete as a brief. A room that only practises being open will produce more ideas and no way to stop the weak ones. Discipline is the part the sponsor has to supply. Which assumption is riskiest. What result would end the idea. Who is allowed to say so while the idea still has a champion in the room.

Who has to stay

Our lean startup and product sprint is built for this decision. Innovation and venture teams, product squads and the sponsor who funds or kills the work are the people the day is for. The sponsor has to stay for the decision, not only the welcome. If they open the session and leave, the team will design a test that dies in the next steering meeting.

Bring the person who knows the customer or the operator, and someone who can make a thin version the same day. A prototype, a concierge offer or a landing test. Past a small group, the person who does the work stops talking and the day turns into a presentation. I would rather have the sponsor, the operator and a builder than a full leadership offsite watching them.

What the corporate lean startup day should test, once the bet is on the table, is in what a lean startup workshop for corporate teams should test. The longer note on writing the line before you fund anything is test the bet before you fund it. Programmes that only ever practise on hypothetical cases are one of the types of innovation theatre I see most often.

The smallest test

The test should be the smallest experiment that could change your mind, using resources you already have. A landing page. A concierge version run by hand. A conversation with people who would have to switch. The room should leave holding evidence it collected, or a test it can run the following week with an owner and a date. A thicker build can wait until that evidence exists. Most of the time it should wait.

Agree the kill line before anyone is attached to the outcome. What result ends the idea. What result earns another test. What result would justify a thicker build. Write it where the sponsor can see it, in language a budget meeting will accept. If your funding process still demands a full business case before any test, the evidence will lose to a spreadsheet. Settle that on the call, or the day will produce a result your process cannot use.

Regulated teams can do this. The test has to learn something without putting a customer or a licence at risk. A paper offer, a role-played call or a run on dummy data can teach you whether the bet is real. Put the constraint in the brief so the room designs a test that can actually run. Hide the constraint and the team will design a clever trial you will have to cancel on the way out.

A day or a longer sprint

A single day can name the bet, find the riskiest assumption and design the test. A multi-day sprint gives you time to build the thin version and put it in front of someone outside the team before you decide. Both run in person or remote. The remote version needs shorter blocks. A long stretch of silent sticker work on a webcam wears the room out before the useful argument starts. The customer conversations still work on video, provided someone has booked them.

If the brief is still a solution looking for a problem, you are early for this sprint. Frame the problem with the people who live it before you spend a day testing a bet nobody can describe. I will say that on the scoping call. Booking the sprint anyway, because the date is in the diary, produces a tidy experiment on the wrong question.

What a proposal gives away

Some warning signs show up before you sign. The agenda lists a stack of canvases and no customer. The pack promises a culture shift and never names an output. The facilitator offers a case from another company so the team can practise without touching a live bet. Any one of these means the day will feel busy and the pipeline will look the same next month.

Another sign shows up in the guest list. The sponsor is optional. The people who would have to sell, operate or block the idea are absent. You will leave with a plan the people who can enact it have not seen. I would rather move the date than run the room without them. A showcase for people who were not in the work teaches the company that innovation is a performance.

Watch the language in the proposal as well. A document that cannot name the bet in one sentence will struggle to become specific at 9am. Ask for the sentence. If they cannot write it, they have not understood the brief, and another workshop will not repair that on the day. This sprint aims at a business bet you can test. A screen can be part of the thin version. The decision is still to stop, to change the test or to fund the next one.

What to ask before you pay

1. Which live bet will we bring, and who has agreed it is the one?
2. What result would end the idea, and will the sponsor stay to sign that line?
3. What is the smallest test, and whose week will it use?
4. What will we hold at the end, and which meeting will use it?

The last question separates a workshop from a wall. If the answer is a showcase with no date, you are buying a story. Ask it while changing supplier is still cheap. If you want the day, send me the bet in one sentence, the name of the sponsor who can stop it, and whether you need one day or a longer sprint. We will shape the work around that bet and plan the conversations with you.