What Is Micromanagement? When to Get Into the Detail and When to Let Go
In Staffordshire Pottery and its History, published in 1913, Josiah Clement Wedgwood, a descendant of Josiah Wedgwood, recounts a scene involving his famous ancestor. Whenever the potter spotted a flawed vase in the workshop, he would smash it with his walking stick and say: "That won't do for Josiah Wedgwood."
The book's reading of the scene is more interesting than the scene itself. Wedgwood didn't break the vase because it offended his taste; he broke it because it would damage his name and his sales. He wanted perfection, but so that it would sell.
On 28 May 1768 the same man had his leg amputated because of an old knee complaint. A year later, in June 1769, he opened his Etruria works beside the canal. Historians describe Etruria as built on the division of labour. One man's walking stick could not reach every vase in an entire factory.
This tension between the stick and the system is the oldest question in management: when should you get into the detail, and when should you let go?
Is micromanagement always bad?
"Don't micromanage" has been repeated so often that many managers have swung to the other extreme: not managing at all. An article published by First Round Review in June 2025 starts from exactly this point. Its advice is not to run from detail but to change altitude deliberately: get down on the ground on some issues, and on others build a system that lets your team do excellent work without you.
Set the standard by showing it yourself
According to Lattice co-founder Jack Altman in the article, micromanagement is a tool to be used sparingly. If the person you are hovering over can't handle the job, it's a crutch, and perhaps a sign that the team needs to change. But writing a blog post yourself or fixing a mistake yourself shows everyone where the bar is. Wedgwood's stick was a statement of standards too.
Look at the ground, not the dashboard
Matt MacInnis, chief operating officer at Rippling, says one of the company's principles is "go and see". When what people tell you contradicts the numbers on the dashboard, the manager goes down to the ground truth personally. In MacInnis's example, listening to a recorded sales call revealed that the sales team couldn't explain the feature that set the product apart from its competitors. After that, the work was handed to the relevant department heads as a hypothesis. Once the metrics moved, he stepped back. He describes himself not as a micromanager but as "micro-curious".
According to the same article, Rippling's CEO Parker Conrad still personally approves any expense over 5 dollars and runs payroll himself. The aim is not control but to keep seeing the product through the customer's eyes.
Scale the process, not the taste
Krithika Shankarraman, Stripe's first marketing hire, explains that the company scaled not "taste" but the process that protects it. Every piece of copy going out to more than a hundred users was read by someone whose title really was "red pen owner", reading it as a user who knew nothing about the subject. Checks happened at the 20 per cent and 80 per cent marks: the first to see the direction, the second to see the craftsmanship. Both while there was still time to change course.
Swim like a porpoise
Mike Brown, one of Uber's early employees, calls this balance "porpoising": staying at the surface like a porpoise to watch everything, then diving deep on a few issues. He says that at Uber, every quarter or six months, he went deep on one project in each of four areas: people, growth, cost and customer experience. When there is an existential threat, you don't wait for the calendar: when the service was suspended for a month in the Philippines, he flew to Manila and worked alongside the local team.
When trust is slipping, say so openly
Jay Desai, former CEO of PatientPing, sees micromanagement as a symptom of lost trust. With someone new, he works closely at first, then steps back once trust has formed. If he notices himself diving back into the detail, he tells the other person plainly: my trust is slipping, let's work out why together. It is a far more honest route than silently looking over someone's shoulder.
Give a box of ideas, not a list
Michael Lopp, an engineering director at Apple, says that instead of a to-do list, he offers his team a box full of ideas. Even when asked for step-by-step instructions, he often doesn't give them. Everyone has to season the soup to their own taste.
Holding by hand, sending an envoy
According to the etymology given by Wiktionary, the English word "manage" comes from the Italian verb "maneggiare": to handle, to control. Its Old French counterpart "manege" meant the training of horses and horsemanship. At the root lies the Latin "manus", the hand. In its first sense, to manage is to hold a horse's reins in your hand. Micromanagement is like going back to that original meaning: never letting go of the reins.
"Delegate", meanwhile, comes from the Latin verb "delegare": to send, to appoint. "Legate", meaning envoy, belongs to the same family. To delegate is to make someone your envoy. They represent you, but they speak in their own voice. If you make your envoy memorise every sentence, you haven't sent an envoy; you've sent a letter.
A good manager lives between these two roots. Some days they keep a tight grip on the reins; most days they trust their envoy.
When the people say "we did it ourselves"
Chapter 17 of the Tao Te Ching, attributed to Laozi, ranks rulers on four levels. In Wang Bi's text the chapter begins and ends like this:
"太上，下知有之；其次，親而譽之；其次，畏之；其次，侮之。... 功成事遂，百姓皆謂：我自然。"
Of the best, people know only that they exist. The next they love and praise. The next they fear, and the worst they despise. When the work is done and complete, the people say: "We did it ourselves."
Wedgwood's stick showed where the bar was; Etruria held that bar without the stick. Which vase should your stick break today, and which should you now leave to your team?
If you're wondering what to say when you do get into the detail, take a look at How to Give Feedback to Your Team.
