Every organization has policies.

And every organization has a way that work actually gets done.

Ideally, those two things align closely. In practice, there is almost always some space between them.

A written procedure may require three approvals, while employees have learned that one conversation usually resolves the issue.

A records policy may specify where documents should be stored, while a team has developed its own spreadsheet or shared folder because it works better for the information they use every day.

An organizational chart may assign responsibility to one position, while everyone knows that a particular employee has become the person who actually knows how to get something accomplished.

These differences are sometimes described simply as noncompliance or workarounds.

But that explanation can miss something important.

Work as imagined and work as done

Human-factors and organizational researchers use the concepts “work as imagined” and “work as done” to describe this distinction.

Work as imagined is how a process is expected to operate—through policies, procedures, job descriptions, workflow designs, and management expectations.

Work as done is what actually happens when employees apply those expectations in a real environment with competing priorities, limited time, available resources, changing circumstances, and accumulated organizational knowledge.

The difference matters.

A 2024 study published in the International Journal of Industrial Ergonomics examined how managers and employees viewed deviations from work procedures. Researchers found meaningful differences between management expectations and how employees described actually completing their work.

Employees reported adapting procedures more often than administrators believed they did. Importantly, the reasons were not limited to simple error or unwillingness to follow instructions. Organizational conditions, the nature of the task, environmental factors, and individual circumstances all contributed.

Other research examining “work as imagined” and “work as done” has reached a similar conclusion: understanding how employees actually perform a task can provide valuable information for designing better procedures.

That does not mean every workaround should become policy.

It means every meaningful workaround may be worth understanding.

Before correcting the behavior, understand the reason

When a written procedure and actual practice differ, a natural management response may be:

“Why aren't employees following the process?”

Sometimes that is exactly the question that needs to be answered.

But another question can be equally important:

“What is making the established process difficult—or impractical—to follow?”

Perhaps the procedure was written when the organization was smaller.

Maybe technology has changed.

Perhaps a required approval creates an unnecessary bottleneck.

A position may have changed while the procedure remained the same.

Employees may have discovered a more efficient approach.

Or the workaround may reveal a genuine control, compliance, safety, or accountability problem that needs to be corrected.

Leadership cannot know which of these is occurring without first understanding the work itself.

That makes one of the most useful questions in an operational review surprisingly simple:

“Show me how this really works.”

The role of workplace norms

Written policy is only one source of instruction inside an organization.

Employees also learn through observation.

They see which procedures supervisors reinforce.

They learn which approvals are considered essential and which ones are routinely bypassed.

They notice how experienced employees solve problems.

They learn who actually has decision-making authority, regardless of what the organizational chart says.

They also notice whether the organization's behavior supports its stated policies.

The National Institute for Occupational Safety and Health has addressed this relationship between formal policy and organizational culture through its Total Worker Health framework.

NIOSH encourages organizations to involve workers in the design and implementation of workplace programs and to examine whether workplace culture actually supports formal policies and procedures.

That is an important distinction.

An organization can have an excellent policy on paper while everyday workplace norms communicate something entirely different.

Over time, those informal norms can become the real operating instructions.

When the gap becomes an organizational risk

Not every difference between policy and practice is a problem.

But an organization should understand where significant differences exist.

Otherwise, the gap can create vulnerabilities that are difficult to see.

For example:

  • A new employee may follow the documented procedure only to discover that everyone else follows a different process.
  • A key employee may leave and take an undocumented workflow with them.
  • Managers may believe an internal control exists because it appears in policy, while employees stopped using it years ago.
  • Two departments may perform the same process differently without realizing it.
  • Staff may develop increasingly complex workarounds to compensate for a system that no longer fits the work.
  • An organization may be unable to explain its actual process clearly during an audit, transition, funding review, or leadership change.

Those are not necessarily employee-performance issues.

They are often operational issues.

Policy review should include reality

Traditional policy review often asks:

Is the policy current?

A more useful operational review goes further.

It asks:

What does the policy say should happen?

What actually happens?

Why are they different?

Is the current practice effective, appropriate, and compliant?

Does it create unnecessary risk or confusion?

Should the policy change, should the process change, or should both change?

Could another employee successfully perform this work using the documentation that currently exists?

The answers can reveal far more than reviewing a policy document in isolation.

Employees are an important source of operational intelligence

The people performing the work every day often know where the friction points are.

They know which instructions are unclear.

They know where information gets duplicated.

They know which approvals delay otherwise routine work.

They know which spreadsheet quietly became mission-critical.

And they often know which process would become difficult tomorrow if one particular employee were unavailable.

That knowledge is valuable.

Inviting employees to explain how work actually happens does not mean turning every preference into organizational policy.

It means giving leadership better information before deciding what should change.

The objective is not to eliminate judgment or flexibility.

The objective is to understand where organizational expectations and operational reality have separated—and determine whether that separation is helping or hurting the organization.

Bringing policy, process, and practice back together

Strong policies provide structure, consistency, accountability, and protection.

Strong operations make those policies workable.

And healthy organizational cultures help employees understand why the processes matter.

When all three reinforce one another, employees spend less time navigating around systems and more time doing the work those systems were intended to support.

For leaders, that may mean moving beyond asking whether a procedure exists.

Ask whether it is understood.

Ask whether it is practical.

Ask whether it is followed.

Ask what employees have learned that leadership may not be able to see from the policy document alone.

And occasionally, simply ask:

“Show me how this really works.”

The answer may identify an outdated policy.

It may reveal a training need.

It may expose an unnecessary control.

It may uncover a compliance concern.

Or it may reveal that employees have already developed a better way of working that simply needs to be evaluated, documented, and incorporated into the organization's formal processes.

That is not a failure of policy.

It is an opportunity to make policy more useful.

Sources and Further Reading

  1. National Institute for Occupational Safety and Health (NIOSH), Centers for Disease Control and Prevention. Total Worker Health® Frequently Asked Questions. NIOSH emphasizes worker participation, organizational-level interventions, and employee voice in the conditions and design of work.
  2. National Institute for Occupational Safety and Health (NIOSH). Fundamentals of Total Worker Health® Approaches: Essential Elements for Advancing Worker Safety, Health, and Well-Being. DHHS (NIOSH) Publication No. 2017-112.
  3. Ashraf, A.M., Peres, S.C., et al. (2024). The realities of procedure deviance: A qualitative examination of divergent work-as-done and work-as-imagined perspectives. International Journal of Industrial Ergonomics, Volume 100, 103564.
  4. Ashour, A., Ashcroft, D.M., & Phipps, D.L. (2021). Mind the gap: Examining work-as-imagined and work-as-done when dispensing medication in the community pharmacy setting. Applied Ergonomics, Volume 93, 103372.
  5. de Carvalho, P.V.R. et al. (2018). Reflections on work as done (WAD) and work as imagined (WAI) in an emergency response organization. Applied Ergonomics, Volume 68, 28–41.