Skip to main content
Before creating the engagement, define the business question outside the tool.

​
Minimum setup inputs

Prepare:
  • client or workspace;
  • project name;
  • business objective;
  • process boundary;
  • relevant teams;
  • expected stakeholder groups;
  • evidence sources;
  • intended deliverable.

​
Naming convention

Use names that make the engagement recognisable later, for example: Client — Process — Quarter/Year Avoid generic titles such as “AI Project”.

​
Write useful project context

Good context explains:
  • what the client wants to understand;
  • why the issue matters now;
  • which process is in scope;
  • important exclusions;
  • known systems or constraints.
Do not pre-load the engagement with conclusions you want the evidence to prove.

​
Before inviting participants

Confirm the stakeholder plan and participant communication first. The client should understand why interviews or observations are being requested.
Exact buttons, required fields and current workspace setup flow are [PRODUCT DETAIL TO CONFIRM] and should be captured with current screenshots before external publication.