If You Re-engineer Mush

If you re-engineer mush, all you have is re-engineered mush.

Mush is work the organization cannot explain well enough for someone else to follow. People still get the job done. They know whom to call, which exception matters, and what to do when the handoff fails. How much of that knowledge would survive a redesign?

The Sergeant Major of the Army calls it mush

At Management Centre Europe, around 1994–96, Philip Andreae remembers hearing the Sergeant Major of the Army, the senior enlisted adviser to the Chief of Staff of the U.S. Army. He challenged the executives in the room directly. As Philip remembers it, his words were, “All you’re doing is re-engineering mush.”

He explained readiness in threes. Two were ready for duty. The third was in maintenance or being upgraded. Before changing that cycle, you had to know what kept the two ready, what work remained on the third, and what it would take to bring it back into service. The count on the books gave you three. Knowing the work told you what you could actually count on.

What Britain learned before building GOV.UK

Before the United Kingdom replaced Directgov and Business Link, the Government Digital Service examined what those sites already helped people do. The project team wrote user needs on index cards and spread them across the floor to sort them. Its first public beta addressed 667 user needs. While people tried the beta, Directgov remained available for their actual government business.

The floor full of cards is the part worth remembering. The team made the work visible before choosing how to redesign it. The future they wanted was one place to find and use government services. That gave them a reason to keep some things, redesign others and test the new service while the old one still worked.

Sources: Government Digital Service project history and GOV.UK beta announcement.

You must know how the work gets done

If you manage a project, a product or an organization, you must know how the work gets done because your decisions can change what other people are able to do. Document the work as it actually operates. Record enough detail for a successor to inspect the work and for a team to trace the consequences of a change.

  • Applications and interfaces. Record what each application does, who owns it, which versions are in use, and what systems, integrations, or scheduled jobs depend on it.
  • Data and data structures. Record where the data comes from, what the fields and identifiers mean, how records relate, which rules validate or transform them, and where the data goes next.
  • Work processes and procedures. Record the sequence, roles, handoffs, decision rules, exceptions, and workarounds. Follow an ordinary case and one that went wrong. Find out who noticed, who could act, and who had to wait.
  • Equipment, utilities, and capacity. Record what the operation depends on, including electrical load under normal and peak conditions where relevant. Note available capacity and what happens if a limit is reached or a supply fails.
  • Human checkpoints. Record who inspects, approves, or stops the work, when they intervene, what evidence they use, and who takes over if the usual person is unavailable.
  • Quality standards and adherence. Record the applicable standards, acceptance criteria, and tolerances. Show who checks them, how and when checks are made, where results are kept, and how deviations are corrected and checked again.

Keep this record current. Ask the next person to follow it through an actual case and inspect the evidence at each checkpoint. If they have to stop and ask how something works, add what they needed to know. When the market, volume, or cost changes, use the same record to see what would be affected and who must act.

This applies to any change. If you are redecorating an occupied floor of a building, walk it with the people who use and maintain it. Record how people move through it, which rooms and equipment must stay available, where power and data connections are needed, and who checks that the floor is ready to reopen. A change in layout can affect work in a room you never planned to touch.

If you are replacing an air traffic control system, document the applications, data and interfaces, the handoffs between controllers, the human checkpoints, and the standards the replacement must meet. Agree on the evidence needed to show that it meets those standards and that the people who use it can carry on safely through the transition.

In either case, first establish what people depend on today. Let the consequences of getting it wrong determine how much detail to record and how thoroughly to test the change.

A project manager must know which team depends on a handoff because a delay can stop work elsewhere. A product manager must know what customers and support staff rely on because removing a step can create work somewhere else. A corporate manager must know where costs and workloads sit because a saving in one department can become a cost in another.

What established project practices ask you to do

  • Process mapping. Trace the work as people do it, including the decisions, exceptions, and handoffs. Walk through the map with the people who do the work. ASQ’s flowchart guide
  • Lean value-stream mapping. Draw the current flow of work and information across teams before proposing a future state. Use the map to see what happens downstream when one team changes its part. Lean Enterprise Institute
  • Formal change control. Record the baseline and assess a proposed change before approving it. A program manager can use that assessment to see which interfaces and requirements would change, who else has to act, and what the change would do to cost and schedule. NASA Systems Engineering Handbook

Leave a record someone can use

When you hand over your duties, the next person should be able to read the record and inspect the work for themselves. They should be able to see what happens, check that it still happens that way, and know who can help when it doesn’t. Ask someone who has never done the job to walk through the record with you. Where they get stuck is where the record needs work.

Change is a reality. Adapt where you can.

A market shifts. Volume grows. The organization needs to cut costs. Before choosing what to change, use the record to trace the repercussions. Who gets more work? What might break? Which rule, team or customer would be affected? Who will address each consequence?

Before deciding what to change, trace how the work gets done and what people depend on. If the existing system can meet the new need with a limited adjustment, start there. Test the change under ordinary conditions and under strain, and keep a way to restore the service if it fails.

When the existing design can no longer meet the need, replacement may be the better choice. The same understanding tells you what the new system must carry forward, what must keep working during the transition, and what evidence will show the replacement is ready.

That understanding gives you a place to begin when you design the present as the past of the future.

The session, the speaker’s appointment, and the wording of his challenge are presented as Philip Andreae’s recollection.