Your Team's Time Does Not Belong to You
Hayagreeva Rao, professor of organizational behavior at Stanford Graduate School of Business, recently offered a definition of leadership that holds up better than most books on the subject: "Great leaders are people who think of themselves as stewards of other people's time."
There are no war metaphors. No references to transformational vision or charisma as a managerial asset. There is an operational premise that, if taken seriously, compels a fundamental rethinking of almost everything an organization does with its teams' time.
Context matters. Rao formulated this idea on Stanford GSB's If/Then podcast, in an episode dedicated to distinguishing between harmful friction and useful friction within organizations. Harmful friction is the kind that consumes time without adding anything: the meeting that could have been a message, the approval process that nobody can explain with any precision, the form that exists because it always has. Useful friction, on the other hand, is the kind that deliberately slows things down to protect quality, ethics, or coherence. Rao was not offering a definition of leadership as a rhetorical exercise. He was deriving it from a more technical observation: that organizations accumulate harmful friction because their leaders do not feel the weight of other people's time as something they are responsible for stewarding.
Bill Murphy Jr., contributing editor at Inc. and founder of Understandably, picked up this phrase and wrote that, having read many books on leadership, he cannot recall ever seeing it expressed with such clarity. That is not empty praise. Rao's conciseness points to something that conventional definitions tend to sidestep: leadership is not only a relationship with the future, with vision, or with results. It is a daily relationship with the attention and time of the people who depend on your decisions.
When Scarce Time Is Managed as Though It Were Abundant
The organizations I know that struggle most to retain high-performing talent share a pattern: they do not have problems with salaries or benefits. They have a problem of systematic waste of their best people's time. Meetings are called out of inertia. Approval processes multiply as political defense mechanisms. Weekly reports are prepared for audiences that never read them. All of this happens while the managers responsible for those decisions speak fluently about organizational purpose and a culture of excellence.
Murphy puts it precisely in his piece: high-performing employees have options. If the market pays the same elsewhere, what retains them is not the salary. What retains them is the perception that their time is being used well, that the demands placed on them make sense, that what they are being asked to do contributes to something worthwhile. When that perception disappears, the salary is no longer enough.
This transforms the management of the team's time into a strategic problem with direct financial consequences. The cost of replacing a qualified professional in knowledge roles ranges, according to widely documented estimates in human resources literature, between 50% and 200% of their annual salary, depending on the complexity of the role. Those numbers accumulate quietly in organizations where teams' time is spent with no one keeping track.
Rao's definition is not just an elegant way of talking about meetings. It is an audit of who assumes responsibility for time as a scarce resource. In most organizations, that responsibility is not assigned to anyone. It is implicitly delegated to shared calendars that nobody governs, to reporting traditions that nobody questions, to approval structures that grew because someone had a bad experience five years ago.
The Stewardship of Time as Decision Architecture
Accepting that you are a steward of your team's time implies something more uncomfortable than cutting meetings: it implies that every demand you introduce into another person's agenda requires justification. Not rhetorical justification, but operational justification. Why this meeting and not a written document. Why this three-signature process and not a one-signature process. Why this weekly report and not a real-time indicator.
This is precisely the distinction Rao draws between harmful friction and useful friction. Useful friction has a reason for existing that survives scrutiny: an additional approval that prevents high-cost errors, a review process that protects the quality of a critical product, a meeting that enables alignment on decisions where mistakes are irreversible. Harmful friction, on the other hand, exists because eliminating it requires someone to actively decide to do so, and nobody in the organization has felt responsible for making that decision.
Leadership as stewardship of time transforms that problem of organizational inertia into a problem of deliberate design. A leader who internalizes this responsibility does not only manage their own agenda: they actively design the mechanisms that determine how time flows within their organization. They evaluate which processes add measurable value and which add only bureaucratic comfort for whoever imposed them. They question recurring meetings with the same discipline they would apply to questioning a line item in the budget. They accept that protecting their team's time sometimes means absorbing the friction themselves rather than distributing it downward.
This stance has political consequences within organizations. Deciding that a meeting is unnecessary sometimes means telling someone with authority that their convening of it does not justify the time it consumes. Deciding that an approval process is excessive sometimes means dismantling a structure that someone built in order to feel relevant. The stewardship of time is not an attitude that can be managed from a position of comfort: it requires the leader to bear the political cost of defending their team's time against institutional pressures that push in exactly the opposite direction.
What Organizations That Ignore This Principle Reveal About Themselves
There is a category of organizations particularly prone to violating this logic in a systematic way: those that confuse activity with progress. These are organizations where a packed calendar functions as a signal of commitment, where large meetings convey the illusion of alignment, where complex processes project institutional seriousness. In these organizations, harmful friction is not a failure of the system: it is the system.
What Rao's definition places on the table is that this pattern is not neutral. It carries an opportunity cost that accumulates invisibly. Every hour that a high-performing professional spends in a purposeless meeting is an hour that was not used to produce the work for which that person was hired. Multiplied by the size of the team and the frequency of unjustified demands, the result is an organization that devotes a fraction of its installed capacity to the work that truly matters.
The contrast with organizations that manage their teams' time with greater discipline is notable in their productivity per hour worked, in their ability to attract and retain talent without paying extraordinary premiums, and in the speed with which they convert decisions into actions. They do not arrive at that outcome because they solved complex strategic problems. They arrive at it because someone, at some point, decided that the teams' time was a resource that deserved active stewardship.
The distinction Rao introduces between harmful friction and useful friction also demands an additional clarification: eliminating all friction is not the answer. Organizations that eliminate quality controls, review processes, or deliberation instances in the name of superficial efficiency end up paying the price in the form of costly errors or rushed decisions. The stewardship of time is not synonymous with maximum speed. It is synonymous with discrimination: knowing which friction serves a purpose and which friction drains one.
The Stewardship of Time Is a Strategic Position, Not a Managerial Virtue
What makes Rao's definition analytically sound, beyond its elegance, is that it repositions leadership within the economy of scarce resources. Time cannot be recovered. Unlike capital, you cannot obtain more of it by doing things right. Unlike reputation, it is not restored by the next good decision. Every hour of a team's time spent on a valueless task is a permanent loss.
This transforms the stewardship of time into a responsibility with long-term strategic consequences. Organizations whose leaders do not assume this responsibility accumulate friction until the talent they most want to retain finds somewhere else where their time is managed with greater rigor. They do not leave for money. They leave because someone else demonstrated that their time was worth looking after.
Murphy summarizes it in terms that any executive should be able to translate operationally: it is not enough for the mission to be valuable. Every demand you introduce into someone's life — every meeting, every process, every form — must justify its existence. Leaders who understand this do not treat it as a service-oriented attitude. They treat it for what it is: a design responsibility with a direct impact on the organization's capacity to do its work.
Rao's definition is not an aspiration. It is an evaluation criterion. A leader who cannot demonstrate that they manage their team's time with rigor is not exercising stewardship: they are exercising power over a resource that does not belong to them.
