What Is the Best Way for Service Advisors and Technicians to Communicate?

It is 11:15 on a Tuesday, and Rosa is walking to bay six for the fourth time this morning. She has a customer on hold at the podium, a second line blinking, and a sticky note in her hand that says Sienna, brakes, approved? in her own handwriting, which she wrote two hours ago and still cannot answer.

In bay six, Andre is under a different car. He has both hands inside a wheel well and a torque wrench across his knee. He hears her footsteps before he sees her, and he knows, before she says a word, that she is going to ask about the Sienna. He already wrote it up. He put the measurements and a photo in the inspection notes at 9:30, said the rotors were under spec and the front strut was weeping, and asked for approval. Then he kept working, because a technician who waits for an answer does not get paid to wait.

Rosa never saw the note. Between 9:30 and now she answered nineteen phone calls, and if you asked her what most of them were about she would laugh, not happily, and tell you: the phone won't stop, and every call is "is my car ready." So she walked back to ask. Andre stops, pulls his hands out, wipes them, and tells her from memory what he found. She writes it on the back of the sticky note. She walks back to the drive. The customer on hold has hung up.

Rosa and Andre are not real people. They are a composite, built from a shape that anybody who has worked a service drive will recognize in about three sentences. Nobody in this story is bad at their job. Rosa is a good advisor. Andre is a good technician. And between the two of them, a minivan that needed a forty minute brake job will not leave the building until tomorrow morning, a promise of "by three o'clock" will be broken, and both of them will go home feeling like they spent the day chasing each other.

This page is about that gap. Not the repair, not the customer, but the twenty five feet of shop floor between the podium and the bay, and every message that has to cross it: approvals, parts times, "is it done," "I found something," "it's going to be longer." It is the part of a service department that nobody draws on an org chart and everybody feels in their legs by four o'clock.

Here is the thing we want you to hear first, because it changes what you look for: the best way for advisors and technicians to communicate is not a channel. It is an agreement about which message goes where. Walk-ups, group texts, repair order notes and team threads all have a job. Most service departments are not short on channels. They are short on a decision about what each one is for.

Four things on this page are yours to use, all taps, nothing to type: a scene player that follows one minivan through the day twice, a channel picker that tells you where any message belongs and what to say, a calculator that counts what interruptions cost your bays and your drive, and a one-page communication agreement to put on the wall. We do not need anything back.

The answer, in two sentences

The best way for service advisors and technicians to communicate is a short written agreement about which message goes where: routine messages such as approvals, parts times and job status go in one written place tied to the repair order, posted at a few fixed status points so nobody has to ask, and only three kinds of message get a face to face conversation, a safety problem, a comeback and an upset customer. Group texts are for announcements that truly concern everyone, and the repair order notes stay the permanent record, written once the conversation is settled.

That is the whole idea. The rest of this page is what it looks like on a real Tuesday, at a real podium, with nineteen phone calls before lunch, and how to get there in two weeks without a new system, a consultant or a speech.

Why this got harder, and who pays for it

Advisor and technician communication used to be simpler for a boring reason: the shop was smaller, the cars were simpler, and the advisor and the technician had often worked side by side for years. A look across the floor carried a lot of information. That still happens in plenty of stores, and where it works, it is beautiful to watch.

But three things have changed in most service departments, and each one puts more weight on the messages that cross the floor.

The cars ask more questions

A modern vehicle produces more findings per visit. A routine maintenance visit turns up an inspection with photos, measurements and a list of recommendations, each of which may need a conversation with the customer, which means a conversation between the technician and the advisor first. More findings means more approvals, and every approval is a round trip across the floor.

The bench is thinner

Most service managers do not need a report to tell them that good technicians are hard to find, but the numbers are worth knowing. TechForce Foundation's 2022 Technician Supply and Demand Report found that new automotive technician completions from postsecondary programs fell 11.8 percent in 2021, to 28,866 (TechForce Foundation). When the bench is thin, every minute a technician spends stopped, waiting, walking or re-explaining is a minute the whole department cannot get back from somebody else. Protecting a technician's focus is no longer a courtesy. It is capacity.

The customer expects to hear from you

Customers now expect updates while their car is in the shop, and when they do not get them, they call. Each of those calls lands on the advisor, and the advisor can only answer it with information from the bay. So the phone ringing at the podium becomes footsteps toward the shop. We wrote about the customer side of this in how service advisors keep customers updated without living on the phone. This page is the other half: the information has to get from the bay to the podium first.

Who pays when it breaks

The technician pays in focus. Every interruption stops a job in the middle, and a job stopped in the middle is a job where a step can be lost. On flat rate, the minutes spent wiping hands and walking to the drive are minutes nobody pays for.

The advisor pays in steps and in credibility. They walk the floor all day, and they stand at the podium making promises with information that is an hour old. When a promise breaks, it is their face the customer remembers.

The parts counter pays in surprises. Parts learn about an approval late, or not at all, and then get asked why the part is not here.

The customer pays in a day off they did not plan to lose. They do not see the twenty five feet of floor. They only see that nobody called them, and that the car was not ready when they were told it would be.

Watch one minivan's day, then watch it again

Press play and follow one minivan with a brake grind from the write-up to the moment it leaves. Then play it again. Same van, same advisor, same technician, same parts counter, same nineteen calls. One change: the store agreed which message goes where.

Count the things that did not change. The brake job took the same forty minutes. Andre did not work faster. Rosa did not answer fewer calls in the morning. What changed is that the approval traveled once, to everyone who needed it, at the moment it existed, and Andre's status points meant Rosa could call the customer before the customer called her. Four walk-ups became one. A sticky note became a line in the right place. And the van left at 1:55, not the next morning.

Every channel, compared honestly

Every service department already uses some mix of these. None of them is bad. Each one is good at something specific and quietly terrible at something else. The trouble starts when one channel is used for everything, usually whichever one is closest at that moment.

Read the "breaks when" column again. Every channel breaks the same way: it gets used for messages it was not built for. The walk-up is perfect for a safety finding and wasteful for "is it done." The group text is perfect for "we close at two on Friday" and wasteful for "the Sienna is approved." The repair order notes are the best record you have and a poor way to tell someone something right now.

So the question "what is the best way to communicate" has a slightly annoying honest answer: the best way is to stop asking which channel is best and start deciding which message goes in which one. That decision fits on one page, and there is one at the bottom of this one.

The walk-up: the best channel used for the wrong things

There is nothing wrong with walking back to the shop. A face to face conversation carries tone, urgency and trust in a way nothing else does. When a technician finds that a customer's brake line is about to fail, that should be a walk-up, every time, and it should be the technician walking to the advisor, not the other way around.

The trouble is that in most stores, the walk-up is not reserved for the important things. It is the default for everything, because it is the only channel guaranteed to get an answer. If an advisor has learned that notes go unread and texts go unanswered, they walk. Of course they do. Walking is the one thing that works.

What a walk-up really costs

Picture the technician's side. They are in the middle of a job, which in practice means they are holding a sequence in their head: which bolts are out, which connector was unplugged, what they were about to check. An interruption breaks that sequence. They answer the question, and then they have to rebuild where they were. Most of the time they do. Sometimes they do not, and a clip is left off or a step is skipped. We wrote about how those small skipped steps turn into return visits in how service departments cut comebacks.

Now picture the advisor's side. Every walk-up is time away from the podium, where customers are arriving and phones are ringing. An advisor who walks to the shop ten times a day spends a real part of the morning on the shop floor, carrying questions that could have been answered in writing.

The rule that fixes it

Keep the walk-up. Protect it. Reserve it for the three messages in the section below, and for anything where the person on the other end needs to see your face. For everything else, use a written channel, and make that channel reliable enough that nobody feels the need to walk.

The group text: built for everyone, used for one

Almost every service department has one: a group text with every technician, the advisors, the foreman and sometimes the parts counter. It started as a good idea, usually around a schedule change or a holiday, and it slowly became the place where "who has the Sienna?" goes.

Here is what happens to that message. Fourteen phones buzz. Twelve people check their phone with dirty hands, read a message that has nothing to do with them, and put it away. One person answers "not me." The person who has the Sienna is under a car and does not see it for twenty minutes. By then the thread has moved on to someone's lunch order, and the question is three screens up.

The group text is not the villain. It is a broadcast tool, and it is very good at broadcasting. "We close at two on Friday." "The recall bulletin for the pickups is on the board." "Pizza is here." Those messages concern everyone, so it is right that everyone hears them.

A message about one repair order concerns two or three people. Sending it to fourteen is not communication. It is noise with an answer buried inside it.

Notes on the repair order: the record, not the conversation

The repair order is the most important document in the service department. It is how the store gets paid, how warranty work is supported, and how anyone can reconstruct what happened on a car six months from now. The concern in the customer's words, the cause, the correction, the measurements, the photos: all of it belongs there, and none of what follows is a reason to write less of it.

But a record and a conversation are different things. A record is written once and read later. A conversation needs the other person to know, now, that something was said.

In many stores, notes added to a repair order or a digital inspection do not reliably tell the other person that something changed. Some systems do send an alert, and some stores have it set up well. But where they do not, the technician writes "rotors under spec, need approval" at 9:30, and the advisor, buried in phone calls, has no reason to open that repair order until the customer calls about it. The note is perfectly written and completely unread. That is the gap Rosa fell into.

The rule that fixes it

The repair order holds the record. The conversation lives somewhere designed to tell the other person something happened. When the conversation settles (approved, declined, parts here, done) the result goes on the repair order, in the usual place, in the usual words. One written conversation, one written record, and nobody confuses the two.

A thread per job: where the day's conversation lives

The channel most service departments are missing is the simplest one: a written conversation about one job, with only the people who touch that job in it. The advisor, the technician, and the parts counter when parts are involved. Nobody else gets pinged. Everything said about that car today is in one place, in order.

This is not a new idea and it does not require any particular product. Some stores do it inside their existing systems. Some use a messaging tool with a thread for each repair order number. Some do it, honestly, with a clipboard hanging on each bay. What matters is the shape:

• One thread per job, named by the repair order number or the car, so it is obvious where a message goes.
• Only the people who touch the job, so nobody else is interrupted.
• Read at a stopping point, not the instant it arrives. A technician finishes the torque sequence, then looks.
• The result goes on the repair order, once it is settled, so the record stays complete.

Why this works when notes and texts did not

It works because it fixes both failures at once. Unlike the group text, it only reaches the people who need it. Unlike repair order notes, it is built to tell them something was said. And unlike the walk-up, it lets the technician answer at a stopping point instead of in the middle of a job.

What it does not fix

A thread does not fix a store where nobody reads it. That is why the agreement matters more than the tool. If the advisors and technicians decide together that routine messages go in the job's thread, that technicians post at fixed status points, and that walk-ups are for three things only, then any reasonable thread will work. If they do not decide, the best tool in the world becomes one more place to check.

Where does this message belong? The channel picker

Here is the agreement in a form you can poke at. Tap a message that crosses your shop floor every day, then tap how urgent it is. The picker tells you which channel it belongs in, who should hear it, and the words to use. Nothing is saved or sent anywhere.

Notice the pattern after a few taps. Five of the eight messages land in the job's thread, whatever the urgency. Urgency changes how fast someone should look and whether a short shoulder tap follows, not where the message lives. Only three messages change channel completely, and they are the three in the section after next.

Status points: the end of "is it done yet"

If you only change one thing after reading this page, change this one. The single most common message between advisors and technicians is a question: is it done, where is it, how long. And the single best way to stop that question is to answer it before anyone asks.

Status points are a handful of fixed moments in every job where the technician posts one short line in the job's thread. That is all. Here are the ones most service departments settle on:

1. Started. "On the lift." The advisor now knows the car is being worked on, which is the first thing a calling customer wants to hear.
2. Concern verified. "Heard the grind, front left, light braking." It tells the advisor the problem is real and found, which is the second thing.
3. Diagnosis ready. The finding, the measurement, a photo if there is one, and what needs approval. This is the message that starts the clock on the customer's answer, so it should never sit unread.
4. Waiting. "Waiting on parts, ETA 11:15" or "waiting on approval." The car is not being worked on, and everyone can see why.
5. Done and road tested. The most important line of the day. The advisor can now call the customer before the customer calls.

Five lines a job, each a few seconds to write, each one at a moment the technician has already stopped anyway. In return, the technician is not interrupted with "is it done," because the advisor can see it. That is the trade, and it is a very good one for both sides.

What this does to the phone at the podium

Remember Rosa's nineteen calls. Most were "is my car ready." With status points, Rosa can answer those calls from the podium in ten seconds, because the answer is in front of her: on the lift, waiting on parts until 11:15, done and road tested. Better, she can call the customers whose cars just hit "done" before they call her. Each of those outbound calls is one inbound call that never rings. The phone does not go quiet, but it rings less, and the calls it does get are shorter.

The advisor's half of the bargain

Status points only work if the advisor's replies are just as reliable. When a technician posts "diagnosis ready, need approval," the advisor answers in the thread with what happened: "calling now," then "approved: rotors and pads, strut declined, noted on RO." If the customer cannot be reached, say that too: "left a message, will try again at 11." A technician who knows their question was seen does not need to come looking for the answer.

The three messages that always get a face

A written channel is the right home for most messages. It is the wrong home for three of them. These always start with a conversation, in person, and then get written down afterward so the record is complete.

1. A safety problem

When a technician finds something that makes a car unsafe to drive, they walk to the advisor. Not a note, not a thread, not a text. The advisor needs to understand it well enough to explain it to a customer who may not want to hear it, and that means seeing the person who found it, asking questions, and maybe walking back to look. After the conversation, the finding goes in writing, with measurements and photos, on the repair order.

2. A comeback

When a car comes back for the same concern, the advisor and the technician who worked on it should talk face to face, ideally with the foreman. Comebacks carry feelings: pride, embarrassment, defensiveness, frustration. Text strips the tone out of a message, and on a comeback, missing tone reads as blame. A two minute conversation that starts with "what did the customer say this time" goes better than the same words in writing.

3. An upset customer

When a customer is angry, or asks to speak with the technician, the advisor should walk back and prepare the technician before anyone meets anyone. What the customer is upset about, what they have been told, what the advisor thinks a good outcome looks like. A technician walked into an angry customer cold is set up to fail, through no fault of their own.

Count what interruptions cost your people

Interruptions are invisible because each one is small. Three minutes here, five there. They only become visible when you add them up across a department and a year. Drag the sliders to match your own store. The defaults are placeholders, not industry figures, so set each one to what you actually see. Nothing is saved or sent anywhere.

Look at the technician hours and imagine them as bay time. On a thin bench, those hours are jobs that could have been done, or a technician who could have gone home on time. Look at the advisor hours and imagine them at the podium, with customers, instead of on the shop floor. Most of those trips carry a routine message that could have been one line in the right place, posted once and read at a stopping point.

Written to each person in the department

To the service advisor

You are not walking to the shop because you like walking. You are walking because it is the only thing that reliably gets you an answer, and you are the one who has to give that answer to a customer on hold. The phone won't stop, and every call is "is my car ready." The agreement on this page is mostly for you. It trades your walk-ups for status points, so the answer to "is my car ready" is in front of you when the phone rings. Your half is to answer every question in the thread as reliably as you want yours answered, even when the answer is "still waiting on the customer."

To the technician

You are interrupted all day by people who need something from you, and every interruption costs you time you are often not paid for and focus you have to rebuild. The agreement protects you from most of it. In return, it asks for five short lines a job, at moments you have already stopped. Post "done and road tested" the moment it is true, and watch how many times nobody comes to your bay to ask. And when you find something unsafe, walk to the podium. That one is always worth the trip.

To the shop foreman or dispatcher

You are the person both sides already come to when they cannot find each other. You are the right person to keep the agreement alive, because you can see when a technician has stopped posting status points or when an advisor has gone back to walking. Watch for the first week. Most habits slip in the first five days, not the fifth month.

To the parts counter

You are usually the last person to hear about an approval and the first person asked why the part is not here. Ask to be in the thread for any job that needs parts. When you post an ETA, post it once, in the job's thread, and both the advisor and the technician will see it. You will get asked "where's the part" a lot less.

To the service manager

You will not fix this with a memo, and you probably will not fix it by buying something. You fix it by getting one advisor, one technician and the foreman in a room for twenty minutes to agree which message goes where, writing it on one page, and holding to it for two weeks. If it works on one team, it will spread. If it does not, the agreement will tell you exactly which line people are not keeping.

To the porter and the shuttle driver

You move the cars, which means you know where they are. If a car is parked in the back lot waiting on a part, say so in the thread. A single line from you can save an advisor a trip and a customer a wrong answer.

Your first two weeks, day by day

Here is how a service department can start, with what it already has, in an order that works.

Day 1, Monday: count the trips

For one day, each advisor makes a tick mark every time they go to the shop to ask or tell something. Each technician makes a tick mark every time someone comes to their bay. No changes, just counting. Most people are surprised by their own number.

Day 2, Tuesday: sort the ticks

Look at the trips with the foreman. What was each one about? Status, approval, parts, a safety finding, an upset customer? Put each in a column. In most stores, status and approvals fill most of the page, and the three face to face messages are a small handful.

Day 3, Wednesday: write the agreement

Twenty minutes, one advisor, one technician, the foreman. Use the sheet at the bottom of this page as a starting draft. Decide where the job's conversation will live, which status points technicians will post, and which messages always get a face. Write it on one page.

Day 4, Thursday: status points, one bay

Start with one technician who is willing. They post the five status points on every job. The advisor replies to every question in writing. Everyone else watches.

Day 5, Friday: compare the ticks

Count again for that one bay. Fewer trips? Fewer "is it done" walk-ups? Ask the technician how their day felt, and ask the advisor how many calls they could answer without moving.

Days 6 and 7, the weekend: nothing

Let it settle. Habits stick when people are not asked to change something every single day.

Day 8, Monday: every bay

Bring it to the morning huddle. Read the agreement out loud, all of it, in under two minutes. Every technician posts status points. Every advisor answers in writing. The group text goes back to announcements only.

Days 9 to 11: watch for the slip

The foreman watches for two things: a technician who stopped posting "done," and an advisor who went back to walking for routine questions. Neither is a failure. Both are a reminder, given kindly, the same day.

Day 12, Friday: count one last time

Same tick marks as Day 1. Put the two days side by side. The number does not need to be perfect. It needs to be visibly smaller.

Days 13 and 14: decide what stays

At the next huddle, ask the team one question: what in the agreement is not working? Change that one line. Then keep it. That is the whole program. It is not exciting. It works because it is not exciting.

Eight ways stores try to fix it and fail

1. Banning walk-ups

It sounds efficient, and it removes the one channel that carries trust. Safety findings, comebacks and upset customers need a face. Ban the routine walk-up, not the walk-up.

2. Adding a tool before deciding anything

A new app with no agreement about what goes in it becomes a fourth place to look. People will use it for some messages, the old channels for others, and nobody will know where anything is.

3. Moving everything into the group text

Usually done in the name of "keeping everyone in the loop." In practice it puts everyone in every loop, and the important message drowns under the routine ones.

4. Treating repair order notes as the conversation

The note is written beautifully and read by nobody until the customer calls. Keep the notes as the record and give the conversation a place built to tell the other person something happened.

5. Asking technicians for status updates without asking advisors for answers

If a technician posts "need approval" and hears nothing for an hour, they will stop posting and start walking. The agreement has two halves, and both have to hold.

6. Too many status points

Ten status points a job is a form, not a habit, and technicians will rightly ignore it. Five is plenty. Some stores do well with three: started, diagnosis ready, done.

7. Rolling it out by memo

A memo tells people what to do and gives them no part in deciding it. The advisors and technicians who will live with the agreement should write it, even if the manager holds the pen.

8. Giving up after the first busy day

The first slammed Monday will test everything. People under pressure go back to the channel that always worked, which is walking. That is normal. Name it the next morning, without blame, and keep going.

What it feels like when it works

It does not look like much from the outside. There is no new sign on the wall, apart from one sheet of paper. But inside the department, the day changes shape.

The technician gets long stretches of uninterrupted work, and notices, around the second week, that they are finishing jobs with fewer loose ends because nobody pulled them out of the middle. The advisor stands at the podium for longer stretches and answers "is my car ready" with a real answer instead of "let me check." The parts counter stops being surprised. The foreman stops being the person everyone goes to when they cannot find each other.

And the customers feel it without knowing why. Their phone rings before they have to call. The time they are given is the time it is done. When something needs their approval, they hear about it within minutes of it being found, with a photo, from someone who sounds sure.

In the second version of Rosa's Tuesday, the minivan leaves at 1:55. The customer picks it up on her lunch break instead of taking a second morning off. Rosa makes one walk to bay six all day, at 2:40, because Andre posted that the next car had a brake line about to let go, and she wanted to see it before she called the owner. Andre spends that afternoon under cars, not wiping his hands to answer questions. At 5:30 they both leave on time. Neither of them thinks about the twenty five feet of floor between the podium and the bay. Which is exactly the point.

The communication agreement, yours to keep

Copy this and print it for the podium, the dispatch board and the bays. Drop it into your team's thread. Change any line that does not fit your store. It is yours. We do not need anything back.

Where Tarvis fits, and when not to use it

We are Class Company US. We started in New Orleans as a web design studio, grew through Houston and across Texas, and now build for brands nationwide. Tarvis is the AI agent we built, and Tarvis AI is the app around it. We are telling you this so the next part makes sense, not as a pitch.

Everything on this page works with what you already have: a repair order system, a clipboard, a printed sheet and a twenty minute meeting. You do not need any app to fix how advisors and technicians talk. Many service departments do it with nothing but an agreement and a foreman who keeps it.

Where Tarvis AI helps is the thread itself. It is a team chat with our AI agent in the thread, so a job's conversation (the finding, the approval, the parts time, the status points) can sit in one place with only the people on that job. Permissions are set per member, so a porter or a parts counter sees what they need and nothing else. A task can be assigned to one named person, and assigning a step to a teammate who is not in the app yet is also how they get invited. A busy week can be its own project with dates, a countdown and a checklist. Money is tracked per project. And Tarvis drafts files and a weekly status report from what actually happened in the thread, which is most of a Monday huddle already written.

It is free while in beta, two teammates are free with every brand, and it installs from the browser to a home screen, with no app store needed.

Do not use Tarvis for this if your repair order system already gives your advisors and technicians a reliable conversation per job and people use it: the agreement is your fix, not a second app. Do not use it as the permanent record either. It does not connect to your dealer management system or your scan tool, it does not write your repair orders, and it does not diagnose anything. The concern, cause and correction still belong on the repair order. And it does not replace the three conversations that need a face. What it can do is give the everyday back and forth one place to live, so nobody has to walk across the floor to find out what was already said.

If the honest question at the end of your day is what actually got done in the bays, this one is for you. If the front of the funnel needs work too, we walked through the booking path in how car dealerships get more service appointments online. And the habit of one name on each step works the same on any crew: how to assign jobs in a group chat without things falling through.

Questions service teams actually ask

What is the best way for service advisors and technicians to communicate?

There is no single best channel. The best way is a written agreement about which message goes where: routine updates such as approvals, parts times and job status go in one written place tied to the repair order, where the technician reads them at a natural stopping point, and only three kinds of message get a face to face conversation: a safety problem, a comeback, and an upset customer.

Should service advisors walk back to the shop to talk to technicians?

For a safety problem, a comeback or a hard conversation, yes. For routine questions such as whether a car is done, no. Every walk-up stops a technician in the middle of a job and takes the advisor away from the drive, so routine questions belong in a written channel the technician can answer at a stopping point.

Is a group text a good way for a service department to communicate?

A group text is fine for announcements that truly concern everyone, such as the shop closing early. It is a poor place for messages about one repair order, because every technician gets interrupted by a message meant for one of them, and the message is quickly buried and hard to find later.

Are notes on the repair order enough?

Notes on the repair order are the right permanent record, and every store should keep them. They are often not enough on their own for the day's conversation, because many systems do not tell the other person a note was added, so an approval can sit unread while the technician moves on to another car.

How do you stop technicians being interrupted all day?

Agree on status points instead of questions. The technician posts at a few fixed moments, such as concern verified, diagnosis ready, waiting on parts and done and road tested, so the advisor never has to ask. Then keep walk-ups for the three messages that need a face: safety, comebacks and upset customers.

What should a service advisor never do over text?

Never handle a safety problem, a comeback, or a conflict with a customer or a coworker only in text. Those need a conversation first, and then a short written note so the record is complete.

How do I get technicians to actually post updates?

Keep it short, put it at moments they have already stopped, and make sure the advisors answer every time. A technician who posts "need approval" and hears back in minutes will keep posting. One who hears nothing for an hour will start walking again, and they will be right to.

Do we need a new system to do this?

No. Start with the agreement and whatever you already have. If after two weeks the only thing failing is that your current tools cannot hold a conversation per job, then look at a tool, and judge it by one question: does it make the agreement easier to keep?

Somewhere this Tuesday, an advisor will stand up from the podium with a sticky note in her hand and walk to the shop for the fourth time before lunch. Somewhere a technician will hear the footsteps and pull his hands out of a wheel well. Neither of them is doing anything wrong. They are doing the only thing that has ever reliably worked. It does not have to keep going this way. One page, one place for the everyday, five status points and three conversations that always get a face. Everyone carries a little, and nobody spends the day chasing anybody. Send this to your team. They will know exactly what it means.