First, some background…
I work for a very large corporation that manages the supply chains of various companies all over the world. When we take over a supply chain, this is referred to as an ‘implementation’. My title is Implementations Process Writer which is fairly self-explanatory. I write work instructions for our operators so that they can perform their jobs more effectively. I find the work interesting because, as part of the implementation team, I get to work with engineers, IT, operations managers, quality managers and many other individuals depending on the scope of the work. An average implementation takes about a year and my engagement happens usually 4-6 months out from the ‘go live’ date. As a management employee with 15 years of experience, I am expected not just to perform my core job function, but also to provide my perspective on problems when I think I can contribute.
Many of my coworkers studied business management or industrial engineering and so their minds work much different than my own. As I have shared on this site before, my academic background is in the social sciences.On the best days our different backgrounds provide a balance in the work we do. While many of my coworkers approach our projects from a business perspective first, my default setting is always to think of the cultural impact. They see process flows and hard data and I consider the human factor, which leads me to the theme of this post.
Right now we are in the middle of a huge multi-state project. As part of the project we are opening a new facility for our customer in New Hampshire. My company does not have a large footprint in New Hampshire, since most of our large facilities are either in Louisville or Atlanta. This new facility is special in that it will employee a workforce of over 200 people who are almost all newly hired. Because it will exist on an island of sorts, away from our large corporate centers, it will have its own culture.
One thing we have talked a lot about recently is language. There are three sources for the jargon that will be used in the facility. One source will be our customer. We need our employees to use the same terminology when they speak to them about the business. We need to call a widget the same thing they call it. If their software has a function called DOTHIS then we must also call it DOTHIS. The next source of language comes from our own internal workspeak. The terms we use are sometimes different from our customers and the employees will have to learn that as well. Lastly, we have the language used by our vendor who is designing much of the automation technology for the facility. We have the most flexibility here because the vendor has allowed us to help with the final design of the software and we can suggest changes to the wording in most places.Even then, if there is a problem we need to be able to tell them what it is using their own terminology.
The challenge we face is in choosing which language to use in a certain scenario and also in teaching the employees to be ‘bilingual’. My job as a process writer is to help facilitate this. Sometimes we bend towards the customer’s needs and sometimes we insist on leaning in our direction. It is a fine line to walk.The writing I do for my job is much different than the writing I do here, but in both cases it requires careful forethought to convey ideas in a clear way.
In addition to language, there is the workplace social culture. New Hampshire is not Louisville and Louisville is not Atlanta. Our corporate offices exist in Atlanta, so they have a higher degree of formality in some respects, but our average employee is also more friendly thanks to good Southern manners. In Louisville we like to think of ourselves as the leading edge of the business because we are doing some of the most innovative work. We also have a huge workforce so we can throw a lot of labor at problems when we need to. We tend to see all problems as solve-able because we have the strength of numbers.Our local culture is that of a corporate powerhouse where we see no task that we cannot accomplish (for better or worse).
In New Hampshire we will draw many employees from the Boston area. These employees will have varying degrees of education and work experience and their own personal histories will be a variable to consider. The funniest conversation I have heard recently was between a team member from the North Shore and one of our engineers who grew up in rural Kentucky. There were so many dropped R’s and G’s that it would have made a grammar teacher blush. We have different ways of doing things. In my experience the Southerners tend to be a bit more patient (sometimes too patient) and the Northerners tend to be a bit more focused (sometimes too focused). When I am explaining things I don’t know if they care for using analogies to illustrate my points and I sometimes wish they were less inclined to talk business at during lunch.
There are certain elements of our corporate culture which we insist upon in all of our facilities. We pride ourselves on being a very safe company. Whereas our customer may have one safety standard for the guy that drives the forklift, we may have a more stringent policy. We also have our internal HR process, which includes things like pay scale, dispute resolution, chain-of-command, etc. Both of our companies are quite old and habits are hard to change.
What will be unique to this facility is the things I cannot write into a document and that our corporate office cannot codify. We can’t tell a manager how to motivate his workforce. We can’t tell a floor supervisor how to interact with their employees. We can’t predict how a local hourly employee expects to be treated.
It’s one thing to start a new company and consciously create a workplace culture from the start. It is quite another to open a new facility within the structure of a company that has existed for over 100 years and which has pre-existing facilities all over the globe. That makes everything we are doing both familiar and new. From an anthropological standpoint, the best analogy I can make is that of a colony. Once upon a time a settler in Jamestown was very much an English place. By the time of the Declaration of Independence an ‘American’ culture had begun to form. Even then though, each of the original thirteen had their own local idiosyncrasies. I suspect that eventually this new facility will be much like a colony. It will have elements, both acquired naturally and insisted upon by the corporate office, and those things which make it unique. The first year of this facility’s existence will set the tone in many of these areas and I will find it fascinating to observe.
Mike Dwyer is a freelance writer in Louisville, KY. He writes about culture, the outdoors and whatever else strikes his fancy. His personal site can be found at mikedwyerwrites.com. You can also find him on Facebook. Mike is one of several Kentucky authors featured in the book This I Believe: Kentucky.