The review in five passes
Any pass can stop the evaluation. An appealing demo does not repair an unclear need; a useful feature does not repair data that cannot be governed.
Problem
Describe the current moment of work without naming the app.
- 01Who performs the task?
- 02In which Atlassian host product does it happen?
- 03Which information or decision is missing?
- 04What observable indicator proves that the problem is resolved?
Demonstration
Use the path that is genuinely exposed and treat every missing state as blocked evidence.
- 01Entry point, action, and feedback are actually visible.
- 02The empty state is tested when exposed; otherwise it is recorded as absent.
- 03Error and insufficient-permission states are tested or requested as evidence.
- 04Exit or uninstall behavior is observed or recorded as missing proof.
Trust
Connect every requested access to an observed capability.
- 01Permission scopes and a functional justification.
- 02Data flow, storage, retention, and deletion.
- 03Subprocessors, transfers, and regions.
- 04Security support and incident-handling readiness.
Deployment effort
Calculate the work around the license and limit the scope to the evaluated app.
- 01Initial configuration of the selected app.
- 02Import or migration of that app’s own configuration and data.
- 03An accountable internal owner.
- 04Enablement, app support, and a measurement plan.
Decision
Write the conditions that would make a yes defensible.
- 01Selected scenario.
- 02Evidence received and source links.
- 03Accepted risks and explicit exclusions.
- 04Pilot, owner, and next review date.