There are two types of people in every organisation. The ones who think. And the ones who report that they thought about thinking.
There are two fundamental types of employees in an organisation, and understanding which type dominates your team matters more than most management frameworks acknowledge. Now, I have observed a good many things in my time. I have seen honest men turned into nervous record-keepers by a single well-placed question from a corner office. I have watched talented human beings spend the finest hours of their professional lives constructing Excel sheets nobody reads, writing status updates nobody acts upon, and attending review meetings where the primary outcome is a date for the next review meeting.
And I have concluded, after much reflection, that the fault lies not entirely in the people. It lies in what their leaders have trained them to become. As someone I know calls them CPUs and Monitors.
The CPU and the Monitor: Two Types of Employees in Every Organisation
Inside every computer there is a CPU. The Central Processing Unit. A formidable thing. It receives inputs, wrestles with them, runs calculations, makes decisions, and produces outputs that actually change the state of the world, or at least the state of the document. The CPU does not merely observe the situation. It processes it. It transforms raw information into judgment, and judgment into action.
Then there is the monitor. A handsome device, no doubt. Sleek. Sometimes very large, which impresses visitors. But the monitor does only one thing: it displays what the CPU has already decided. It shows the numbers. It presents the picture. It reflects, faithfully and obediently, whatever is happening inside the machine. The monitor, for all its brightness, originates nothing. It generates nothing. It merely shows you what is already there.
Now here is the question that will make certain managers extremely uncomfortable: when your leader asks you for a report, what you tend to be? A CPU or a monitor?
How Leaders Accidentally Build an Organisation of Monitors
The first sixty seconds of a leader delegating work tells a lot about them.
Some managers lean back and say: “I trust your judgment. Do what you think is right.” Others lean forward and say: “Keep me in the loop. I will need regular updates.”
Both sentences take five seconds to deliver. The organisations they construct take five years to reveal themselves fully, and another decade to dismantle, if they are dismantled at all.
The first manager has activated what psychologists Richard Ryan and Edward Deci identified as the single most powerful driver of intrinsic motivation: autonomy. The employee receives the mandate and something shifts, not just motivationally but neurologically. Complex reasoning, initiative, and long-range judgment become available. A CPU has been switched on.
The second manager has transmitted an altogether different signal. And here is what makes it so insidious: the signal is not delivered in malice. It arrives wrapped in the perfectly reasonable language of accountability. Yet the employee decodes it with the unerring accuracy of someone whose career depends on reading such signals correctly. The thinking happens upstairs. Your job is to make it visible. A monitor has been commissioned.
Douglas McGregor, writing in The Human Side of Enterprise in 1960, called these two orientations Theory X and Theory Y. Theory X assumes people must be directed and controlled. Theory Y assumes people wish to contribute and will do so if trusted. What McGregor observed at the level of management philosophy, Yale neuroscientist Amy Arnsten has since confirmed at the level of biology. Her research demonstrates that environments of low autonomy and high surveillance trigger a cortisol-driven stress response that functionally impairs creativity, judgment, and problem-solving, the very capabilities that knowledge work demands.
In other words: when you ask for constant reports, you do not merely redirect your team’s attention. You reconfigure how they think. You are not managing a monitor culture. You are manufacturing one, one status update at a time.
It begins innocently enough. A leader, possessed of genuine curiosity or perhaps genuine anxiety, begins to ask for updates. Daily updates. Then hourly updates. Then updates on the updates. The team, being a sensible collection of human beings who would like to keep their jobs, responds accordingly. They begin to optimise not for outcomes but for reporting. They develop a preternatural gift for dashboard construction. They learn which numbers the boss likes to see trending upward, and they arrange, through perfectly legal means, to ensure those numbers do precisely that.
The team has now become a very expensive, very human monitoring system. It displays information. It does not process it. It shows the boss what is happening but exercises no particular judgment about what should happen next. The CPU function, the actual thinking function, has been quietly outsourced to the leader who keeps asking for the reports.
The irony, and it is a rich one, is that this leader is now receiving more information than any reasonable person can process, and processing none of it as well as the people closest to the problem could, if only they were permitted to try.
Henry Mintzberg, who has spent a career studying what managers actually do versus what they claim to do, noted that the monitor role in management involves scanning the environment and gathering information. That is a legitimate function. The trouble arises when the leader turns the entire team into monitors too, creating an organisation that is phenomenally good at gathering information and constitutionally incapable of acting on it.
The Real Cost, and It Is Not Small
Research highlighted by McKinsey found that organisations scoring high on what researchers called organisational health, essentially a measure of trust and empowerment, produced three times the total return to shareholders compared to those scoring low. Three times. That is not a rounding error. That is the difference between a functioning CPU and a very expensive monitor.
Neuroscience, that cheerful field that ruins so many management assumptions, offers further inconvenience. The human brain, when it senses that its autonomy is being constrained and its judgment is not trusted, shifts into what researchers describe as a short-term survival mode. The grasshopper brain, one expert called it. Jumping here and there, reacting, defending, reporting. Not the long-term processing brain that considers consequences, builds relationships, and solves complex problems. You cannot have an organisation of grasshopper brains and expect them to construct anything worth keeping.
And there is the talent drain to consider. Monitors, it turns out, are interchangeable. If all you ask of a person is that they display information, you will find that such people are not especially difficult to replace. More importantly, the people you most cannot afford to lose will figure this out before you do, and arrange their departure accordingly.
The Distinguished History of This Problem
This is not a new predicament. Mankind has been constructing elaborate reporting structures to avoid the discomfort of actually trusting people since at least the time of the Pharaohs, who had scribes count grain and report back rather than permitting the farmers any particular say in agricultural policy.
In more recent centuries, Frederick Winslow Taylor gave this tendency a scientific veneer and called it Scientific Management. Taylor believed, with the confidence of a man who had never been wrong in his own estimation, that workers should execute and managers should think. The workers most certainly were not expected to process anything of strategic importance. They were expected to perform precisely the operation they had been assigned and report any deviation upward through proper channels.
Taylor’s ideas built the twentieth-century factory. They also produced, as a side effect, generations of workers who were exquisitely trained to do exactly what they were told and absolutely nothing more. A monitor culture, implemented at industrial scale.
We have since invented knowledge work, which requires the opposite of everything Taylor prescribed. And yet the instinct to demand reports and thereby transform knowledge workers into reporting machines persists with remarkable tenacity.
What a CPU Culture Looks Like: The Two Types of Employees in an Organisation
A CPU culture is not anarchic. The CPU does not ignore inputs. It receives them carefully, processes them with rigour, and produces outputs that it is accountable for. The CPU is not free of oversight. It operates within a system. But the system trusts it to process, not merely to display.
In practical terms, a CPU culture is one where a team member does not merely present you with a problem and wait for your instructions. They present you with the problem, their analysis, two or three possible responses, their recommended response, and the reasons for it. They have processed. You review. You decide if you agree. You might send them back with a different parameter. But the thinking happened closest to where the information lives, which is where it should happen.
The leader in a CPU culture asks different questions. Not what happened, but what did you make of what happened. Not give me the numbers, but what do the numbers suggest we should do. Not how many tasks were completed, but which problems did you solve that I did not know needed solving.
The leader, in this arrangement, is not absolved of thinking. They are elevated to thinking about the things that only they can think about: strategy, culture, the external environment, decisions that genuinely require their authority. They have more processing capacity available because they have not consumed it all reading status reports.
A Modest Diagnostic, for the Courageous
If you suspect you may be operating a monitor culture without having intended to, I offer the following gentle examination.
Consider the last five interactions you had with your team. In how many did you ask for information? In how many did you ask for judgment? If the ratio favours information heavily, you are collecting display output. You are asking your people to be monitors.
Consider the last significant problem your organisation solved. Where did the solution originate? If the answer is consistently that it originated with you, or was only adopted once you had endorsed it, your team has learned that processing is not their function. They have learned to wait for the CPU to run.
Consider what happens when someone brings a recommendation rather than a report. Is it welcomed? Is it acted upon? Or does it quietly expire in a committee that meets to discuss whether the recommendation merits a further committee?
The answers will tell you a great deal about the machine you have built.
The Matter of Trust, Which Is Always the Matter
Under all of this lies a simpler question, one that leaders find uncomfortable because the honest answer is occasionally unflattering. Do you trust your people to process, or do you only trust yourself?
The demand for constant reporting is, at its root, a trust deficit wearing the costume of diligence. It presents itself as thorough management. It is, more often, the anxiety of a leader who is not confident that things will go well unless they are watching. And the watching, paradoxically, ensures that things go less well, because the people being watched stop thinking and start performing for the watcher.
Harvard Business School’s Tsedal Neeley put it plainly: you have to trust that people are intelligent enough and well-intentioned enough to get the work done. That trust is not naive. It is the precondition for having a team that processes rather than merely displays.
You hired these people because, one presumes, they were clever. Give them something to be clever about. Ask them not what happened, but what they think about what happened, and what they propose to do about it. Let them process. Review their outputs. Hold them to account for the quality of their thinking, not the frequency of their reports.
You might be surprised to discover how much processing capacity your organisation has been sitting on, waiting politely for permission to run.
About the Author
Ameya Agrawal is an IIM Kozhikode Gold Medalist and Executive Director at MIT World Peace University (MIT-WPU), Pune, leading the launch of WPU GŌA — India’s first transdisciplinary residential university campus. Previously CEO of Mahatma Gandhi Seva Sangh (MGSS), his disability rehabilitation work earned two Presidential National Awards from the Government of India, impacting over 100,000 lives across Maharashtra.
Author of the bestselling self-help book “A Leap Within” (published at age 21, earning him a National Record), Ameya has been published in Forbes, Business Standard, and The Print. He founded the SkillSlate Foundation, which trained 25,000+ individuals across 100+ organizations during the pandemic. Admitted to Harvard University in 2021, he chose to stay in India to continue his social impact work.
Projects on GitHub | Connect on LinkedIn | Follow on Twitter @ameyaagrawal | Read more at blog.ameya.page
Leave a Reply