Six Myths About Client Rules That Slow Down DevOps Engagements

Every consultant has a story about the first week at a new client. A laptop that cannot install the usual tools, a change window nobody mentioned, a repository where direct commits to the main branch trigger an automatic revert. In most of these stories, the underlying rules were available from day one. They sat on a wiki page, in a runbook-adjacent folder or in the head of a senior engineer. What blocked progress was a set of assumptions about rules, and those assumptions are remarkably consistent. In DevOps consulting, reading the client’s house rules first is one of the cheapest accelerators available, yet six myths keep people from doing it.

Below, each myth is paired with the evidence that undermines it. The evidence is observational rather than statistical: patterns that repeat across engagements, described honestly without invented figures.

Myth 1: “Rules slow delivery down, so the fast route is to skip them”

The reasoning feels sound. Approval steps, naming schemes and review requirements all consume minutes, so cutting them should save time. What it overlooks is rework. A change that bypasses a review requirement tends to be reverted, redone and re-reviewed, usually with an audience that now trusts the author a little less. The rule was a toll booth, but ignoring it turns out to be a detour. Reading the rule takes minutes, and following it from the start is the quickest path to a merged change.

Myth 2: “Every organisation’s rules are basically the same”

Experienced consultants are most vulnerable to this one, because pattern recognition usually serves them well. Yet tolerances differ enormously. One client expects two reviewers on infrastructure code; another trusts a single reviewer and relies on automated policy checks. One treats production access as routine for approved staff; another gates it behind a ticket and a time limit. Borrowing last quarter’s assumptions is a reliable way to violate this quarter’s policy. The remedy is a fresh read for each engagement, however familiar the stack looks.

Myth 3: “If it is automated, the rules no longer matter”

Automation encodes rules; it does not retire them. A pipeline that blocks unsigned images is a rule with a robot enforcer. When people stop reading the policy because “the pipeline will catch it,” they lose the ability to explain why a build failed or to propose a sensible exception. Consultants who understand the intent behind a gate can suggest improvements to it. Those who only meet it as a red cross are left pressing retry.

Myth 4: “Only auditors and compliance staff read the rulebook”

In practice, the people who benefit most from reading are the ones doing the work. Auditors learn the rules as part of their job. Engineers who skim them discover the same material through failure. A short, deliberate read that covers allowed actions, forbidden ones and the named enforcer gives a consultant the same vocabulary as the client’s own compliance team. That shared footing makes later conversations about change much easier, because you are arguing about specific clauses rather than vague preferences.

Myth 5: “An unwritten rule is not really a rule”

This is the cousin of Myth 3, and it is just as persistent. Plenty of binding norms are never written down: do not deploy on Fridays, never touch the billing database without a named colleague present, always announce changes in a certain channel. Violate them and you will discover their force quickly. The way to surface them is conversational. Ask three people, “What is something new people always get wrong here?” The overlap in their answers is your list.

Myth 6: “Consultants are outside the rules because they are outside the org chart”

Quite the opposite. External staff typically face stricter expectations, since the client carries risk for access it granted. Background checks, logging of sessions, restricted data zones and tighter exit procedures are common. Treating them as an obstacle damages credibility. Treating them as part of the job signals professionalism, and it speeds up the later conversation when you want a permission widened.

What the evidence suggests, taken together

Lay all six beliefs next to one another and a common thread appears: each one tries to save the cost of reading by trusting a belief. Beliefs are cheap, yet they are wrong often enough to turn into expensive surprises. A short read of the actual rules, backed by two or three honest conversations, replaces belief with knowledge at a fraction of the price of one reverted release.

If you are scoping a transformation, our overview of how advisory work can raise an enterprise’s agility shows the wider setting, and the piece on moving a client from first assessment through to enablement describes where a rules review fits in the opening weeks.

How to test these myths in your own engagement

Whether these six hold up is something you can check for yourself. Keep a plain tally during your first month: every time a task stalls, write down whether the cause was a rule you did not know, a rule you knew but misjudged, or something else entirely. At the end of the month, count. In most engagements the first two categories dominate the list, which tells you where your next hour of preparation will pay off. If your tally says otherwise, trust your data and adjust; the aim is evidence, not loyalty to this article.

Share the tally with your sponsor, too. Clients are often delighted to learn which of their rules are poorly signposted, and some of them quietly fix the signposting before the next newcomer arrives.

A short protocol for the first three days

1. Day one: request every policy, standard and contribution guideline the client has, even the ones described as “a bit old.”
2. Day two: read them with a highlighter, marking permissions, prohibitions and named enforcers.
3. Day three: walk the marked-up list through with your client sponsor and ask what is missing.

One last point from a different corner of professional life. Consultants who write publicly about their work meet another set of house rules, those of the publishing venue. A free directory such as FreePostFinder lists sites where people can publish at no cost and reminds users to respect every platform’s community rules. The advice is the same wherever you go: look at the rules before you step onto the stage.

None of the six myths is silly. They persist because they sound reasonable and because rules are dull. The evidence says otherwise: a disciplined first read is among the highest-return activities available at the start of any engagement.

Kabir Malhotra