In this article
Begin by choosing the leadership work you want to make space for. Examples include reviewing a difficult trade-off, understanding a recurring team problem or preparing a thoughtful conversation.
Give AI leadership a thinking objective
Define the judgement that deserves your attention before automating surrounding work. Otherwise efficiency becomes an open invitation for more low-value activity.
A Microsoft WorkLab conversation with Michael Platt discusses AI, decision-making and leadership. It is an expert perspective, not evidence that a particular scheduling routine will improve your brain or guarantee better leadership.
The practical approach here is simpler: create room for a specific question and protect that room long enough to consider it properly.
In a hypothetical regional team, the question could be why operational issues repeatedly reach the manager late. A cleared inbox does not answer it. The manager needs time to examine the process and listen to colleagues.
Separate preparation from judgement
Identify work that organises information and work that requires your interpretation. AI may support the first, but the second still needs context, accountability and often direct conversation.
For the hypothetical issue, approved notes could be organised into recurring themes for review. The manager must then check the themes, understand missing perspectives and decide which questions to take to the team.
Do not ask the tool to infer motives from messages. “The escalation arrived late” is an observation; “the supervisor did not care” is an unsupported explanation with consequences for a person.
Keep those categories separate in any preparation brief.
Reserve a defined block for the real question
Choose a realistic period and one written question. Remove routine notifications where your role permits, while preserving an appropriate route for urgent issues.
Prepare a small thinking page:
- The decision or problem.
- What is confirmed.
- What you currently assume.
- Who has information you lack.
- The next question or conversation needed.
This page is more useful than an unrestricted request for strategic advice. It connects reflection to a decision and makes missing information visible.
If your role requires continuous availability, use shorter protected intervals or arrange cover. Do not copy a routine that conflicts with operational responsibilities.
Use AI to challenge the preparation
Ask for gaps or alternative explanations using approved or fictional information. Keep the final interpretation with the people who understand the situation.
A useful prompt is:
Review this fictional problem brief. Identify assumptions, missing perspectives and questions that would distinguish alternative explanations. Do not diagnose individuals or recommend disciplinary action.
Read the response as a list of possibilities. Confirm relevant observations through real sources and conversations before acting.
NIST's AI Risk Management Framework offers risk-management context. For leaders, the immediate responsibility is to prevent convenient preparation from becoming unsupported judgement.
Convert reflection into a proportionate next action
End the thinking block with something specific: obtain a missing record, speak with a colleague, test a process change or defer a decision until evidence is available.
In the hypothetical escalation problem, the manager might ask two supervisors to explain the actual handoff path. That is more useful than announcing a new reporting tool before understanding the obstacle.
Record what would change your current view. This makes the next conversation an investigation rather than a search for agreement.
Use a decision note to prevent circular thinking
Write a brief note at the end of the protected block: the question considered, evidence examined, assumption challenged and next action. If no decision is ready, state exactly what is missing.
In the hypothetical escalation problem, the note might say that the available records show late reporting but do not establish the cause. The next step is to understand the handoff with the people doing it, rather than instructing the team to communicate better.
Bring the note to the relevant conversation and invite correction. A protected thinking block should prepare you to listen more intelligently, not produce a theory you defend against local knowledge.
Review the note after obtaining new information. What changed? Was the original question useful? Did you confuse the most visible symptom with the problem that needed attention?
This creates a connection between reflection and action. Without that connection, a thinking block can become another private activity with no effect on the work. The objective is not to spend more time appearing strategic; it is to make a better-supported next move and explain the reasoning to the people involved.
Protect the purpose of any time saved
When a workflow becomes easier, decide what the recovered capacity is for. The answer may be better review, coaching, reflection or simply a sustainable workload.
Do not claim time savings without observing the full task. Preparation, checking and correction can absorb the apparent gain.
Choose one leadership question for the coming week and reserve a realistic block to work on it. Use AI only for a narrow supporting task that you can inspect.
Explore PiOfAI, staying calm while leading under pressure and clear manager communication to connect better preparation with thoughtful leadership.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.