Run stakeholder use-case testing

Stakeholder use-case testing collects structured evidence from people who will use or be affected by the solution. The project Stakeholder workflow pairs a stakeholder, project vendor and published stakeholder evaluation. The respondent follows a secure external invitation without becoming a full workspace member, and the submitted score can contribute to the stakeholder or sandbox comparison stream.

Before you start

• Define the use case, success criteria, testing environment and support window before inviting anyone.

• Publish the stakeholder evaluation and add the target vendor and stakeholder with a verified email.

Step by step

1. Open stakeholder testing

From the project, open Stakeholder and review existing invitations and completion status so you do not duplicate an active test.

2. Choose or add the stakeholder

Select an existing stakeholder or use the quick-create path with their name and email. Explain why they are being invited and how their response will be used.

3. Select vendor and use case

Choose the project vendor being tested and the published stakeholder or use-case evaluation. Confirm the form matches the sandbox or scenario the person will experience.

4. Send the secure invitation

Send the respondent-specific link. The external journey uses its token and may require an email one-time-code step; the stakeholder does not receive broad project access.

5. Support testing without coaching scores

Resolve environment access and factual questions, but do not tell the stakeholder which rating to choose. Keep credentials in the approved secure channel.

6. Monitor and review results

Track opened, in-progress and submitted state, remind incomplete respondents and review their evidence. Confirm the stakeholder or sandbox stream weight before relying on the score in Compare.

What happens next

• Use several relevant stakeholders where one person cannot represent the whole user population.

• Create a new invitation and version when the use case or environment changes materially, preserving earlier results.

Troubleshooting

The evaluation is not selectable

Confirm it is the stakeholder or use-case type, belongs to the project and has a published release.

The stakeholder link fails

Use the newest invitation, verify the invited email and complete any current one-time-code step. Resend from the existing assignment rather than sharing another person’s link.

A submitted test does not affect comparison

Check that it was submitted for the intended vendor and evaluation and that the relevant project stream is enabled with a non-zero weight.

Related guides