Standards You Can Require
A standard stated as a property of the output is a commercial requirement; taught and corrected it is a method, and most businesses reach for the latter.
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. Training is the instrument most often used without anybody noticing what it moves.
A standard stated as a property of the output is an ordinary commercial requirement. The same standard taught, supervised and corrected afterwards is a method, and almost every business reaches for the second because it is the one they know how to operate.
The management distinction in “Standards You Can Require” matters when software turns a brief into a continuous stream of instructions. Teams considering open the corresponding solution overview for limbic resonance in relationships should define the outcome being measured, limit access and preserve the contractor’s ability to organise the method where the agreement requires it.
The distinction is not a trick of wording. It changes who holds the judgement and what happens when the work falls short.
Teams documenting “Standards You Can Require” can also review Notion work and knowledge articles. Record which ideas fit the engagement and which still need confirmation from the contract owner or local adviser.
The standard as a property of the thing
Written into the brief, before anybody starts, in terms somebody could check: it has to meet the accessibility level we publish, it has to pass the test suite, it has to be in the house voice as set out in the guide, it has to survive the review our client runs.
Each of those says what the output must be. None says how to get there, and all of them give you a clean basis for rejecting work.
The standard as something you instil
The same requirement delivered as induction, a training session, a review cycle and corrections over several months.
That is how an employer raises the standard of a team, and it works. It also makes the person's method yours, which is the factor that weighs most heavily nearly everywhere, and it does so slowly enough that nobody notices.
What you can hand over without moving anything
Quite a lot, as long as it describes the result rather than the route:
- A style guide, a brand book, a specification the output must meet.
- Examples of previous work that was accepted, and of work that was not, with the reasons.
- The standard your own client imposes on you, passed through.
- The acceptance criteria you will judge against.
Giving somebody the target and letting them find their own way to it is both the commercially correct position and, in practice, how you get better work.
Published, not taught
A useful test for anything you are about to tell a supplier: could this be published as a document that any supplier would receive?
If yes, it is a standard. If it only makes sense as something said to this person about their work, it is feedback on their performance, and performance feedback is an employer's instrument.
The standards that are genuinely yours to impose
Some are not negotiable and should not be: safety rules on your site, data handling where the law or a client requires it, regulatory requirements that attach to the work being done at all.
Those go in the engagement as conditions, stated up front, and a supplier who will not meet them is not the right supplier. Nobody should soften a safety requirement out of anxiety about a factor.
Where the standard did not exist until they failed it
The most common failure in this article. Work comes back wrong, and the business discovers it has a standard it has never written down.
At that point the honest move is to write it, agree it as a change, and judge the next piece against it. The tempting move is to explain it verbally and expect it to be absorbed, which is training, and which leaves you with nothing to point at next time.
Reviews, and what they are for
A review that checks the output against stated criteria is acceptance. A review that discusses how somebody works, what they should do differently and how they are progressing is appraisal.
Both happen in meetings of the same length with the same people. The difference shows up in what is written down afterwards and in whether the conversation would make sense about a firm rather than a person.
Raising a standard mid-engagement
Legitimate and common, and it is a change like any other. New requirement, agreed, priced if it costs anything, recorded.
Raising it without agreement — simply expecting better and being dissatisfied until it arrives — is the version that produces both a resentful supplier and an arrangement that has moved.
What good looks like after a year
The supplier knows what they will be judged against because it is written down. You can reject work without it being a conversation about them. Nobody has been trained and nobody has been appraised.
That is a thinner relationship than a business has with its staff, and it is the one you bought. The quality comes from choosing well and specifying clearly rather than from improving somebody, which is the instrument you do not have.
The thing that is easy to forget
A standard you never enforce is not a standard. Businesses that write careful acceptance criteria and then accept everything have the paperwork of one arrangement and the practice of another, and the practice is what anybody will look at.