# Handoff exercise for a second founder

A print shop uses a fictional app to send design proofs. You are covering today's onboarding requests. Use this packet on your own. All product behavior, references and cases are fictional. Read the case notes on paper or in your editor. No customer contact, application access or file upload is needed.

## What to return

For each case, record the case name, one decision, the detail that decided it, and the next action. Use one of the four decisions below. Write down any question you could only answer by asking the person who made the playbook. Read the answer key after completing all four.

## The decision rule

1. Compare the exact action and symptom with the known issue below. If both match, choose **link to existing issue** and cite its number.
2. Compare the recorded action with the product instructions. If it behaved as documented and the person wanted a different outcome, choose **explain the workflow** and name the action that produces it.
3. If the notes give the steps, expected result and a repeatable different result on a clean sample, choose **file a new issue**. Include those three details in the report.
4. Otherwise, choose **request missing detail**. Ask one specific question that would distinguish two plausible explanations. Use fictional or redacted examples for the replay.

## Product instructions and known issue

- **Save draft** keeps a proof in the shop's workspace. **Send proof** creates an invitation to review it.
- **Export PDF** includes all pages from the saved proof version currently being previewed.
- An approved proof should show **Approved** in the order list after the reviewer accepts it.
- **Issue 17** covers a mobile reviewer accepting a proof while the shop's open order list continues showing **Sent** until the shop refreshes the list. The original issue already records that sequence.

## Four requests

**Maple.** On two clean sample orders, a shop opened the saved two-page version 3. Both pages appeared in Preview. The operator selected Export PDF and opened the downloaded file. It contained only page one both times.

**Birch.** A shop entered the correct review address, selected Save draft and closed the editor. The proof is visible in Drafts. The shop expected an invitation and asks what to do before tomorrow's review.

**Elm.** The entire note reads “The link stopped working.” It gives no screen, error text, proof state or last action. The customer has not given permission to share their actual link.

**Cedar.** A reviewer accepted a proof on a phone. The shop's already-open order list kept showing Sent. Refreshing that list changed the status to Approved.

## Your record

| Case | Decision | Detail that decided it | Next action |
| --- | --- | --- | --- |
| Maple | | | |
| Birch | | | |
| Elm | | | |
| Cedar | | | |

Record any missing instruction and where you looked for it. After all four decisions, compare with the [answer key](https://creditable.vc/guide/founder-playbook-handoff#answer-key).

## Adapt the handoff to your own work

Name the task and who can run it. List the minimum inputs they may see. Write the steps, the condition that ends the task and the matching record they should produce. Include one ordinary case, one boundary case and one case that should stop. Remove customer identifiers and replace private files with invented examples.

Give the packet to a peer who has not done the task. Save their first pass before explaining it. Revise the specific step that required a hint, then try a fresh case with the revised instructions. Keep the owner, revision date and reason for the change alongside the playbook.
