I was volunteered for a committee (I think this happened while I was on vacation). The committee's task is to figure out ways to optimize the employee experience based on results from a GAP survey from last fall.
One of the items on the agenda: Figure out a way to improve new employee on-boarding.
Since I was the newest employee on the committee (everyone else had been with the university 5 years or longer), I wound up talking more than I had intended.
What interested me most about the conversation was how apparent everyone's biases are.
One area of discussion - figuring out ways to get new employees (and everyone else) the information they need to answer small questions. Especially small questions that would only be of interest to the IT department. Questions such as:
- How do I get access to our Enterprise system?
- Which group builds the online tutorials?
- Who is responsible for interface programming and what is their intake process if you need help?
We have a university-wide portal (a little tricky to find information in, but it's there).
We have a departmental web site (which is also tricky to use and appears somewhat outdated). I'm not sure whether the original intent of the site was for outside use or as only a departmental resource. I get the feeling it was originally meant for outside access.
The HR person facilitating the meeting admitted she could be used as a resource for HR-type questions. Her job is to serve as the liason between the department and the general HR department anyway.
I hate to call it a brainstorming session since the group seemed to be looking for more fully fleshed out solutions. A facilitated straight brainstorming session would have been very useful - I think we need ideas first. Nevertheless, some of the comments were quite telling.
There was more than one person who's first reaction was "let's print an employee handbook." I have a couple of employee handbooks somewhere on my bookshelf. I haven't opened them since orientation 15 months ago. I look online. The information there is more current anyway.
Throughout the meeting, I kept thinking a Wiki would be useful. These are IT folks. I know at least a couple of people around the table were familiar with them.
I hesitated to mention the Wiki as an idea. Not sure what caused me to pause there. Probably the concerns about implementation - and these folks were looking for fully formed solutions, ideally with full implementation plans to give to the managers.
Hopefully, we can get away from the knee-jerk "let's print a handbook" to solve our information woes.