A satirical story based on a 2013 draft. Bine is a fictional character. Unfortunately, his way of working requires no fictional technology.
Bine was the head of IT at a medium-sized company which, in his professional opinion, was slightly too large for the capabilities of its users.
The company had a managing director, sales, accounts and production. Bine was responsible for all of them, although the organisation chart did not adequately reflect this.
The last management meeting had made that particularly clear.
The accountant wanted to present her financial projections, but the projector was not working. Bine stood up, sighed loudly enough for those by the door to appreciate the seriousness of the situation, and began his diagnosis.
Ten minutes later, there was a picture on the screen.
The accountant then spent almost an hour talking about costs, revenues and variances. Bine sat back down in silence. Nobody thanked him, even though his was the only contribution without which the meeting could not have happened at all.
When they reached “IT” on the agenda, the director asked whether he had prepared next year's plan.
Bine looked towards the projector.
Apparently, making things work was no longer enough. Now he had to plan them as well.
Back when the system had a door
Things used to be different.
He and Lojz had kept the server in the same room as their desks. If something started humming, they heard it. If something stopped humming, they heard that even more clearly. System monitoring was direct and reliable, and, most importantly, required no weekly report.
Whenever they were doing something important, Lojz hung a sign on the door:
DO NOT DISTURB — SYSTEM FAULT UNDER REPAIR.
The company understood. Nobody knocked. Nobody asked what it would cost. Nobody demanded that the fault be classified according to its business impact.
Once, the sign remained on the door for three days after the fault had been fixed. Those were among the most productive days in the department's history.
Bine had kept his white lab coat from that period. It lay neatly folded in the bottom drawer, beneath some old catalogues. Occasionally, he still put it on in the evening. It had pockets for screwdrivers and a dignity that a polo shirt with the company logo simply could not replace.
Meanwhile, the servers had been moved to the basement. The director called this setting up the data centre.
Bine mainly saw it as increasing the distance between the expert and his expertise.
Two youngsters and a dangerous idea
As the company grew, Bine was given two colleagues.
He had asked for help. HR had apparently interpreted this as permission to recruit people with ideas of their own.
The first wanted to organise the documentation. The second suggested automating repetitive tasks. Bine listened with the patience of a man who would one day have to repair the consequences of their enthusiasm.
“First, you need to understand how we do things here,” he explained.
“That's why we'd like to write it down,” said the first.
Bine put down his cup.
Some things were simply too complex to document. For instance, before the monthly accounts run, a particular service had to be restarted, but not before Thursday and certainly not until Marija from accounts had called.
Why?
Because once, they had done it differently.
Bine remembered. That should have been enough.
When they proposed checking and tidying up the procedure, he decided there was currently no time for experiments. The monthly run was approaching, and he needed to be available.
Nothing worked without him.
The whiteboard
One Monday, he found a large whiteboard in the office.
It stood where his weeping fig had been. Beneath it, his old cassette player was gone too. It did not work, admittedly, but that made it no less his.
The board had three columns: “To do”, “In progress” and “Done”.
Bine first checked whether his name was on it.
Then he asked who had approved it.
His younger colleagues explained that it would make it easier to see who was working on what, what was waiting and where they needed help.
Bine saw rather more than that. Anyone walking into the office could form an opinion about their work. Without the necessary background. Without context. Possibly even the director.
“You can't squeeze our work onto sticky notes,” he said.
By lunchtime, he had nevertheless written one of his own.
It said “ongoing matters”.
He put it in the middle column.
It stayed there.
The reports were good. People were the problem.
Bine liked automated reports, especially the green ones. Green reports confirmed that the department was well managed.
He reviewed the red ones when there was more time. They usually required other people's involvement, which always complicated the work.
One morning, the head of sales called because they could not issue quotations.
Bine opened the dashboard. The server was reachable. The processor was not overloaded. There was plenty of disk space.
“Everything is green on our side,” he said.
“And on our side, a customer is waiting.”
Bine regarded this as unnecessary pressure on IT. If everyone stayed calm, the problem would be easier to resolve.
His younger colleague later discovered that the connection between two applications was not working. He suggested adding a check to the monitoring system to see whether a quotation could actually be produced.
Bine thought that would only put more red on the dashboard.
The phone system was paid for
When the director requested a review of telephony costs, Bine began to have serious doubts about the company's future.
The phones worked. Handsets on the desks. Wires in the walls. The switchboard paid for. Pick up, dial, talk, hang up. Which part of that needed transforming?
He intended to put all this in his analysis, but could not remember the switchboard model.
He went to the room the external maintenance engineer used to visit.
There was no door.
He stood in the corridor for a while, staring at the smoothly painted wall. Then he remembered the refurbishment. They had moved partitions, fitted out a new meeting room and, somewhere in the process, bricked up access to a room nobody apparently knew was important.
The phones still worked.
Bine saw this as proof of the quality of the existing solution.
His younger colleagues saw a somewhat different problem, but by then they had learnt that every professional discussion needed the right moment.
After two days, one argument with the maintenance man and some work on the wall, the switchboard was accessible again.
At the management meeting, Bine reported that the critical situation had been successfully resolved.
The director thanked him.
It was the first good meeting in a long time.
The director wanted something strategic
At the next meeting, however, the director raised the future of IT again.
Bine was supposed to become more strategic.
The phrase hurt. Only the previous Friday, he had fixed the director's home computer. On Saturday, he had been at the company for the accounts run. On Monday, he had rescued the warehouse printer. If that was not a comprehensive understanding of how the organisation worked, what was?
But this time, the director had a problem too, although he was not yet fully aware of it.
For years, he had rewarded Bine for always being available and somehow fixing everything. When Bine asked for time to put the systems in order, there was none. When he proposed replacing something worn out, it had to last another year. When he miraculously revived a system late in the evening, he was a hero.
Now the director wanted fewer heroics and more order.
Bine should have recognised the moment and joined him. Instead, he took it as a lack of gratitude.
“I could always go on holiday. Then you'd see,” he said.
For a moment, the meeting room fell silent.
Bine read the silence correctly: the message had reached its recipient.
What he did not quite understand was the message he had sent.
The experiment
A few weeks later, he did go on holiday.
Before leaving, he gave everyone the phone number they already used to reach him. He reminded his younger colleagues not to tackle anything major on their own.
On the first day, he placed his phone on the table beside his sun lounger.
It did not ring.
On the second day, he checked the signal.
On the third, he called the office.
“Everything all right?”
“Yes,” said his younger colleague.
“The accounts run?”
“Done.”
“Did Marija call?”
“Yes. We went through the procedure together and wrote it down.”
Bine sat up.
“Just be careful. Things here aren't that simple.”
“We know. That's why we documented the exceptions too.”
After the call, he stared at his phone for a while. He should have been pleased. His colleagues clearly knew a thing or two, the business was running and, for the first time in ages, he could finish his holiday in peace.
Instead, he worried whether, when he returned, anyone would understand how much work it had taken to put all of this in place.
That was not an entirely unfair question. Bine really had done a great deal. Spent many nights at the company and solved many problems when nobody else was around.
The trouble was that he wanted only one kind of proof of his contribution.
That nothing worked without him.
When he returned, he found several new sticky notes in the “Done” column. His “ongoing matters” were still in the middle.
The director met him at the door.
“You've trained them well,” he said. “Everything ran smoothly.”
Bine had already drawn breath to explain why things were not that simple.
Then he looked towards the board.
He had been praised.
Just for something he wasn't proud of.