Month by Month Goals

Client has a pattern of postponing goals until a vague future state — after the busy period ends, when the team is more stable, once the project closes. The goals are genuine but treated as contingent on circumstances the client does not control. Placing a goal in a specific month converts it from a conditional intention to a scheduled one, which is a different category of commitment.

Frame this as a scheduling conversation, not a goal-refinement conversation. 'You have the goals. What we're going to do today is decide when each one gets attention. Not if — when. Putting a goal in March or June is a different kind of statement than saying you'll get to it when things calm down.' The resistance pattern is clients who argue that they cannot schedule because the future is too uncertain. Name it: 'The schedule isn't a contract — it's a decision. You can move a goal from April to June. What you can't do is leave it in an indefinite future and expect it to happen.'

Watch the distribution of goals across months. Clients who cluster everything in the second half of the year are deferring in calendar form. Clients who spread goals evenly across twelve months without regard for seasonal patterns, workload cycles, or life events are not planning realistically. The most useful discussion is about the months that are conspicuously empty or conspicuously overloaded.

After the grid is filled, step back and look at it as a whole. Ask: 'Are there any months where you've scheduled more than you can realistically manage?' Then: 'Are there any goals you placed in Q3 or Q4 that you have placed there because they feel uncomfortable to start sooner?' Those are two different problems and both are worth naming.

Client has generated a comprehensive list of goals — often 10 or more — across multiple domains and wants all of them addressed this year. The month-by-month grid is useful here not as a scheduling tool but as a constraint mechanism: there are 12 months and the grid has a finite capacity. The structure forces prioritization that the client has been avoiding.

Frame this as a capacity reckoning. 'Let's take your full goal list and see what the year can actually hold. The grid has twelve months and you have ten goals. The math is going to require choices.' Some clients will want to schedule two goals per month across every cell. Let them try — the resulting grid usually looks implausible even to them. Then: 'Looking at this, what would realistically have your full attention in any given month?'

Watch for goals that the client places in every month — 'I'm working on this all year.' Goals that span the full year are not goals; they are intentions without milestones. Push for a specific deliverable for each month the goal is active, or force the client to pick the three months where the goal will receive the most concentrated effort. Also watch for the top-10 list itself: if all ten goals score as equally important to the client, something on that list is not genuinely theirs.

After the grid is filled, ask: 'Which month looks most like your actual life, and which looks most like who you want to be?' The honest answer usually surfaces 2-3 months that are planned for an idealized version of the client's capacity. Scaling those back to reality is the most productive part of the debrief.

Client is aware of their goals, reports genuine desire to pursue them, and does not follow through. The pattern is not ambivalence — they want the outcomes. The issue is that without an external structure, goals compete with immediate demands and immediate demands consistently win. Scheduling goals into specific months converts the calendar from a reactive record to a proactive accountability mechanism.

Frame this as externalizing the accountability. 'You already know what you want to do. What we're building here is a structure that holds the decision outside of you, so on the days when your motivation is low, the calendar has already made the choice.' Some clients find this framing uncomfortable because it implies they do not trust themselves. Name it: 'This isn't about distrust. It's about the reality that motivation is variable and schedules are not. The goal is to create the conditions where follow-through doesn't require motivation every day.'

When the client reviews a completed month-by-month grid in a subsequent session, watch for goals that have been silently moved forward without discussion. The goal placed in February that migrated to April is a pattern worth naming explicitly. Also watch for clients who schedule goals but do not treat the schedule as binding — they know what month the goal was in but treat it as advisory rather than committal. The distinction between 'I planned to' and 'I committed to' is the coaching conversation.

After completing the grid, pick the most important goal on the list and ask: 'What needs to happen in the month before you start this for it to be ready to begin?' Backward planning from the scheduled month surfaces setup work that the client has not yet done. Without that setup, even a scheduled goal will not launch on time.