“It only took me a second” tells you how long you spent answering. It does not tell you how long the business waited. The office cannot confirm a job. A technician needs a purchasing decision. An invoice sits until you check the details. By the end of the day, you know you were needed everywhere, but the pattern is hard to see. In Episode 003 of The STREAMLINED. Podcast, Easton Wiechert and Kat explain The 48-Hour Owner Dependency Audit: What Still Has to Come Through You? The goal is to turn those everyday moments into a record you can use to make one practical change. What is the 48-hour owner dependency audit? It is two normal working days of observation. Keep answering the phone, supporting your team, and doing your regular work. Record where work needs something from you before it can continue. Tell your team what you are tracking and invite them to document where they wait for you. Keep questions and issues coming as usual. At the end, aim for a record of the dependencies, an understanding of why they happen, and one recurring situation to address. What counts as a dependency? Look for work that needs your information, decision, permission, or intervention. That includes a customer promise stored only in your messages, a routine purchase waiting for approval, and an approved estimate waiting for a scheduling decision. Include work that quietly waits in your pile: evening quote reviews, unreleased schedules, and invoices assembled from texts and photos. Also record tasks you take back yourself, even when nobody asked you to step in. Ask: could this person reasonably continue if I were unavailable? An update from someone who can keep working is different from a blocked next step. Record what happened before deciding whether it needs to change. The five details to write down What was happening? Describe the work or situation. Who or what was waiting? Identify the person, job, customer, or next step. What did they need from you? Capture the information, decision, approval, or intervention. What did you do? Note whether you answered, approved, investigated, or took over. What was the effect of waiting? Record the delay or consequence if known. Label estimates and leave unknowns unknown. Use paper, a phone note, or a simple spreadsheet. Write a short entry soon after the interaction when safe and practical, then check your calls, messages, and unfinished work at lunch and at the end of the day. Illustrative entry from the episode: Tuesday, 10:15. The office asked whether Friday’s job could be confirmed. It needed the owner to verify that materials had arrived. The owner called the supplier, and customer confirmation waited about 40 minutes. Similar interruptions can have different causes In a made-up service-business morning, the office asks for scheduling approval, a technician asks about a substitute part, the team needs a customer discount recorded, and the owner takes over an estimate. Scheduling: the office may have the information but lack permission to act. Substitute parts: the decision may need a clearer purchasing boundary or qualified technical review. Customer commitments: the team may be missing information only the owner has. Estimate takeover: the owner may be correcting a meaningful error, following a review requirement, or taking back work unnecessarily. Each entry needs its own diagnosis. Some decisions appropriately remain with the owner, including substantial commitments outside the team’s authority. Review the list with your team Ask what made your involvement necessary. Look for missing information, unclear authority, incomplete work, training needs, or an owner stepping in before someone could finish. Ask the person what they were missing, what they would have done, and whether they understood that the decision was theirs. Changing expectations can teach people to keep asking permission. Training and practice may be needed before expanding authority. Group the repeats by what the work needed A question about materials, a crew missing equipment, and a customer waiting for an appointment confirmation may all point to one unclear job-readiness handoff. Group entries by the missing step, even when different people raise them. Consider frequency and consequences. Keep a one-time issue with a major delay visible. Two days provide a sample; extend the observation if those days are unusual. Add known payroll, month-end, or other recurring dependencies separately so you distinguish observed events from patterns you already know about. Choose one change to try first Pick a recurring dependency that happens often enough to practice, creates a meaningful delay or interruption, and has a clear boundary with manageable risk. For example, if the office already has scheduling authority but material status lives in your messages, the first change may be to put that status in the job record and name the person responsible for keeping it current. A simple progression from waiting for materials to materials received can make the next step visible. Understand the cause before choosing software or a broader delegation effort. Finish these two statements: This work keeps waiting for me because… The first change we’re going to try is… Check whether the work can move correctly After a few real opportunities to use the change, review it with the person doing the work. For a daily process, the following week is usually a useful time to check. Can the office find and trust the material status? Can it schedule an eligible job and confirm the appointment? Are jobs still kept off the schedule until they are ready? “You want the work to move, the standard to hold, and the team to know what to do when something falls outside the normal situation.” — Easton Wiechert Fewer calls alone do not establish success. If the question repeats, investigate whether the information is updated, the team knows where to find it, and everyone shares the same meaning of “ready.” Include the work you pull back Changing someone’s plan without telling them or giving a customer a private route around the office can recreate the dependency. Keep the observation specific: an unrecorded customer commitment is something you can change. Use the exercise to examine habits and handoffs with your team. Your challenge: two workdays, one recurring dependency Choose two normal working days and tell the team what you are observing. Capture the five details, including quiet waiting and work you take back. Review why your involvement was needed and ask the team for its perspective. Group the repeats and choose one dependency to address. Try one clear change and check whether the work moves correctly. Tell us what surprised you Message Streamlined with AUDIT. Share the pattern that repeated, how often something came back, or where you caught yourself taking work back. Leave out customer names and private details. Audience insights will help shape future conversations with the hosts and guests. At Streamlined Solutions, we help service businesses build clear processes, usable systems, and stronger team ownership. Your business should grow without everything falling back on you.
