Setting Up Your GR Measurement Cycles
Why Most GR Measurement Programs Fail Within 90 Days
You've been here before. You set up a dashboard. You define some KPIs. You track them for a few weeks. Then the data starts looking the same week after week, or the numbers are too noisy to mean anything, or you just stop finding time to check it. By the end of the quarter, the dashboard is abandoned and you're back to measuring GR the way you always have - intuition and outcomes.
This isn't a motivation problem. It's a structure problem.
Most GR measurement programs fail because they skip directly to metrics before establishing the cycles that make measurement useful. They treat measurement like a scoreboard; something you check after the work is done. The conjugate model treats measurement as a feedback loop. Something you check during the work so you can change what you're doing.
The difference is cycle structure.
The Three Horizons of GR Measurement
In the conjugate method, Westside Barbell tracks three distinct time horizons. Each horizon answers a different question, uses different data, and drives different decisions.
GR measurement works the same way.
Microcycle (one week)
The question: what did we actually do this week?
This is an activity audit, not a diagnostic. You're confirming that the specific actions you planned to take were taken. Did you run the monitoring scans you scheduled? Did you log the stakeholder conversations? Did you enter the consultations you intended to enter?
The microcycle is about execution fidelity - are you doing what you said you would do? If your accessory movements include a weekly monitoring sweep, the microcycle asks: did the sweep happen? If it didn't, you note it and understand why. If it did, you log the output.
Microcycle data doesn't tell you if you're improving. It tells you if you're executing.
Mesocycle (one month)
The question: are our accessory movements producing the expected results?
This is where the diagnostic thinking kicks in. You're looking at the proxies you defined in Article 3 and asking whether they're moving in the right direction.
Compare this month to last month: is your consultation entry rate improving? Is your stakeholder map completeness score rising? Is your average days-to-awareness shrinking? Are submission quality scores getting stronger?
The mesocycle is where you learn whether your accessory movements are actually addressing your diagnosed weak points. If the proxy isn't improving, the mesocycle is where you ask why - and decide whether to adjust the accessory movement, change how you're executing it, or revisit whether the diagnostic was right.
This is the feedback loop that most GR teams skip. They collect microcycle data and they look at quarterly outcomes, but the month-level review - "is what we're doing actually working?" - rarely happens systematically.
Macrocycle (one quarter)
The question: has our weak point landscape changed?
The macrocycle is the strategic review. You're not looking at whether any individual accessory movement is improving - you're looking at whether the overall diagnostic picture has shifted.
After a quarter, some things you worried about have improved. Some haven't. Some new gaps have appeared. The macrocycle asks: given everything we've learned in the last three months, what is our weak point picture now? Do we need to change our primary accessory movements? Are we tracking the right things?
The macrocycle also surfaces the gap between aspiration and evidence. If you thought coverage was your biggest gap but the data shows timing failures have cost you more in the last 90 days, the macrocycle is where you update your priorities.
The Weekly Review Meeting (30 Minutes)
Most GR teams can run an effective weekly review in 30 minutes if they have the right structure. Here's what works:
Activity check (5 minutes): What did we plan to do this week? What did we actually do? What didn't we do and why? This isn't about accountability - it's about understanding your execution patterns. If you're consistently not doing the monitoring sweeps, the question isn't "why are people lazy?" It's "why is the workflow broken?" Fix the workflow.
Alert triage (10 minutes): What came in this week that matters? What did we surface that we wouldn't have surfaced last quarter? This is qualitative, not quantitative. The point is to notice whether your monitoring is catching things earlier.
Microcycle log: Update the tracking sheet with this week's activity. Nothing elaborate - just a log of what was done and what was found.
The weekly review doesn't produce decisions. It produces a record.
The Monthly Review Meeting (One Hour)
The monthly review is where the diagnostic loop actually runs. Here's the structure:
Proxy scorecard (20 minutes): Pull the numbers on your accessory movements. Plot them on a simple trend line - not just this month vs. last month, but the trajectory over the last six months. Are you going up, down, or flat?
Diagnostic interpretation (20 minutes): For each proxy that's not improving, ask why. Some questions to surface: — Are we actually doing the thing that should move this proxy, or are we doing something related but not the same? — Did something external happen that explains the flat period? — Is the metric defined correctly, or are we measuring activity instead of the underlying behavior?
This is where most GR teams discover they've been tracking vanity metrics. A consultation entry rate that measures "did we submit" rather than "did we submit before 50% of the comment period had passed" will move in ways that feel like improvement but aren't.
Decision (20 minutes): For each proxy that isn't moving as expected, decide: adjust the accessory movement, adjust the execution, or revisit the diagnostic. Document the decision and the reasoning. This becomes your institutional memory for the quarterly review.
The Quarterly Review Meeting (Half-Day)
The quarterly review is strategic, not operational. It shouldn't be run by the same person who runs the weekly review - or if it is, that person needs to step out of execution mode and into assessment mode.
Weak point reassessment (90 minutes): Go back to the three diagnostic questions from Article 2. Apply them to the last 90 days specifically: — What cost us the most in the last 90 days? — What did we consistently discover too late? — Who do we wish we had a relationship with that we still don't?
Compare the answers to what you thought your weak points were at the start of the quarter. The macrocycle is where you find out if your diagnostic was right.
Measurement system audit (60 minutes): Are your accessory movements still addressing the weak points you identified? Should any of them change? Are there new proxies worth tracking? Should any existing proxies be retired because they've become normal practice rather than diagnostic tools?
This is also where you look at the compounding effects. If your consultation entry rate has improved 40% over the quarter, are you also seeing earlier awareness on files? Are submissions landing differently with departments? The macrocycle is where you look for the second-order effects of improvement.
Next quarter priorities (30 minutes): Based on the reassessment, define your primary weak point for the next quarter and the accessory movement that will address it. This isn't a long strategic planning exercise - it's a one-page summary of: what we learned, what we're changing, what we're measuring.
The Structural Requirement That Makes All of This Work
All of this cycle structure only works if one condition is met: someone owns the measurement system and treats it as a genuine priority, not a reporting obligation.
Most GR teams that try this and fail do so because the quarterly review becomes a reporting exercise - a deck that goes to leadership that justifies activity rather than diagnoses improvement. The review produces no decisions. Nothing changes.
The difference between a measurement system that works and one that doesn't is whether the reviews produce decisions. If you finish a monthly review and nothing has changed - not the proxies, not the accessory movements, not the execution - the review was a waste of time.
Measurement is only useful if it changes what you do.
What Gets In the Way
Three things consistently derail GR measurement cycles:
Too many metrics. If you're tracking more than three accessory movements per weak point, you're over-measuring. The signal-to-noise ratio collapses. Pick one primary proxy per weak point and track it consistently.
No designated owner. If nobody is specifically responsible for pulling the numbers, running the review, and driving the decisions, the measurement system will quietly die. It needs a home.
External outcome bias. The macrocycle will show you files where you did everything right and lost, and files where you did everything wrong and won. The gravitational pull toward outcome thinking - "we won, so our GR worked" - is strong. The whole point of the conjugate model is to keep your attention on the proxies, not the outcomes. Outcomes are downstream of factors you can't control. Proxies are where your leverage is.
A Realistic Starting Point
If you're not measuring anything now, don't try to implement all three cycles at once. Start with the monthly mesocycle. Pick one accessory movement that maps to your most obvious weak point. Track it for 90 days. Run the monthly review. Make a decision based on what you find.
Once the monthly rhythm is solid, add the weekly microcycle. Once that's working, add the quarterly macrocycle.
The structure compounds. You don't build it all at once. You build the habit first.
PoliTraQ helps GR teams run systematic measurement cycles and track the inputs that compound over time. Request a demo to see how GR intelligence works in practice. Request a demo