Your Law Firm Doesn't Have an Accountability Problem. It Has an Ownership Problem.

"We need more accountability."

I hear some version of this from law firm leaders all the time.

People aren't following through.

Projects aren't getting completed.

Problems linger too long.

Employees aren't taking enough initiative.

Managers aren't managing.

Everyone is frustrated that things keep falling through the cracks.

So leadership concludes:

We have an accountability problem.

Sometimes that's true.

But often, when I dig into the organization, I find a different problem.

Nobody clearly owned the outcome in the first place.

The firm is trying to create accountability after something goes wrong without establishing ownership before it does.

Those are not the same thing.

Before I ask:

Who should be held accountable for this?

I want to know:

Who owned it?

And if nobody can answer that question clearly, I don't think you have an accountability problem yet.

You have an ownership problem.

Accountability Starts Before Something Goes Wrong

Law firms often talk about accountability reactively.

A deadline gets missed.

A client complains.

A prospect doesn't get followed up with.

A project stalls.

A receivable reaches 120 days.

A software implementation goes nowhere.

Then leadership starts asking:

"Why didn't anyone catch this?"

"Why wasn't this done?"

"Why didn't somebody follow up?"

"Who was responsible?"

Those are reasonable questions.

But they're being asked too late.

The more important question should have been answered before any of that happened:

Who owns the outcome?

Not who participates.

Not who helps.

Not who gets copied on the email.

Not who has a task somewhere in the process.

Who owns whether the thing actually works?

That's where accountability begins.

Participation, Responsibility, Ownership, and Accountability Are Different

These concepts get blurred together constantly.

Someone can participate in a process without owning it.

Someone can be responsible for a task without owning the ultimate outcome.

Multiple people can have responsibilities.

But if an outcome matters to the business, I generally want one person who knows:

I own whether this works.

Take intake.

Marketing may generate the lead.

Reception may answer the phone.

An intake specialist may qualify the prospect.

An attorney may conduct the consultation.

Someone may send the engagement agreement.

Accounting may collect the retainer.

Technology may automate follow-up.

Lots of people participate.

Lots of people have responsibilities.

But who owns the outcome?

Who owns qualified-lead-to-engaged-client conversion?

If conversion falls significantly next month, whose number turned red?

Who notices?

Who investigates?

Who determines what changed?

Who listens to calls?

Who evaluates follow-up?

Who looks at individual performance?

Who changes the process?

Who reports back on whether the changes worked?

If the answer is:

"Well, all of us, really."

Then my concern is that nobody owns it.

When Everyone Is Responsible, Nobody Is Accountable

This is one of the most common organizational problems I see in law firms.

Ask who owns collections.

You may hear:

"Accounting sends the invoices and statements."

"The attorneys are responsible for their clients."

"The billing person follows up."

"Partners get involved when something gets really old."

"The managing partner looks at A/R."

Okay.

Who owns A/R performance?

Silence.

Everyone has a piece.

Nobody owns the outcome.

You see the same thing with:

intake.

marketing.

recruiting.

employee development.

client experience.

technology implementation.

attorney utilization.

process improvement.

matter profitability.

staffing.

performance management.

Lots of people touching the work can create the illusion that something is owned.

It isn't.

Stop Asking "Who Dropped the Ball?" Start Asking "Who Owned the Ball?"

That's the question I want leadership asking.

If you can't tell me who owned the number before it turned red, don't ask me who should be accountable after it does.

That's not fair accountability.

That's retrospective blame.

Real accountability is created by clarity.

The employee knows what they own.

Leadership knows what they own.

The expected outcome is defined.

Authority is clear.

Performance is measurable.

Everyone knows what happens when the result isn't where it should be.

Now you have something you can manage.

The Managing Partner Becomes the Default Owner of Everything Nobody Else Owns

This is where unclear ownership becomes especially expensive.

Problems don't disappear just because nobody owns them.

Eventually, they move upward.

A project stalls.

The managing partner notices.

A client hasn't paid.

The managing partner gets involved.

An employee isn't performing.

The managing partner handles it.

The CRM implementation isn't moving.

The managing partner asks for an update.

Intake numbers decline.

The managing partner starts asking questions.

Nobody followed up on something important.

The managing partner follows up.

Then I hear:

"Why does everything come back to me?"

Because the organization never gave those outcomes anywhere else to live.

When ownership isn't deliberately assigned, the owner of the business becomes the default owner.

And eventually, the owner's capacity becomes the organization's capacity.

Your Managing Partner Shouldn't Be the Default Owner of Every Problem Nobody Else Owns

This is a structural issue, not a time-management issue.

You can give the managing partner a better calendar.

You can teach them to delegate.

You can hire an executive assistant.

You can tell employees to "take more initiative."

But if nobody else clearly owns important business outcomes, the problems will keep coming back.

The organization has been designed that way.

This is one reason I care so much about organizational structure as firms grow.

A scalable org chart isn't simply a collection of titles and reporting lines.

It should answer:

Who owns what?

Who decides what?

Who is accountable for what?

What can they change without asking permission?

When does something need to be escalated?

If those answers aren't clear, putting boxes on an org chart won't solve much.

Ownership Without Authority Isn't Ownership

This is where firms often get halfway there.

Leadership says:

"Jane owns intake."

Great.

Can Jane change the intake scripts?

Can she modify follow-up?

Can she adjust the CRM workflow?

Can she coach the intake team?

Can she address poor performance?

Can she change scheduling procedures?

Can she recommend staffing changes?

Can she implement reasonable process improvements?

Or does Jane have to ask the managing partner before she changes anything meaningful?

If Jane is responsible for intake conversion but doesn't have the authority to influence intake conversion, Jane doesn't actually own intake.

She owns the blame.

That's very different.

I've said this before because it matters:

Authority without accountability creates chaos. Accountability without authority creates frustration.

You need both.

Sometimes Leaders Say They Want Ownership but Keep All the Decisions

This is an uncomfortable one.

A managing partner tells a manager:

"I need you to take ownership."

The manager makes a decision.

The managing partner changes it.

The manager handles an employee issue.

The employee goes directly to the managing partner and gets a different answer.

The manager changes a process.

The managing partner wants to approve every detail.

The manager addresses performance.

The managing partner softens the consequence because they don't want the employee upset.

Then leadership says:

"Why won't my managers take more ownership?"

Because you've taught them that ownership isn't real.

People stop confidently making decisions when their decisions are routinely overridden.

Eventually, the safest behavior becomes:

Ask the managing partner.

Now the managing partner has exactly the organization they claim not to want.

Ownership Requires an Outcome, Not Just a Job Description

Here's another place firms get stuck.

"Who owns marketing?"

"Sarah."

Okay.

What does Sarah own?

"Marketing."

That tells me almost nothing.

Does she own vendor coordination?

Social media?

Brand?

Lead generation?

Qualified lead volume?

Marketing spend?

Cost per acquisition?

Marketing ROI?

Business development?

Website traffic?

Those are very different things.

Likewise:

"John owns intake."

Does John supervise the intake employees?

Or does John own the performance of the intake function?

Those aren't necessarily the same thing.

A title does not automatically define an outcome.

Stop Assigning Tasks When You Should Be Assigning Outcomes

This is one of the biggest shifts I try to make when developing managers.

Compare these two instructions:

"Run the A/R report every Friday."

versus:

"You own keeping A/R over 90 days below our target. The weekly report is one of the tools you'll use to manage it."

The first person owns a task.

The second person owns an outcome.

That's a very different job.

Or:

"Review intake calls every week."

versus:

"You own intake conversion. Call review is one of the ways you'll diagnose performance and improve it."

Or:

"Send the monthly utilization report."

versus:

"You own monitoring attorney capacity and identifying when workload, utilization, or allocation indicates we need to intervene."

Tasks tell people what to do.

Outcomes tell people what they're trying to accomplish.

Strong organizations need both.

But if you want ownership, eventually you have to move beyond task assignment.

If You Have to Tell Someone Every Step, They Don't Own It Yet

This doesn't mean employees should be thrown into the deep end without training.

Someone learning a new role may need significant direction.

That's normal.

But mature ownership should eventually sound like:

"Here's the outcome."

"Here are the guardrails."

"Here are the resources."

"Here are the decisions you can make."

"Here is when I want you to escalate."

"Here is how we'll measure success."

Then let them operate.

If the managing partner is still determining every step, solving every exception, and making every meaningful decision, ownership hasn't actually transferred.

The task has.

Ownership Requires Numbers

Not every outcome can be reduced perfectly to a KPI.

But if someone owns a business function, I usually want some objective way to understand whether that function is healthy.

If someone owns intake:

What's conversion?

What's speed to contact?

What's live-answer percentage?

What's follow-up compliance?

If someone owns billing and collections:

What's A/R?

What's over 90 days?

How quickly are invoices going out?

What percentage is being collected?

If someone owns attorney capacity:

What's utilization?

How is work distributed?

Where are the bottlenecks?

If someone owns marketing:

What are we spending?

How many qualified opportunities are we generating?

What is converting?

What is becoming collected revenue?

Ownership without visibility is difficult.

People need to know whether the thing they own is working.

But Don't Turn Ownership Into KPI Theater

Assigning someone a metric isn't enough.

"You're responsible for this number."

Okay.

What can they actually do about it?

A KPI should be connected to a management process.

Let's say intake conversion falls from 40% to 29%.

The intake owner shouldn't simply report:

"Conversion was 29% this month."

They should be asking:

Why?

Did lead quality change?

Did response time change?

Did call volume increase?

Did one team member's performance change?

Did follow-up decline?

Did consultation availability become a bottleneck?

Did a marketing source change?

Did the CRM automation break?

What are we doing about it?

What should we expect next month?

That's ownership.

The number isn't the job.

Managing the outcome is the job.

Ownership Doesn't Mean You Personally Do Everything

This is another important distinction.

Owners delegate.

In fact, they have to.

If you own intake, that doesn't mean you answer every phone call.

If you own collections, that doesn't mean you personally send every statement.

If you own recruiting, you don't personally perform every administrative step.

Ownership means you're responsible for making sure the system works.

You may coordinate people.

You may delegate tasks.

You may use software.

You may involve outside vendors.

You may escalate certain decisions.

But you remain the person watching the outcome.

That's what makes ownership scalable.

Accountability Is Not Blame

Some employees hear "accountability" and immediately assume:

"If something goes wrong, I'm going to get blamed."

That's not how I think good accountability should work.

Suppose the intake manager owns conversion.

Then marketing launches a new campaign that generates a large volume of low-quality leads.

Conversion falls.

Is that automatically the intake manager's fault?

No.

But I still expect the intake manager to notice.

I expect them to identify the change.

I expect them to bring the information forward.

I expect them to collaborate with marketing.

I expect them to help determine what's happening.

They own the health of the outcome even when they don't personally control every variable affecting it.

Ownership means:

I don't let this sit broken because technically someone else caused it.

That's very different from blame.

Good Owners Escalate. They Don't Dump.

There's a difference between escalation and transferring ownership upward.

A good manager might say:

"Here's the problem."

"Here's what the data shows."

"Here's what I've already done."

"Here are the two options I see."

"Here's the decision I need from you."

That's escalation.

Dumping sounds like:

"We have a problem. What do you want me to do?"

One preserves ownership.

The other hands it back to the managing partner.

If you're developing managers, teach them that distinction.

"Just Keep Me in the Loop" Can Quietly Destroy Ownership

Managing partners often say they want people to own things but also want to be copied on everything.

They want visibility into every decision.

They want to know about every issue.

They want to approve anything remotely unusual.

Some visibility is reasonable.

But be careful.

If every decision requires an audience, people start behaving like they need permission.

If every email includes the managing partner, employees may naturally look to the managing partner for the answer.

If every exception gets escalated, managers never develop judgment.

The goal isn't to create information silos.

It's to establish appropriate visibility without accidentally pulling ownership back upward.

Clear Escalation Rules Make Ownership Easier

People are more comfortable taking ownership when they know the boundaries.

For example:

You can resolve client service issues up to this point.

You can approve expenditures up to this amount.

You can make reasonable process changes without approval.

You can coach and document performance issues.

You need leadership approval before terminating an employee.

You need partner involvement if a client issue creates significant legal or reputational risk.

You should escalate if this KPI remains below target for two consecutive periods.

Now people aren't guessing.

Clear decision rights create confidence.

One Outcome Should Usually Have One Owner

This doesn't mean every process only involves one person.

Far from it.

Most meaningful business outcomes are cross-functional.

But if three people equally own something, I get nervous.

Who notices when it isn't working?

Who calls the meeting?

Who pushes the project forward?

Who follows up?

Who makes sure a decision gets made?

Collaboration is valuable.

Ambiguous ownership isn't.

Everyone can contribute to an outcome.

One person should own it.

Projects Need Owners Too

This doesn't only apply to permanent business functions.

It applies to projects.

"We're implementing a new CRM."

Who's the project owner?

"The CRM company is helping us."

That's not what I asked.

"We have a committee."

Still not what I asked.

"Several people are involved."

I know.

Who owns getting the implementation successfully completed?

The vendor doesn't own your implementation.

The committee doesn't magically create ownership.

Someone inside the organization needs to know:

This project is mine to drive across the finish line.

Otherwise projects drift.

Meetings Reveal Ownership Problems Quickly

Listen to the language in leadership meetings.

"We need to..."

"Someone should..."

"We should probably..."

"Can somebody..."

"Let's make sure..."

Those phrases should make you nervous.

Who?

By when?

What outcome?

Who follows up?

I don't want every meeting to become bureaucratic.

But decisions without owners are often just conversations.

Your Organizational Chart Should Answer More Than "Who Reports to Whom?"

This is why I think firms often misunderstand organizational design.

Reporting relationships matter.

But the better questions are:

Who owns intake?

Who owns collections?

Who owns people management?

Who owns attorney capacity?

Who owns technology?

Who owns marketing performance?

Who owns client experience?

Who owns recruiting?

Who owns financial reporting?

Who owns operational improvement?

Then:

Do they have the authority required to own it?

Do they have access to the necessary information?

Do they know how success is measured?

Does everyone else understand their authority?

That's a functioning organization.

Sometimes the Right Owner Isn't the Most Senior Person

Law firms have a tendency to assign ownership based on hierarchy.

The partner owns it.

The most senior employee owns it.

The person who's been here longest owns it.

Maybe.

But seniority doesn't automatically make someone the best owner.

Ownership should sit with the person best positioned to influence the outcome.

That person needs the appropriate skill, visibility, authority, and capacity.

Sometimes that's a partner.

Sometimes it's a COO.

Sometimes it's a department manager.

Sometimes it's an experienced staff member.

Sometimes it's a newer leader who has been specifically hired to build the function.

Put ownership where it can actually work.

Ownership Also Means Letting People Own Success

There's a positive side to this that doesn't get discussed enough.

Clear ownership doesn't only tell you who is accountable when something goes wrong.

It tells you who deserves credit when something goes right.

Intake conversion improves materially.

A/R declines.

A software implementation succeeds.

Attorney utilization improves.

Turnover decreases.

A process becomes dramatically more efficient.

When ownership is clear, you can recognize the person who drove the outcome.

That matters.

People are much more likely to think like owners when they're allowed to own both the responsibility and the success.

If Someone Repeatedly Can't Own the Outcome, Then You Have a Performance Question

This is where accountability finally enters the conversation.

Once ownership is clear...

Once the expected outcome is clear...

Once the person has appropriate authority...

Once they have the necessary tools and information...

Once leadership has provided reasonable support...

...then we can fairly evaluate performance.

Did they manage the outcome?

Did they identify problems?

Did they respond?

Did they communicate?

Did they exercise judgment?

Did they improve?

If not, now you may have an accountability or performance problem.

But notice how much groundwork came first.

Accountability works much better when the organization has earned the right to demand it.

Leaders Have to Be Accountable for Creating Accountability

You cannot build a vague organization and then blame employees for operating vaguely.

Leadership owns the structure.

Leadership decides who has authority.

Leadership determines whether managers are allowed to manage.

Leadership establishes expectations.

Leadership decides whether employees can bypass managers.

Leadership decides whether it will tolerate chronic underperformance.

Leadership determines whether responsibilities remain fuzzy because nobody wants to have a difficult conversation.

If you want an accountable organization, leadership has to create the conditions where accountability is possible.

Start With the Outcomes That Matter Most

You don't need to turn your firm into a giant RACI chart tomorrow.

Start simply.

What are the most important outcomes in the business?

For each one, ask:

Who owns this?

What does success look like?

How do we measure it?

What authority does this person have?

What decisions can they make?

When should they escalate?

How often do we review the outcome?

What happens when performance isn't where it should be?

If you can't answer those questions, start there.

The Problem Isn't Accountability. It's Ownership.

Most employees don't wake up thinking:

"How can I avoid accountability today?"

They operate inside the organization leadership created.

If roles are unclear, decisions are unclear, authority is unclear, and outcomes are unclear, you will get inconsistent ownership.

Then leadership will spend an enormous amount of energy chasing people.

Following up.

Reminding.

Checking.

Solving.

Escalating.

And eventually complaining that nobody takes accountability.

You can keep asking people to "take more ownership."

Or you can build an organization where ownership is actually clear.

Define the outcome.

Name the owner.

Give them authority.

Give them visibility.

Set the guardrails.

Measure the result.

Let them operate.

Then hold them accountable.

Because accountability shouldn't begin when someone drops the ball.

It should begin when everyone knows exactly who owns it.

If your managing partner is still the default owner of every important problem, your law firm may not need another conversation about accountability.

It may need clearer ownership.

At ING Collaborations, I help law firms build operational structures that define who owns what, where decision-making authority sits, how performance is measured, and when issues should escalate.

Because accountability isn't created by telling people to be more accountable.

It's created by building an organization where ownership is clear enough that people actually can be.