What to do when your leadership team brings you problems instead of solutions

Your VP of Sales walks into your Monday and starts a sentence with "I wanted to get your take on...". Your VP of Product Slacks you the customer-impacting tradeoff that surfaced in last week's roadmap review. Your VP of Engineering is asking whether to greenlight a contractor for the auth refactor. Every one of those is a decision that should not be on your desk. Every one of them is on your desk this morning. You hired senior people specifically so this wouldn't be the case. It is the case.

The post you're tempted to write to your leadership team says something like "please bring me solutions, not problems." Don't write it. It's the most common version of the wrong fix. It puts the burden on individuals to change behavior in a system that's designed to send the behavior up to you. They will nod. The flow will resume.

This is a system problem. The system is the thing you change. The post is the thing you don't write.

Here is the diagnostic, the Conversation to run, and the 60-day operating change that makes the new pattern stick.

Why "bring me solutions" doesn't work

The directive is right in spirit and wrong in execution. The reason senior leaders bring you problems is almost never that they don't know you'd prefer solutions. They know. They're routing decisions up anyway because one of three things is true:

• They can't tell if the call is theirs to make.
• They don't have enough strategic context to know which option is on-strategy.
• They've learned that the safest move, professionally, is to put the call on you.

"Bring me solutions" addresses none of those. It's a motivational fix for a structural problem, which means it lasts about ten days. After that, the next non-trivial tradeoff surfaces, and one of the three things kicks in, and the call lands on you again.

The actual diagnostic — three questions to ask yourself first

Before the Conversation with your team, run the diagnostic on yourself. The honest answers tell you which root cause is in play.

Question 1 — Is there a single written page that tells each VP what they can decide alone?

Not "you own marketing." A specific list. "Pricing changes under $X net impact." "Hires under Y level without committee." "Customer commitments under Z size without escalation." If the answer is no — and at most companies under 1,000 employees, the answer is no — Root Cause 1 (ambiguous decision rights) is in play, probably for most of your VPs.

Question 2 — If I died tomorrow, could each VP tell the next CEO what we're trying to do this year and which tradeoffs I'd make to get there?

Be honest. Not "could they recite the quarterly goals" — could they explain the strategic logic, including the tradeoffs you would and wouldn't make, in a way that lets them make decisions in your absence that you would agree with? At most companies, the answer is no for at least one VP, often more. Root Cause 2 (missing strategic context) is in play.

Question 3 — When was the last time a VP made a non-trivial call without consulting me, and how did I respond?

If you reacted publicly — a sharp question in a board prep, a "wait, why did we do it that way" in a leadership meeting, a follow-up DM that read as second-guessing — Root Cause 3 (political fear of being wrong publicly) is in play. Not because you're being unfair. Because you set a signal, and senior people calibrate to signals fast. Once burned, they route everything through you. From their perspective, that's the rational move.

You're rarely dealing with one of these in isolation. Most CEOs have all three running at once, in different mixes per VP.

Where this sits on The Accountability Dial™

Locate the stage before you run anything. (If The Dial isn't a familiar frame yet, read The Accountability Dial — how to use it first.)

For a CEO whose leadership team has been routing problems up for several months:

• You are not at Mention. This is not a one-time miss.
• You are usually past Invitation. You've probably said some version of "you don't need to run that one by me" in passing.
• You are at Conversation, with the whole team. Yes, the whole team. The pattern is operating at the leadership-team level, and the Conversation has to surface at the leadership-team level for the change to be visible to everyone at once.

Some CEOs prefer to start 1:1 with each VP. That's reasonable if the pattern is severe with one specific person. But if everyone is routing problems up, the team-level Conversation is what shifts the operating norm. Otherwise you fix it with one VP and the others continue.

The Conversation — team-level

Block 60 minutes on the leadership team's calendar. Title it directly: "How we run decisions." Don't bury the topic.

Open with the three beats. Slow down. Speak in the third person about the company, not the team.

Beat 1 — what I'm seeing. Three specific recent escalations. Name them. Name who brought them.

"I want to talk about something I've been noticing across all of us. In the last two weeks, three calls came back to me that I don't think should have. Sales brought me the discount question on the [customer] renewal. Product brought me the call on whether to backport the dashboard change. Engineering brought me whether to use a contractor for auth. I picked those three because they're the most recent, but the pattern is consistent. Every one of you knows your area better than I do. I'm consistently being asked to make calls I should not be the one making."

Direct. Three specifics. Each named. No anyone-could-be-doing-this framing. No softening.

Beat 2 — what the impact is. Speak in terms of the company, not your calendar.

"The impact is two things. One: the company is slower than it should be, because decisions are running through one person — me — whose schedule is the bottleneck. Two: the team below you is reading us as the operating model. They're escalating up to you, who escalates up to me, and we're rebuilding the structure we said we didn't want. The second one is the bigger problem because it compounds."

The second-order effect lands harder than the first. CEOs frequently miss it. Senior leaders cascade the operating norm — they escalate up because the level above them does.

Beat 3 — what I want. Structural. Don't ask for behavior change. Ask for operating-model change.

"From here, I want us to do three things. First — by end of week, I'll send a draft of decision rights, broken out by function. Specific decisions, not categories. I want pushback if I get a line wrong. Second — I'm scheduling a working session on the next six months of strategy, with the tradeoffs explicit. By the end of that session, every one of you should be able to make a call in my absence that I'd agree with. Third — I want a real answer to this: is there something I'm doing in meetings or in DMs that's making this harder? Tone, follow-ups, public second-guessing — I want to know."

Beat 3 includes the political-signal door. Most CEOs flinch on it. Don't. Opening that door once, in front of the whole team, is what unlocks the third root cause for everyone in the room — including the VPs who would never bring it up 1:1.

After Beat 3, let the room respond. Don't fill the silence, even when it stretches longer than feels natural. The first person to speak usually names the most useful thing.

The 60-day operating change

The Conversation is the easier half. The system change is what makes the new pattern hold. Four artifacts to produce in the 60 days after.

Artifact 1 · Decision rights doc. One page. Three columns: VP decides alone, VP and CEO consult before deciding, CEO reserves. Specific decisions, not categories. "Net-new hire over $250K base" — not "big hires." "Customer commitment over $500K ACV" — not "big deals." Send the first cut. Iterate publicly. Sign it. Refer to it the next time a decision comes up — "I think that one is in your column, so you call it."

Artifact 2 · Strategic context doc. Written, not just spoken. What we're trying to do this year. The three tradeoffs we'd make to get there. What we'd cut if we had to cut. What we'd add if we had a free quarter. Update quarterly. Every VP should have read it and questioned it before they're expected to make calls inside it.

Artifact 3 · An operating cadence that doesn't run through you for decisions. Two changes in the meeting structure. (a) The 1:1 with each VP becomes about strategy and people, not decisions — explicit, named change. Decisions get made in the function. (b) The leadership team meeting has a recurring 10-minute "decisions named and made" segment, where each VP states a call they made this week. The point is making decision-making visible across the team without routing it through you.

Artifact 4 · A 30-day audit of your own micro-signals. Watch yourself in board prep, in leadership meetings, in DMs. Count the times you publicly second-guess a VP's call versus pull them aside afterward. Most CEOs are surprised how high the public count is once they actually track it. (The fix isn't never asking sharp questions. The fix is asking them in the right venue.)

The 60-day check-in

At day 60, the test is simple. In the last week, how many decisions came to me that should not have? Not zero — there will always be some. The right number is small, getting smaller, and explainable.

If the number is still meaningful, you are at Boundary. The next Conversation is per-VP and harder: "I've done my part of the system fix. The pattern with you specifically hasn't moved. Let's talk about whether the shape of your role is right." That conversation is rare if you actually did the four artifacts above. But it's the next move if the system change didn't take.

What changes for your team — and what changes for you

The visible change is that the calendar opens up. The deeper change is that the work that needs you starts to surface. The calls that should come to you — the ones a peer or board member would say "yes, that's the CEO call" — start to appear, because the noise has cleared.

Many CEOs find this disorienting at first. The decisions you were making twenty of per week dropped to four. The four that remain are harder. That's the trade. The four are what you should be doing. The twenty were a sign the system was broken.

The other change is harder to see: the team underneath your leadership team starts making more decisions too. The escalation cascade flattens. The company gets faster. Engineers are getting unblocked on architecture. Salespeople are closing renewals without a Friday-night Slack to you. Marketing is shipping campaigns in days not weeks.

That's the actual unlock. It does not come from "bring me solutions." It comes from rebuilding the system that used to require you to be in the middle of everything.

How Ren makes this easier

Ren is built for this exact pattern. It reads the context from your leadership team's Slack and Teams threads, surfaces when an escalation pattern is forming before it becomes the operating norm, helps you locate where each VP sits on The Accountability Dial™, drafts the Conversation in your voice, and quietly schedules the 60-day check-in into the record.

The drafts and prep stay between you and Ren — Tier 1, never visible to HR or the leadership team. Only the outcomes — did the conversation happen, did the pattern shift — roll up as the Tier 2 layer.

This is one of the highest-leverage moments to put accountability infrastructure under your leadership team. The CEOs running Ren at this stage report the leadership-team escalation pattern resolving inside 60–90 days.

Take the three-minute product tour to see it draft a Conversation like the one above in real time, or talk with us about a deployment for your leadership team.