Fictional sample assessment

From enquiry to a clear next action

A fictional Miami service team receives project enquiries by email, records them in a spreadsheet, and shares work between an enquiry owner and a delivery lead.

All people, workflow observations, findings, and recommendations in this sample are fictional. Measures are proposed definitions, not measured savings, achieved improvements, or customer results. No real customer records are included.

The boundary

One team. The workflow begins when an enquiry arrives and ends when the delivery lead accepts a scoped handoff or the enquiry is closed.

The process map

Current workflow · fictional

  1. Enquiry arrives in a shared mailbox
  2. Owner copies details into a spreadsheet
  3. Follow-up sits in an email thread
  4. Delivery lead asks for missing scope details

Proposed workflow

  1. Owner reviews the enquiry and records the source
  2. Owner sets status, next action, and due date
  3. Team reviews a short scope and acceptance checklist
  4. Delivery lead accepts the handoff or returns it for clarification

Three priorities

Priority 1

Next actions have no consistent owner or due date.

Give each open enquiry one accountable owner, next action, and due date.

Priority 2

A handoff can happen before the scope is complete.

Require an objective, exclusions, acceptance criteria, and an explicit receiving owner.

Priority 3

The team has no agreed baseline for the workflow.

Define the measures first, then record a baseline before implementation.

Walk through the proposed handoff.

Open each step to see the decision the workflow needs to support.

1. An enquiry needs a next action

The enquiry owner reviews the request and sets the next action and due date. The enquiry remains open until it has a clear disposition. A stage label alone does not show that follow-up happened.

2. The scope needs a receiving owner

The owner prepares the objective, exclusions, and acceptance criteria. Missing information returns the item for clarification instead of treating the handoff as complete.

3. The team reviews the result

The delivery lead explicitly accepts or returns the handoff. Compare the agreed measures with a real baseline after implementation; this sample reports no actual improvement.

The implementation brief

Objective

Make ownership and the next action visible from first review through delivery handoff.

Proposed scope

One enquiry list with an owner, status, next action, due date, and an agreed handoff checklist for one team.

Acceptance criteria

An open enquiry can be assigned an owner and due date. A handoff cannot be marked accepted until its required scope fields are complete. The receiving owner can accept it or return it with a reason.

Dependencies

A named workflow owner, agreed status definitions, approved tools and data rights, and team availability for review. Customer-data access requires a separate readiness decision.

Exclusions

Bulk email, payment collection, customer accounts, historic data migration, external integrations, and live customer-data activation.

Delivery decisions

Confirm the useful scope, effort, fee, review milestones, and acceptance in a separate written proposal before building. No implementation is included in the assessment fee.

Agree how to measure it.

These definitions would guide a baseline and later review. No baseline, target, or achieved result is asserted.

Proposed workflow measures
MeasureDefinition
Ownership coverageOpen enquiries with an owner and next-action date divided by all open enquiries.
Time to first reviewElapsed time from enquiry receipt to its first recorded human review. Compare equivalent working periods.
Handoff completenessHandoffs accepted without clarification divided by reviewed handoffs in the same period.

Bring your own workflow.

Start with one team and one process. We agree the assessment before work begins, then use its findings to decide whether implementation is useful.

Discuss a $750 Workflow Assessment