An executive can leave a public design course with a new vocabulary and still be unable to point to a decision the team made on the following Monday. The gap is rarely the definition. It is the room, the case, and whether anyone was allowed to stop an idea.
That is the choice hiding inside a search for design thinking training. The words on the brochure can match. The thing that comes back to the organisation can be a credential, a poster, a prototype nobody will test, or a method a named team can run again. Those are different purchases. Treating them as one market is how a capable sponsor buys the wrong room.
What the buyer is actually choosing
Tim Brown's essay in Harvard Business Review is still the account many executives have read. It describes a discipline that uses a designer's tools on problems that are not only product problems: understand the people in the situation, frame the problem, try a response, learn. The essay is a description of a practice. It is not a syllabus, and it is not a vendor list. Training starts when a specific group has to perform that sequence on work they own.
Collective Campus has done capability building for teams since 2015. The work is how a group frames a problem, tests a rough response and decides. AI has been part of that practice since 2022. It can cluster notes or draft a screen. It does not replace the person who has the problem, or the sponsor who is allowed to stop the work. A buyer who wants only a tool demonstration is in a different market from a buyer who wants the judgement.
The useful question is therefore not which provider sounds most like the article. It is which format returns the artefact you actually need. A credential for one person. A shared language across strangers. A decision on a live problem. A method the same team will use next month. Write that sentence before you open a second tab. If you cannot write it, you are not ready to compare proposals, and a polished proposal will choose for you.
Australia makes the mix visible. University business schools run short courses. Public workshops sell tickets. Specialist firms run in-house sessions. Agencies attach a design process to a build they hope to deliver. Internal facilitators try to hold the method after the outsiders leave. Each can be competent. They fail in different ways, and the failure is expensive when an executive mistakes one for another.
A test to run before any shortlist
Ask four questions of your own organisation before you ask them of a provider. What decision is actually waiting? Who feels the problem, in a way you could introduce them to a stranger? Who is allowed to kill an idea without calling another meeting? What would count as a bad outcome, said in advance, so a weak prototype can die?
If the decision is not real, training becomes entertainment. People will enjoy the room and return to the same backlog. If the people with the problem cannot be named, the room will invent them, and a model will now invent them faster. If nobody can kill an idea, the workshop will produce a longer list. If a bad outcome has not been defined, every prototype will be described as promising.
These questions are not a trick to disqualify providers. They disqualify briefs. A good facilitator will ask them on a scoping call and will sometimes say the session should wait. A weak proposal will skip them and send an agenda that could be delivered to any company in any city. Prefer the person who will delay you. The delay is cheaper than a day that cannot be wrong.
Also name the constraint you are least willing to say in a group. A regulation. A vendor already chosen. A launch date a board has heard. A leader who wants the original idea protected. That constraint is the real brief. A provider who is not told it will design a cheerful workshop around a fiction. A provider who is told it can either work inside the constraint or tell you the workshop is the wrong tool.
The kinds of design thinking training an executive will meet
The labels overlap on purpose. Everyone can say human-centred, prototype and iterate. The differences show up in who sits in the cohort, whose case is used, what exists on Monday, and who is expected to run the method the next time. Use those four, not the adjectives.
University and business school short courses
A university short course usually enrols a person. The cohort is mixed: people from other organisations, other sectors, sometimes other countries. The curriculum belongs to the school. The case is often the school's case, or a softened version of the student's own problem that has to be explainable to strangers who do not share the constraint.
The return is real. A shared vocabulary. Practice on a contained problem. Often a credential the person's development plan can record. A network of peers who are dealing with similar politics. For an executive who needs the language before sponsoring anything, or for a single high-potential person between roles, this can be the correct buy. It is not a consolation prize. It is a different product.
The limit is transfer. The notes do not include your customers. The credential does not give permission to stop a project. The person still has to persuade their own team, their own risk partner and their own calendar. Many capable people do this well. Many return to an operating rhythm that treats the course as personal development and leaves the work untouched. If that is acceptable, buy the course. If you needed the work to move, you bought the wrong shape.
Public workshops
A public workshop is a ticket. It can be a strong introduction, especially for someone who cannot yet convene their colleagues. The exercises are often well designed. The room is still a room of strangers, and the case is still not the live service your customers use on Tuesday.
The misuse is organisational. Attendance gets reported as capability. A learning dashboard shows a completion. The team that owns the service never sat together, never killed an idea, and never heard a user react. If you need exposure, buy the ticket and call it exposure. If you need a decision, a ticket will not make one.
In-house capability building
An in-house workshop enrols the people who share the problem. The case is theirs. A sponsor can be in the room when an idea is cut. The output is a problem statement, notes, a list of what was killed, and something rough that a person outside the team could react to. The point of design thinking training in this shape is that the same people can run the sequence again without the facilitator.
This is the format Collective Campus runs. It suits a leadership group that must choose what to fund, and a delivery team that will carry the next test. It is a poor buy when there is no live problem, when the sponsor wants the original solution protected, or when the organisation actually wanted a credential for one person's file. We would rather say that on the call than deliver a cheerful day around a locked decision.
In-house work is also where tailoring is real. The industry constraint, the procurement step, the clinical rule, the partnership agreement: these are not colour on a generic exercise. They are the conditions the prototype has to survive. A session that could be delivered unchanged in a bank, a council and a law firm has not been tailored. It has been branded.
A method attached to a build
Some agencies run genuine design workshops as the front of a build they expect to deliver. The interviews can be good. The prototype can be good. The commercial pressure is to continue. That can be a sound commercial relationship when you want a partner to ship the thing.
It is a different purchase from capability building. Ask who facilitates the next round, after this engagement. If the answer is only the vendor, you are buying delivery with a workshop at the front. There is nothing dishonest about that, unless it is sold as the team learning to do it themselves. Read the proposal for the word transfer, and then ask what transfer looks like in the calendar of your own people.
An internal facilitator
A strong internal facilitator is the point of the work, not a competitor to it. The outside session should make that person more useful: a shared sequence, a sponsor who has seen a cut, a first prototype that was allowed to be rough. The outside session fails if it leaves the internal facilitator with a method the leadership group has never watched and will not protect.
If you already have that person, ask the provider how the day hands over. Who keeps the notes. Who is allowed to call the next test. What the sponsor will say when someone uses the method on a sacred project. Training that ends when the facilitator leaves the building has rented a skill for a day.
Executives and the team are not the same buyer
An executive session and a team session can share a name and still need different rooms. The executive is usually trying to see the decision: which problem is real enough to fund, which idea stops, who owns the next conversation with a user. The team is usually trying to do the steps: sit with someone, write the problem, make the rough thing, survive the reaction.
An executive-only room is the right buy when the leadership group has not agreed the problem, or when every proposal arrives as a solution looking for permission. The work in that room is the decision. People should leave with a sentence they are willing to say, a short list of what will not be funded, and a named owner. They do not need a performance of sticky notes. They need to practise stopping something in front of each other, while it is still cheap.
A team room is the right buy when the problem is live and the people who will carry the next month are in the chairs. The output is operational. Notes in the words that were said. A problem statement a sponsor can read back. A cut list. A prototype. A way to repeat the sequence. Product, service, people and culture, policy, a professional practice, a council group: the industry changes the constraint, not the sequence.
The common failure is to train one and hope. Executives who never see a prototype get killed keep asking for finished cases. Teams who learn the method and then meet a sponsor who wants the original idea back will stop using it. The sturdier pattern is a short pass with the people who decide, then a pass with the people who do the work, on the same problem, with the sponsor returning to hear what the test changed.
If you can only buy one room, buy the one where the blockage sits. A team that already knows how to interview, and a leadership group that will not hear a no, does not need another ideation tool. It needs the leadership group in the cut. A leadership group that is aligned, and a team that has never sat with a user, does not need another offsite. It needs the interviews.
What the agenda has to show
Ask for the agenda as sessions, and ignore the theatre of a clock if the provider has not yet heard your brief. A serious in-house agenda can be shorter or longer once the problem is known. What should not move is the order. A public walk-through of that order is in what a corporate design thinking workshop should cover. Use it as a checklist against the proposal in front of you, not as a script to insist on before the scoping call.
Before anyone is allowed to ideate
The first sessions frame the challenge and get into the world of the person who has it. Nielsen Norman Group's note on design thinking is a fair public standard here: the practice still depends on learning from users, not on a brainstorm with better stationery. Notes should stay in the words that were said. An empathy map is a holder for those notes. It is not a place to invent a lifestyle the team finds attractive.
If the proposal jumps from introductions to ideas, it is teaching optimism. The frame should pull the solution out of the sponsor's opening sentence and park it. The research should say who will be heard, and what happens if those people cannot be reached. A session that pretends a persona written in the room is the same as a conversation is not being careful. It is saving time it should not save.
The ideas, and then the cut
Divergence is the easy half to sell. People like producing options. The cut is the half that makes the day training rather than a suggestion box. Ideas should be written before they are spoken, so the most senior voice does not set the menu. The problem statement should be the test, not the energy in the room.
Watch what the proposal says executives will do in this session. If they are there to inspire and then leave, they will miss the only moment that teaches them how the team decides. If they are there to bless the idea they walked in with, the team will learn that the method is decorative. A useful executive presence is a person who will name what they will not fund, in the room, while the idea is still a sketch.
A prototype a person can react to
The kept idea should become something rough: a sketch, a fake click-through, a role-played service moment, a one-page form, a script. Fidelity stays low so a change is cheap and so comments land on the idea rather than the colour. A model can draft the words. A person still chooses what is shown, and the draft should look like a draft.
Then someone who did not make it reacts. The team watches what the person does, not only what they say they would do. The room decides to continue, change, or stop. If the proposal has no moment where a weak idea can die, you are buying a presentation. Ask what the team is supposed to do when the reaction is poor. The answer should be allowed to be stop.
Methods worth asking about
The methods are public. You should hear them named plainly. Interviews and observation. Empathy maps that trace back to notes. Journey maps when the work really is a service someone already uses. How-might-we statements as a bridge, not as a result. A diverge-then-close rhythm. The Double Diamond from the Design Council is the simplest public picture of that rhythm: open, close, open, close. Teams that only open leave with a pile. Teams that only close leave with the first idea that sounded senior.
Ask which method will be used on your material, and which will be demonstrated on a toy example. A toy example can teach a hand movement. It cannot teach the political moment when a senior person's idea is the one that should be cut. Prefer a provider who will use your constraint in the exercise. A council process, a clinical handover, a hiring step, a client matter. The method does not float above the constraint.
Also ask what will be refused. A facilitator who will run any tool you name is collecting techniques. A facilitator who will say that a journey map is the wrong tool until the user is agreed, or that a prototype is premature until the problem is a sentence, is protecting the sequence. You are paying for that refusal as much as for the exercise.
Prototypes deserve a specific question. What materials? Who is allowed to make them? How rough is rough? A proposal that promises a high-fidelity concept by the end of the session is often promising a picture the room will be reluctant to kill. Rough is not a lack of craft. It is a decision to keep the idea cheap until a person outside the team has reacted.
Outcomes to insist on
Judge the offer by artefacts, not by adjectives. A problem statement the sponsor can read back, with the user and the behaviour named. The notes, or an empathy map that cites them. A list of ideas kept and a list of ideas killed. One rough prototype, and a record of who reacted to it. A named owner for the next test, and the evidence that would stop the work later.
Executives should insist on a decision in sentences. What will be tested. What will not be funded. Who speaks to the next user. What would make the team stop. If a proposal describes outcomes as mindsets, confidence and alignment, ask for the page those mindsets will be written on. Confidence without a killed idea is a mood.
Teams should insist on having done the uncomfortable step themselves. Watching a facilitator demonstrate an interview is not the same as running one. Watching a cut is not the same as killing your own idea. The transfer you want is ordinary: next month, without the outsider, someone on the team can set up the sequence and the sponsor will recognise it.
Do not insist on a culture change by the end of the workshop. Culture is what people do when the visitor has gone. A workshop can make the next three uses more likely, if a sponsor protects the time and treats a stopped idea as a success. A proposal that promises a new culture by Friday is selling a feeling. You can buy a feeling elsewhere, more cheaply, and with less disruption to the people who still have to ship the work.
University short course or in-house workshop
Neither format wins in the abstract. The mistake is to rank them as if they were the same shelf of product. Put the need in a sentence, then see which format can return it. Collective Campus sells the in-house workshop. The comparison below is still meant to be usable if that means you should not hire us.
When the short course is the better buy
Buy the university or business school short course when one person needs the language and a credential, and the team is not ready to bring a live problem. Buy it when the executive is new to the idea and would waste a team's day by learning the vocabulary in public, on the team's real customers. Buy it when the development plan is the actual customer of the purchase, and everyone honest in the room knows that.
Buy it when you want a mixed cohort on purpose. Strangers can ask questions your own hierarchy will not. A school can hold a standard your internal calendar will interrupt. Those are features. Use them when the goal is a more capable individual who will later sponsor a team, not when the goal is a decision this quarter.
A short course is also the better buy when you cannot yet name the user. Paying an in-house facilitator to help you invent one is a poor use of the team. Do the course, or do a smaller piece of research, and come back when a person and a problem can be introduced in a sentence.
When the in-house workshop is the better buy
Buy the in-house workshop when an intact team shares a live service, product, policy or internal process. Buy it when a sponsor can attend the cut and is willing to stop something. Buy it when the artefact you need on Monday is a decision and a method, not a line on a CV. Buy it when the constraint is specific enough that a teaching case would teach the wrong lesson.
Buy it when several teams need the same sequence and you can name who will coach the next one. The first room is the demonstration on real material. The value is the second and third room, run with less outside help. If you cannot name the internal owner, budget for that gap or do not pretend the capability will remain.
Buy it in the city where the work actually sits when being together matters. A physical prototype, a new group, a sponsor who needs to watch the cut: those are reasons to sit in one room. A distributed team and a paper process can be remote without apology. The standard of the method does not soften because the room is a screen. The design of the session should, so remote is built as remote and not as a camera in the corner of a workshop.
What neither format can do
Neither will repair a strategy that is three priorities pretending to be one. Neither will give a team permission the sponsor will revoke on Monday. Neither will produce evidence if nobody with the problem can be contacted. A workshop can reveal that the permission is missing. It cannot supply the permission.
Neither should be asked to bless a decision that has already been made. If the feature is chosen, the vendor is chosen, and the date is public, a design workshop is a costume. You can still run a session on how to implement with less harm. Call it that. Do not call it discovery.
Questions to take into the scoping call
The scoping call is the product sample. You are not only buying a day. You are buying the judgement of the person who will shape it. A provider who cannot adapt the questions below to your constraint, or who answers all of them with a slide title, is showing you the workshop you would get.
Ask who will be in the room, by role, and who is explicitly not required. Ask what the team must bring, and what will be refused if they do not bring it. Ask how users are included, and what the fallback is when they are not. Ask to see a sample agenda as sessions, and ask which session would be dropped if the brief turned out to be a solution looking for permission.
Ask what the sponsor is expected to do at the moment of the cut. Ask what the artefacts are. Ask what happens in the following fortnight, and who owns it. Ask how AI is used, and which outputs are forbidden to count as research. Ask how the work is priced. A straight answer is that the shape is tailored after an initial conversation, because the problem, the people and the choice of executive room or team room change the work. A rate card that ignores those is a fiction, or a sign that the session is the same every time.
Ask what they will not do. The useful answers include: we will not pretend a generated persona is an interview, we will not protect a pre-chosen solution, we will not promise a culture by Friday, we will not award a university credential. If a provider will not name a refusal, they will not refuse anything once the room is booked.
AI-assisted design thinking, and the question to add
Any current proposal will mention AI. Treat that as a claim to test, not as a feature to collect. Used well, a model clusters notes the team already gathered, drafts problem statements for the room to reject, and produces the words on a rough screen. It raises the number of drafts you can look at. It does not raise the quality of the decision on its own.
Used badly, the model supplies the user. A generated persona, a generated quote, a generated journey. The page looks like insight and has no source. Teams that are behind on research are tempted, because the output resembles the artefact the agenda asked for. The facilitator should forbid that substitution in the same breath as they allow the draft. If they cannot explain the difference, they have a tool policy and not a method.
Executives set the price of this shortcut. If speed of output is what gets praised, the team will bring generated output. If the question in the room is who we heard this from, the model stays a drafting tool. A workshop can practise the question. It cannot invent the praise. Ask the provider how they will behave when a senior person prefers the polished generated version to the rough tested one. That moment is the real curriculum.
There is a narrower format when the brief is already one bet and the team wants AI inside the making of the prototype. Do not let a provider blur that into a general capability program. A sprint that ends in a decision on one idea is not the same as training a team to frame the next ten problems. Buy the one you named at the start. If you need both, sequence them, and do not let the sprint replace the skill.
Sydney, Melbourne, Brisbane, and everywhere else
For an Australian organisation the city is a delivery detail, not a different method. Design thinking training in Sydney, design thinking training in Melbourne and design thinking training in Brisbane should show the same sequence, the same artefacts and the same right to stop. What changes is the room, the travel, and the local brief. A hybrid group split across those cities is normal. A team outside them can work remote. None of that is a reason to accept a thinner standard.
Use a city page to check that a provider really facilitates there, and to see whether the examples they cite are even in the same kind of work. Use the national account to decide whether the method is what you need. A page that changes only the city name, and keeps a generic case, is a national brochure with a suburb painted on. Ask what, in that city, would be different about the brief, not about the catering.
Government buyers have an extra check. A council or an agency is not a startup in a costume. The prototype has to survive a process, a duty, a public complaint. Training that treats those as annoyances will produce ideas the organisation cannot run. Training that puts the constraint on the table will produce fewer ideas and better ones. Prefer fewer. The published design thinking accounts we are willing to point at, including councils and a law firm, sit on the workshop page and stay inside what those write-ups already say. If a salesperson adds a result that is not written down there, ask them to send the page.
Where Collective Campus fits, and where it does not
We fit when you have a live problem, people who share it, and a sponsor who can stop an idea. We fit when you want capability building rather than a credential, and when you want the team to be able to run the next session with less of us. We work in person in Sydney, Melbourne and Brisbane, hybrid across them, and remote when that is the honest shape of the group. The format is tailored after an initial conversation. We do not publish a price, because a price without the brief would describe a session we are not going to run.
We do not fit when you need a university credential, a public cohort, or a single person developed in isolation from their team. We do not fit when the solution is already chosen and the room is there to endorse it. We do not fit when you want a build partner whose workshop is the front door to a delivery contract. Those can be legitimate needs. They are not this one. A scoping call that ends in a referral, or in a delay, is a successful call.
Steve Glaveski founded Collective Campus and still facilitates. The design thinking room is also led by facilitators whose daily work is this method, including in public-sector and corporate teams. You should ask who will actually be in your room, not who is on the masthead. A founder on a brochure is not a facilitator on the day. The day is the product.
If you are still comparing, take the checklist below into every call, including ours. The provider who welcomes it is showing you the standard. The provider who is irritated by it is also showing you the standard.
Read a proposal the way you would read a business case that is not allowed to fail. Mark every sentence that would still be true if the client name were swapped. Those sentences are the generic core. Then mark every sentence that could only be true of your problem, your user, or your constraint. If the second set is thin, the provider has not started the work, and the workshop will spend its first hour discovering what the proposal should have asked. A scoping call that produces a rewritten agenda is a better signal than a proposal that arrived complete.
Ask for one example of a session that stopped an idea, described without a new number and without a client you cannot check. You are listening for the mechanism. Who objected. What the artefact was. What the sponsor said. What the team did the next week. A story that only has energy, alignment and a pile of concepts has not yet shown a decision. You can still hire that provider for a different job. Do not hire them for this one and then act surprised when the list comes back longer than it went in.
Finally, decide what you will do if the honest answer is to wait. Waiting is a legitimate outcome of a good selection process. A team that cannot name a user, a sponsor who cannot attend, a solution that is already on a public roadmap: each of these is a reason to buy nothing this month. The executives who get value from design thinking training are the ones who can leave a shortlist empty. The ones who need a workshop because the quarter has a training line will get a workshop, and they will get the artefact that line item was shaped to buy.
A checklist for the call
- The need is written as one sentence: credential, exposure, decision, or a method the team will repeat.
- The live problem can be named, or you have admitted there is not one yet.
- The user can be introduced, or the provider has said what happens if they cannot.
- A sponsor who can stop an idea is identified, and is expected in the cut.
- The agenda shows framing and contact with users before ideas.
- Ideas are written before they are spoken, and then cut against the problem statement.
- The prototype is rough on purpose, and a person outside the team can react to it.
- A poor reaction is allowed to end the idea.
- AI may draft. AI may not count as the research.
- The artefacts on Monday are listed as things a person can point at, not as mindsets.
- Someone inside the organisation is named to run the next session.
- The provider has said what they will not do, including protecting a pre-chosen solution.
- Price is discussed after the brief, not copied from a rate card that ignores it.
- You know whether you needed a university short course instead, and you are willing to buy that instead.
After you choose
The workshop is not the capability. The following month is. Put the next test in a calendar before the room is booked, with the internal owner and the sponsor both named. If that calendar cannot be found, the training will be a pleasant interruption. Protect one hour in the following fortnight for the team to look at what the user actually did, and to decide again. A single decision, revisited, teaches more than a binder of templates.
Then judge the purchase on the sentence you wrote at the start. If you needed a credential, did the person earn the one they needed? If you needed a decision, can you point to what stopped? If you needed a method, did someone inside the organisation run the sequence without the visitor? Those are ordinary tests. They are also the ones a brochure cannot pass on your behalf. Choose the room that can fail them in advance, out loud, while you are still allowed to walk away.
