The Business Rule Archaeology Problem: Why Nobody Knows Why the Process Works That Way

Get In Touch

Related Posts

The Business Rule Archaeology Problem: Why Nobody Knows Why the Process Works That Way

Business rule archaeology is what happens when a team has to dig through old emails, spreadsheets, system settings and half-remembered conversations to work out why a process runs the way it does. Someone asks a simple question: “Why do we need three approvals for this?” Nobody knows. The person who set it up left years ago, the documentation is missing and the system just does it. Yet nobody dares change it, because it might be holding something important together.

This guide explains why business rule archaeology has become such a common headache in Australian organisations, what it costs, and how business analysts uncover, document and challenge hidden rules safely. If you are curious about building these skills yourself, we will also point you to practical training from Business Analyst Courses Australia.

What Is Business Rule Archaeology?

Think of it as detective work on your own organisation. Over the years, processes collect rules: approval limits, validation checks, naming conventions, exception paths and manual workarounds. Many were created for a good reason. Over time the reason fades from memory, but the rule stays.

Business rule archaeology is the effort of recovering that lost context. Analysts, managers and developers work backwards from the way a process behaves today to find out where each rule came from, who needs it and whether it still makes sense. It is slow, sometimes frustrating, and absolutely necessary before any serious change.

Why Nobody Knows Why the Process Works That Way

Lost rules are not a sign of sloppy people. They are the natural result of how organisations evolve. Here are the usual culprits.

Staff turnover and tribal knowledge

Experienced people carry unwritten knowledge in their heads. When they retire, move teams or change employers, the reasons walk out with them and only the habits remain.

Rules buried inside systems

Many rules live as code, workflow settings or spreadsheet formulas. They run quietly in the background, and nobody sees them until something breaks or someone tries to migrate to a new platform.

Quick fixes that became permanent

A temporary workaround added during a crisis often becomes “just how we do it”. Years later it is treated as policy, even though it was never meant to last.

Mergers, restructures and system changes

When teams merge or systems are replaced, documentation is rarely carried across completely. Rules from several eras end up layered on top of each other, sometimes contradicting one another.

Regulatory and policy drift

A rule may have started as a legal requirement that later changed. The law moved on, but the process did not, so the business keeps paying for a control it no longer needs, or worse, misses one it does.

The Real Cost of Business Rule Archaeology

Hidden rules do not just irritate people. They slow projects, raise risk and inflate budgets. A system upgrade that should take months stretches out because the team keeps discovering rules nobody listed. A new hire spends weeks learning unwritten exceptions. A well-meant change breaks something that used to work, because nobody knew it was relied upon.

As a simple illustration, imagine a finance team that adds an extra approval step to every invoice over a certain amount. Years later, nobody remembers why, so the step stays, adding days to payment times. When a new system is introduced, the team either copies the step blindly or removes it without checking if it was linked to an audit requirement. Both choices carry risk. This is business rule archaeology in a nutshell.

Signs Your Organisation Has a Business Rule Archaeology Problem

  • People say “that is just how we do it” and cannot explain why.
  • Only one or two staff understand a critical process.
  • Projects keep uncovering “surprise” requirements late in delivery.
  • Different teams follow different versions of the same process.
  • Nobody wants to change a legacy system for fear of breaking something.
  • Documentation exists, but nobody trusts it.

How Business Analysts Solve the Business Rule Archaeology Problem

This is where a trained business analyst earns their keep. Instead of guessing, they use structured techniques to find rules, test them and record them properly. The table below shows how common symptoms map to analysis techniques.

What you see Likely hidden cause Analysis technique Explore
“We have always done it this way” Rule created for a forgotten reason Five whys and stakeholder interviews Business Analysis Techniques
Staff do extra steps not in the procedure Informal workarounds Process observation and BPMN-style mapping Fast Start in BA
Different teams, different results Conflicting or duplicated rules Business rules catalogue and decision tables BCS BA Foundation
Surprise requirements late in the project Rules buried in systems or spreadsheets Document and system analysis, traceability BA Practice Practitioner
Fear of changing the legacy system Unknown dependencies Impact analysis and iterative delivery AgileBA Foundation
Rules lost in a cloud migration Logic hard-coded in old platforms Requirements mapping and cloud decision-making AWS Business Essentials

None of these techniques is magic. Together, they turn vague folklore into evidence that decision makers can use.

A Practical 7-Step Approach to Business Rule Archaeology
business rule archaeology

1. Define the scope

Pick one process or system to investigate. Trying to excavate the whole organisation at once is a recipe for burnout.

2. Collect existing artefacts

Gather policies, old requirements, user guides, emails, tickets, spreadsheets and system configuration. Even incomplete documents give clues about intent.

3. Observe the process in action

Watch people do the work. What they actually do often differs from the official procedure, and the differences point to hidden rules and workarounds.

4. Interview the right people

Talk to long-serving staff, frontline users, compliance, IT and anyone who has “fixed” the process before. Ask open questions like “What would go wrong if we stopped doing this?”

5. Ask “why” repeatedly

The classic five whys technique gets beneath surface answers. Keep asking until you reach a business reason, a legal requirement or the honest answer “nobody knows”.

6. Record each rule with its rationale

Create a business rules catalogue with the rule, its source, its owner, the date reviewed and the reason it exists. Link each rule to related requirements so future teams can trace it.

7. Classify and decide

For every rule, decide whether to keep, change, retire or investigate further. Involve the process owner and, where relevant, legal or compliance teams. The idea of testing before removing a rule is sometimes called respecting the fence: understand why it was built before you tear it down.

Business Rule Archaeology in Australian Cities

The problem shows up wherever long-running organisations exist. Banks and insurers in Sydney and Melbourne carry decades of layered policy. Government agencies in Canberra manage complex legislated rules. Resource and utility companies in Perth and Adelaide run long-lived operational systems, and Brisbane organisations modernising their platforms face the same hidden-rule discoveries. Business analysts in every city are in demand to untangle them.

If you want to build these skills locally or online, explore our business analyst course options for Sydney, Melbourne, Brisbane, Perth, Adelaide and Canberra, or see the full locations page.

Business Analyst Courses That Teach These Skills

Good analysis is a learnable craft. If you are new to the field, the Fast Start in Business Analysis course introduces the role, key concepts and practical tools. The Business Analysis Techniques course goes deeper into methods such as process modelling and requirements elicitation, which are the backbone of business rule archaeology.

For recognised qualifications, consider the BCS Business Analysis Foundation course or the Business Analysis Practice Practitioner course. If you work in agile teams, the Agile Business Analyst (AgileBA) Foundation course shows how analysis fits with iterative delivery, and the AWS Business Essentials course helps when your legacy processes are moving to the cloud. Compare everything on the courses page, learn about us or read more on our blog.

For further reading, the International Institute of Business Analysis publishes professional standards and guidance, the BCS explains its business analysis qualifications, and Jobs and Skills Australia offers labour market information. Logitrain also describes its business analysis training courses for those comparing providers.

Frequently Asked Questions About Business Rule Archaeology

What is business rule archaeology?

It is the process of uncovering, documenting and validating the hidden or forgotten rules behind a business process, usually by studying documents, systems and the people who use them.

Why do organisations lose track of their business rules?

Common reasons include staff turnover, rules embedded in software, temporary fixes that became permanent, restructures and outdated documentation.

How do you document business rules properly?

Use a business rules catalogue or decision tables that record each rule, its source, owner, rationale and related requirements. Keep it in a shared, version-controlled location.

What does a business analyst do about legacy processes?

They investigate how the process works today, uncover the reasons behind its rules, engage stakeholders, recommend improvements and make sure changes are documented and traceable.

Which business analyst course should I start with?

Beginners often start with a fast-start or foundation course, then add techniques or practitioner-level training. The right choice depends on your experience and goals.

Final Thoughts: Dig Before You Change

Business rule archaeology is not glamorous, but it protects organisations from expensive mistakes. Every hidden rule you recover is one less surprise in your next project. Capture the reason along with the rule, and the next team will thank you.

If you want to learn how to do this professionally, contact our team or call 1300 649 299. An adviser can help you pick a business analysis course that fits your background.

Scroll to Top