Can You Say How the Work Is Done?
You can say what the finished thing must be and by when; the moment you specify the method you hand over the factor nearly every test weighs most heavily.
Reads as a businessReads as employmentCuts both waysDepends where you are
Four factors, and no total. Every bar is the same length: the side is the claim, the size is not. The heaviest factor in most tests, and the easiest one to give away by accident.
What a single instruction moved, in one engagement
Who chooses the method
The brief was reissued naming the software and the order of the stages
Who chooses the working hours
Added in the same message, because a client call needed covering
Who supplies the equipment
Unchanged: their own machine, their own licences
Right to send somebody else
Unchanged, and still never used by either side
Who carries the overrun
Unchanged: rework unpaid, but a day rate that does not move
Reads as a businessReads as employmentCuts both waysDepends where you are
Five factors, and no total.
One message, two factors moved, and nobody in the business recorded that anything had changed. The instruction was reasonable and the work needed doing. One company's own arrangement, reconstructed for itself; which factors matter, and how much, differ by jurisdiction.
You can say what the finished thing must be, when it is needed and what it has to satisfy. The moment you specify the method — these hours, this software, that sequence — you have handed over the factor that nearly every test weighs most heavily.
The practical issue in “Can You Say How the Work Is Done?” becomes clearer when expectations and evidence are visible to both sides. Used for does microsoft teams track your activity, does microsoft teams track your activity for contractor workflows can add time and project context, provided the purpose is disclosed, access is limited and every consequential interpretation receives human review.
That is not a reason never to do it. It is a reason to know you are doing it, because almost nobody does.
The workflow in “Can You Say How the Work Is Done?” can be cross-checked against MeisterTask workflow articles. A useful review should end with named owners and written decisions instead of a copied checklist.
The line, as far as there is one
The usable distinction is between the what and the how. What the output must be, by when, to what standard, working with what: all of that is ordinary specification and nobody raises an eyebrow at it.
How the person gets there — which tools, in what order, during which hours, at what desk — is the territory an employer occupies. There is no sharp boundary and the weight given to any of it differs by jurisdiction, but this is the axis everything moves along.
Why control of method weighs so heavily everywhere
Because it is the thing that most reliably separates buying a result from directing a person. Most other factors can be arranged on paper. Control of method shows up in the ordinary traffic of a week and cannot be dressed up afterwards.
It is also the factor a buyer gives away most easily, because giving it away usually solves a real problem in front of them.
The reasonable instruction that moves something
Almost every instruction that causes trouble was sensible at the time:
Use the staging server, not your own. Start on the data import rather than the interface. Do the regional pages before the national one. Be on the eleven o'clock call. Use our template, not yours.
Each of those has a real reason behind it. Several of them are genuinely about interoperating with your business rather than about method. The difficulty is that from outside they look identical.
Interoperation and instruction
There is a defensible middle. Requiring that work be delivered in a format your systems can accept, on infrastructure you control for security reasons, or to a standard your own client imposes on you, is about the result and its context.
The way to keep it there is to put it in the specification as a constraint on the output, agreed at the start, rather than issuing it as a direction in week three. Same requirement, different instrument, and a later reader can tell the two apart.
What to do when you genuinely need to direct
Sometimes you do. The work is going wrong, the client is on the telephone, and the correct answer is to tell somebody to do it differently right now.
Do it, and then do two things: record it as a change to what was agreed, and ask afterwards whether this is going to keep happening. If it is, the honest response is to change the arrangement rather than to keep reaching across it.
The manager who has only ever employed people
This is the commonest source of the problem and it is not anybody's fault. A manager who has run teams for fifteen years directs by reflex, because that is what good management looked like in every previous job they have had.
They need to be told, once, that the instrument they are used to is not available here and what to use instead. Businesses almost never tell them, and then are surprised at the result.
What happens to the work when you stop directing
Usually it gets better, which surprises people. Somebody who does this for several clients has seen more variations of the problem than your team has, and their method is often better than the one you would have imposed.
Where it does not get better, you have learned something about the supplier that no amount of instruction was going to fix.
What you are left holding
The specification, the date, the standard, the right to reject, and the right to stop buying. That is a thinner set of tools than a manager is used to and it is enough for most work, provided the first item exists.
Where it is not enough — where the work genuinely requires somebody who can be redirected hour to hour — the arrangement itself is the wrong one, and no amount of careful wording changes that.
What this costs in practice
Time, mostly. A specification takes an afternoon that an instruction takes a minute. A rejection takes two days that a correction takes ten minutes.
That is the price of the arrangement. A business that will not pay it is not running the arrangement it says it is, and the drift it is about to experience will not feel like a decision at any point along the way.