If you run on EOS® (Entrepreneurial Operating System®), you already have more signal than you realize.

Every week, your leadership team updates a scorecard, reviews Rocks, and works through an Issues list. Some items move. Some stall. Some keep coming back like a bad penny.

Most teams treat those as meeting artifacts. I want you to see them as something else:

Your Rocks, Issues, and scorecard misses are a live feed of your transformation backlog.

EOS is already telling you where your business is asking for real change. The question is whether anyone is listening, and whether you have a system to act on it.

When the Same Rocks Keep Coming Back

You have probably seen this pattern:

• The same Rock appears three quarters in a row
• The same Issue shows up in L10 notes with a new date
• The same metric flashes red on the scorecard, then amber, then red again

It sounds like:

• We still don't have a real CRM process.
• We're still short on capacity in implementation.
• We still have quality problems in that one region.

On paper, these look like isolated problems. In reality, they are early warning signs that your operating model is outgrowing its current shape.

A few common repeat Rock patterns:

• Recurring tech debt. Systems patched together, manual workarounds, spreadsheets everywhere. You see it as duplicate entry, reporting delays, and frustrated teams.
• Chronic capacity issues. One function is always underwater: onboarding, delivery, customer support. Hiring helps for a month, then the backlog returns.
• Persistent quality or consistency problems. One product line or location keeps missing standards. You fix a symptom, but the pattern returns.

When these show up once, they might be local issues. When they show up again and again, across quarters and teams, they are not just Rocks.

They are transformation signals.

They are telling you: The way this part of the business works needs to change, not just be patched.

Reading the EOS Dashboard as a Transformation Backlog

So what do you do with those signals?

Instead of asking, What is wrong with this Rock owner? — start asking, What is this Rock telling us about the system?

Here is a simple way to mine your EOS artifacts into a transformation backlog.

Step 1: Pull a few quarters of EOS data

Look back over the last 2–4 quarters for:

• Rocks that were re-scoped mid-quarter, carried over, or marked complete but later resurfaced as new Issues
• Issues that appear in multiple L10s, involve more than one department, or tie directly to a scorecard metric that stays red
• Scorecard metrics that miss target for 3 or more weeks in a row, require explanation every meeting, or trigger the same excuses: still waiting on X, still unclear on Y

You are not collecting everything. You are looking for patterns and repeats.

Step 2: Group by change theme, not department

Next, cluster these items into themes. Think in terms of capability or system, not org chart.

For example:

• Customer onboarding and handoff (Sales, Operations, Finance)
• Data and reporting for decision-making (IT, Finance, Operations)
• Delivery capacity and scheduling (HR, Operations, PMO)

Now you are not staring at forty scattered Rocks and Issues. You are looking at four to six transformation themes.

Each theme is a hint that part of your operating system needs redesign, not just another heroic effort.

Step 3: Turn themes into a transformation portfolio

For each theme, ask three simple questions:

• What is the real outcome we need?
• What would have to change to get there?
• Is this a project, a program, or a bigger transformation?

A project is bounded and focused (for example, Implement a new onboarding workflow in the CRM).

A program touches multiple projects (for example, New customer journey from sale to renewal).

A broader transformation reshapes strategy, structure, technology, and culture (for example, Move from project-based work to subscription services).

What you have just created is a transformation portfolio:

• A visible list of the most important changes your business is asking for
• Backed by real EOS data, not opinions or buzzwords

Now the question becomes: who owns this portfolio, and how do you run it?

Running the Portfolio with a PMO or TMO

Depending on your size, you may have a Project Management Office (PMO) or a Transformation Management Office (TMO) for continuous change.

If you are a small or mid-sized business without a TMO, you can still get most of the benefit by having your PMO run a TMO-lite structure.

The goal is the same either way:

Give your biggest changes a clear owner, a simple lifecycle, and a steady rhythm.

At Flatirons, I use a simple four-phase lifecycle: Assess → Align → Execute → Sustain. Here is how a TMO or TMO-lite puts it to work.

Assess: Turn noise into a clear picture

For each major theme, ask: What is really happening today, where are the delays and rework, and how is this hurting customers, cost, or risk? Keep it fast and practical — the goal is clarity, not perfection.

Align: Decide what you will actually change

Align leaders around a few clear bets: the outcome you want, what must change in process, roles, systems, or governance, and who owns which decisions. This turns a vague wish list into a short, sequenced set of initiatives.

Execute: Run the work like a portfolio, not a pile

Track all major change efforts in one view, surface cross-team conflicts early, and connect progress back to your EOS scorecard. A short weekly transformation huddle, a simple decision log, and a few readiness gates before big moves give structure to work that is already heavy and risky.

Sustain: Make sure the change sticks

Update roles and KPIs, retire old tools and processes, and feed lessons learned back into your Rocks, Issues, and scorecard. That is how you avoid the big push, slow slide back and keep those same Rocks from returning next year.

Closing Thoughts

If you run on EOS, your system is already telling you where deeper change is needed. Recurring Rocks, persistent Issues, scorecard metrics that stay red — these are not minor annoyances. They are signals.

When you pull those signals into a clear transformation portfolio and give that portfolio an owner and a simple lifecycle, the way you work starts to change. Whether you have a formal TMO or a lightweight version, the principle is the same. EOS helps you run the business. A transformation portfolio and a basic TMO structure help you change the business on purpose.

So if your Rocks keep coming back, it is not a sign to push harder. It is an invitation to pause, read what the system is telling you, and turn those signals into a roadmap.

Will you keep treating those signals as noise, or will you turn them into a roadmap?

EOS® and Entrepreneurial Operating System® are registered trademarks of EOS Worldwide. This post is based on my experience working with organizations that use EOS. Flatirons Consulting is independent and not affiliated with, sponsored by, or endorsed by EOS Worldwide.