A Letter from a Compliance Strategist

A compliance strategist discovers why perfect dashboards can conceal unsafe workplaces, inaccessible reporting, and unresolved harm. Through fictional organizational cases, this original letter explores compliance culture, ethical risk management, accountable discretion, meaningful remediation, and the difference between documented controls and real protection.

A Letter from a Compliance Strategist printed in dark serif lettering on vintage parchment.

To the executives who ask me how to make an organization compliant without changing the way it behaves,

I have learned to recognize the question before anyone says it aloud. It arrives in a conference room with a polished slide deck, a revised code of conduct, and an instruction to make the audit findings disappear by the next quarter. Someone asks how many employees have completed the training. Someone else asks whether every policy has an owner. Nobody asks whether the employee who reported the original problem still feels safe coming to work.

I am a compliance strategist. I design systems intended to help organizations obey laws, meet obligations, detect misconduct, and correct failures before they become crises. I believe this work matters. I also know how easily it can be reduced to a performance of control, complete with charts, signatures, and reassuring percentages.

At the start of my career, I thought my job was to build a fortress of procedures. I collected requirements, assigned responsibilities, designed approvals, and created dashboards. Each new control seemed to close another gap. I could show a board how a risk moved from identification to mitigation. I could explain which manager owned which obligation. The diagrams were elegant.

The trouble with a diagram is that it never tells you who is afraid to draw on it.

Consider the fictional company Merrow Components, where I was asked to review a recurring problem with equipment maintenance records. On paper, the system was impressive. Operators signed daily inspection sheets. Supervisors confirmed that the sheets were complete. Internal auditors sampled the forms each month. Training completion stood above ninety-eight percent.

Yet machines kept failing in ways the records did not predict.

My first instinct was to tighten the process. More frequent checks, stronger signatures, and additional spot inspections were obvious recommendations. They would also have been easy to sell. Every proposed action could be counted, and every completed action could be displayed as progress.

Then I spent a morning beside a production line.

The operator I shadowed, a woman named Farah, checked a machine at the beginning of her shift. She pointed out a vibration that did not yet meet the threshold for a formal defect but was unusual enough to concern her. She had mentioned it twice. Her supervisor had told her to record only faults that met the published criteria. If she marked the machine as requiring attention, the line might stop, and the team would miss its daily output target.

Farah did not falsify the form. She followed its instructions. The form had no useful space for what she knew.

When I asked how she raised a concern that did not fit a category, she showed me a separate incident portal. It required a computer login, several dropdown selections, and a description that could identify the reporting employee. She had used it once. Afterward, her supervisor asked why she had escalated a matter he believed should have remained within the team.

The problem was not a missing control. It was a control that competed with another incentive, supported by a reporting channel people had reason to distrust.

I began to understand the difference between compliance architecture and compliance culture. Architecture tells people what the organization formally expects. Culture tells them what will happen if they take those expectations seriously.

A code of conduct can require honesty while a manager rewards the concealment of bad news. A policy can promise nonretaliation while employees see colleagues excluded from desirable assignments after speaking up. A safety procedure can demand that work stop when conditions are unsafe while a production target punishes every interruption.

When written requirements and lived consequences disagree, employees often learn which one the organization truly enforces.

I brought these findings to the leadership team. The operations director pointed to the training statistics and asked whether I believed the staff had misunderstood the rules. I said the rules were understood. The conflict lay in the consequences of following them. He looked irritated, as though I had moved the problem from a manageable document into the more difficult territory of management.

He was right about one thing. It was more difficult.

Real compliance strategy requires decisions about resources, authority, and accountability. It asks whether the person responsible for meeting a target is also allowed to pause the work that produces it. It asks whether a whistleblower’s identity is protected in practice, not only in a policy. It asks whether managers are assessed on the quality of the problems they surface, or merely on the absence of reported problems.

A low incident count can indicate good performance. It can also indicate silence. A high training completion rate can indicate participation. It cannot, by itself, prove comprehension or ethical judgment. A clean audit can reflect effective controls, but it may also reflect a sample that never reached the places where the organization is most vulnerable.

Metrics are useful evidence. They are not the whole case.

At Merrow, we changed the inspection form to include an observation field for emerging concerns. We separated reporting a potential hazard from assigning blame for a confirmed failure. We required supervisors to document how they responded to concerns, and we examined whether employees who raised them suffered adverse changes in scheduling or evaluation.

These changes were less glamorous than a new dashboard. They were also more expensive than an additional online course. Supervisors needed time to investigate. Maintenance teams needed capacity to act. Leadership had to accept that a rise in reported issues might signal improving visibility rather than deteriorating performance.

The first quarterly report looked worse. More potential problems were recorded, and the number of open corrective actions increased. An executive asked why the strategy had produced such alarming numbers. I answered that the earlier numbers had described what the organization was willing to see.

That answer did not win me friends.

Compliance work contains a peculiar temptation: to treat every uncomfortable fact as a threat to the reputation of the programme. When a control fails, the person who designed it may feel personally accused. When a manager breaches a rule, the compliance team may fear that reporting the problem will make its oversight appear weak. The system then begins protecting its image rather than its purpose.

I have done this myself. I have softened findings because I thought a harsh report would be ignored. I have presented a completed action plan as proof of improvement before the change had been tested in daily work. I have used the word ‘residual’ to make a risk sound smaller than the people exposed to it would have considered it.

Strategy requires compromise, but compromise becomes dangerous when we conceal it from the people who bear its consequences.

I now insist on separating three questions that are too often collapsed into one. Is a requirement legally or contractually binding? Does the current control actually reduce the relevant risk? And who carries the burden created by that control? A rule can be mandatory but badly implemented. A voluntary practice can be valuable. A protective measure can shift costs onto workers, customers, or communities who have little say in its design.

Without those distinctions, compliance becomes a contest to accumulate obligations rather than an effort to meet them intelligently.

At another fictional organization, a charitable housing provider called South Lantern, I saw the opposite mistake. Staff were so committed to helping applicants that they routinely bypassed documentation requirements intended to prevent duplicate awards and conflicts of interest. The exceptions were compassionate in individual cases, but the pattern was not transparent. Some applicants received help quickly because they knew a sympathetic employee. Others waited for the formal process.

Good intentions had produced unequal treatment.

We did not solve the problem by forbidding judgment. We defined a documented emergency route, made eligibility criteria understandable, and required periodic review of how exceptions were distributed. Staff could respond quickly without hiding what they had done. Applicants could challenge a refusal without needing a personal connection.

That experience taught me that the goal is neither maximal rigidity nor unlimited discretion. It is accountable discretion within a system people can understand.

A strategist must also distinguish a control from a remedy. A mandatory declaration may reveal a conflict of interest. It does not resolve the conflict. A complaint channel may receive allegations. It does not investigate them. A training module may describe retaliation. It does not protect a person whose supervisor quietly withdraws opportunities after a report.

Organizations love controls that end with a completed form because completion is easy to verify. Remedies require a more difficult question: what changed for the person or process the control was meant to protect?

I once asked a team to trace one complaint from the moment it was submitted to the point where the complainant experienced a result. The official record showed a timely acknowledgement, an investigation, a finding, and closure. The employee had never received an explanation of the outcome and had been transferred to a less desirable shift. The file was closed. The problem was not.

We changed the closure criteria. The case manager had to record whether corrective action had been implemented, whether retaliation concerns had been reviewed, and whether the reporting person had received an appropriate explanation consistent with confidentiality. Closure no longer meant only that the investigator had finished writing.

Some readers may hear this as an argument for endless procedure. It is not. Every new requirement consumes attention, and attention is finite. A system that asks employees to complete twenty overlapping attestations may make them less attentive to the one warning that matters. A compliance programme can become a hazard when its paperwork crowds out the work it exists to protect.

Good strategy therefore includes subtraction. Remove duplicate approvals. Retire controls that do not address a credible risk. Simplify language. Give people one reliable way to report a concern rather than six channels with unclear ownership. Test whether a new process works for someone with limited time, unfamiliar terminology, or imperfect access to technology.

Efficiency is not the enemy of care. Efficiency becomes dangerous when we save time for the institution by transferring uncounted work to everyone outside it.

I often return to An Open Letter on Efficiency That Excludes when I evaluate a proposed control. The question is not only how much administrative work it removes. It is where the work goes. I also think about An Open Letter on Accountability That Dissolves, because responsibility divided among many offices can disappear unless someone is charged with seeing a problem through to its actual resolution.

There is a further risk that strategists rarely confess. We can become fluent in the language of ethics without remaining attentive to ethical experience. We speak of risk appetite, control maturity, escalation pathways, and assurance. These terms can be useful, but they can also place a pane of glass between us and the person who waits for an answer.

Every technical term should survive translation into ordinary language. If I cannot explain a control to the employee expected to follow it, I may not understand its purpose well enough. If I cannot explain who benefits and who may be harmed, I may have designed an instrument of convenience rather than protection.

I have learned to ask frontline workers what happens on a bad day. Not the ideal day described in the process map, but the day when a colleague is absent, a machine is unreliable, a customer is frightened, and the supervisor is under pressure. Rules that work only when nobody is tired are not resilient rules.

I ask managers what news they least want to hear. I ask auditors what evidence their sampling method might miss. I ask the legal team where discretion is allowed and where it is not. I ask employees whether the easiest way to meet a target conflicts with the safest or most honest way to do the work.

These questions do not replace professional judgment. They give judgment something real to work with.

To the board that hired me, I would offer a different kind of dashboard. Keep the measures of training, reporting, remediation, and audit findings. But place beside them the time it takes to correct a known problem, the proportion of employees who believe they can raise concerns without retaliation, the number of controls retired because they were ineffective, and the evidence that corrective actions changed outcomes.

Do not reward the absence of bad news until you know whether bad news is allowed to travel.

To the compliance teams beneath those dashboards, I would say that your professional integrity does not require you to be severe in every case. It requires you to be consistent about purpose, honest about uncertainty, and prepared to defend the people whom a requirement was created to protect. Sometimes that means refusing a powerful person’s request. Sometimes it means challenging a procedure that burdens a vulnerable person without reducing any meaningful risk.

Both forms of courage are necessary.

Farah still works at Merrow in the story I have told you. The machine she worried about was repaired after a later inspection confirmed the defect. She did not receive an award for spotting it. She received something more useful: a supervisor who asked her to explain the early signs to the maintenance team, and a process that recorded the next warning without making her choose between honesty and her standing at work.

I do not know whether Merrow will remain attentive. No compliance programme can guarantee that. Systems drift. People change roles. Targets become urgent. The temptation to make a report look clean will return.

That is why I no longer promise a fortress of rules. A fortress can keep danger out, but it can also keep the truth from entering.

I promise a system capable of hearing what it would rather not hear, tracing responsibility to a decision, and changing when the evidence demands it.

With less confidence in perfect diagrams and more respect for imperfect people,

A compliance strategist who measures success by what the rules protect

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to Top