Protect a PM's attention with a 6-week plan
How PMs can treat focus, time and energy as constraints: map the drains, set guardrails, run short experiments and measure what changes.

This guide is for product managers who split their week between roadmap work, stakeholder requests and the heads-down thinking that makes both worth doing. By the end you will have a 6-week plan that turns your weekly goals into meeting budgets, two protected deep-work blocks, daily energy checkpoints and a simple three-metric dashboard.
- Your calendar, not your strategy, decides what you ship. Change the calendar on purpose.
- Treat your attention as a scarce resource with a capacity you can measure.
- Turn time and energy into commitments: slots, rhythms and rules you can test and change.
- Run each commitment as a short experiment, and judge it by outcomes, not by effort.

The problem: the calendar ships the product
Most PMs can name their top three priorities. Fewer can say where last Tuesday went. The gap between the two is the calendar. Whatever gets a slot gets done. Whatever does not get a slot waits for the gaps, and there are rarely any gaps.
This is a design problem, and you already know how to handle those. You have a scarce resource, several kinds of users with competing needs, and a system that behaves badly when nobody shapes it. Treat your attention the same way. Define what you need from it, look at how it is used now, set constraints, test them and keep what works.
There are five steps. Each one is small. The value comes from doing them in order and writing the answers down.
Clarify the outcomes you need
Before you protect any time, decide what the time is for. A PM's week usually has three kinds of outcome: decisions made, deep work finished, and stakeholders aligned. Write down what each looks like for the coming weeks.
Be concrete. Not 'work on strategy' but 'decide the scope of the next release'. Not 'keep sales informed' but 'agree one shared view of the top customer requests'. If an outcome cannot be checked at the end of the week, it is not yet an outcome.
Map the current calendar drains
Look back over a recent week or two and sort every block of time into a few groups: recurring meetings, one-off meetings, reactive pulls (a message, a quick call, a drive-by question) and real focus time. Then ask of each group whether it moved one of your outcomes.
Also note how you feel at the end of each day. Energy is part of capacity. Two hours of focus after a calm morning is not the same resource as two hours after back-to-back calls. This map is your baseline. Without it you cannot tell later whether anything improved.
Set guardrails
A guardrail is a commitment you can keep and check. Three kinds cover most cases:
Meeting budgets. A cap on the hours you spend in meetings each week. When the budget is full, a new meeting means swapping one out or saying not yet.
Focus blocks. Long, named slots in the calendar for heads-down work, treated like a meeting with yourself that others can see.
Energy-aware scheduling. Put demanding thinking where your energy is usually best, and put routine work, inbox and admin where it is usually lower.
Guardrails that touch other people need their agreement. Tell your team and key stakeholders what you are trying, why, and how to reach you when something is truly urgent. This is a social contract. Skip it and your rules will be broken within a week.

Run short experiments
Write each guardrail as a hypothesis: if I do this, I expect that, and I will see it in this measure. For example: if I hold two protected blocks each week, I expect to finish my deep work earlier, and I will see it in my uninterrupted hours.
Change one thing at a time, give it a fixed length, and set a review date before you start. A rule you cannot end is a habit you have stopped questioning. A rule with a review date is an experiment.
Measure the effect and adjust
Keep the measures few. Four are enough, and each is easy to collect.
| Measure | What it tells you | How to capture it |
|---|---|---|
| Decision lead time | How long a question waits before it is decided | Note the date a decision is raised and the date it is made |
| Heads-down hours | How much real focus time you had | Count blocks with no meeting and no reactive pull |
| Reactive interruptions | How often others set your agenda | Keep a simple tally through the day |
| Energy at day end | What the week costs you | Give a quick rating, for example one to five |
At each review, decide for every guardrail: keep it, change it or drop it. If the outcomes improved and nobody was harmed, keep it. If nothing moved, change one variable and run it again.
Worked example: a 6-week plan
Here is how the five steps fit into a 6-week Personal Development Plan. The plan turns weekly goals into meeting budgets, two protected deep-work blocks, daily energy checkpoints and a dashboard of three metrics. If you want a place to write it down, the Personal development plan tool on PikoPM is built for this kind of plan, though a notebook works too.
Each week starts with a short list of goals drawn from your three outcome types: the decisions to make, the deep work to finish and the alignment to reach. Each goal then becomes a commitment in the calendar.
The commitments
- A meeting budget. You choose the weekly cap in hours after seeing your baseline, and you spend it on the meetings that serve this week's goals.
- Two protected deep-work blocks. Two named slots each week, placed with energy in mind and shared with your team.
- Daily energy checkpoints. A quick note at set points in the day, ending with a rating at day end, so patterns show up in the data and not just in memory.
The three-metric dashboard
- Decisions made. How many decisions closed this week, and how long each waited.
- Uninterrupted hours. The real total of heads-down time, not the planned one.
- Inbox peaks. The times of day when messages and requests surge, so you can see when reactive work takes over.
Baseline and outcomes. Map the drains, write the weekly goals, start the energy checkpoints and fill in the dashboard without changing anything yet.
First guardrails. Set the meeting budget, place the two deep-work blocks, agree them with your team and compare the dashboard to your baseline.
Adjust and decide. Use the energy notes and inbox peaks to move blocks, tighten or loosen the budget, then keep, change or drop each rule.
At the end of week six, read the dashboard and your day-end energy notes together. You are looking for a simple story: did decisions close sooner, did uninterrupted hours rise, did inbox peaks matter less, and did you finish the days in better shape? That story tells you which rhythms to carry into the next plan.
Three mistakes to avoid
Writing a to-do list
A list of good intentions is not an experiment. Without a hypothesis, a measure and a review date, you cannot learn from it.
Hiding the permission problem
Blocks and budgets affect other people. Without a social contract with your team and stakeholders, your rules rely on willpower alone.
Rigid rules, no data
A rule that cannot bend will break on the first real emergency. Collect outcome data so you can adjust the rule with evidence.
Checklist for week one
- I have written down the decisions, deep work and alignment I need this period.
- I have mapped where last week went and noted my energy at day end.
- I have a baseline for all four measures.
- I have told my team and key stakeholders what I am testing and how to reach me when it is urgent.
- Each guardrail has a hypothesis and a review date.
Why this scales
A personal development plan frames your attention as product work. You define the users: your stakeholders and your future self, who inherits whatever your calendar produces today. You run experiments, read the results and iterate. The same loop works whether you manage one product or several, and it works again each time your role changes. The calendar stops being something that happens to you and becomes something you build.


