Getting Started with Scoop

Onboarding puts your operating knowledge to work across the business. We work with your experienced operators to capture how they investigate performance and decide what to do, then use that playbook to produce briefings for your managers.

Our team does the setup and runs the service. Your team provides the data access and operating context, then helps us test the usefulness of the briefings during the pilot.

We agree the pilot schedule during discovery, based on the scope, data readiness, and availability of your operators.

The onboarding steps

1. Discovery

We learn how your business is organized and how performance is reviewed today. Together we agree:

• the goals for the engagement;
• your organizational structure, such as locations, districts, regions, and divisions;
• who should receive briefings, and how often;
• where the pilot should run.

2. Connect your data

Scoop works with the data and reports you already have. Your IT team either provides read-only access to your data warehouse or sets up a scheduled extract of the relevant reports. We confirm which tables, reports, history, and access arrangements are ready, then scope any preparation work with you.

3. Capture your playbook

This is the most important step. In a series of structured conversations, your best operators walk us through how they read performance:

• which metrics matter and what counts as a problem;
• how they investigate a problem when they find one;
• which exceptions they know to make;
• which actions they take, and when.

We agree the time needed from your operators when we scope the pilot. We start from templates for your industry, so the conversations focus on what makes your business different. We build that knowledge into your playbook, and it becomes the standard applied at every location.

Bring examples of a result that looked worrying but had a reasonable explanation, a problem hidden by a healthy total, and an action that worked under specific conditions. Those examples help us capture the judgment behind the rule. Existing management reports and standard action guides are useful starting material. Your Operating Playbook explains how we use them.

4. Define the briefings

We agree what each level of management receives, starting from proven formats: the metrics shown, the level of detail, the terminology your teams use, the language, and the delivery schedule. We also agree how your managers will use the portal and respond to recommended actions.

5. Pilot

The pilot usually runs in one region, ideally one with meaningful variation in performance between locations. We review the briefings with that management chain, cycle by cycle. Do the investigations explain the results? Do the visit questions help managers check the right things? Are the recommended actions practical? Their feedback guides the refinements before expansion.

We also check the details that can change a conclusion: metric definitions, comparison periods, the locations included in a peer group, and whether an action belongs with the person receiving it. Managers should be able to connect the finding to the underlying business and use it in a real performance discussion.

6. Roll out

After the pilot, we extend Scoop to the rest of the business, either in stages or all at once. Business units that use different definitions or languages are usually best brought on with their own short pilot.

Agree what a useful briefing looks like

Use the sample performance briefing as a starting point. Choose representative locations, including a stronger performer and a location with a difficult result. Your operators should be able to follow the evidence, recognize relevant exceptions, and use the recommended questions during a real review.

Agree the pilot's review criteria before expansion: definitions and dates are correct, findings account for local context, each manager receives the right scope, and recommendations lead to practical discussion. The pilot establishes whether the service is useful in your operating process.

What we need from you

• Data access: read-only access or a scheduled extract, set up by your IT team.
• Your organizational structure: which location belongs to which district, region, and division, and how that changes over time.
• Time with your best operators: structured conversations and review of the pilot briefings.
• A pilot sponsor: a leader in the pilot region who will read the briefings and give feedback.
• Ongoing feedback: managers' responses to action plans, and corrections when something is wrong.

What we do

• Build and maintain your playbook.
• Run every reporting cycle.
• Review each cycle's briefings before release.
• Deliver the briefings to the agreed recipients.
• Update the playbook as your business changes.

What "live" means

Scoop is live when briefings are delivered on the agreed schedule to the agreed managers, after our review each cycle.

---

Related: How Scoop Works · What You Receive · FAQ