RECLAIM: A Is for Autonomy

In previous articles, I introduced the RECLAIM model as a cultural operating system for law firms and explored the first four elements: Respect, Equity, Clarity, and Learning. This month, I turn to A: Autonomy.

Let me introduce you to Priya.

Priya is a fifth-year associate with a busy corporate practice at a mid-sized firm. She is capable, hardworking, and well-liked by clients. She has recently found her work coming from one partner, and the working relationship follows a pattern. He hands her a file and tells her it is hers to run. Then he rewrites her drafts, not for substance, but for style. He asks to be copied on every client email. When opposing counsel sends over a question, he often answers it before she has seen it.

Priya has noticed a change in her own work lately. She no longer asks herself what the best approach to a problem is. She asks what the partner would want.

She has stopped doing her best thinking. She is guessing at his. She is also feeling increasingly demotivated to the point that she has started talking to a recruiter about options.

Autonomy.

Why Autonomy Is Not Optional

A quick reminder about how this fits into our human operating system. Neuroscientists describe the brain as a prediction machine. At every moment it is forecasting what will happen next and checking those forecasts against what arrives from the environment, the body, and the social world. The more accurate the predictions, the more efficiently the brain manages its energy budget and the safer we feel. Security enhances cognitive capacity. That is the deep logic our brains operate from.

Autonomy is a social input our brain is alert to. It is one of the five social domains in David Rock’s SCARF model. When we have meaningful control over our work, our choices, and our environment, we can predict more of what happens to us, and the brain reads that control as reward. When control is stripped away, the brain registers threat. Attention narrows. Stress rises. The quality of thinking, which is the product law firms actually sell, degrades.

This is why micromanagement is so reliably corrosive, and why the cost runs in both directions. The associate (or staff member) disengages, and the supervising lawyer stays trapped in work the firm hired other people to do. Nobody reclaims their time by doing everyone’s thinking for them.

More Than “Stop Micromanaging”

The usual prescription for autonomy is simple: stop micromanaging. The advice is correct. It is also incomplete.

Telling a supervising lawyer to let go of a file is like telling a conscientious driver to take their hands off the wheel. A lawyer who hands a matter to a third-year with “it’s all yours” and disappears has granted abandonment not autonomy.

Autonomy is not the absence of structure. It works because of structure.

Build the Sandbox

The sandbox metaphor usually gets used in business as a play area: a consequence-free corner where people can experiment. I want to use it differently.

Think about why a sandbox works. The walls. The walls hold the sand in. They mark the edge between where the child decides and where the parent does. And they are precisely what allows the parent to sit on the bench instead of hovering, because everything inside the walls is safe.

The walls do not constrain the play. The walls are what make unsupervised play possible.

That is what autonomy needs in a law firm. The walls are the defined edges of a piece of work: what done looks like, when it is due, when you will talk about progress and answer questions. Inside the walls, the how belongs to the person doing the work. Build the sandbox well and three things happen at once: autonomous action becomes safe, errors surface while they are still small, and files become opportunities for learning.

Three walls matter most.

First: A delegation process that sets everyone up for success

Delegation is where autonomy is granted or withheld, and most firms leave it to individual habit. A sound process is not complicated: clear instructions about the outcome and its context, a timeline, genuine availability for questions, and check-in points agreed at the moment of handoff.

That last element is crucial. A check-in agreed in advance is structure. Structure provides a sense of security. A check-in imposed midstream can come across as surveillance. “Is it done yet?” “Have you started?” These questions signal distrust and aren’t simply annoying. They are motivation killers.

Second: Ownership of the how

Once the metaphorical sandbox walls are set, team members decide how they tackle their work and are held accountable for the quality of the product and timely delivery. Define outcomes, not methods, unless necessary. If a precedent is to be followed or a firm convention applies, say so at the handoff; that is a wall, and walls are fair. What is not fair is leaving the method open and then rewriting the work to match an unstated personal preference.

The same principle applies to change. When firms roll out new technology or workflows, leaders rightly decide the destination, but the people who live inside those systems every day need to have genuine input and real choices about how to get there. Autonomy during change is the difference between a team that adopts and a team that complies and grumbles.

Third: A shared discipline of feedback

Autonomous work is best supported by a feedback system that flows smoothly in both directions. The associate running a file, or staff member taking on a task, needs to know how the work is landing. The supervising lawyer who has stepped back needs confidence that problems will be surfaced fast. Both depend on feedback, and at many firms feedback is left to individual personality: some partners give it well, some give it harshly, and others barely give it at all.

The fix is to train every lawyer in one consistent approach to giving and receiving feedback. On the giving side: specific, behavioural, tied to the work, and oriented to progress, catching what is working as well as what needs to change. On the receiving side, the half that is almost always skipped: how to ask for feedback, how to listen without mounting a defence, and how to turn a vague “this needs work” into something usable.

When everyone at the firm gives and receives feedback along the same lines, feedback stops being an event and becomes a regular part of the work. Course corrections feel routine rather than personal. Errors get surfaced while they are easily remedied. The sandbox stays safe, and the learning never stops.

Operationalizing Autonomy

Here are three actions a supervising lawyer can put in motion this quarter:

1. Adopt a delegation protocol. Put it in writing and follow it. When assigning work, provide background information, the outcome and why it matters, the deadline, and check-in points. Provide feedback on the work product. Use this protocol for every significant delegation for ninety days to firmly establish the walls of your sandbox.
2. Make effective delegation and feedback and essential part of your firm’s operations. Train the whole firm in one consistent. Not just partners. Lawyers and staff, giving and receiving. Develop a simple model, run a working session, and practice with real examples.
3. Audit your own redlines. For two weeks, choose some opportunities to review your edits. Notice, what were the substantive edits, and what was a stylistic preference. Send the substance back with your reasons. Let the preference go, or name it once as a convention you like followed. Then watch what happens to the next round of drafts.

Watch out for these Autonomy undermining moves

• Rewriting a draft for personal style rather than substance, without explaining the difference
• Taking back a task at the first wobble instead of coaching through it
• Requiring a cc on every email after handing over a client relationship
• “It’s faster if I just do it myself”
• Announcing changes to systems and processes with no input from the people who use them daily

Each of these examples is small. Each one teaches the same lesson: this is not really yours. People who learn that lesson stop bringing judgment to work and start bringing compliance. Compliance does not develop nor produce the thinking clients pay for.

Returning to Priya

Nothing Priya’s supervising lawyer does is malicious. He is careful, his standards are high, and every override feels to him like quality control. But each one lands in Priya’s brain the same way: as a threat to her control over her own work. And the work product he gets back is shrinking to fit the space he leaves for it.

Now picture the same partner and the same files with a sandbox in place. A clear handoff. Check-ins agreed in advance. Feedback flowing both ways in a shared language. The how belongs to Priya. Errors surface at the check-in, while they are small and fixable. Priya is learning at full speed, and the partner is sitting on the bench, free to do the work only he can do.

One parting thought: While AI will throw a spanner into how we develop lawyers in the future, the need for autonomy and the feedback that supports learning and growth will remain a dependable constant. Start honing your leadership approach now.