
(This is a continuing story – Part 4 is found here, or if you’re just dropping in please go here for Part 1)
After the Bosch presentations wound down, and the group got smaller, we changed the location for our meetings. In Lincoln, conference rooms were cleverly named by the paint color on the walls, we moved from the Red conference room to the White conference room. Of course, the White conference room was smaller, more intimate with ten chairs around two tables, arranged in a “U” (three sides), with a projector shining on the fourth wall of concrete blocks used on the outside of the building; you can imagine that the wall was painted white.
Our meetings were meandering, not focused, and frankly looking for something to do; we had checked off most of the issues from the complaint list by this time, either by solution, by handing off to the appropriate manager, or by tabling it as too hard. So, the group was looking for its next effort. I started discussing how projects could be started, including a lightweight portfolio management; none of this computed with them, their calipers weren’t calibrated for this kind of thinking yet.
Pivoting, I gave them a project – the File 5S project. In case you aren’t versed in 5S methodology, here is a small explanation:
5S (Five S) is a workplace organization method that uses a list of five terms – ‘sort’, ‘set in order’, ‘shine’, ‘standardize’, and ‘sustain’.
The initiating issue was the share drive of the service organization, which allowed anyone to put anything out on it in any way they felt would work. And with this many anys, you can imagine – it was a mess.
It was, in retrospect, a perfect project. They all had felt the pain of trying to find something in the morass. People would just sling links in an email, and forget the diligent maintenance. Documents were in various states of use, non-use, and decrepitude. No one really understood it all, including me; I’d been there around 3 years at this time, and I still had to ask at times to find the right place.
I did set up some constraints on the group with this project. From a former life as an IT support person, I knew that putting spaces in a filename would make it harder to forward links through text-based platforms like email. From a former life as a data security responsible, I knew that documenting the responsible party for a file is important. And, from my life with this new location, I knew that a common structure would be helpful in navigating, but a rigid structure would be stifling and rejected.
We got to work; I made a proposal for the root of the drive – all departments would get a folder (SRA1, SRA2, SRA3, and SRA4). From there, the second layer would be also rigid (i.e. “100-OrganizationDocumentation”). The third layer, would be carried out by the department (i.e. “100.01-FocusGroup”). Subsequent layers (fourth and up) were at the discretion of the department, but could also be numbered directly.
We discussed, listened, and honed over what the second level was going to be; my recollection was that it was 6 folders. We documented our way through this, all agreeing to how this would operate, then we created our first folders. Then, we moved all the Focus Group documentation in (there was quite a bit by this time), using it as our test. Finally, we put the document on the root of the drive, calling it FileSystem5S.doc. We also created a plan, using the CIP Project Template (1 11×17 sheet with all elements of a small project, like the GANNT chart), and launched. We anticipated that this would be a yearlong project, and it turned out that we were right.
Fred, of course, gave the direction to the supervisors to start the movement in their organization. But, strategically, the supervisor had an ally – the department’s Focus Group member. They themselves, understanding and executing the vision, could assist with the movement, and develop what the department needed. One of their own was deeply involved, taking care of the file movement, and the attendant process changes. Progress was made, sometimes quite quickly.
We ended up choosing an easily-measured KPI – folders on the root. It was meant to be as low as possible, but not lower than 4. Transparency, ease of collection, and visible progress was assured by this counting.
There were inevitable squabbles over who was responsible, especially for dual-departmental use folders. There were some folders that no one claimed; they were eventually moved to a root “Archive” folder, and deleted after 6 months of no claim. There were difficulties with software like Bartender, which demanded a rigid structure. There were some that just didn’t want to move their folders out of familiarity. But, we all could see the numbers trending down, and the three first S’s (“sort, “set in order”, “shine”) were done equally and in parallel.
Certainly, there was much work going on, new ways to handle processes, new organizational capability addressed. Some folders were left empty, with just a file to show the new location for a few weeks. The review of the Archive folder was ongoing, and also coming down.
After 8 months or so, we were down to a few stubborn file structures; most were migrated by this time, and the last ones were the hardest. But, perseverance won, and by month twelve, we had four root folders, after we ceremonially deleted the Archive folder. We were at Standardize now!
But, one more last lesson was to be learned.
I came in, probably about two months after Standardize was achieved and saw a new folder, sticking out conspicuously in our pristine root. I showed it to the Focus Group, and they only had one question for me: how to determine who created it. After showing them how to get this information, the folder disappeared – the respective member had taken care of it. The Focus Group was now monitoring and maintaining what we gave blood, sweat, and tears over; they learned that difficult things can be achieved together over an extended period.
This is also the first time I ever saw Sustain implemented in any environment.
Servant Leader Lessons
Conceptualization – I saw the need, and created a vision (how could this share drive work for us)
Persuasion – I couldn’t manage this transition all on my own, I needed the help that the Focus Group brought, and they caught the vision without needing to be forced
Foresight – With prior experience, I brought the knowledge of not using spaces in file structures and aligning responsibility to a department as my enabling wisdom
Community – the Focus Group became a group here; accountable to one another, working together on cross-department folders, and encouraging to keep momentum up as the folder count went down
Healing – the Focus Group, who couldn’t think in systems a year ago are now guarding a system they built. The Focus Group also discovered they could do hard things together over time




