Pilot online book holds slide deck

```meta
title: Pilot online book holds
subtitle: A six-slide proposal for a two-week trial at one library branch.
tag: DECISION DECK · EXAMPLE
```

## Make the first release a branch pilot {split}

Members currently call a desk to request a book. This proposal tests online
holds at Central Library before expanding to other branches. The scenario,
estimates, and success criteria are illustrative.

```scqa
situation: Members can search the catalogue but call the desk to request a hold.
complication: A full rollout would change the workflow at every branch at once.
question: How can we test the service with a small operational commitment?
answer: Run a two-week pilot at Central Library with a daily staff review.
```

## Compare three ways to start

The effort estimates cover the hold request and confirmation flow. They exclude
catalogue replacement and changes to the existing circulation system.

```options
items:
  - title: Keep phone requests
    pros: [No implementation work, Familiar staff process]
    cons: [Members must call during opening hours]
    verdict: Keep as a fallback during the pilot
    tone: viable
  - title: Pilot at one branch
    pros: [Small support group, Direct feedback from staff]
    cons: [Members at other branches must wait]
    verdict: Proposed scope
    tone: chosen
  - title: Launch at every branch
    pros: [All members receive the new option]
    cons: [More staff training, More complicated recovery]
    verdict: Revisit after the pilot
    tone: neutral
```

## Limit the pilot to one complete task {split}

A member searches for a book, chooses Central Library, places a hold, and sees
a confirmation. Staff review the queue each day. Renewals and saved searches
stay outside this trial.

```steps
items:
  - Search the catalogue — preserve the query when filters change
  - Place a hold — show the selected book and pickup branch before confirmation
  - Confirm the request — show its status in My holds
  - Review the queue — staff check new requests each working day
```

## Decide the checks before the trial

These are proposed acceptance criteria. Record observations during the pilot;
none of the values below represents a measured result.

```table
columns: [Check, Proposed criterion, Owner]
rows:
  - [Task completion, At least 8 of 10 test participants place a hold without help, Product designer]
  - [Request accuracy, Every test hold names the intended book and branch, Engineer]
  - [Staff workload, Staff can review the queue within the agreed daily time budget, Branch lead]
  - [Recovery, Staff can pause online requests and direct members to the phone desk, Engineer]
```

## Approve the scope and name the owners

Request approval for one branch and two weeks. The product designer schedules
the member sessions. The engineer checks failure and recovery paths. The branch
lead confirms the daily review budget before the trial starts.

```takeaways
items:
  - text: Start with Central Library
    detail: Keep other branches on the existing process during the trial.
  - text: Measure the complete hold task
    detail: Record failures and staff feedback alongside completion counts.
  - text: Review before expanding
    detail: Extend, revise, or stop the pilot based on the agreed checks.
```