.................................CONTACT US..|.SITE INDEX.| SEARCH:  
 
4SIGHT    

Content on this page requires a newer version of Adobe Flash Player.

Get Adobe Flash player

 

Wednesday, June 12, 2013

Leveraging "Teach"nology: Improving DC Productivity through Personnel Observation & Coaching

By: Brian Ehlenberg

As a supply chain systems implementation professional, I know the value of applying the right technology to increase efficiency.  However, I also know how common it is for companies to overlook or under-utilize their workforce in the quest to make their operations more productive. Given how pervasive technology is throughout supply chain operations, we sometimes forget that people are often the source of untapped savings. We tend to forget that taking the time to improve our people, leveraging our “teach”nology, can create significant gains with little capital expenditure.

Recently, one of my clients in the foodservice business reaped strong rewards with a “low-tech, high-teach” initiative. Faced with an underperforming distribution center, the client brought in a new DC management team, giving them a clear mandate for improvement and an 18-month timeline for accomplishing it.

The new management team immediately installed an observation and coaching program whereby the supervisors conducted two coaching observations, and a follow-up interview, every day with each associate.  By the 18-month deadline, with no changes to the DC processes, material handling, information technology or layout, the facility achieved a 40% productivity improvement. The only change implemented by the new management was a regimen of disciplined and regular observation, coaching and follow-up. As a result, the operation rose from the bottom of the DC network productivity scale to the top five. With their gains solidified, management was able to reduce the coaching sessions to one per day while maintaining their improved productivity.

What does it take to implement an observation and coaching program that “sticks”?

The first key is for your coaching supervisor to take the time to fully understand the “best practice” for the process being reviewed. It’s important for the coach to observe the process on the floor, in the associate’s work environment, preferably during peak activity.  Flow charts and whiteboards don’t cut it for truly understanding the process. As important, all work should be observed for at least a complete cycle.  If the cycle times are short, it’s helpful to observe multiple cycles.

Along with truly understanding the process, the coach must be able to effectively communicate deviations from best practice in a positive manner. The best way to accomplish this communication is through a review session off the floor, immediately following the observation. This session should be conducted privately in a quiet setting with no distractions. Done properly, the review should take no more than 15 minutes. For optimal results, the coach should begin by pointing out one or two positive behaviors he/she witnessed during the observation. Next the coach can point out any gaps in the process best-practice, along with any suggestions for improvements. Finally, the associate should be given the opportunity to provide feedback and make recommendations for any process or environment changes that may help him/her improve performance. Be sure to provide the associate with a copy of the feedback report for future reference.

Without question a properly executed observation and coaching program requires a significant investment of time, but this commitment will pay off in associate and DC performance improvements.  And as a side benefit, you will likely see more effective communication – and a stronger working relationship - between your associates and supervisors.

Labels: DC productivity, supply chain systems management

posted by 4SIGHT Supply Chain Group at 3:02 PM 16 Comments

What’s Next for SaaS and On-Premise TMS Providers

By: John Blanchard, Vice President of Transportation

SaaS TMS solutions have reached the point of sustainable viability in recent years.  In fact, an argument could be made that sales of SaaS solutions have been propping up the Transportation Management System market in general. As we support our clients in the evaluation and selection of TMS solutions, we no longer see strong bias against SaaS solutions. Rather, it is increasingly common to hear things like “we don’t really have a preference” or “we just want the best TMS for our business”. The application delivery model has now become secondary to features, functions and value. To gauge the impact of SaaS technology, consider the efforts and investment of the Tier 1, traditionally on-premise TMS vendors to provide SaaS options for their customers.

When it comes to a SaaS deployment, the “pure” SaaS players enjoy an architectural head start over the traditional on-premise vendors that designed their solutions to be primarily single tenant. While it could be argued that, for some industries and functional requirements, the legacy on-premise solutions have advantages in breadth and depth of functionality, which gap is easier the close: technology or functionality? In my opinion, it’s the functionality gap.
As hardware and internet bandwidth become more powerful, inexpensive and ubiquitous, functionality like complex optimization is no longer as difficult for SaaS vendors to support.  These vendors are focused on closing the functionality/flexibility gap and are steadily broadening and deepening their offerings.  There are no inherent limitations to their ability to develop and implement deeper functionality. The most daunting challenge the SaaS providers face is maintaining the multi-tenant, single instance concept that underlies the collaborative potential of their solutions.
Traditionally on-premise solutions, on the other hand, face challenges when it comes to developing true SaaS solutions.  In many cases their solution architecture was originally developed without consideration for SaaS needs.  This often means that the core code and database is not optimized for true SaaS performance and relies heavily on local processing and large, dedicated hardware stacks.  Revamping the fundamental data structures, communication protocols, APIs and other key components is an additional hurdle that pure SaaS vendors do not have to clear.
The great news for the TMS buyer is that this fervent competition of ideas will ultimately result in solutions that combine the best of both worlds, providing real options and strategic flexibility.

Labels: SaaS TMS, TMS SaaS, transportation management system

posted by 4SIGHT Supply Chain Group at 2:51 PM 9 Comments

Previous Posts

  • Leveraging "Teach"nology: Improving DC Productivit...
  • What’s Next for SaaS and On-Premise TMS Providers
  • Parcel Manifesting: To Pre or Not To Pre?
  • Taking Control of Inbound Transportation: Change Y...
  • 5 Ways to Improve Order Picking Productivity
  • What Do All Successful Labor Management System Imp...
  • WMS in the Cloud: Is it Ready for Prime Time? – Pa...
  • Voice Enabled Technology Has Proven It's Value
  • An Overview of Supply Chain Software Evaluation
  • Buiding Relationships and Streamling Inventory Man...

Archives

  • October 2009
  • December 2009
  • March 2010
  • April 2010
  • March 2011
  • February 2012
  • March 2013
  • April 2013
  • June 2013

Subscribe to
Posts [Atom]