Skip to content

Assessment and priorities

Know what to examine first.

An assessment of real work, the people doing it and the information flows around them to decide what should be tested or improved first.

Discuss your priorities

What you receive

A view of the user task, visible and behind-the-scenes work, tools and data exchanges, followed by plausible interventions and the evidence needed to choose among them.

  • Observed problems, affected people and desired outcomes
  • Options to examine: a process change, connection, automation or interface
  • Critical assumptions, dependencies and a first useful test

Your participation

Process owners describe the actual work, share examples and validate the starting information. The scope identifies the teams and processes included.

The decision it enables

Choose a first assumption to test, implement a bounded improvement when ready, or clarify what remains unknown. A unified interface is considered where the task calls for one. The assessment does not include implementing every option.

Which assumption should we test first?

Fictional positions · No measured impact or client result.

Fictional examples: each position needs investigation and a test
#TaskAssumptionSmallest useful test
01Prepare an appointmentWould shared context help the process owner?Try a fictional view with one request.
02Follow up on a quoteWould a controlled draft prevent missed follow-ups?Have a person review an unsent draft.
03Handle an exceptionWould a named owner reduce waiting?Try a manual assignment on one case.
04Review an invoiceIs the needed information accessible?Examine one record and its access rights.
05See work across teamsWould a shared view help a real decision?Show a mockup to the people involved.
Read the explanation

Illustrative estimates only. The plotted position does not establish user need, technical access or business value. Compare each task, critical assumption, dependency and available evidence before deciding what to test.

  1. 01: Appointment Fictional position to check against the need, dependencies and evidence.
  2. 02: Quote Fictional position to check against the need, dependencies and evidence.
  3. 03: Exception Fictional position to check against the need, dependencies and evidence.
  4. 04: Invoice Fictional position to check against the need, dependencies and evidence.
  5. 05: Across teams Fictional position to check against the need, dependencies and evidence.

Next step

Where does the work get stuck?

Start with the processes and questions you want to understand.

Discuss your priorities