Read a sample: 1. Leading Where Rules Matter
Maya has just sat down for a routine team meeting when an analyst asks a question that changes its direction.
A client is waiting for a service request to be completed. The analyst, Eli, has found a mismatch between information in the request and information in an existing record. The team’s written procedure says to resolve specified discrepancies before processing. Eli cannot tell whether this mismatch falls into that category. The colleague who usually handles unusual cases is away, and the client’s account manager has already asked why the request is taking so long.
“What do you want me to do?” Eli asks.
Maya manages the team responsible for reviewing these requests. She knows that releasing the request without the required review could create a compliance problem. She also knows that stopping work on every minor inconsistency could delay clients unnecessarily and overwhelm the people who handle escalations. Most important, she does not yet know whether this particular mismatch requires a hold.
Her answer will do more than move one request forward. It will tell Eli what matters, how uncertainty should be handled, and whether raising an awkward question is welcome. It may also shape what the rest of the team does the next time a client is waiting and a procedure is unclear.
Maya could give an immediate instruction: “Pause this request while we check the applicable procedure. Don’t make changes to the original record.” She could ask the team what they have seen in similar cases and where the current procedure leaves room for interpretation. She could guide Eli through the evidence and help him identify the point at which he needs a decision from someone else.
Each response has a place. None is a substitute for knowing the relevant requirement, and none makes Maya’s responsibility disappear.
This fictional team will appear throughout the book. Its circumstances are intentionally ordinary: people are trying to serve clients, follow procedures, meet deadlines, and use their judgment with imperfect information. The pressure does not come from a villain determined to break the rules. It comes from a familiar collision between work that must move and a decision that must be made carefully.
Leadership in regulated work begins with a dual responsibility: uphold applicable requirements and support the human judgment needed to carry them out.
The first responsibility is easy to state. Some actions are required, some are prohibited, and some decisions belong to designated people or functions. A manager cannot turn a binding requirement into an optional team preference because it feels inconvenient. Nor can a well-intentioned employee create authority simply by being confident.
The second responsibility is just as important, although it is sometimes treated as secondary. Rules do not interpret every fact, resolve every conflict in a procedure, or tell employees how to notice that something is wrong. People must recognize exceptions, distinguish evidence from assumptions, ask for help, and communicate information that others may not want to hear.
A manager who emphasizes requirements but neglects judgment may produce a team that follows familiar instructions and freezes when a situation changes. A manager who emphasizes empowerment without clear boundaries may produce a team that makes enthusiastic but unauthorized decisions. Effective leadership holds both responsibilities together.
That does not mean every decision must be a group discussion. It means the manager is deliberate about where direction is necessary, where consultation can improve a choice, and where coaching can build an employee’s ability to reason within the limits of the role.
The distinction matters because “compliance” can sound like a single, fixed instruction when the work contains several different kinds of decisions. A confirmed obligation may require a particular action. An internal policy may prescribe how the organization carries it out. A local procedure may leave the team a choice about sequence, assignment, or communication. And sometimes the people involved do not yet know which of those categories applies.
In Maya’s case, the immediate question is not whether the team likes the discrepancy rule. It is whether the facts of Eli’s request fall within it. Until that is clear, Maya needs an appropriate way to manage the work and obtain an answer from the right source. Her authority to manage the team does not automatically make her the final interpreter of every applicable requirement.
This book examines directive, consultative, and coaching leadership as approaches to a decision or interaction. They are not permanent personality types. A manager can use all three in the same afternoon, sometimes in the same conversation.
Directive leadership makes an instruction or decision clear. It identifies what must happen, who is responsible, and, when relevant, when to stop or escalate. Maya might direct Eli to pause processing while the discrepancy is checked. That instruction reduces ambiguity at a moment when acting prematurely could be difficult to undo.
Directive leadership is valuable when the requirement is established, authority is clear, or the situation calls for prompt action. It becomes less useful when a manager gives orders without listening to information that could change the decision. If Maya says, “Just follow the procedure,” without checking whether the procedure answers Eli’s question, she has supplied the appearance of clarity rather than clarity itself.
Consultative leadership seeks relevant input before a decision is made. Maya might ask the analysts where similar mismatches appear, what steps they currently take, and which part of the procedure is difficult to apply. The people closest…