You know productivity is broken, but not exactly where. Or you can see several problems at once and cannot tell which one to fix first. That distinction matters more than it sounds.
Productivity breaks in five places: how you set priorities, how you manage capacity, how you run meetings, how you carry work to done, and how individuals focus. They depend on each other in a predictable order, so the symptom you feel most is often downstream of a cause you have not named. Fixing meetings while the real constraint is unclear priorities just produces better-run meetings about the wrong work. This diagnostic scores all five, finds the one constraint that is most holding back the others, and hands you a sequenced plan that starts in the right place.
This is a sorting instrument, not the fix itself. It will not set your priorities or rebuild your meetings. It tells you which of those to do, and in what order. It takes about thirty to forty five minutes and an honest view of how work actually flows day to day. You do not need data. You need to be straight with yourself.
If the real problem turns out to be a broken process or technology rather than how people manage work, that is operational efficiency. If you cannot prioritize because there is no strategic direction to prioritize against, that is strategic planning. The diagnostic will say so if it sees it.
Before you score anything, name what you are actually living. Work through each of the five sub-domains, priorities, capacity, meetings, completion, and individual effectiveness, and mark every symptom that is true for you right now. A sub-domain with several symptoms checked is a candidate problem area. One with none is likely already functional.
Open the Productivity and Workflow Snapshot →Now turn each symptom picture into a level from one to five, which is what makes the work measurable. Answer honestly for each sub-domain below, then read your finding. The capability line most organizations are crossing sits between Level 2, where the thing lives in someone's head and runs reactively, and Level 3, where it is defined, visible, and repeatable.
Your finding above names the one sub-domain most holding back the others, using the dependency order: priorities sits upstream of everything, capacity gates completion, meetings are the cross-cutting coordination layer, completion is downstream, and individual effectiveness is the person-level foundation. Your binding constraint is the lowest-scoring sub-domain that sits highest in that order, so a Level 1 in Priorities outranks a Level 1 in Completion. If two feel equally bad, the one further upstream wins.
Open the Productivity Constraint Map →Start with the guide that addresses your binding constraint. Then add every other sub-domain scored below Level 3, in dependency order. Drop any sub-domain already at Level 3 or above, it is not where your leverage is. Do not run more than two guides at once. Your finding lists this sequence for you.
Open the Prioritized Productivity Action Plan →Turn the sequence into a written plan. For each sub-domain in order, record its current level, a target level one above it as a default, the first concrete action drawn from the first step of the guide you will engage, and the single owner of that action. The finished plan tells you what to work on first, what better looks like, and the next thing to do. That is what makes the rest of this pathway executable rather than overwhelming.
Continue in the Prioritized Productivity Action Plan →You can state your binding constraint in one sentence. You have a sequenced list of guides with a current and target level for each, and you know your single first action and who owns it. You have moved from "something is wrong with how we work" to a clear baseline read you can measure real progress against later.