Friday, March 17, 2017

Handoff Like a Team

Do you have handoffs in your company?  A handoff is when one group transitions work-in-progress to another.  For example, your awesome sales department has signed a specific contract or scope of work with a client, and now it is time for the project execution personnel to deliver.  Or Engineering has designed a terrific product and now Manufacturing has to produce it.  Perhaps a diligent pre-construction group has procured all materials and prepared a construction site for the build crew to begin work.  Whatever the situation, handoffs occur all the time, and ensuring they happen smoothly for the whole team is critical for business success.


Having established that most companies have handoffs in one form or another, let’s consider the very simple flow diagram below:

Figure 1: Basic Order Fulfillment Process
Represented here is a basic Order Fulfillment Process of many companies.  Design may be swapped out for preparation, and sometimes is combined with execution, but the steps will still be applicable.  In a small company, the same person may be doing one or more steps, but for AJC clients, these basic steps have generally been divided into different departments.  The trick is, how to ensure that the knowledge learned in each step is effectively handed off to the next?  Especially when one group may have incentives to merely “throw [the work] over the fence,” as is often said when complaining about how ineffective handoffs can be.  Wouldn’t it be better if groups handed off like a true team?

Here are three steps for ensuring effective, team-oriented handoffs.  Note that the assumption here is that the basic process has been defined at a high level.  Since this is how to ensure robust handoffs from one group to another, the processes to list are the ones handled by each department.  Inter-departmental steps are better described via Process Maps.
1.   Define the information required for each departmental step of the process to be effective.  One tool that can be used is a SIPOC.  SIPOC stands for Supplier, Inputs, Process, Outputs, Customer and can be used for one or more processes and to varying levels of detail.  Remember that a SIPOC may have internal suppliers and customers as well as external!  The example below shows one step, but rows may be added for subsequent steps.


Figure 2: Example SIPOC for a Sales Step

2.   Ensure alignment across all departments on the requirements at each stage, and who is responsible to provide each.  This can mean getting alignment on the SIPOC.  During this step, emphasize teamwork –overall business success depends on all groups acting as one team.
3.   Utilize standard tools and processes to transfer information.  Document applicable tools and processes/procedures and store them in a designated storage area with universal access like a Document Management System.  Ensure that all team members are trained on procedures and tool use; get buy-in from everyone.
a.   Examples of tools that help with handoffs: Checklists, Forms (with only useful information, see previous article “What’s in a Form”), holding handoff or “kick-off” meetings with standard agendas, and schedule templates.

The most important thing to remember is that relevant information needs to flow from one group to the next accurately, thoroughly, and right the first time.  Any gaps with these items likely will result in rework or an extended duration to complete each step and begin on the subsequent one, not to mention people getting disgruntled with each other.

Finally, I would urge everyone who is involved in handoffs to be patient with each other.  As one of my valued clients likes to say, no one comes into work intending to do a terrible job and undermine their co-workers.  Sometimes things may seem that way, but with a little respect and consideration, nipping these concerns in the bud with timely face-to-face discussions can really go a long way.  Be willing to work with each other, agree on what is needed and what will be done. Follow through on the needs of the downstream team, and to hold upstream teams accountable for what they promised to deliver.  Ask questions when you are unsure, and communicate the answers to the wider team because if one person has a question, chances are someone else could also benefit from the answer. After all, most people want what is best for the customer and the company, and everyone truly is on the same team.

Read this article and more on AJC’s blog, and sign up for our newsletter online at: http://andreajonesconsulting.com/blog.aspx




Wednesday, March 8, 2017

The Tuckman Model: Forming Storming Norming and Performing are Normal

After the "Storming"

As a consultant, I often find myself in the position of working with new teams.  In general, I love this aspect of my chosen profession.  Meeting new people, learning new things, hearing new perspectives, and being in a position of service to help others achieve their fullest potential; all these are positive aspects about working with teams.
There are definitely some drawbacks to constantly forming new teams, however, and that is where today’s topic comes into play.  The Tuckman Model, coined by psychologist Bruce Tuckman in his 1965 article entitled “Developmental Sequence in Small Groups” describes “forming, storming, norming, and performing,” as a typical path that most teams follow as they work together.   As would be expected, the “Storming” part of team interaction is not always sunshine and rainbows. *Reference: https://www.mindtools.com/pages/article/newLDR_86.htm  
However, rather than eschew or deny the natural progression of the Tuckman Model, it is quite helpful to embrace it.  Merely knowing that it is NORMAL to “Storm” at some point helps to give perspective and provide assurances that we are just like everyone else.  This awareness can alleviate some of the emotional response which inevitably follows the “Storming” phase, and offers the light at the end of the tunnel that the “Norming” phase is coming soon!
A few more considerations for each stage, based on personal experience.  “Forming” a team is often an exciting time, where people are happy to get to know each other, and everything is fun and new.  Then as reality sets in, often accompanied by ambiguity and feelings of being overwhelmed, the “Storming” ensues.  The speed of this transition seems to depend on the frequency of interactions.  If your team interacts less frequently, it often will take longer to hit “Storming.” 
Last year I began working with a new client on a particular project and things seemed to be going great for several weeks.  We were only meeting once per week, though, and it became obvious around the 6-week mark that some team members were not performing the responsibilities we agreed they would perform given their role as described in our Charter.  Storms ensued!  Another time, I was working with a project team more than full-time on a two week fixed duration project.  We started storming around Day 3 when personality conflicts arose and a few too many “cooks” appeared in the kitchen.
In both cases, however, the teams moved into Norming, again at different times.  In the case where the team was meeting weekly, we actually had to re-evaluate the goals of the project as well as the roles and responsibilities, and unfortunately that project was shelved in favor of another one that benefited from the team’s better understanding of each other’s personalities and strengths before beginning.  In the two-week blitz project, we divided task ownership and moved on within 2 days to leave a full week of truly productive work (norming to performing!) before finishing. 
In Norming, teams are productive and work together to deliver results, but there may still be some hiccups in knowing who is most proficient at what, and who to ask for certain types of help.  However, if your team ever gets into Performing, it feels like a well-oiled machine; I recall one project team that definitely experienced all phases, but the project endured long enough to get to the point where we could count on each other for specific types of help or results, and it felt like we were just knocking balls out of the park every day! 
Sadly, a final drawback of a Consultant’s life is that consulting engagements often end before the team really hits its stride in Performing.  However, AJC hopes to leave teams poised to move into this phase internally, and hopefully there will be opportunities for future engagements with many of the same team members.  This does not eliminate going through the Tuckman Model stages all together, but definitely helps increase the pace from Forming to Norming and sets us up for achievement of the coveted stage of Performing!
Read this article and more on AJC’s blog, and sign up for our newsletter online at: http://andreajonesconsulting.com/blog.aspx