Self-management

Self-management is the manager turning their judgment on themselves: how they spend their time, where their energy goes, which boundaries they hold, and how they keep thinking clearly under load. No v1.0 competency took the manager as its object, and the previous edition of this standard treated an overloaded manager as something for their own leader to notice. v3.0 makes it a competency because a manager who cannot manage their own time, energy and boundaries cannot keep up any of the other twenty-eight. One-on-ones are the first thing to be cancelled. The difficult conversation is put off because there is no energy for it. Decisions get made to end a meeting instead of to get the answer right. And the team reads the manager's state and copies it. It matters because the failure cannot be seen from inside. An exhausted manager does not feel their judgment slipping; they feel that their days are full. At scope, a leader's state also becomes the organisation's state. The examinations test it through the new manager working evenings to keep up with two jobs, the calendar full of meetings with no one-on-ones in it, the senior manager who realises they have snapped at two people who had done nothing to deserve it, and the executive who sees that the organisation has grown anxious and traces the anxiety back to themselves.

1. Your time is the team's scarcest resource, and the inbox does not get to allocate it. Each week the manager decides where the hours go, measured against what the team needs, instead of finding out on Friday where they went.
2. Leverage decides what you do yourself. An hour on something only you can do, such as the delegation brief, the hard conversation or the decision, is worth ten hours on things others could do. Left alone, a calendar fills up with the second kind.
3. Boundaries are a management practice, not a personal indulgence. The hours you keep, the recovery you take and the load you turn down are what keep your judgment usable. They also show the team what is permitted.
4. Your state is a signal the team reads. People copy anxiety, exhaustion and irritation before anyone notices them. A manager who snaps at two people who did nothing to deserve it has one problem, which is load, and it is a mistake to treat it as two problems with people.
5. Recognise your own overload early and ask for help before it reaches the team. A manager who soaks up everything until they break has handed the cost to the very people they meant to protect.
6. Separate your anxiety about a situation from the decision it needs. The urge to act, to answer or to make the discomfort stop tells you nothing about what the situation requires. The decision is made on the situation's terms.

The unit draws on research into work and recovery, on one body of findings that is honestly contested, and on practitioner writing about the manager's own effectiveness.

Managing your own time practice

Peter F. Drucker, The Effective Executive (1967) sets out the discipline. Find out where your time goes by recording it instead of guessing. Cut whatever does not need doing at all. Gather what remains into blocks long enough to use, and put first things first, which means deciding what not to do. Drucker wrote for executives, and the advice holds for any manager. His central finding is that people are reliably wrong about where their time goes until they measure it, and that is why the first practice in this unit is a time log.

Managerial leverage practice

This is Grove's framing, introduced in PL-1 Delegation, ownership, and decision rights. A manager's output is the output of their organisation, and some activities yield far more than others. In self-management it becomes the test for what the manager keeps doing. The high-yield activities, such as a clear delegation, a hard conversation or a decision only they can make, are protected. The low-yield activities that fill a calendar by default are delegated, declined or batched.

Burnout as a job condition research

The research summarised in Christina Maslach and Michael P. Leiter, Understanding the Burnout Experience: Recent Research and Its Implications for Psychiatry (2016) applies to managers too. Burnout shows as exhaustion, cynicism and reduced efficacy, and it is caused by the conditions of the job (workload, control, reward, fairness), not by a shortage of resilience. So a manager's own burnout is dealt with by changing their load and their control over it. A manager who treats their exhaustion as a character flaw to overcome has misread the research in the same way as an executive who offers wellness on top of an impossible plan.

Recovery and detachment research

Sabine Sonnentag and Charlotte Fritz, The Recovery Experience Questionnaire: Development and Validation of a Measure for Assessing Recuperation and Unwinding from Work (2007) distinguishes four experiences through which people recover from work: psychological detachment from work outside working time, relaxation, mastery experiences, and control over one's own time. Of the four, detachment showed the strongest relation with well-being. The study is cross-sectional, so it shows association rather than cause. For managers this means a boundary consists in detaching from work, and stopping work is not enough on its own. A manager who answers messages every evening has rested, perhaps, but has not recovered.

Ego depletion and decision fatigue contested

Roy F. Baumeister, Ellen Bratslavsky, Mark Muraven and Dianne M. Tice, Ego Depletion: Is the Active Self a Limited Resource? (1998) and the work that followed it claim that self-control and decision quality draw on a limited resource that runs down over the day, so later decisions are worse. The large multi-laboratory replication in Martin S. Hagger, Nikos L. D. Chatzisarantis and 47 co-authors, A Multilab Preregistered Replication of the Ego-Depletion Effect (2016) did not find the effect. The honest position is that the strong claim lacks support, and managers should not organise their lives around a resource that may not exist. The practical advice that survives (make important decisions when rested, and do not decide something just to end a discomfort) rests on the recovery research and on ordinary experience, and does not need depletion to be true.

The manager's own resilience practice

Lara Hogan, Resilient Management (2019) gives a practical treatment of the manager's own state as their team goes through change: noticing one's own reaction, building a support network made up of people other than one's reports, and asking for help. Here it supports the executive-scope practice of building the support that sustained judgment depends on. It is also a reminder that this support belongs with a leader's peers. The team is the wrong place for it.

The time log

For two weeks the manager records every hour as it is spent. They compare the log with what the team needs (one-on-ones, the hard conversations, the decisions only the manager can make), and the gap is the first thing to change. The log is repeated once a year, because calendars drift.

The leverage sort

Every recurring activity goes into one of three groups: only I can do this, someone else could do this, or this does not need doing. The first group is protected in the calendar, the second is delegated with a brief, and the third is stopped. When a manager's calendar is all meetings, they have usually skipped the sort.

The protected hours

One-on-ones, and time to prepare for hard conversations, are fixed in the calendar and are not moved for status. Two hours a week stay unscheduled for whatever will come up. The team can see the protection, and that is part of the point.

The boundary, kept and shown

The manager decides which hours they work and which they do not, sticks to them, and lets that be seen. Messages go out in the morning instead of at midnight, and holidays are taken without interruption. What the manager does is what the team learns is allowed.

The state check

Once a week the manager asks privately: have I been short with anyone who did not deserve it, have I decided anything just to end a discomfort, have I cancelled a one-on-one? A yes to any of these counts as a signal of overload and is acted on that same week, by delegating something, declining something or asking for help.

The support network

The manager builds relationships with peers, and with a mentor outside their reporting line, and uses them for the things that cannot go to the team or upward. At executive scope this has to be deliberate, because the executive's peers are the only people who can hear these things.

At team scope the object is the first-line manager's own time, energy and boundaries: the calendar, the evenings, and the one-on-ones that get cancelled first. The manager sets them on purpose and is seen to keep them. At organisational scope the object is the manager's effectiveness as the layer between teams and executives. The pull is to be in every room, load starts to degrade judgment about people, and short temper lands on managers who did nothing to earn it. The practice is to change the load before it changes the decisions. At executive scope the object is the leader's own resilience when consequence and visibility reach the whole organisation, along with the support that makes sustained judgment possible. The leader also has to recognise that their state becomes the organisation's. An anxious executive produces an anxious organisation, and the repair begins with the executive. The pattern is set out in How Judgment Scales; the team's pace, for which the manager's own pace sets the example, is covered in CC-4 Motivation, recognition, and sustainable pace.

• Manages their own time and calendar so that the hours go where the team needs them and the inbox does not decide. team
• Protects one-on-ones and preparation for hard conversations against status pressure. team
• Spots their own overload and burnout early, sets boundaries and asks for help before the team feels it. team
• Keeps working hours deliberately and visibly, so the team learns what is allowed. team
• Separates their own anxiety about a situation from the decision it needs.
• Failure mode: the new manager doing both jobs by working evenings, and visibly exhausted. team
• Failure mode: a calendar full of meetings with no one-on-ones in it. team
• Failure mode: treating exhaustion as a character flaw to overcome. team
• Failure mode: deciding in order to end the discomfort instead of to get it right.
• Manages their own effectiveness as the layer between teams and executives with deliberate care for time, attention and the temptation to be in every room. org
• Recognises when overload is degrading their judgment about people, and changes the load before it changes the decisions. org
• Notices that they have been short with managers who did not deserve it and reads that as a signal of overload, not as two problems with people. org
• Helps an overloaded manager who reports to them shed load before it breaks them, and does the same for themselves. org
• Failure mode: forty hours of meetings a week and no proper one-on-one with a manager in a month. org
• Failure mode: absorbing every escalation until the manager's job has quietly become theirs, and calling it support. org
• Failure mode: a support network made up of one's own reports. org
• Keeps their own judgment and resilience intact under consequence and visibility on an executive scale, and builds the support that makes this possible. exec
• Recognises when their own state is shaping the organisation's, and acts on themselves first. exec
• Takes proper recovery, a break without interruptions, and is seen to take it, because the organisation copies the top. exec
• Failure mode: going two years without a proper break and making decisions to end conversations. exec
• Failure mode: an anxious organisation whose anxiety began at the top, treated as everyone else's problem. exec
• Failure mode: a leader with nobody to tell. exec

Availability versus judgment. The manager who is always available is valued, and makes worse decisions than the one who is not. Protected time and a visible boundary resolve it, and the discipline lies in holding to them when the urge to help pulls the other way.

Absorbing versus passing on. A good manager shields the team by taking load on themselves, until they break and the team gets all of it at once. The judgment lies in when to ask for help, which is before the state check comes back yes.

Boundaries versus the moment. Some weeks need the evenings and some crises need the weekend. The tension is between a time-boxed exception that ends when the time is up and a boundary that has quietly turned into a suggestion.

Self-care versus self-indulgence. A manager can read the recovery research as permission to do less, and a manager's load is real. The test is managerial leverage. A boundary that protects the manager's judgment on the things only they can do is a management practice. A boundary that protects them from the hard conversation is avoidance.

Honesty about state versus authority. Saying "I am overloaded and need help" can feel like an admission that will cost standing. The alternative costs more: snapping at people, cancelling one-on-ones and deciding badly, all of which people notice anyway.

A manager promoted from within the team four months ago is still taking the two hardest technical tickets each sprint, because nobody else on the team has the context. They also attend the eight cross-team meetings their predecessor attended, and they do the management work (one-on-ones, planning, two hiring loops) in the evenings. They are visibly exhausted. They have cancelled one-on-ones twice in the past month, and this week they snapped at an engineer who asked a reasonable question. They have told nobody, because the team is delivering and asking for help feels like admitting they cannot do the job.

The temptation is to keep going. The team is delivering, the promotion is recent, and the evenings feel like the price of the transition. This is the failure the unit describes, and from inside it cannot be seen. The manager experiences full days and has no sense that their judgment has slipped. The cancelled one-on-ones and the sharp reply are the first evidence that it already has.

At a colleague's suggestion the manager keeps a time log. It shows what they half knew and had not looked at: twenty-two hours a week in meetings, most of which the predecessor attended out of habit, twelve hours of individual technical work, and the management done at night. Next comes the sort of recurring activities. The two hardest tickets are the most valuable thing to delegate, because the context only the manager holds is precisely what the team most needs to gain. The manager hands them to the two most senior engineers, with a brief and a pairing session each, and accepts that the tickets will take longer this sprint. Five of the eight meetings go. The manager declines three with a note and delegates two to an engineer who is closer to the subject. One-on-ones and hiring move into the working day, into the hours the meetings freed, and are fixed in the calendar.

Then the harder part. The manager tells their own manager what the past four months have been like, that they have been doing both jobs in the evenings, and that they are changing it. They ask for one thing: cover in the two cross-team meetings that do need a manager present, until the engineer taking them over is up to speed. They apologise to the engineer they snapped at and briefly explain why it happened. And they keep the boundary they have set, sending messages in the morning and not at midnight, where the team can see it.

The team notices the change before the manager does. The manager does not accept exhaustion as the price of the job. Had they done so, the team would have lost its manager and the manager would have lost the job.

• CC-4 Motivation, recognition, and sustainable pace: the team's pace and energy, for which the manager's own sets the example.
• PL-1 Delegation, ownership, and decision rights: delegation as the way a manager's time is freed, and Grove's point that a manager's output is the output of their organisation.
• PL-6 Leading through leaders: the leader of managers who notices an overloaded manager, and the manager who tells them.
• CC-1 Psychological safety and productive conflict: the safety that makes "I need help" possible to say, in both directions.
• PL-2 Feedback and difficult conversations: the apology for the short reply, as feedback owed to oneself as well as to the other person.

1. Why is self-management a competency rather than a personal matter?
   Answer

   A manager who cannot manage their own time, energy and boundaries cannot keep up any of the other competencies. One-on-ones are cancelled, the hard conversation is put off and decisions are made to end the meeting. The team also reads the manager's state and copies it.
2. What is the first practice, and why does the research say to do it?
   Answer

   The time log, a two-week record of where the hours go. People are reliably wrong about where their time goes until they measure it, and the gap between the log and what the team needs is the first thing to change.
3. What decides what a manager keeps doing themselves?
   Answer

   How much each activity yields, which turns on whether only they can do it. The things only they can do (a clear delegation, a hard conversation, a decision) are protected. Those others could do are delegated with a brief, declined or batched. Those that do not need doing are stopped.
4. What does the recovery research say a boundary is?
   Answer

   Detachment, meaning psychological distance from work outside working time, which is the experience most strongly related to well-being. Stopping work is not enough on its own. A manager who answers messages every evening has not recovered, even if they have rested.
5. What is the honest position on decision fatigue?
   Answer

   It is contested. The strong claim that self-control and decision quality run down over the day did not survive a large multi-laboratory replication. The advice that survives (make important decisions when rested, and do not decide something just to end a discomfort) rests on the recovery research and on experience, and does not depend on depletion.
6. You realise you have been short with two managers this week and neither deserved it. What is it a signal of, and what do you do? org
   Answer

   Of overload, and not of two problems with people. Treat it as the state check coming back yes: change the load that week by delegating something, declining something or asking for help, and apologise briefly to both, explaining why.
7. The organisation has become anxious and you notice it started with you. What is the repair? exec
   Answer

   Act on yourself first. Take proper recovery and be seen to take it, lean on peers who can hear it, and show a visible change in your own state before sending any message to the organisation about theirs. The organisation copies the top.

• Peter F. Drucker, The Effective Executive (1967): know where your time goes; put first things first.
• Christina Maslach and Michael P. Leiter, Understanding the Burnout Experience: Recent Research and Its Implications for Psychiatry (2016): burnout as a condition of the job, applied to the manager.
• Sabine Sonnentag and Charlotte Fritz, The Recovery Experience Questionnaire: Development and Validation of a Measure for Assessing Recuperation and Unwinding from Work (2007): the four recovery experiences; detachment and well-being.
• Roy F. Baumeister, Ellen Bratslavsky, Mark Muraven and Dianne M. Tice, Ego Depletion: Is the Active Self a Limited Resource? (1998): the original ego-depletion claim.
• Martin S. Hagger, Nikos L. D. Chatzisarantis and 47 co-authors, A Multilab Preregistered Replication of the Ego-Depletion Effect (2016): the multi-laboratory replication that did not find it.
• Lara Hogan, Resilient Management (2019): the manager's own resilience and support.