How to Understand What Your Organization Is Telling You

hello@kerriequeen.com (Kerrie Queen) — Tue, 18 Aug 2026 14:13:35 GMT

SIGNALS FRAMEWORK

Organizations are constantly sending signals about what's working, what's getting in the way, and what's ready to change.

Sometimes these signals are obvious:

👀 “Our CRM is a mess.”
👀 “Decisions are taking too long.”
👀 “People keep creating workarounds.”
👀 “Our teams aren't communicating.”
👀 “We've hired great people, but we're still struggling.”

Other times, the signals are quieter.

🤔 Meetings multiply.
🤔 Information starts living in spreadsheets.
🤔 Leaders become the bottleneck.
🤔 People develop their own ways of doing things.
🤔 A new system is introduced, but everyone keeps using the old one.

It's tempting to treat each of these as an individual problem.

✔️ Fix the CRM.
✔️ Improve communication.
✔️ Add a process.
✔️ Implement the new technology.

But the visible problem isn't always the real problem.
How do you find the real problem?...

Start by listening.

When I work with an organization, I don't want to start by deciding what needs to be fixed. I want to understand what the organization is telling us.

That means listening to leaders and teams, looking at how work actually happens, understanding how decisions get made, seeing where information moves or gets stuck, and paying attention to the systems and tools people rely on.

① I look at the goal first:
Where are we trying to go?

② Then I ask:
What's getting in the way?
How are people actually working?
Where does work get stuck?
How do decisions get made?
Are the systems supporting the way people work?
What's changing around the organization?

The goal isn't to collect information for the sake of collecting it.
It's to connect the signals.

Signals become patterns.

A CRM problem → that might actually be an ownership problem

A communication problem → that might actually be a decision problem.

A process problem → that might actually be the result of teams designing their own solutions because the organization never established a shared way of working.

An AI problem → that might actually be a process problem.

Once the patterns become clear, we can make better decisions about what actually needs to change.
And that's the point.

The Signals Framework isn't about finding problems. It's about understanding what those problems are telling us.

From there, the work becomes much more practical:

Understand → Identify → Design → Build → Measure → Transfer

The work doesn't end with a recommendation.

The Goal

The goal is to build something that works, establish how we'll know it's working, and leave the team with the systems, knowledge, and capability to continue without me.

That's what it means to listen to the organization before deciding what to change.

Your Business Has Changed. Has the Way You Work Changed With It?

hello@kerriequeen.com (Kerrie Queen) — Tue, 18 Aug 2026 13:58:21 GMT

Growth is exciting. Until the way you've always worked starts getting in the way.

👏 The team gets bigger.
👏 There are more customers.

But, there's also

More meetings.
More decisions.
More tools.
More information.
More people involved in every decision.

And somehow, things that used to be easy become harder.

The informal communication that used to keep everyone aligned starts breaking down.

✔️ A founder who once knew everything now can't possibly stay involved in everything.
✔️ A process that worked with five people doesn't work with fifty.
✔️ People create workarounds.
✔️ Departments develop their own processes.
✔️ Information starts living in different places.

Nobody necessarily did anything wrong.
The organization changed. The way it works didn't.
And, that's often where the real problem begins.

Growth creates new organizational demands.

The answer isn't always to add another tool, another meeting, or another person. Sometimes the organization needs to redesign how work happens.

❓ Who owns what
❓ Who makes which decisions
❓ Where does information live
❓ How do teams hand work to each other
❓ What needs to be standardized
❓ What should remain flexible
❓ What does leadership actually need to see
❓ What does the team need in order to move without waiting for leadership

These are organizational design questions. And they're easy to overlook because the symptoms show up somewhere else.

You might think you have a technology problem when you actually have an operating problem
You might think you have a people problem when people are working inside a system that makes their jobs harder.
You might think you have an execution problem when priorities and decision ownership aren't clear.

The goal isn't to make the organization more complicated. It's the opposite.

The goal is to intentionally design the way the organization works so people can do their jobs, leaders can make decisions, and the business can continue moving toward what comes next.

Your organization doesn't have to stay the way it was just because that's how it got here.