The first step in controlling is to set a standard. Sounds simple. It isn't.
Most managers skip it. Plus, you're not controlling anything. But without a clear, agreed-upon standard, everything that follows is just noise. Even so, they jump straight to measuring, comparing, correcting — the "fun" parts where you get to fix things. You're just reacting.
What Is the Control Process
Control, in a management context, isn't about micromanaging or hovering. Four steps. It's a systematic process: set standards, measure performance, compare results against those standards, and take corrective action when needed. The first one does the heavy lifting Worth knowing..
The classic four-step loop
- Establish standards — define what "good" looks like
- Measure performance — collect actual data
- Compare — gap analysis between standard and reality
- Correct — fix the variance or adjust the standard
Textbooks present this as a neat cycle. Now, corrections create new problems. Which means in practice, it's messy. Standards drift. Because of that, measures lie. But the logic holds — and it all starts with step one Not complicated — just consistent..
Why "set standards" isn't "set goals"
Goals are aspirations. Now, standards are commitments. A goal says "we want to grow revenue 20%." A standard says "each sales rep will make 50 qualified calls per week, maintain a 30% close rate, and log every interaction in the CRM by Friday 5 PM." One inspires. The other enables control.
Why It Matters
Without standards, you have no basis for accountability. No way to say "this is off track" — because "on track" was never defined.
The vacuum gets filled anyway
When leadership doesn't set explicit standards, implicit ones emerge. Culture becomes the standard. Habit becomes the standard. So the loudest voice in the room becomes the standard. None of these are chosen. None are measurable. All are defensible — because nobody agreed to them in the first place Surprisingly effective..
This is where a lot of people lose the thread.
I've seen this play out in startups and Fortune 500s alike. Also, the manager asks "why? A team misses a deadline. And " Both are telling the truth. Even so, " The team says "we didn't know that was the priority. The standard didn't exist That alone is useful..
Standards create fairness
When standards are clear, documented, and shared, everyone plays by the same rules. The new hire knows what's expected. Consider this: the veteran can't coast on reputation. The manager can't move the goalposts mid-quarter without a conversation Easy to understand, harder to ignore..
Fairness isn't a feel-good bonus. In practice, people stop second-guessing. It's operational efficiency. They stop asking "is this good enough?" They know And it works..
How to Establish Standards That Actually Work
This is where most organizations fail. They set standards that are vague, unrealistic, disconnected from strategy, or all three.
Start with the outcome, not the activity
Bad standard: "Write 10 blog posts per month." Better standard: "Publish 10 SEO-optimized articles targeting keywords with combined monthly search volume >50K, each scoring 80+ on our content rubric."
The first measures activity. The second measures value. Activity standards encourage gaming — short posts, thin content, keyword stuffing. Outcome standards align with why the work exists.
Make them SMART — but don't stop there
Specific, Measurable, Achievable, Relevant, Time-bound. Good checklist. Incomplete Easy to understand, harder to ignore..
Add these:
- Observable — can two people independently verify if it's met? In practice, - Controllable — does the person own the levers to achieve it? - Cost-aware — does meeting this standard create waste elsewhere?
A standard that's measurable but destroys margin isn't a standard. It's a trap.
Involve the people who'll live by them
Top-down standards get compliance. Co-created standards get commitment.
Sit with the team. Show the business context. Ask: "What would a great month look like? Because of that, what's realistic? On the flip side, what gets in the way? " You'll get better numbers — and you'll surface constraints you didn't know existed.
Document, distribute, discuss
A standard in a PDF on a shared drive is a wish. A standard reviewed in onboarding, referenced in 1:1s, displayed on dashboards — that's a tool.
Review them quarterly. Products change. Even so, markets shift. And a standard set in January might be nonsense by June. Build the review into the calendar.
Common Mistakes
Confusing targets with standards
"Hit $1M ARR this quarter" is a target. "Maintain a 3:1 LTV:CAC ratio while growing ARR" is a standard. Also, targets are destinations. In real terms, standards are guardrails. You need both — but they're not interchangeable.
Setting standards nobody can measure
"Improve customer satisfaction.If you can't point to a dashboard and say "there it is," it's not a standard. Support ticket volume? So nPS? CSAT? " How? Churn rate? It's a slogan Easy to understand, harder to ignore..
The "perfect is the enemy of good" trap
Some teams spend months crafting the ideal standard. A decent standard today beats a perfect one next quarter. Practically speaking, ship it. Paralysis. Iterate.
Ignoring leading indicators
Lagging indicators (revenue, churn, defects) tell you what happened. Leading indicators (pipeline velocity, code review turnaround, first-response time) tell you what will happen. Standards on leading indicators give you time to course-correct But it adds up..
One standard for every role
Sales has quotas. Practically speaking, engineering has velocity. Support has SLA. But marketing has MQLs. Each function needs its own standards — but they must ladder up to the same business outcomes. Siloed standards create siloed behavior.
Practical Tips
Use a standard template
Every standard in your organization should answer:
- What is being measured? Now, - How is it calculated? - What's the target?
- What's the frequency?
- Who owns it?
- What triggers a review?
Consistency reduces cognitive load. People learn the format once, then focus on the content Worth knowing..
Pair every standard with a counter-metric
Standard: "Resolve 90% of tickets within 24 hours." Counter-metric: "Customer satisfaction score on resolved tickets."
Without the counter-metric, agents rush closures. Quality tanks. The standard is met — the outcome isn't.
Make standards visible in real time
Dashboards. Scorecards. Automated alerts. If someone has to ask "how am I doing?In real terms, ", the system failed. They should know before you do Surprisingly effective..
Celebrate standard-setting, not just standard-hitting
The team that proposes a better standard — tighter, clearer, more aligned — just saved the organization months of drift. Recognize that. It signals that standards are living tools, not bureaucratic chains It's one of those things that adds up..
Build in exception paths
Rigid standards break in edge cases. Day to day, define the escalation process upfront: "If X happens, escalate to Y within Z hours for a waiver or adjustment. " Exceptions shouldn't be ad-hoc. They should be governed Worth keeping that in mind..
FAQ
How many standards should a team have?
Five to seven core standards max. More than that and nobody remembers them. Prioritize ruthlessly. If everything is a standard, nothing is.
What if the standard turns out to be wrong?
Change it. Fast. Document why. Communicate the change. Standards are hypotheses — "we believe this metric at this level drives this outcome." When evidence contradicts, update the hypothesis It's one of those things that adds up..
Should standards be public across the organization?
Yes, with context. Transparency builds trust and enables cross-functional alignment. But don't weaponize them. "Marketing's MQL standard is lower than Sales expects" is a conversation starter, not a blame tool And that's really what it comes down to..
How do you handle standards for creative work?
Define the constraints, not the output. "Brand voice guidelines,
Define the constraints, not the output. But "Brand voice guidelines, accessibility requirements, legal review checkpoints" — these are standards. "Write a viral blog post" is a wish. Creativity thrives within guardrails; it suffocates under quotas.
How often should we review standards?
Quarterly for most. Monthly for fast-moving teams (growth, early-stage product). Annually for foundational infrastructure (security, compliance). Put the review cadence in the standard itself — meta-standards prevent meta-neglect.
What's the biggest mistake leaders make?
Setting standards they don't personally follow. If the CEO's inbox has 3,000 unread emails, "inbox zero" isn't a standard — it's theater. Model the behavior. Audit yourself first.
Conclusion
Standards are not about control. They're about clarity at scale And that's really what it comes down to..
In a five-person startup, you align over lunch. Plus, in a five-hundred-person company, you align over dashboards, definitions, and shared language. The standard is the lunch conversation — codified, accessible, and durable.
But a standard without trust is compliance theater. Even so, a standard without context is a weapon. A standard without an owner is a ghost.
The organizations that win don't have the most standards. Now, they have the right standards — few, sharp, owned, and alive. They treat standards as product: designed for users, iterated on feedback, retired when obsolete.
Start with one. Define it well. Which means make it visible. Review it honestly. Then build the next.
Because the alternative isn't freedom. The alternative is drift — slow, silent, and expensive Less friction, more output..
