Define One Service Lane and Baseline

What you will complete

A service-lane brief with scope, baseline definitions, human gates, prerequisites, and stop conditions.

Make the operating decision

Name one service, service area, lead source, appointment type, operating owner, and business-hours policy. Define the start event precisely: a valid form receipt, an inbound call event, or another approved signal. Define separate finish events for acknowledgement, human acceptance, connected conversation, and booking so a quick automated message cannot masquerade as a useful outcome.

Record a baseline only from an identified source and period. If response or booking data is unavailable, mark the baseline unknown and plan how to collect it. Do not import vendor multipliers as the learner's result. The first proof can be operational: a valid test enquiry produces one traceable record, owner, disposition, and next action.

Write the human boundary before implementation. Emergencies, safety statements, technical diagnosis, complaints, warranty decisions, unusual service promises, identity concerns, and pricing disputes require a person. Define the callback owner and unavailable-person fallback. A custom build is not automatically the right answer; a packaged vertical tool or process repair may be the capstone decision.

Worked fictional example: Harbourlight Roofing

Harbourlight Roofing chooses website inspection requests in Toronto and Mississauga. A submitted form begins the path. Separate states record acknowledgement, reviewed fit, accepted owner, and confirmed inspection. A named dispatcher handles safety, warranty, complaint, and uncertain cases.

Harbourlight Roofing, its staff, customers, enquiries, service rules, and results are fictional. The course does not claim a live deployment, faster response, more bookings, or revenue improvement.

Complete workbook section 1

Use the evidence available for your own bounded job. Write unknown when the evidence is missing, and record the person or action that can resolve it.

1. Name the service lane, geography, source, appointment, and owner.
2. Define start and each meaningful finish event.
3. Record available baselines and unknowns.
4. List human-only decisions and stop conditions.

Open the course workbook PDF or read the workbook details.

Critical gate before continuing

• One lane can be tested end to end.
• Automated and human response measures are separate.
• Every high-consequence condition has a human owner.
• A packaged-product or stop decision remains valid.

If a gate fails, repair the current section, narrow the scope, leave the route manual, or record a blocked or stop decision. Continuing is not the only successful learner action.

Common failure modes

• Expanding beyond a service-lane brief with scope, baseline definitions, human gates, prerequisites, and stop conditions. before the current artifact can be graded.
• Turning a missing value, unavailable source, or blocked integration into a confident conclusion.
• Treating a prompt instruction as proof that the effective tool or permission boundary works.
• Marking a manual, simulated, or untested route as live.

Check your application