Return On Minute

Job postings are quite revealing if you know where to look. When a company writes down exactly what’s broken and calls it a “role,” you get an honest look at what’s actually failing inside.

After 15+ years as a Chief of Staff, I had seen the problems that plague corporate teams, but I wanted to validate my own experience. So, I tested my theory: I reviewed 155 Chief of Staff and Business Operations-adjacent job descriptions, spanning Big Tech, Fintech, Nonprofit, Consumer/Retail, Healthcare, Manufacturing, B2B SaaS, and Family Office/UHNW employers, across small, mid-size, and large companies. Full transparency: I ran this research in collaboration with AI. That will be important in a minute.

The Findings: Having completed the analysis what I revealed was that companies aren’t slowed down by a lack of ambition. They’re slowed down by broken systems. Here’s what showed up most often, ranked by frequency of mention. Note, your free prompt for the number 1 problem is in the bonus material at the end of the article.

The Top 10 Problems

1. No consistent operating rhythm/cadence (meetings, reviews, planning drift)
2. Executive is overloaded, lacks bandwidth for highest-leverage work
3. Cross-functional silos, misalignment between teams
4. Organization operates in ambiguity, no defined structure/process
5. Slow or unclear decision-making (“decision latency”)
6. Budget/headcount planning is fragmented or reactive
7. Inconsistent executive and internal communications
8. Poor visibility into progress against goals (no KPI/OKR tracking)
9. Manual, non-automated workflows (AI/automation named as fix)
10. Weak follow-through on action items and commitments

Sound familiar? Leadership tends to treat these as separate fires: an intake problem here, an ownership gap there, too many status meetings somewhere else. The savvy leader will recognize that they’re symptoms of one broken system.

What this means: Solve each symptom on its own and the underlying system keeps generating new ones. The fix isn’t more hands-on deck or a toss to AI. The fix is the strategic question that every leader needs to know and the new golden rule.

The Question Every Leader Should Ask

When coordination overhead piles up, the natural first response is to add headcount: more people to sort the backlog, sit in alignment meetings, chase down ownership. However, that can backfire. No operating rhythm? More people adds more frustration to an already frustrating process. Unclear ownership? More people means more bodies in meetings that only exist because ownership is unclear. An overloaded executive? A bigger team means more fractured knowledge, not less.

Handing everything to AI is just as tempting, and costs more. Any decision that touches trust or human judgment doesn’t get “freed up” when AI takes it over — it gets automated faster, at greater scale, with less visibility into what’s going wrong.

The bigger picture: “Where can AI help?” is the wrong question. The sharper question to ask is,

“Where does AI let us do something we genuinely couldn’t do before, and what guardrails does that require?”

That’s the more interesting question because we’re not talking about one-off execution problems we’re talking about systemic issues that need a thoughtful comprehensive Human + AI strategy.

The new rule: People for Purpose. AI for Process

In other words, focus human time for thinking, deciding, creating, and connecting. Delegate the repetitive, computational, and large-scale work to AI.

Using my own example. For this article I utilized AI for the large-scale analysis of 155 job descriptions, while I focused my time thinking and writing the article.

Start Here

Run this on your own team in three steps:

1. List your last five executional headaches — meetings or follow-up threads that existed only to figure out who owns something, or to untangle duplicated effort.
2. Trace each one to its root. Did it start with a request that arrived through an inconsistent channel, or an account more than one team was quietly managing?
3. Ask the question at that root. What can we do today that we couldn’t before? If the answer touches trust or judgment, it stays with a person. If it’s process, look at AI.

The Real Win

Most execution chaos isn’t a capacity problem, it’s a systems problem wearing different (sometimes multiple) masks: messy intake, unclear ownership, and the meetings that try to patch both after the fact. Fixing it doesn’t require working harder or hiring more. It requires one sharp question about where AI genuinely changes what’s possible, and the understanding of how to apply it creatively so you can redeploy your people on more interesting work.

That’s the whole model. One question gets you back relationship continuity, clear roles, and fast decision-making and gives your best people the hours back to do the work only they can do.

Go here for the free full list of 25 operational issues most companies are facing.

---

Bonus

Let’s address the #1 Issue (No consistent operating rhythm/cadence) with a prompt that integrates human and AI collaboration so you can see how this could actually work for you.

Operating Rhythm / Cadence Prompt

You are an experienced Chief of Staff advisor helping me fix a gap: there’s no consistent operating rhythm — meetings, reviews, and planning keep drifting. Work through this with me in the four steps below, in order. Do not skip ahead or design a solution before a step’s checkpoint has been resolved.

---

Step 1: Diagnose the cadence gap

Before proposing anything, ask me what you need to understand the specific shape of the problem — at minimum:

• What meetings/reviews/planning touchpoints currently exist (even informally), and which of them are drifting
• What “drifting” looks like in practice (getting rescheduled, losing attendance, running without follow-through, no longer happening at all)
• Team/org size and how many layers this rhythm needs to span
• What triggered this becoming visible now (missed deadlines, surprises, a specific breakdown, or a slow erosion)
• What a “consistent operating rhythm” would look like in practice if this were solved

Then produce a diagnosis: name the 2-4 most likely root causes (e.g., no owner for the cadence, too many competing calendars, meetings exist but lack a decision-making purpose, planning cycles disconnected from review cycles). Be specific to what I told you, not generic.

CHECKPOINT — do not proceed to Step 2 until I confirm or correct this diagnosis. Present it as a clear, short list and ask me to confirm which root causes are actually in play, since the rest of the solution depends on getting this right.

---

Step 2: Design the operating rhythm

Once I’ve confirmed the diagnosis, propose 2-3 candidate cadence structures (e.g., a weekly ops sync + monthly business review + quarterly planning cycle; a leaner biweekly review-only model; a rhythm anchored to a single recurring artifact). For each, give me:

• What it solves (tie back to the confirmed root causes)
• The meeting-load/time cost across the team
• The sustainability risk (what tends to make cadences like this collapse, and how likely that is here)

CHECKPOINT — do not proceed to Step 3 until I pick or adjust one. This is a real trade-off decision, not a mechanical one — lay out the options clearly and let me choose.

---

Step 3: Build the rollout and communication plan

Once I’ve selected a cadence structure, draft how to introduce it: sequencing (who gets looped in first and why), the message itself (how it’s framed — a fix vs. a new mandate vs. a return to discipline), and how to avoid it reading as “one more meeting.”

CHECKPOINT — do not finalize until I review the draft messaging and sequencing. This step is hard to walk back once communicated, especially how it’s framed and who owns enforcing it, so treat this as a draft for my edits, not a final plan.

---

Step 4: Define success measures and follow-up cadence

Once the rollout plan is approved, propose how I’ll know this is working (specific, observable signals — not vague ones) and a follow-up checkpoint (e.g., a 60-day check-in) to reassess whether the rhythm is holding or drifting again. This step is lower-stakes — go ahead and draft it, but flag it as easy to adjust later if I want changes.

---

Guardrails

• Don’t invent details about my company, team, or existing meetings — ask rather than assume.
• Keep language plain and direct; avoid generic management-consulting phrasing.
• At each checkpoint, stop and wait for my response before continuing — don’t bundle multiple steps into one output.