The power of a pilot group: Before you deploy that shiny new technology, put your office geek to work

February 24, 2013 |
Sasha Reed

Last week we discussed the importance of taking a step back to fully understand your processes prior to making productivity improvements. Just as critical to the process—and perhaps more critical to your success—is the pilot group. Who better to put new software or hardware to the test than your in-house office geek, the internal tinkerer who is forever offering up suggestions of what you can do to work better, faster and more efficiently? You know who I’m talking about… every office has one!

Many times in our haste to get straight to the promised land of results, we skip over the ever-important stop to testing-land. Testing software in a small, controlled environment is not only a necessary part of the process but a critical step that ensures you don’t create more work for everyone down the road.

When putting a pilot group together, be sure to clearly define your objectives and desired results. Just as important, allow flexibility within your timeline to achieve those results. Often when one puts technology to the test, unexpected things come up. Knowing this is the case, build in time for your team to do some rework along the way. If you give your pilot group breathing room to figure it all out, your entire team will benefit down the road. 

Seemingly simple processes may be put to the test as your pilot group comes to a consensus on best practices—and frankly, no detail is too small. Details like standardizing naming conventions for files and file folders help streamline your workflow by taking the guesswork out of accessing project documentation. Also, be prepared to document, document, document. It’s important to know what works and what doesn’t so that higher-level stake holders can clearly see what guided your path to success. Likewise, a clearly documented path will aid training efforts downstream.

Too many times I’ve seen decision makers skip over the critical step of a pilot process in their zeal to realize the return on their investment. And, in the end, they miss the mark on their objectives, lose valuable time in failed attempts to implement change and dampen morale in the process. Lesson learned? If you build the pilot process into your implementation timeline, allow your office tinkerers to do what they do best and provide clear objectives for desired results, you will not only see the effects on your bottom line but also stronger employee buy-in.  And that, my friends, may be the best ROI of all.

Sasha Reed | Digital COM
Bluebeam, Inc.
Vice President of Strategic Development

As Vice President of Strategic Development at Bluebeam, Inc., Sasha Reed collaborates with leaders in the architecture, engineering and construction industry to guide Bluebeam’s technology, partnerships and long-term goals. She joined Bluebeam in 2007 and co-created the Concierge Approach, a distinctly branded process of customer engagement, product feedback and solution delivery to which much of Bluebeam’s success is attributed, and which today is replicated at every organizational level.

Sasha is known industry-wide as a “conversation facilitator,” creating platforms for exchanges necessary to digitally advance the industry, including the BD+C Magazine Digital COM Blog, which she authors and manages. She’s been a featured presenter at numerous national and international conferences, including the 2014 Design-Build Institute of America (DBIA), Federal Project Delivery Symposium and NTI Danish BIM Conference. Sasha also co-chairs the Construction PDF Coalition, a grassroots effort to provide a common industry framework from which to create and maintain construction PDF documents, serves on the City College of San Francisco BIM Industry Council, and is Advisor to the Board of Direction for the National Institute of Building Sciences BuildingSMART Alliance.

Related Blogs

March 15, 2017 | Digital COM

Who is succeeding, and on what terms? And what will it take for everyone to experience the benefits of that...

October 04, 2016 | Building Team | Digital COM

As the construction industry bounces back from the Great Recession, an entirely new class of tech-savvy con...

July 11, 2016 | Building Team | Digital COM

The lead up to AECX featured a discussion providing insight into the current state of the AEC technological...

June 23, 2016 | Digital COM

Two truths from the jobsite: 1) The best part about uncovering a problem is discovering its solution, and 2...

June 09, 2016 | AEC Tech | Digital COM

Rather than fighting to control the proliferation of apps, perhaps we should be training our eyes to look f...

December 17, 2015 | BIM and Information Technology | Digital COM

Sascha Vesterlund, a VDC Specialist, Design Processer with MT Højgaard, and Nathan Wood, Innovation at DPR...

November 25, 2015 | BIM and Information Technology | Digital COM

I recently sat down with two Architects-Turned-VDC-Process-Managers to discuss the ways in which they are l...

Is the PDF revolution advancing BIM workflows?

From left to right: Sasha Reed, V.P. Strategic Development at Bluebeam Software, Nathan Wood of DPR Construction, and Kris Lengieza, Director of VDC at Stiles Construction.

November 12, 2015 | BIM and Information Technology | Digital COM

Many project teams who struggle to get everyone up to speed with BIM, find PDFs a useful tool to bridge the...

Microsoft’s Surface Pro 3 – designed with the AEC industry in mind

Microsoft explains how they made the impossible, possible in building the Surface Pro 3 with Bluebeam Revu in their keynote presentation here:

October 07, 2015 | BIM and Information Technology | Digital COM

Sasha Reed sits down with Microsoft’s Senior Director of Programs, Pete Kyriacou to discuss the unique chal...

Add new comment

Your Information
Your Comment

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Overlay Init