An AnchorPoint Allegory
Process had a reputation problem.
It wasn't entirely undeserved.
Over the years, Process had been accused of making simple things complicated, slowing everyone down, and insisting that perfectly sensible people complete forms nobody intended to read.
There had been meetings. There had been complaints. Someone in the workshop had once called Process "the reason nothing gets done around here," which was particularly hurtful considering Process had spent the better part of Tuesday making sure the right materials arrived for Thursday's jobs.
But Process was accustomed to being misunderstood.
In fact, Process had been misunderstood for so long that they'd begun to suspect it was simply part of the job.
Every morning, before the first employee arrived, Process wandered through the little business making sure everything was connected.
They checked that whoever answered the phone knew how to reach the person preparing estimates, that the estimates made their way to the schedule, and that the crews knew which materials to collect before heading out.
They weren't particularly interested in telling anyone how to do their job.
They simply wanted to make sure that when one person finished something, the next person could begin.
It was humble work. Invisible work.
And on a good day, nobody noticed Process at all.
Unfortunately, today was not a good day.
"PROCESS!"
The shout came from the little office beside the workshop.
Process sighed, straightened their jacket, and followed the sound.
Standing beside a mountain of paperwork was Procedure, looking exceptionally pleased with herself.
"I've reorganized the customer booking system," she announced.
Process examined the mountain.
"Have you?"
"Yes! Every new job now requires three forms, two approvals, and a verification checklist."
"Why?"
"Consistency."
"Consistency of what?"
Procedure blinked.
"Well. The forms, obviously."
Process rubbed their temples.
Procedure was a distant cousin. They shared certain interests, but their philosophies differed considerably.
Procedure believed that if something was worth doing, it was worth documenting in excruciating detail.
Process believed that if something was worth doing, it was worth understanding why.
Their eldest cousin, Policy, believed that if something was worth doing, there ought to be a rule about it.
Preferably one he'd written himself.
Policy had been around for as long as anyone could remember. He was a dignified fellow with a fondness for laminated notices, sensible shoes, and the phrase "We've always done it this way."
He considered himself the family's moral compass.
Process considered him a necessary influence who occasionally needed reminding that a compass was only useful if someone knew where they were going.
At that moment, Policy appeared in the doorway carrying a clipboard.
"I understand we're changing the booking system," he said gravely.
"Improving it," Procedure corrected.
"Has the owner approved this?"
"Not yet."
"Then we can't proceed."
"Why not?"
"Because changes require approval."
"Who established that rule?"
"I did."
"And who approved it?"
Policy paused.
"That's hardly the point."
Process looked from one cousin to the other.
"Does any of this help the customer?"
Procedure looked offended.
"The customer doesn't fill out the forms."
"Yes, I noticed."
Policy cleared his throat.
"Customers are not authorized to make decisions about internal operations."
Process opened their mouth, thought better of it, and continued toward the workshop.
There were bigger problems to solve.
Near the back door, Chaos was having a wonderful morning.
Chaos was not technically an employee. Nobody remembered hiring them, and the owner had certainly never agreed to pay them. Nevertheless, Chaos had been with the business for years and seemed remarkably comfortable.
At present, Chaos was perched on a stack of empty paint buckets, swinging their legs and watching two employees argue over a missing materials order.
"I sent it yesterday," said one.
"Well, I never got it," said the other.
"You were copied on the email."
"Which email?"
Chaos giggled.
Process approached carefully.
"What's happened here?"
Both employees began speaking at once.
Process listened.
The first employee had completed the order correctly. The second had followed the instructions they'd been given. Somewhere between the two, the information had disappeared into an inbox nobody regularly checked.
Neither person had made a particularly unreasonable decision.
The trouble was that each had assumed the other knew something they didn't.
Process turned to Chaos.
"You've been busy."
Chaos grinned.
"I hardly had to do anything."
That was the infuriating thing about Chaos. They rarely needed to create problems. They simply moved into the spaces between things.
A missing conversation. An unclear responsibility. A decision nobody realized needed making.
Chaos loved those spaces.
Process pulled over an overturned bucket and sat between the two employees.
"All right," they said. "Show me what happens from the beginning."
Chaos stopped smiling.
It was a small question, but a dangerous one.
Process had discovered long ago that most confusion became considerably less mysterious when someone took the time to follow the work.
Not the version described in the binder gathering dust above the kettle.
Not the version the owner remembered agreeing to three years ago.
The actual work, as performed by actual people, on an ordinary Tuesday.
The employees began explaining.
Within ten minutes, they discovered that the materials request had been sent to an old email address.
Within fifteen, they realized that three other employees had developed separate methods of handling the same problem.
Within twenty, they had agreed on a simpler way to confirm that an order had been received.
Chaos slid off the paint buckets.
"You're no fun," they muttered.
"You're welcome to stay," Process replied. "Just stop rearranging the furniture."
By lunchtime, Process was exhausted.
They had helped the person answering the phones untangle a recurring misunderstanding, discovered that two employees were keeping separate lists of the same supplies, and persuaded Procedure to retire a form that still asked customers for their fax numbers.
Policy had objected to the last change on principle, although he couldn't remember which principle.
It had been a productive morning.
Nobody thanked them.
That was fine.
Process wasn't looking for applause.
What troubled them was something else.
For several weeks, they'd noticed an unfamiliar figure moving through the business.
The figure was quiet, rarely spoke, and seemed to be everywhere at once.
They stood behind the owner during difficult decisions. They hovered beside experienced employees when someone asked a question. They followed people home in the evenings and sometimes returned with them on weekends.
Process had initially mistaken the figure for Responsibility.
But Responsibility usually looked rather proud of themselves.
This figure looked tired.
Eventually, Process found them sitting alone at the little table beside the workshop kettle.
"Hello," Process said.
The figure looked up.
"Hello."
"I don't believe we've met."
"Oh, we've met. You just haven't noticed me."
Process frowned.
"I'm usually quite observant."
"Not about me."
"And who are you?"
The figure hesitated.
"Dependency."
Process sat down.
Now that they were looking closely, they could see that Dependency was carrying an extraordinary number of things.
Keys. Passwords. Phone numbers. Customer preferences. Supplier relationships. Unwritten instructions. Little scraps of information tied together with string.
Some of the bundles were so old that their labels had faded.
"Good heavens," Process said. "Why are you carrying all that?"
"Someone has to."
"Surely other people could help."
Dependency gave a small, humourless laugh.
"They could. But everyone is busy. It's usually easier if I just take care of it."
Process recognized the words immediately.
They'd heard them a thousand times.
From the owner who approved every purchase because it was quicker than explaining the limits.
From the crew supervisor who corrected everyone's work rather than showing them how to catch the mistakes themselves.
From the longtime employee who had become indispensable by quietly remembering everything nobody else knew.
Dependency shifted the weight on their shoulders.
"I used to be useful," they said.
"You still are."
"No. I used to help people. Now I think they're afraid to do anything without me."
Process considered this.
Through the office window, they could see the owner answering a call while simultaneously reviewing an estimate and trying to eat a sandwich.
It was nearly two o'clock.
The sandwich appeared to have been there since eleven.
"How long have you been carrying all this?" Process asked.
"Years."
"And has anyone ever asked whether you wanted to?"
Dependency looked surprised.
"No."
For a while, neither spoke.
Then Process reached across the table and picked up a small bundle marked Customer Changes.
"Would you mind showing me what's in here?"
Dependency hesitated.
"It's complicated."
"Most things are until we understand them."
The bundle contained a collection of rules, exceptions, habits, and judgments accumulated over years of experience.
Some were genuinely important.
Others had made sense once but no longer served a purpose.
A few existed because someone had made a mistake in 2018 and nobody had ever quite recovered from it.
Process listened carefully.
They didn't suggest writing everything down.
They didn't summon Procedure.
And they certainly didn't invite Policy to establish a committee.
Instead, they asked who needed to know what, which decisions truly required experience, and which could safely be made by someone else.
They asked what would happen if Dependency took a holiday.
At that, Dependency began to cry.
Not loudly.
Just a few quiet tears that fell onto the table between them.
"I haven't had one," they whispered.
Process stayed with them until the tears stopped.
Then they got to work.
The changes weren't dramatic.
A few people learned things they'd never been shown. Some responsibilities were clarified. A couple of unnecessary approvals disappeared.
The owner discovered that several decisions she'd been making every day could be handled perfectly well by her team.
Policy helped establish clear boundaries for those decisions, so everyone understood what they could approve and when they needed to ask for help.
Procedure was invited to help document the handful of instructions that genuinely needed to be consistent.
She was delighted.
Policy, having finally found a rule that made someone's life easier, was quietly rather pleased with himself.
Chaos complained bitterly about the shrinking number of places to hide.
And Dependency, relieved of several bundles, began standing a little straighter.
Not everything improved.
Some people resisted. Some old habits returned. A promising new approach turned out to create more work than it saved.
Process wasn't surprised.
Businesses were living things, full of people who changed, learned, forgot, improvised, and occasionally did something completely inexplicable.
There was no perfect arrangement that would remain perfect forever.
Process had never believed there was.
One evening, several weeks later, Process found Dependency standing by the workshop door.
They were holding a small suitcase.
"Going somewhere?" Process asked.
"Camping. Just for the weekend."
"How lovely."
"Apparently, they can manage without me."
Process smiled.
"Imagine that."
Dependency looked back toward the office.
"Will everything be all right?"
"Probably not everything."
Dependency's face fell.
"But that's rather the point," Process continued. "They don't need everything to go perfectly. They need to know what to do when it doesn't."
Dependency thought about this for a moment.
Then they smiled, opened the door, and stepped outside.
Process watched them leave.
Behind them, the business hummed along.
Someone answered a customer inquiry. A delivery arrived. Two colleagues solved a problem without asking their supervisor. The owner finished her paperwork and, for once, ate her lunch before it became dinner.
Nobody cheered.
Nobody made an announcement.
Nobody even noticed that Process was standing in the doorway.
And for once, Process didn't mind.
After all, the point had never been to make themselves indispensable.
It was to help everyone else become a little less so.
Process turned out the workshop light and went home.
Tomorrow, there would be more work to do.
There always was.
********************************
AnchorPoint Workflow Solutions helps Vancouver Island businesses understand how work really happens, strengthen the connections between people, and build operations that don't depend on any one person holding everything together.
Understand today. Protect tomorrow. Build what lasts.
