Stanley Black & Decker

A Platform for Multi-Channel Digital Strategy

WCM/CMS Platform Selection

WCM/CMS Platform Selection

Working closely with Stanley Black & Decker’s marketing and strategy departments, TBG (The Berndt Group) developed the criteria for a world-wide enterprise WCM platform selection, and then proceeded to provide the analysis and business cases for the final choice. This process involved considerable discovery and analysis of the organization’s business challenges, international business practices, and digital operations—as well as deep research into current best practices for multi-market enterprise CMS.

Black & Decker screenshot
Co-development & Training

Co-development & Training

TBG took the lead in developing expertise and development standards for Stanley Black & Decker on the new enterprise platform—working to train, mentor, and integrate digital operations around the new platform and set up development test beds.

Stanley Black & Decker plus TBG
Site Implementation

Site Implementation

TBG worked with the Stanley Black & Decker Web team to launch the site in CMS and optimize internal practices. The initial site—for a specific product line—was sleek and took advantage of the platform’s capabilities.

Black & Decker screenshot

TBG & Stanley Black & Decker

Stanley Black & Decker is an international company that is one of the world’s best known tool brands, reaching both businesses and consumers and activity in many markets around the world. With household name brands like Black & Decker, Porter Cable, DeWalt, and Bostitch, the company has a sizeable portion of the tool market and a complex set of business considerations.

Stanley chose TBG (The Berndt Group) as its partner to make the transition to greater economy, control, and capability by adopting a new enterprise WCM platform based on TBG’s longstanding leadership in WCM consulting. Working through a highly detailed, structured process, the goal was to create a best-of-breed platform that could sustain the organization’s Web operations for years to come.

In the course of the process, TBG worked with the Stanley digital team to focus understanding of requirements in various areas including:

  • short- and long-term feature set needs;
  • multi-site, multi-lingual, localization and multi-market considerations;
  • integrations and technical ecosystem considerations;
  • content and code reuse;
  • mobile and content targeting strategies;
  • operational efficiencies and governance; and
  • development roadmaps and time-to-market.
  • award ribbon iconFortune 500 Company
  • calendar iconFounded in 1843
  • trophy iconWCM Platform Selection
  • star iconCo-development & Training
Multiple Overlays of Considerations

Multiple Overlays of Considerations

Complicating the selection process were the multiple overlaying decisions of technology choices, potential skill building, and the choice of enterprise platforms—which is hardly conducive to simple “apples to apples” comparison. Sorting through these considerations is one of TBG’s strengths and this project was no different, in that we bring to bear not only knowledge of CMS best practices, but also an intimate understanding of the enterprise and mid-market CMS/WCM options, and substantial large-site developer experience. Working through a process that included requirements definition, independent research, multiple meetings with vendors, conversations with references and multiple check backs on technical points, we were able to come to a recommendation and reach consensus with Stanley on a new platform. (For reasons of client confidentiality, we unfortunately can’t name the platform). 

Process Transformation

Process Transformation

Of course, a new CMS/WCM platform is only as good as the development that can be executed on it, and TBG was engaged to work through training, development mentoring, and initial site creation with Stanley’s excellent technical team. Because the move to a full-featured CMS/WCM platform requires multiple changes in process, transformation of the whole process from front-end to back-end development needed to be addressed—the more so because of the imperatives of Responsive Web Design and multi-lingual scenarios.