Communicating and leading, one lesson a day

Imagine you are the production manager in a family-owned bakery. For years you have worked six days a week, opening before dawn, solving supplier problems and stepping onto any station that falls behind. Now you are starting an intensive certification course, and the owners have agreed that you will work three shorter shifts. The agreement sounds clear. But if the same calls, favors and emergencies still find you, the schedule will shrink on paper while the job stays the same.

Today’s lesson is about making a reduction visible. A limit nobody else can see is not yet a working limit.

Start with Peter Drucker in The Effective Executive. Before you manage time, he says, record it. Not from memory and not from the feeling that you were busy. Write down where the hours actually went, then ask what would have happened if you had not done each thing. People who work by responding to demand are especially bad at estimating their own time. The days blur into a sense of constant motion.

For the bakery manager, “three short shifts” is an agreement. A record showing eighteen hours across mixing plans, deliveries and staff coaching is evidence. Keep the record while the new arrangement is young. Without it, every conversation about whether the change is working becomes a contest between two memories.

The second idea comes from Greg McKeown’s Essentialism: if it is not a clear yes, it is a no. That sounds easy until you notice how much work arrives without a direct request. A driver cannot find the receiving key. A decorator wants approval on a rush cake. A regular customer asks for an exception. Each task appears already halfway accepted because solving it would be quick.

The useful move is to make the choice explicit. “Supplier planning is part of my reduced role, so I’ll take that.” Or: “Same-day counter changes belong to the shift lead now.” The second sentence is not refusing to help the business. It is carrying out the new agreement in public, where other people can learn the new route.

This is where the two ideas meet. If only you know that your hours changed, coworkers will keep sending the old volume. Their workday has not changed. To change what arrives, change what they can see.

Cal Newport, in Slow Productivity, describes a pull system. Instead of allowing every request to be pushed onto you, keep a short visible list of active work. New work waits until something finishes. In the bakery, that might be a card beside the production board with the two issues you own this shift, followed by a queue. Everything else has a named route: the floor lead, the purchasing owner or next week’s planning session. The queue says no without turning every request into a personal confrontation.

The practical shape has three parts. First, keep a daily time record in plain language. Second, write a short scope statement: what you still own, what moved and who owns it now. Share it as confirmation, not as a plea. Third, put current work where the people around you already look. Keep only a few items active and route the rest to the queue.

The trap will appear quickly. You are experienced, so doing the small thing is faster than explaining the new path. That is true once. Across a month it rebuilds the old job. Newport calls the meetings, messages and follow-ups attached to every commitment an overhead tax. The five-minute favor rarely costs only five minutes. It creates a tail, and the tails are what consume the time you removed.

The record is not only for the owners. It is for you later, when you are tired and trying to decide whether the arrangement really held. Without a record you will have a feeling. The feeling may be accurate, but it is weak in a negotiation and easy to dismiss. A simple log lets you talk about time, value and the next adjustment without guessing.

Try this today. Open a page and write what took your time over the last four working days. Use one line per day. Then draft three sentences: what you own now, what you no longer own and where that work goes. If the note sounds apologetic, remove the apology. Finally, choose one place the team already checks and make your active queue visible there.

That is lesson eighteen. A smaller role survives when the hours, scope and queue can all be seen.