liveBook · Manning

Role-playing scenario

As explained in Think Like a CTO

A role-play scenario is a structured simulation in which participants act as specified roles to reveal processes, knowledge, or behavior.

A role-playing scenario is a structured simulation in which participants act as specified roles to reveal processes, knowledge, or behavior. In engineering due diligence, it creates a relaxed way to understand a team’s product, language, priorities, and working knowledge. section 14.5.2

A customer-oriented role-play can help an evaluator:

  • Learn the language and terms used with clients, improving the precision and comfort of follow-up questions. section 14.5.2
  • Identify the product features that matter most to customers and distinguish them from capabilities that are rarely used. section 14.5.2
  • Probe operational details naturally as participants demonstrate the product, such as where uploaded files go and whether they are backed up. section 14.5.2

Customer onboarding simulation

Ask participants to pretend they are onboarding a new customer, including demonstrations and training. Afterward, pause for a break before continuing with the second role-play session. section 14.5.2

How Think Like a CTO covers it

How deep it goes
Explains one onboarding scenario and its investigative purposes, but does not detail the second scenario’s content.
Examples
Uses a new-customer onboarding demonstration, product training, file uploads, storage questions, and backup questions.
What you can do after
Evaluate team communication, customer priorities, product usage, and operational details through a low-pressure simulation.
How it connects
Connects due diligence with customer onboarding, product demonstrations, training, and operational questioning.

Also explained in

Compare how 2 books explain role-playing scenario →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.