by Örjan Sjöholm
How can you introduce a new co-worker the first day at work, so that he or she will feel welcome and become a committed team member as soon as possible?
With recent experience from two well working start-ups, last month I’ve been thinking about what I appreciate during the first week. Things like trust, being dedicated and having fun are important to keep me healthy and happy, both at work and as a person in general. I think Antonovsky‘s three parts in “Sense of coherence” sums up my feelings pretty well:
- Comprehensibility: a belief that things happen in an orderly and predictable fashion and a sense that you can understand events in your life and reasonably predict what will happen in the future.
- Manageability: a belief that you have the skills or ability, the support, the help, or the resources necessary to take care of things, and that things are manageable and within your control.
- Meaningfulness: a belief that things in life are interesting and a source of satisfaction, that things are really worth it and that there is good reason or purpose to care about what happens.
The purpose of this post is not indented to act as guide for the perfect computer setup or routines for the co-workers. This is rather some thoughts and ideas on how to turn a new co-worker into a confident, independent part of the team with a “sense of coherence” and perhaps a friend for life.
Make sure that you are prepared for taking care of the new colleague before he or she arrives. There is some stuff that might take some time to fix. It might be necessary to order things – like a new computer, cell phone, a chair or a desk. Except from the hardware, verify that all needed software licenses are ordered beforehand. Make sure that the colleague will have access to all support systems that’s not under control by the team e.g. login to the AD, management systems for time reporting and salary. It’s also important that the colleague has access to the building.
Things that are controlled by the team and easy to fix are not that important, since the new colleague will become part of the team. The key is to get rid of all impediments that takes time to fix and are not controlled by the team.
Introduction to the company
A well-presented introduction that explains the vision and core values of the company acts as a foundation for the rest of the career and will make it easier for the new colleague to strive against the same goals as the rest of the organization. Give the new colleague a short introduction to the different divisions of the company, to make him or her feel safe, independent and aware of where to turn if problems occur.
Integration with the team
Make sure that another team member team-up with the new colleague during the first stand-up meeting. They should start on a new task with low complexity together. This is a brilliant opportunity for exploring the code base, interesting design choices, code standards, how we write tests, etc.
During this phase, take care of all necessary setup needed for a developer that’s within control of the team. This could be things like access control to the versioning control, issue tracking, continuous integration server and DB. This will add transparency, and give a good overview for the new colleague of what’s needed to get up and running.
Making a push
Work together on the task and make sure that you’re making a push to a new feature branch.
I don’t think that the preparations above will cause any overhead for the company, but rather a nice way to say to welcome.
Don’t forget about soft rules and fun stuff, like routines for lunch dates and after work arrangements.
How do you think the first day should be organized for a new co-worker?
by Björn Johansson
tretton37 office in Lund, Lilla Fiskaregatan 8A, 222 22
Because it is Roy Osherove!
Purchase your tickets here
As soon as we saw that Roy Osherove, the author of The Art of Unit Testing, was looking for companies to help him host TDD courses in Sweden we immediately responded. We didn’t want to miss out on such an opportunity – to have Roy Osherove come to our office in Lund and teach TDD!
Now we can proudly announce that on September 13th, 2011, Roy Osherove will be doing a zero to 60 TDD class at tretton37′s office in Lund!
Want to start doing unit testing *for real* but your devs don’t know what they are doing? In this full 9 hour day, your developers will learn how to write readable, trustworthy and maintainable tests, that won’t hurt your project’s schedule, but actually help it.
By the end of the day we will have covered most of the subjects covered in my book, The Art of Unit Testing, with adapted tooling and examples from today (not using RhinoMocks, for example, but FakeitEasy instead).
Unfortunately, this class has been cancelled. We will try to get Roy to visit us another time soon!
About this blog
We at tretton37 believe in having a strong company culture that promotes craftsmanship, professionalism and knowledge sharing.
We want to use this blog to share what we know and give everyone insight into our thoughts.
Here is the RSS link for this blog:
- March 2015
- November 2014
- October 2014
- September 2014
- August 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- October 2013
- July 2013
- May 2013
- April 2013
- February 2013
- November 2012
- October 2012
- September 2012
- August 2012
- May 2012
- April 2012
- January 2012
- December 2011
- November 2011
- September 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- November 2010
- October 2010
- August 2010
- July 2010