Just Keep Me Under the Radar
Just Keep Me Under the Radar
Sometimes the job is simple.
Keep the complaints down. Keep the problems contained. Keep the organization out of the spotlight.
But what happens when doing that requires you to look beneath the complaints and discover why they keep happening?
More Than a Workplace Story
Just Keep Me Under the Radar isn't a management textbook.
It isn't a compliance manual.
And it isn't a story about having all the answers.
It is a firsthand account of what can happen when someone is asked to solve an organizational problem—and takes the assignment seriously enough to find the problems underneath it.
It is about what happens when accountability meets organizational reality.
And it raises a question that extends well beyond one company:
What happens when the person you hired to keep the organization under the radar starts making everything visible?
From Experience to Perspective
The experiences behind Just Keep Me Under the Radar also inform the work of Anderson Ops Advisory.
The book explores many of the same underlying themes:
Visibility. Accountability. Execution. Dysfunction. Consequences.
But where consulting asks, “How do we fix this?”
The book asks something different:
“How did we get here—and what happens when someone finally starts looking?”
Coming Soon
Just Keep Me Under the Radar
A firsthand account of complaints, compliance, organizational accountability, and the uncomfortable consequences of making problems visible.
Written by Bryan Anderson
Just Keep Me Under the Radar
A firsthand story about complaints, compliance, accountability, organizational politics, and the uncomfortable reality of fixing problems from the inside.
There was a simple directive:
“Just keep me under the radar.”
The assignment appeared straightforward. Take control of a troubled area of the organization. Reduce complaints. Address customer issues. Create accountability. Keep problems from becoming bigger problems.
But complaints are rarely just complaints.
Behind them are processes.
Behind processes are decisions.
Behind decisions are people.
And behind people are organizational priorities.
The deeper the work went, the clearer it became that reducing complaints wasn't simply a matter of answering them faster. The real challenge was understanding why they were happening in the first place.
There was a simple directive:
“Just keep me under the radar.”
The assignment appeared straightforward. Take control of a troubled area of the organization. Reduce complaints. Address customer issues. Create accountability. Keep problems from becoming bigger problems.
But complaints are rarely just complaints.
Behind them are processes.
Behind processes are decisions.
Behind decisions are people.
And behind people are organizational priorities.
The deeper the work went, the clearer it became that reducing complaints wasn't simply a matter of answering them faster. The real challenge was understanding why they were happening in the first place.
When Complaints Become Data
The work began with a desk already carrying a significant complaint burden.
Rather than simply responding to individual complaints, the approach changed.
Complaints were tracked.
Patterns were identified.
Reasons were categorized.
Departments were examined.
Processes were questioned.
Accountability became measurable.
What emerged was more than a complaint-management process.
It was a picture of how the organization actually operated.
And sometimes that picture was very different from the one people believed they were looking at.
Rather than simply responding to individual complaints, the approach changed.
Complaints were tracked.
Patterns were identified.
Reasons were categorized.
Departments were examined.
Processes were questioned.
Accountability became measurable.
What emerged was more than a complaint-management process.
It was a picture of how the organization actually operated.
And sometimes that picture was very different from the one people believed they were looking at.
The Problem With Fixing Problems
Organizations often say they want problems solved.
But solving a problem can create uncomfortable questions:
How long has this been happening?
Who knew?
Why wasn't it addressed earlier?
What process allowed it to continue?
What happens if the evidence points somewhere nobody wants to look?
Those questions change the nature of the work.
Because once the patterns become visible, they are difficult to ignore.
But solving a problem can create uncomfortable questions:
How long has this been happening?
Who knew?
Why wasn't it addressed earlier?
What process allowed it to continue?
What happens if the evidence points somewhere nobody wants to look?
Those questions change the nature of the work.
Because once the patterns become visible, they are difficult to ignore.
Compliance, Customers & Consequences
The story moves through customer complaints, regulatory concerns, internal processes, sales practices, departmental accountability, and the difficult decisions that arise when operational evidence challenges established assumptions.
There are no easy villains.
There are people trying to do their jobs.
There are leaders trying to protect an organization.
There are customers trying to be heard.
And there are systems that sometimes produce outcomes nobody intended—but everyone has learned to live with.
Until someone decides they shouldn't.
There are no easy villains.
There are people trying to do their jobs.
There are leaders trying to protect an organization.
There are customers trying to be heard.
And there are systems that sometimes produce outcomes nobody intended—but everyone has learned to live with.
Until someone decides they shouldn't.
The Cost of Visibility
Operational visibility is supposed to help organizations improve.
But visibility can also expose things that have been easier to leave alone.
A spreadsheet becomes a trend.
A trend becomes a pattern.
A pattern becomes a question.
And eventually, someone has to decide what to do about it.
That is where this story begins to get complicated.
But visibility can also expose things that have been easier to leave alone.
A spreadsheet becomes a trend.
A trend becomes a pattern.
A pattern becomes a question.
And eventually, someone has to decide what to do about it.
That is where this story begins to get complicated.
The Cost of Visibility
Operational visibility is supposed to help organizations improve.
But visibility can also expose things that have been easier to leave alone.
A spreadsheet becomes a trend.
A trend becomes a pattern.
A pattern becomes a question.
And eventually, someone has to decide what to do about it.
That is where this story begins to get complicated.
But visibility can also expose things that have been easier to leave alone.
A spreadsheet becomes a trend.
A trend becomes a pattern.
A pattern becomes a question.
And eventually, someone has to decide what to do about it.
That is where this story begins to get complicated.