Sample page · invented data

Before the session: Northfield Mechanical, Q4, week 6

This is the page an implementer and the client’s owner would both see before a session. The company and every number on it are invented to show the format.

ClientTeamAnswered this cyclePeriodWho sees this page
Northfield Mechanical (fictional), HVAC service34 people11 of 14 asked (79%)Oct 27 to Nov 7You and the owner, the same page
Rocks from the Quarterly

Two on track, two off.

RockOwnerDueStatusWhat the team says
Dispatch board live for all techsOps leadDec 15on track3 techs use it daily. 2 still call dispatch to change a job.
Close 4 commercial maintenance contractsSalesDec 31off track1 of 4 signed. 2 quotes have waited 9 days for pricing approval.
Hire 2 install techsOwnerNov 30off trackNo offers yet. 2 candidates dropped out after the second interview.
Truck stock checklist in every vanWarehouse leadNov 15doneIn 11 of 12 vans. 4 techs say they use it every morning.
Scorecard

Three measurables off goal.

MeasurableGoalLast 2 weeks
Callbacks within 30 days4% or less6%
Jobs per tech per day3.53.1
Quotes waiting on the owner for more than 3 days05
What’s stuck, in the team’s words

Grouped and counted, not interpreted.

  • Quotes wait for pricing approval · 4 people, 2 cycles in a row“I can’t send the Henderson quote until Mike checks the margin.” (sales)
  • Parts missing from the truck · 3 people“Second trip to the supplier this week for the same fitting.” (tech)
  • Second interviews are hard to schedule · 2 people“By the time we called him back he’d taken another job.” (office)
Proposed for the Issues List

Raw issues. The team does IDS in the room.

  • Commercial quotes wait 9 days for the owner’s pricing approvalLinked to the off-track sales Rock and the “quotes waiting” measurable.
  • Install candidates drop out between first and second interviewLinked to the hiring Rock.
  • Two techs still change jobs by phone instead of the dispatch boardLinked to the dispatch Rock.
Open questions for the session

Questions, not answers.

  • Which quotes could go out without the owner?The team named margin as the reason they wait. Nobody has said what margin rule would be enough.
  • What happens between the first and the second interview?Two people mentioned delays. The data doesn’t show where the time goes.
To-Dos from the last session

5 of 7 done.

To-DoOwnerDone?
Send the dispatch board login to every techOps leadYes
Draft the commercial maintenance price sheetSalesYes
Book 3 second interviewsOfficeNo
Order van shelving for 2 trucksWarehouse leadYes
Call the 2 lapsed commercial accountsOwnerNo
Update the callback reportOps leadYes
Post the install tech ad on two job boardsOfficeYes
How this page is built

In a pilot.

Every week or two, each person on the team gets a few short questions through a personal link: what they’re waiting on, what got in the way, what moved. Atlas groups the answers, quotes them and counts them against the Rocks, Scorecard and To-Dos you set at the Quarterly. It doesn’t name a root cause. The owner and the implementer see the same page, and nothing goes to the client’s team without your OK.

EOS® is a registered trademark of EOS Worldwide. Atlas is not affiliated with EOS Worldwide. Rocks, Scorecard, Issues List, To-Dos and IDS are EOS terms used here to show how the page maps to a client already running EOS.