What belongs in an operations playbook for my first hire?

Begin with the shape of the working day

Describe the daily rhythm before explaining individual buttons. Which commitments are reviewed first? When does the warehouse need its release information? What happens before the final carrier collection? Which tasks can wait until the weekly review? This context helps a new hire understand why the work is ordered in a particular way.

Include the purpose of each routine and the result it should produce. A morning order review should end with a clear list of ready work and assigned exceptions. An end-of-day review should identify commitments still at risk and who is following them. Avoid writing the playbook as a list of screens to visit. Screens change; the business questions and expected outcomes are more durable.

Define the records people must keep connected

Explain the relationship between the marketplace order, store order, product variant, shipment, and payment reference. Show an example in which the same purchase has different identifiers in different systems. Teach the new hire which reference to use when speaking to a customer, a warehouse, or a marketplace support team.

Include the minimum information required in an internal note: what happened, what evidence was checked, what action was taken, and what remains to be done. A note that says fixed is not enough for someone reviewing the case later. Good record habits make handoffs smoother and reduce the pressure to remember every detail personally. They also help the business investigate mistakes without turning every question into a search through private messages.

Document decisions, not only instructions

For each important task, explain the conditions under which it should be performed. When can an order be released? When should stock be held unavailable? When can a shipment be marked complete? What makes a refund request ready for review? A button sequence without these conditions can teach someone to perform the wrong action efficiently.

Use short decision examples. If the item is physically present but awaiting inspection, do not treat it as ready to sell. If a cancellation was requested but the warehouse has not responded, do not describe it as confirmed. These distinctions are more valuable than a large library of screenshots. They give the new hire a way to reason about slightly unfamiliar situations without guessing.

A useful task page can fit on one screen: purpose, starting condition, required evidence, action steps, confirmation, and escalation. For a shipment task, the confirmation might require that the tracking reference belongs to the correct package and that the fulfilled quantities match the physical handoff. The escalation might identify what to do when the carrier is unknown or the order is already partially shipped. This structure gives the employee a dependable way to approach the task without requiring a long manual for every possible variation. It also makes revisions easier because the owner can see which decision rule changed.

State authority and escalation boundaries clearly

List the actions the new hire can complete independently, the actions that need review, and the people responsible for approval. Keep the boundaries tied to business consequence rather than vague seniority. Product corrections, stock adjustments, refunds, carrier claims, and account-permission changes may require different levels of authority.

Give every escalation a destination and an expected response path. If the usual approver is unavailable, who is the backup? What evidence should the request include? What should happen to the affected order while a decision is pending? Clear escalation rules protect the employee as well as the business. They make it possible to ask for help early without feeling that every unusual case is a personal failure.

Provide access through roles, not shared credentials

The playbook should describe where authorized access is managed and which role is appropriate for the work. It should not contain passwords, API tokens, or recovery codes. Use individual accounts and supported role controls where the platforms provide them, so actions remain accountable and access can be changed when responsibilities change.

Shopify's user-management documentation provides examples of role-based permissions and two-step authentication controls. Apply the relevant controls in each system your team uses. Include an onboarding checklist that confirms the employee can reach the required tools and an offboarding checklist that removes access. A good playbook makes access predictable without making every new hire an administrator or leaving one person's login as the team's only way to operate.

Teach a handful of exceptions deeply

Choose the unusual cases that occur most often in your business: missing mapping, unavailable stock, incomplete delivery information, a shipment without a scan, a partial cancellation, or an unexplained transaction. For each, show the initial signal, the evidence to inspect, the safe next action, and the condition for closing the case.

Use examples that include uncertainty. A warehouse may need to count stock before an answer is available. A carrier may need time to investigate. Show how to record the owner and next review time while waiting. New staff need to learn that a clear pending state is better than an invented answer. The playbook should make responsible uncertainty manageable, not encourage premature closure just to clear a queue.

Use practice cases before handing over live responsibility

Give the new hire a small set of practice scenarios with known outcomes. Ask them to explain what they would do and why, then review the reasoning together. Include a normal order, a mismatched variant, a split shipment, and a case that requires escalation. The exercise should test judgment as well as navigation.

After supervised work begins, review a sample of completed tasks rather than waiting for a major error. Look for missing references, unclear notes, and actions taken without confirming the previous outcome. Treat the findings as feedback on the playbook as well as the employee. If several people misunderstand the same instruction, the process or wording probably needs improvement.

Give the playbook an owner and a revision habit

Assign someone to maintain the playbook and record when important sections were last reviewed. Update it when a platform changes, a new channel is added, or an exception reveals a missing decision rule. Keep a short change history for consequential updates so staff know which instructions are new.

Invite the first hire to flag unclear steps during the first month. Their questions expose assumptions that an experienced owner no longer notices. Turn those questions into better examples and clearer definitions. A useful playbook grows from the work, but it should remain easy to navigate. Its success is visible when a colleague can complete an ordinary day confidently and bring an unusual case to the right person with the right evidence.