The Gap Between Strategy and Execution Is Measurable Now
Every company runs on two sets of rules: the ones leadership wrote down and the ones the organization actually follows. Until recently, surfacing the delta required expensive consultants, lengthy offsites, or the kind of blunt feedback most teams won't give in a room. That's changed.
Nate Jones ran an AI agent against his own calendar and codebase and published the 15 implicit rules it surfaced — not the rules in his strategy doc, but the ones his company was visibly executing day to day. The method is straightforward: point an agent at your calendar data (who gets time, how much, recurring vs. ad hoc) and your repo or task system (what actually ships, what stalls, what gets revisited), then ask it to infer operating principles from the patterns.
The output isn't a vibe. It's a numbered list of behavioral rules your org is running whether you intended them or not.
Why This Matters for Non-Tech Operators
This diagnostic is especially sharp for companies that don't have engineering culture as a forcing function for explicit documentation. In non-tech organizations, strategy drift happens quietly. A sales leader's calendar fills with deal reviews and empties of pipeline-building time. Product roadmaps shift toward customer escalations. Hiring decisions cluster around immediate pain rather than stated priorities. Nobody announces these changes — they accumulate.
An agent audit makes the drift legible. You're not asking people to self-report; you're reading the artifact layer the organization already produces. That removes the political friction from the diagnosis.
The Jones framework is also copy-paste usable. His 15 rules are concrete enough that most operators will recognize analogues in their own orgs immediately — which makes the exercise useful even before you run the agent yourself.
The Actionable Move This Week
Before your next planning cycle or quarterly business review, run this audit:
- Export 90 days of calendar data for yourself and your direct reports.
- Pull your task or project system — closed tickets, open items, items that have been deferred more than twice.
- Feed both into a capable LLM with a prompt like: "Infer the 10-15 operating rules this organization is actually following based on these behavioral patterns. Be specific and direct."
- Compare the output against your stated strategy or OKRs line by line.
The gaps that show up aren't failure — they're the actual agenda for your next leadership conversation. Running this before someone else surfaces the misalignment is the whole point.