Skip to content
signalby Travis Loudin

Type to search.

    manuals /leadership / the-shield

    The Shield

    Protecting focus

    by Travis Loudin
    Part 3 of 15field-testedplanted

    Deep technical work needs long, quiet stretches. The leader's job is to absorb noise, churn and shifting priorities so the team can build.

    “Be an umbrella, not a funnel.”

    Common in tech circles. Usually with a saltier word.

    What it means

    Pressure from above should stop with you. Pass on the context and the reasons, translated into clear priorities. Hold back the noise, not the information.

    In practice

    Before forwarding an escalation, rewrite it as a calm request with a clear ask and a realistic date.

    “Maker's schedule, manager's schedule.”

    Paul Graham. Essay of the same name, 2009.

    What it means

    Managers work in one-hour blocks. Makers need half days. One meeting in the middle of an afternoon can wreck a builder's whole block.

    In practice

    Cluster meetings at the start or end of the day. Protect no-meeting blocks and defend them when others try to book over them.

    “Every yes is a no to something else.”

    Common usage

    What it means

    Capacity is fixed. Accepting new work silently takes it from existing commitments. Sequencing competing requests is the leader's job, not the individual's.

    In practice

    Answer new requests with "Yes, and here's what moves" rather than a bare yes. Make the tradeoff visible to whoever asked.

    Triage rotation

    Common practice in support and engineering teams. Also called an interrupt shield or on-call.

    What it means

    Interruptions need one front door. When a request can reach anyone at any time, nobody gets to concentrate. One person catching them for a set period lets everyone else go deep.

    In practice

    Decide where requests come in and tell the people who send them. A weekly rotation is the usual form: the person on it acknowledges fast and routes well, and doesn't have to solve everything.

    Clearing the path

    “The day soldiers stop bringing you their problems is the day you have stopped leading them.”

    Colin Powell. My American Journey, 1995, written with Joseph E. Persico.

    What it means

    Problems landing on your desk are a sign that people think you can help and will. When they stop arriving, the problems are still there. People have decided that telling you is not worth the trouble.

    In practice

    When someone brings a problem, do something about it that they can see, and tell them how it ended. If the team has gone quiet, go and ask what they have stopped mentioning.

    Pride of workmanship

    W. Edwards Deming. Point 12 of his 14 Points for Management, in Out of the Crisis, 1982.

    What it means

    Most people want to do work they can be proud of. What stops them is usually built into the job, such as poor tools, unclear standards and targets that reward speed over quality. Deming made removing those barriers management's work.

    In practice

    Ask each person what keeps them from doing work they are proud of. Pick one answer you can do something about, fix it, and tell them when it is done.

    “What do I do that wastes your time without contributing to your effectiveness?”

    Peter Drucker. The Effective Executive, 1967, in the chapter "Know Thy Time".

    What it means

    Some of what is in the team's way was put there by the leader. The report nobody reads, the approval that adds a day and the meeting that could have been a note all cost the team time and give nothing back.

    In practice

    Ask it in one-on-ones and wait for a real answer. Then drop one thing they name, and tell the team it is gone.

    Remove impediments

    Scrum. The Scrum Guide, by Ken Schwaber and Jeff Sutherland, makes this part of the Scrum Master's job.

    What it means

    Asking what is in the way is the easy half. The job is to see that it gets cleared. A leader who can't clear it personally still owns finding who can and staying on it.

    In practice

    Keep a short list of what is blocking the team, where the team can see it, with a name and a next step on each item. When the answer is no, say so and say what was tried.

    The three-email rule

    Common usage. Often credited to Phil Simon, who made the case for it in Message Not Received, 2015. Older versions of the rule exist, some with a different number.

    What it means

    Writing is slow at settling anything unclear. Every relay loses detail and every reply adds a day. Ten minutes of conversation between the people who hold the problem usually ends it.

    In practice

    When a thread reaches its third round without an answer, or a question is travelling second-hand, stop typing. Get the person with the problem and the person who can fix it talking today, then write down what was decided. If it is your team that is stuck, don't wait to be asked: set up the call.