You have an hour at the next product offsite, a team that needs to take more ownership, and a request to “teach continuous discovery.” The session may be worth running. It just cannot carry the expectation that people will leave able to practice discovery independently.

The useful question is not whether to book a talk, workshop, or coach. It is which change you expect to see afterward, how much practice that change requires, and whether your operating environment will allow it. Answer those questions first, and you can buy the right intervention without overselling it to yourself or your team.

Define the capability before you choose the training

“Learn continuous discovery” is not a workable training objective. Continuous discovery combines multiple skills, habits, and ways of thinking. A person might understand the vocabulary, struggle to use a practice with guidance, or use it once and then abandon it when delivery pressure returns. Those are different states, even if each person attended the same session.

Start by separating the service you are purchasing from the benefit you want:

• A talk is a service. Awareness, shared language, or motivation may be the benefit.
• A workshop is a service. A first guided attempt at a selected practice may be the benefit.
• Coaching is a service. Increasingly independent performance, reinforced through repetition and feedback, may be the benefit.
• A training program is a service. A durable change in how the team works may be the benefit, provided managers and operating conditions support it.

This distinction matters because the common request is framed as a service while the expectation is a capability. A leader asks for a keynote but hopes product managers will become more accountable, talk to customers more consistently, and make better decisions. The speaker controls the keynote. The hoped-for behavior depends on practice, management, decision rights, time, and access to real work.

Write the desired change as an observable sentence before discussing format:

“After this investment, the team will be able to ______ on real product work, with decreasing help from ______, and managers will reinforce it by ______.”

Good answers name something you could actually notice: the team can perform a selected discovery practice without the facilitator; evidence from discovery changes a decision; the practice recurs after the event; or a manager can recognize weak execution and coach it. “Think differently,” “be inspired,” and “take ownership” are intentions, not observable capabilities.

Match the format to the outcome it can reasonably produce

A short intervention can be valuable when its job is explicit. The problem begins when a calendar slot is treated as a shortcut to behavior change. Know-how can move quickly; skill and mindset changes need repeated practice.

Format	Realistic outcome	Evidence to look for	Expectation to reject
One-hour talk	A shared mental model, useful language, motivation, and a picture of a different way of working	People can explain why the change matters and identify an appropriate next step	The team will perform continuous discovery independently because it heard the concepts once
Four-hour workshop	Deeper understanding and an initial guided attempt at one or more practices	Participants complete a relevant exercise, receive feedback, and know what they need to repeat on live work	A few hours of practice will create durable habits or resolve organizational constraints
Ongoing training or coaching	Repeated application, feedback, correction, and growing independence	The behavior appears in real work, improves over time, and becomes less dependent on the facilitator	Coaching alone will compensate for missing customer access, time, authority, or managerial support

Do not dismiss the talk simply because it cannot produce mastery. A talk can introduce a common frame, make a new operating model imaginable, and give people permission to try a low-risk behavior. Those are legitimate outcomes. A talk becomes more useful when it sits inside a longer development effort rather than being presented as the entire effort.

The same discipline applies to workshops. Four hours creates room for explanation, questions, and guided work, but it does not provide much repetition. If the team has no scheduled opportunity to use the practice afterward, the workshop is an isolated experience rather than the beginning of capability building.

Longer is not automatically better. A poorly focused program can repeat concepts without improving performance. Laerdal Medical’s six-month model paired outside inspiration with follow-up training. The important design choice is not the six-month duration. It is the connection between inspiration, application, feedback, and continued support.

Build a practice loop, not a curriculum download

A discovery capability develops more like a practiced discipline than a set of facts to remember. Your program therefore needs a place to try the work, see the result, receive feedback, make a correction, and try again. Without that loop, participants may become fluent in the terminology while their day-to-day behavior remains unchanged.

A practical learning loop has seven parts:

1. Select one target behavior. Do not make the first objective “adopt continuous discovery.” Choose the next behavior the team needs to perform reliably.
2. Attach it to live work. Use a current product decision, customer question, or opportunity. A fictional exercise can teach mechanics, but it cannot expose the constraints the team will face in its actual environment.
3. Teach only the know-how needed for that attempt. Give people enough explanation to act. Save adjacent concepts until they become relevant.
4. Let the team perform the practice. Watching an expert is not evidence that participants can do the work themselves.
5. Give feedback on the attempt. Feedback should identify what was effective, where the reasoning broke down, and what to change on the next repetition.
6. Schedule the next repetition before the session ends. Name the work it will be applied to, who will participate, and where feedback will come from.
7. Reduce support gradually. The goal is not permanent dependence on a trainer. It is sound performance when the trainer is absent.

This design also prevents an easy curriculum mistake: trying to expose the team to every discovery habit at once. Broad exposure can be useful for orientation, but capability grows through focused repetitions. It is usually more informative to watch a team apply one behavior to real work several times than to hear it explain many practices it has never attempted.

The manager needs a role in the loop. That does not mean taking the work back from the team or approving every move. It means asking for the evidence behind a decision, helping the team inspect the quality of its process, protecting time for repetition, and allowing new evidence to affect the plan. If managers continue to reward only delivery certainty, employees will correctly infer that discovery is optional.

Remove the conditions that training cannot fix

Some teams do not have a learning problem. They have an environment problem. More instruction will not help if people understand the behavior but lack permission, access, time, or decision rights to use it.

Treat open questions as diagnosis, not dead time at the end of a session. Q&A often exposes the organizational obstacles that determine whether training can transfer into daily work. Ask participants what would stop them from applying the practice next. Their answers belong in the program plan.

Classify each obstacle before buying more training:

• Access problem: The team cannot reach customers, obtain relevant evidence, or navigate the internal process required to do so. Assign an owner to unblock access rather than reteaching the method.
• Capacity problem: Every available hour is committed to delivery. Reserve explicit room for discovery work; otherwise the urgent queue will consume the intended practice.
• Permission problem: The team is told to discover but cannot change priorities, challenge assumptions, or alter a planned solution. Clarify which decisions the team owns and which remain leadership decisions.
• Incentive problem: Leaders ask for evidence but evaluate success only by whether predetermined output shipped. Make learning and decision quality visible alongside delivery.
• Coaching problem: The external facilitator leaves and nobody can assess the next attempt. Decide who will observe, question, and support the behavior between formal sessions.
• Scope problem: “Be more customer-centric” or “take ownership” is too broad to practice. Replace it with a behavior that can be attempted, observed, and improved.

Five questions reveal most expectation gaps before the contract is signed:

1. What should participants be able to do afterward that they cannot do now?
2. Where will they practice that behavior on real work?
3. Who will give feedback after the formal session?
4. What policy, commitment, or management behavior could prevent them from applying it?
5. What evidence will distinguish awareness from independent capability?

If those questions have no answers, narrow the promise. Call the event an introduction, use it to build a shared frame, and make the next investment decision after the barriers are visible. Honest scope protects both the team and the training provider from being judged against an outcome the format could never create.

Measure transfer into work, not attendance at the event

Attendance confirms that people were present. A satisfaction score confirms that they liked the experience. A knowledge check confirms that they remember an idea. None of those measures tells you whether continuous discovery has entered the team’s work.

Evaluate capability as a progression:

• Understanding: The person can explain the practice and when it is useful.
• Guided performance: The person can attempt it with prompts, examples, or facilitator support.
• Independent performance: The person can use it appropriately on live work without step-by-step help.
• Recurring behavior: The team returns to the practice when new decisions arise, including when delivery pressure increases.
• Organizational support: Managers recognize the behavior, coach it, and remove the constraints that would otherwise suppress it.

At each review, ask for concrete evidence: What did the team do? What improved from the previous attempt? What decision did the work inform? Where was facilitation still required? Which operating barrier remains? The answers tell you whether to repeat the same practice, add coaching, change the environment, or move to the next capability.

Business and customer outcomes still matter, but they are influenced by more than training. First establish whether the intended behavior transferred into work. Then inspect whether that behavior is improving the quality and speed of product decisions. This sequence keeps you from crediting a seminar for every favorable result or blaming it for an operating system that never allowed the behavior to take hold.

Key takeaways

• Buy a talk for shared language and possibility, not independent performance.
• Use a workshop for an initial guided attempt, then schedule the next repetition before people leave.
• Expect capability only when real work, repetition, feedback, and decreasing facilitator support are part of the design.
• Separate skill gaps from access, capacity, permission, incentive, and coaching problems.
• Measure recurring independent behavior and its effect on decisions, not attendance or enthusiasm alone.

For your next planning meeting, bring one sentence naming the behavior the team must perform, one real product situation where it will practice, one person responsible for feedback, and one organizational barrier a leader will remove. If the sponsor only wants awareness, book the talk and label it honestly. If the sponsor wants capability, put the practice and management follow-through on the calendar before putting the training on it.

References

• Product Talk — Training Expectations: All Things Product Podcast with Teresa Torres and Petra Wille

---