# Plan a useful first evaluation

Choose one decision, define a useful result, and agree what the first cycle will prove.

AI narration: Ava · female. Actual public pages and illustrative examples.

## 0:00 — Start with a decision.

A useful software evaluation begins with a decision your team needs to make. Start small: one workflow, a representative project, and a result that your manager and reviewers can assess together.

## 0:13 — Make the question specific.

For example, can we explain why the expected finish moved between two updates? That is more useful than asking to see every feature. It connects the walkthrough to a real management conversation.

## 0:26 — Build the working brief.

On Getting started, choose your team and first priority. The working brief brings together the question, the people, the input, and a useful result. It gives the first meeting a clear agenda.

## 0:39 — Agree what good looks like.

Agree what good looks like before the evaluation. For this example, look for a traceable finding, a clear explanation, and a next action. If you measure effort, compare reviews with similar scope and quality requirements.

## 0:55 — Confirm the working arrangements.

Begin with demonstration data if project information is not ready to share. Agree access, data arrangements, responsibilities, timing, and commercial terms before a project evaluation. Save the working brief so everyone starts from the same question.

## 1:12 — Make the first cycle useful.

A successful first cycle gives you evidence for the next decision. Bring the working brief to your walkthrough, agree how the result will be assessed, and decide together whether to expand the scope.