How Detailed Should Action Items Be Without Micromanaging Your Team

An Action Item Is a Weekly Unit of Work, Not a Level of Detail

Josh describes his own starting point without much flattery. Sit down at your desk. Good, you did it, that was seven minutes. Now turn on your computer. He knows it is ridiculous and he does it anyway, because a weekly accountability meeting with nothing in it is worse than one with too much. An empty meeting teaches a leadership team, within about three weeks, that the meeting is optional. Loading the plate is a hedge against an empty room, and as a hedge it works. The trouble is that it works by quietly redefining what an action item is, and once you put the definition back the hedge stops being necessary.

In the Vision framework the layers are fixed and they are not interchangeable. There is a yearly strategic plan. Beneath it sit quarterly initiatives. Beneath those sit monthly goals. Action items live at the weekly level, and that is a statement about size rather than about specificity. An action item is a unit of work scoped to a week, carrying an hour estimate a person can defend. Thirty of them against one initiative goal does not mean the consultant was unusually thorough. It means either thirty weeks of work got assigned to a single month, or a month's worth of steps got relabeled as a quarter's worth of action items. Both are the same mistake, and neither is a question of trust.

• The layer sets the size. If something does not consume a meaningful part of a week, it is not an action item, whatever it is called in the tool.
• An empty weekly meeting is a genuine risk, but overloading the plan is an expensive way to solve what is really an attendance problem.
• Over-specifying is a legitimate coaching choice with a shelf life. Once the person can estimate their own work, the scaffolding has to come down or it becomes the thing they resent.

The Inflection Point Is a Task Versus a Step Inside One

Gary reduces the decision to a single question: are we creating an action item for each step, or are we creating the task that takes about a week and estimating the hours the whole thing will take? That is the inflection point, and he is candid that there is no hard rule on either side of it. What settles it is not the work. It is the person doing the work. A leader who has run an agreement gross profit analysis before needs one line that says run it and bring me your read on why the bottom five look the way they do. A leader who has never opened that report needs the steps, because in that case the steps are the training and pretending otherwise just moves the failure to week three.

Josh's own progression shows what the release valve looks like. He starts deep, gets a realistic picture of how long the work actually takes, and then moves the client to the highlight reel: configure and run the report, identify the agreement gross profit across that client group and form a view on why, remediate the top five offenders. Thirty items become three. Nothing was dropped. The detail did its job, which was to produce an estimate nobody had, and then it got out of the way. The mistake most plans make is treating the level of detail as a property of the plan rather than a property of the relationship, and then leaving it at whatever setting it happened to start on.

• Detail is calibrated to the person's knowledge of the subject matter, not to the importance of the initiative.
• Writing out every step once has a real purpose. It produces an honest estimate, which is what keeps the plan from underestimating the work and setting the quarter up to fail.
• The same body of work is a mixture. Some steps deserve to be action items and some are just steps, and deciding which is which is the actual consulting.

Action Items With No Line Back to a Goal

Josh logs into whatever system a client is running, and what he finds is usually thoughtful. People have put real effort into their lists, the items are specific, the owners are named, the dates are there. What is missing is a line connecting any of it to something larger. The items are well formed and unattached. That produces a failure that looks exactly like productivity from the inside: a team stringing together enough tactics to generate some outcome, with nobody able to say in one sentence why this quarter's work was chosen over anything else that could have been done instead.

The instinct to fight that by loading the plate is understandable. If the plan fills the week, there is no room for the good idea that showed up on Tuesday. Gary is honest that he does not know whether the approach helps or hurts, and his hesitation is the useful part. Volume is a blunt instrument against drift, and it carries a cost the owner pays later in resentment and in hours. The sharper version of the same intent is the one he lands on: prioritize, then time bind. Whatever is next and highest priority is what gets worked on, and the plate is full because the priority is settled rather than because the list is long. The question of whether you have ten things that are all kind of the one thing, or one of those ten that genuinely is the one thing, is answered by ranking rather than by adding.

• An action item that cannot be traced up to a monthly goal, a quarterly initiative and a yearly plan is a task, and tasks belong in the day job, not on the strategic plan.
• Ten things that are all kind of the one thing and one thing too large to start are the same problem wearing different clothes. Both postpone the decision about what comes next.
• Prioritizing and time binding does the job that overwhelming the plate was doing, and it does it without teaching a capable leader that they are not trusted.

Drift Is What Happens When Good Ideas Join the Weekly Meeting

The meetings are not where plans fail. Gary is direct that the weekly cadence is right, that the monthly and quarterly reviews built on top of it are right, and that a true yearly plan is the thing that makes any of them mean something. The plan is what sets up the meetings in the first place. What goes wrong afterward is additive and nearly invisible. Somebody has a genuinely good idea in week six and it gets added to the level 10. In week nine a dependency surfaces that nobody saw in planning, so that gets added too. By month five the agenda is full of real work that has very little to do with the session six months earlier where the year was decided.

Nobody made a bad call. The plan drifted because every individual addition was defensible on its own terms, which is precisely why judgment in the moment cannot catch it. This is the failure mode that makes a weekly meeting feel productive right up until the quarterly review, where the initiative has not moved and no one can point to the week it stopped moving. The structural answer is that the weekly agenda is the plan's action items. Anything else that lands on it is competing for the same hours, and it should have to win that competition out loud rather than by arriving first.

• Drift is cumulative and each increment is defensible, so it has to be caught by structure rather than by somebody noticing in the room.
• The monthly review asks whether the right action items were chosen to raise the probability of hitting the initiative goal. The quarterly review asks whether the right initiatives were chosen at all.
• Staying focused on what was decided six months ago in the planning session is not stubbornness. It is the only way to know later whether the decision was any good.

A C Plus Process Can Still Produce A Plus Results

Gary describes a client three years in who is still deep in the business, still going on sales calls, still doing install work. By the book, the planning discipline has been loose. Meetings happened, but not every one of them, and not always the way the framework says. Graded honestly, Gary puts the process at a C plus or a B minus. The financials are not a C plus. Profitability is high, revenue is running thirty to fifty percent ahead of what they planned for, and the operational targets are ahead too. Every significant decision over three years, the hires, the building, the vans for the technicians, landed at roughly the right time. Sitting with that, the useful question is not whether the process was followed. It is whether the result can be attributed to anything the company actually did, or whether the year was simply generous. Most owners avoid asking that out loud, because the comfortable answer is available and costs nothing.

The way to get an honest answer is to change the time horizon, and Gary's view is that the collapse of time horizons is a general condition rather than an MSP problem. Everyone wants the gym, the business and the relationship resolved by tomorrow. A month is far too short a window to separate a working plan from a good month. Set the horizon at a year, put a real plan in motion, keep showing up to the meetings even when they feel like motion for its own sake, and the difference between doing a little and doing none turns out to be very large. Josh's analogy is the right scale for it: you do not have to train like a fitness influencer, you have to lift something slightly heavier than yesterday and eat a bit more protein, consistently, for long enough that the outcome is not a coincidence. The part that makes any of it legible is targets. The client in question did not know his numbers well enough to know what was possible, and what changed things was being told what gross profit should look like and what revenue each new hire should carry. Once a target exists, a good year stops being indistinguishable from a lucky one.

• A process graded at a C plus that runs for three years beats an A plus process that runs for one quarter and then stops.
• The gap between a company doing a little strategic work and one doing none is much wider than the gap between a little and a lot.
• Without targets you cannot tell a working plan from a good year, because there is nothing for the result to be measured against.

Frequently Asked Questions

What is the difference between an action item and a step inside one?

An action item is a unit of work sized to a week, with an hour estimate attached. A step is one of the moves required to complete it. The test is whether the thing consumes a meaningful part of a week on its own. Running a report, reading the result and remediating the worst offenders are three action items. Opening the tool, filtering the columns and exporting the file are steps inside the first one.

How many action items should one initiative goal have?

There is no fixed number, but the arithmetic constrains it. Action items are weekly and monthly goals sit above them, so a single monthly goal supports roughly four to eight of them before it stops being a month of work. Thirty against one initiative goal is a signal that steps have been promoted to action items, or that a quarter of work has been compressed into a month.

Is weekly the right cadence for reviewing action items?

Yes, provided a real yearly plan exists underneath it. The weekly meeting reviews action items and nothing else: what got done, what did not, and where help is needed. One of those weekly meetings becomes the monthly, which covers financials and initiative goals. One becomes the quarterly, which reviews the initiatives themselves. Without the yearly plan, the cadence has nothing to measure against and turns into a status meeting.

Why do strategic plans drift even when the team is doing the work?

Because items get added to the weekly meeting throughout the year and each addition is individually reasonable. A good idea in week six, a dependency in week nine, a customer request in week twelve. None of them is wrong, and together they crowd out the work the plan was built around. Drift is not a discipline failure in any single week. It is the sum of defensible decisions, which is why it has to be caught structurally.

How can you tell whether a strategic plan is actually working?

By whether you can tie the result to actions taken in the period, and by whether a target existed before the result arrived. If revenue is up and nobody can name the decisions that moved it, the honest position is that the outcome is unexplained rather than proven. Targets are what make the difference visible: knowing what gross profit should look like, or what revenue a new hire should carry, converts a pleasant surprise into evidence one way or the other.

How long should you give a plan before judging whether it works?

A year. A month is short enough that a good month and a working plan look identical, and six months is still inside the range where a single large deal distorts the picture. Set the horizon at a year, follow the plan deliberately even when individual weeks feel like going through the motions, and check back. The results generally do arrive, but not on the timeline most owners want them on.

Episode Highlights

• 00:00 - Cold open: the tension stated plainly, before any of the framing arrives to soften it.
• 00:41 - A leader handed roughly thirty action items says the detail feels like distrust, and the feedback is fair without the underlying plan being wrong.
• 02:03 - The four layers that settle the argument: yearly plan, quarterly initiatives, monthly goals, weekly action items.
• 02:59 - Over-specifying is a deliberate coaching choice, made to guarantee the weekly meeting has something real in it.
• 04:37 - Writing out every step once produces a realistic estimate, which is what allows the list to collapse to a highlight reel afterward.
• 05:45 - There is no hard rule for detail. It is calibrated to the person's knowledge of the subject and to how much guidance the consultant can supply.
• 07:33 - Action items with no visible line back to a larger goal produce a team stringing tactics together toward an outcome nobody chose.
• 10:24 - Prioritizing and time binding replaces overwhelming the plate, and does the same job at a much lower cost.
• 11:39 - Plans drift because every good idea added to the weekly meeting is individually defensible.
• 12:59 - The monthly review asks whether the right action items were chosen. The quarterly one asks whether the right initiatives were.
• 13:26 - The question most owners avoid asking out loud: is the plan working, or did the quarter simply go your way.
• 15:13 - A client three years in, loose on process, running thirty to fifty percent ahead of plan on revenue with profitability to match.
• 17:33 - A C plus process producing A plus results, and why that is not the contradiction it sounds like.
• 19:19 - Short time horizons are the general problem, and they are not specific to business.
• 20:38 - Extend the horizon to a year, go through the motions deliberately, and the modeling tends to hold.

About the Co-Host: Gary Boyle

Gary Boyle is a Partner for Strategy & Business Development at Bering McKinley. With a background spanning network engineering, entrepreneurship, and strategic consulting, Gary brings real-world operator experience to helping MSP owners build stronger, more profitable businesses. On the Vision roundtable he co-hosts with Josh Peterson, working through the planning and execution decisions that determine whether an MSP grows deliberately or by accident.

Connect with Gary on LinkedIn →

About the Host: Josh Peterson

Josh Peterson is the CEO of Bering McKinley and host of The BMK Vision Podcast. Since 2004, Josh has worked with hundreds of MSP owners to build operationally sound, profitable businesses through consulting, peer teams, and direct coaching.

Connect with Josh Peterson on LinkedIn →

Related Resources from Bering McKinley

• How to write a company goal your team will actually care about
• Setting long-term goals in performance management

Want to Continue the Conversation?

Action items are the smallest piece of a strategic plan and the easiest one to get wrong, because the mistake looks like thoroughness from the inside. Keeping the layers straight is the work the Vision Operating System is built to make repeatable, so the weekly meeting stays about the plan rather than about everything else that arrived that week.