Skip ahead to the main page
Partner Huddle
Pages

2 kinds of client decisions: objectives and means

Partner Huddle Editorial Team · Published · 15 min read

The client owns the objectives — what the work is for and what winning looks like — while you own the means: the method, sequence, tools, and team. Consulting on means means the client hears your approach and can raise concerns, not that they pick your tooling.

  • Objectives answer: what problem are we solving, what does success look like, what's out of bounds, what trade-off does the client accept
  • Means include: method and technology, work sequence, team assignments, milestones and check-ins, design pattern or data model
  • When you disagree on means: restate their objective, explain your chosen route and trade-off, name what you need from them to proceed
  • A "dashboard" is a means, not an objective — ask what decisions it should enable to find the real objective
  • Significant changes to scope or fee need updated paperwork; treat minor course corrections inside your means as a practice call you handle in your plan.

Chief takeaways

  • The client owns the objectives — what the work is for and what winning looks like — while you own the means: method, sequence, tools, and team.
  • A "dashboard" is a means, not an objective — ask what decisions it should enable to find the real objective.
  • Significant changes to scope or fee need updated paperwork. Handle minor course corrections inside your means in your own plan.
  • When you disagree on means, restate their objective, explain your chosen route and trade-off, and name what you need from them to proceed.

Why this distinction decides your scope

You scope a project for a client every week. You decide what's in, what's out, who does what, and by when. Half the friction you feel comes from treating all those choices as one pile. They aren't.

ElementObjectiveMeans
OwnerClientYou, with client consulted
Rule languageAbide by client's decisionsConsult as to the means
Example questionWhat problem are we solving?What method do we use?
Scope impactAnchors every later trade-offSets the route to the anchor

The Pennsylvania rule on scope and authority splits them cleanly. A lawyer must "abide by a client's decisions concerning the objectives of representation" and must consult with the client about "the means by which they are to be pursued" ( 204 Pa. Code Rule 1.2).

Two categories. Objectives: what the work is for, what winning looks like, what the client is trying to achieve. Means: how you get there — the method, the sequence, the tools, the route.

You own the second. The client owns the first.

That rule governs lawyers, but the logic transfers directly to partners and operations leads scoping client work. When you hold your side of the line, decisions go faster and nobody feels robbed of control. When you cross it, you either deliver something the client didn't want or stall waiting for approvals that were never theirs to give.

This post works through both kinds of decisions, where they blur, what happens when the client's chosen objective runs into your constraints, and how to write scopes that keep the two separate.

The client's call: the objectives

The commentary on Rule 1.2 makes the boundary explicit: the client holds "the ultimate authority to determine the purposes to be served by legal representation, within the limits imposed by law and the lawyer's professional obligations."

Strip the legal context and the principle is simple. The client decides what the work is for. Your job is to achieve that purpose, not to substitute your own.

In practice, objectives are the answers to questions like:

  • What problem are we solving?
  • What does success look like at the end?
  • What is out of bounds entirely?
  • What trade-off does the client accept: speed over cost, quality over speed, cost over scope?
  • What happens next after this project completes?

If the client answers those, you have your objectives. If you answer them, you've taken a decision that isn't yours.

Why does this matter more than it looks? Because objectives anchor every later trade-off. Once the client has said "we want this ready before the launch window," you know which lever to pull when a delay appears. Without that anchor, you're guessing.

There's a limit, and the rule states it: objectives must stay "within the limits imposed by law and the lawyer's professional obligations." For you, the equivalent limits are your professional standards, your contract, your team's capacity, and anything regulatory about the work itself. The client can choose any lawful objective. They can't order an unlawful one.

Questions that reveal the real objective:

Clients rarely state the objective in one sentence. You draw it out with questions that expose what is actually being achieved:

  • "What will you do differently on the day this ships?"
  • "Which stakeholder will notice first if we miss?"
  • "If we only did part of this, which part matters?"
  • "What's the cost of doing nothing for another quarter?"

Their answers define objectives better than any brief. When a client says "improving efficiency," push until you hear something measurable: which workflow, which metric, which stakeholder. The gap between the vague phrase and the concrete answer is where scope disputes later grow.

Your call: the means

The means are everything else. Not what you're achieving, but how.

The rule is explicit that a lawyer must consult with the client on the means. Consult, not ask permission. That distinction matters enormously for your scoping work.

Means includes:

  • The method and technology
  • The sequence of work
  • Which team member does what
  • How you structure milestones and check-ins
  • The design pattern, the data model, the campaign structure
  • What you try first when there are several viable routes

Consulting means the client hears the approach and can raise concerns. It does not mean they pick your tooling. When you hand them a menu of technical decisions, you've shifted your responsibility onto them. They'll either pick based on what sounds familiar — often a bad outcome — or bounce the decision back to you after a delay.

Handling a disagreement about means

Disagreement about methods is normal and expected. The commentary says outright: "On occasion, however, a lawyer and a client may disagree about the means to be used to accomplish the client's objectives."

How you handle that disagreement decides whether the relationship survives it.

Three moves work:

  • Restate the objective they chose. Put it in their words. Confirm they still hold it.
  • Explain your chosen means and the trade-off you're accepting. Be specific: what you gain, what you give up.
  • Name what you need from them to proceed: a decision by a date, an introduction, access to a system.

If they still insist on their own means, you have a choice. You can accept — provided the route can reach the stated objective — or you can say plainly that you don't think their route gets there. Document what you recommended and what they decided. That protects both sides.

What you don't do is silently comply with a means you believe fails the objective. You've been hired for your judgment. Using it is part of the job.

A side-by-side view of the split

This table maps the split so you can use it when writing or reviewing scope.

QuestionObjective (client decides)Means (you decide, client consulted)
What is this for?YesNo
What does success look like?YesNo
What's out of bounds?YesNo
Which method or tool?NoYes
What's the work sequence?NoYes
Who on your team does what?NoYes
When do we check in?No Yes, with client input

When you review a scope, run each line down the left column and ask: whose decision is this? Anything in the client column that your team has pre-filled is a guess. Anything in your column that you've parked on the client is an abdication.

Where the line blurs, and how to pull it straight

Three common situations blur the objective–means split. Each has a fix.

A client hands you a method and calls it an objective.

"We need a dashboard" sounds like an objective. It's a means. Ask what decisions the dashboard should enable. That answer is the objective. You may then build a dashboard — or you may find a simpler route reaches the same objective faster.

Flip it too. "We need to improve retention" is an objective. It tells you nothing about how. Good. That's your space.

An objective quietly contains means.

"We want this built on our existing stack" is partly an objective (the constraint is real — legacy systems, internal skills, compliance) and partly a means. Separate them. The constraint may be firm; the specific tool choice within it may not be. Write both lines explicitly in the scope so no one sentence carries two kinds of decision.

Your scope document writes means as if they were the client's to set.

This happens constantly. A statement of work lists milestones the client must approve, formats the client must supply, review cycles the client must staff. Those are your means. Consult, agree on what you need from them, then own the plan.

Decision rights when the objective is unlawful or impossible

Sometimes the client's chosen objective runs into a hard limit. The commentary addresses this: if a lawyer comes to know or reasonably should know "that a client expects assistance not permitted by the Rules of Professional Conduct or other law or if the lawyer intends to act contrary to the client's instructions, the lawyer must consult with the client regarding the limitations on the lawyer's conduct."

Two directions of conflict:

  • The client wants something your standards, contract, or the law won't allow.
  • You plan to act contrary to their instructions — perhaps because following them would breach your standards.

In both cases: consult, explain the limit, and agree a revised path. Don't quietly comply. Don't quietly defy.

For scoping, this shows up as: the client asks for a deadline that requires your team to skip testing; they ask you to sign off on claims you can't verify; they ask you to use data in a way your policies prohibit. Name the limit early. Put the revised path in writing. Move on.

If the client has diminished capacity to decide — a rare but real situation — the rule points to a separate framework. For you, the plain-language version: if someone in the room clearly can't evaluate what's being decided, slow down, involve the people who can, and get decisions confirmed in writing by someone authorized.

Changing scope mid-engagement

Objectives shift. The client learns something, the market moves, a stakeholder changes their mind. The means shift too — a tool doesn't work, a dependency slips.

Change typePaperwork neededLogging habit Example
Significant scope changeUpdated letter of engagementDate, who asked, new wordingNew objective added
Significant fee changeUpdated letter of engagementDate, who asked, new wordingPrice rises
Minor means correctionNone Only if cost, timeline, or risk shiftsTool substitution
Objective restatedConfirm in writingOne line for each changeLaunch window moves

The New York State Bar Association guidance on engagement agreements draws the line at materiality: "Where there is a significant change in the scope of services or the fee to be charged, an updated letter of engagement shall be provided to the client" ( NYSBA).

Significant changes get new paperwork. A reasonable working habit: treat minor course corrections inside your means as changes you log in your own plan.

Practical test: would a reasonable client see the change as altering what they're buying? If yes — new objective, new scope line, updated agreement. If no — it's a means adjustment. Handle it in your plan and tell the client briefly.

Two habits keep this clean:

  • Log every objective change with date, who asked, and the new wording. One line each.
  • Log means changes only if they affect cost, timeline, or risk the client accepted. Otherwise they live in your plan.

When you ask for the update, do it before the work starts on the new objective. Retroactive paperwork erodes trust.

Communicating decisions while the work runs

A decision the client can't see is a decision they don't believe you made. Communication obligations run in both directions.

DevelopmentEscalate?ReasonExample
Objective changeYesAlters what the client is buyingSuccess criteria shift
Means change with cost impactYes Touches accepted riskBatch approach adds a week
Developer assignmentNoInternal to your planModule ownership
Discovered constraintYesNarrows their optionsCompliance limit found

The California bar rule carries a useful principle: an oral settlement offer in a civil matter must be communicated if it's "a significant development" under the communication rule ( State Bar of California).

Transfer it: significant developments get communicated, promptly, in clear language. Not buried in a status report. Not held until the weekly call.

What counts as significant for your work:

  • A change to the objective, or a risk to achieving it.
  • A means change that touches cost, timeline, or risk the client accepted.
  • A constraint you've discovered that narrows their options.
  • A decision you've made that they'd reasonably want to weigh in on.

What doesn't need escalation:

  • Which developer handles a module.
  • The internal order of your tasks this week.
  • Tool substitutions inside your agreed constraints that change nothing they can observe.

If you're unsure, over-communicate once and calibrate. Under-communication is what breaks trust.

Sample email: announcing a means change

Hi Maya,

We're still targeting the launch date you set. The import tool we planned to use can't handle your volume, so we're switching to a batch approach.

That adds a week to the build. Cost unchanged.

You don't need to decide anything. Flagging it because you'd want to know before it hits the schedule. I'll confirm the new date by Friday.

—

Note what the note does: restates the objective, names the means change, states the impact, and says clearly that no client decision is needed.

Scoping examples that keep the two apart

A well-built scope writes objectives and means in different sections, with different verbs.

Objectives section. Client-owned. Verbs: achieve, reach, enable, avoid. One line for each objective. No tools, no phases, no deliverable formats.

Means section. Your section. Verbs: build, run, sequence, test. Contains milestones, method, tooling, team, check-in cadence. Mark what you're consulting on and what you've already decided.

Constraints section. Shared. Includes anything that limits either side: dates, budgets, systems, policies, regulations. Each constraint names who holds it.

Change section. Says exactly how objective changes and means changes get handled, and who signs what.

One rule of thumb for the whole document: if a sentence answers "what are we trying to achieve," it goes in objectives. If it answers "how will we do it," it goes in means. Sentences that answer both should be split.

Running decisions in the room

Live meetings are where the split collapses most often. A stakeholder says "let's use the vendor we already have." Another says "no, we should build it." You've now got means debated as if they were objectives.

Pull it back with one question: "Which objective does that serve?" If they name it, you're back on track and can evaluate the means against it. If they can't, the objective isn't clear yet — stop and define it before choosing anything.

Other patterns worth naming:

  • Silence treated as approval. If nobody objects, don't assume agreement on objectives. Restate and get a yes.
  • The loudest stakeholder sets the objective. The client decides, but the client is not one voice. Ask who holds the decision and take the answer to that person.
  • Deciding means to avoid deciding the objective. Tool debates are comfortable; objective debates are hard. If you notice repeated meetings about vendors and none about success criteria, call it.

The delicate case: work already underway

The hardest version of this is mid-flight. The commentary flags it directly: "When the client's course of action has already begun and is continuing, the lawyer's responsibility is especially delicate."

The delicate part: the client has committed money, reputation, people. A new fact arrives. You can see the objective no longer works. But saying so costs them something.

Handle it in this order:

  • Separate what's sunk from what's still open. Sunk cost is not an objective.
  • State the new fact plainly. No framing, no softening that obscures it.
  • Restate the objective as they set it. Confirm it still holds.
  • Offer two routes from here: continue as planned, or change course. Give the cost and timing of each.
  • Let them choose. Record the choice.

You advise; they decide. Even when the decision looks wrong to you, it's theirs — within the limits. Your protection is clean advice, given in time, in writing.

If continuing their chosen course would require you to act against your standards, you're back in the limits territory from earlier: consult about the limitation, agree a path, document it.

Related guides: Accounting Client Intake Checklist for a Clear Handoff · ACH invoice fees: 4 facts to check before a client pays · Bank feed checks: 8 items for client reconciliation.

FAQ

Can the client override my technical approach if I've explained why mine is better?

If it won't reach it, say so in writing and recommend the alternative. Document their instruction. That's your record that you advised clearly.

What if the client keeps adding objectives without changing the budget?

Then they haven't changed the objective — they've asked for more. Restate the original objective, list the new one as a separate objective, and show what each costs in time or money. The choice between them is theirs. If they want both at the original budget, that's a new constraint they're imposing; surface it and let them decide what to drop.

Does consulting on means mean I need sign-off on every task?

No. Consult means the client hears your approach and can raise concerns. Escalate a means decision to them only when it changes cost, timeline, or a risk they accepted. Everything internal to your plan stays yours.

Where does vendor selection sit — objective or means?

Usually means. The exception is when a specific vendor is itself a client constraint: an enterprise standard, an existing contract, a regulatory requirement. Then it's a constraint, and it goes in the constraints section, owned by whoever imposed it.

How do I handle a stakeholder who sets objectives I can't verify?

Ask what evidence would satisfy them before work starts. If nothing would, the objective isn't decidable — push for one that is. If something would, name it in the scope so you both know what you're delivering toward.

What's the fastest way to fix a scope that already mixes the two?

Read it once and highlight every sentence with a decision verb. If the sentence decides what the work is for, move it to objectives. If it decides how, move it to means. Then check every remaining line: whose decision, clearly marked. The exercise takes an hour and usually reveals two or three decisions sitting with the wrong party.

Sources