How to survive your next security tech project

A look at organizational best practices for avoiding common mistakes in technology deployments


One of the most important reasons to manage scheduling as described above is so that you don’t mislead management. Keeping management accurately informed of project status will keep them on your side and allow requests for additional resources to be an understandable outcome of the project situation, rather than a surprise brought about by project leader lack of competence.

Important Lesson #2:  Project status must be provable by inspection or demonstration to be 100 percent up to requirements

It’s not done, if it’s only 90 percent done. Progress payment must be tied to provable 100 percent complete milestone accomplishments.

Payment milestones are a key control mechanism for large projects. Don’t pay 90 percent of a progress payment and expect the 10 percent retained to be a motivational factor. If you do, you will find out the hard way that the real motivation will be to complete the next project milestone to get the next milestone check. The small check (10 percent held back on a previous milestone payment) just won’t matter as much.

You can’t complete the project by accepting partial work.

Important Lesson #3:  To get out ahead of potential problems requires active project risk management as a key customer role

Most contractors and project team members don’t ever envision themselves as sources of risk—they almost always view risk as an external factor. They look at things like as technology defects, backordered products, customer task delays, bad weather, and so on.

For this and a number of other reasons the customer must assume the full responsibility for project risk management. Even though the customer is not the source of most problems that can arise, the customer can identify the areas of project risk and actively manage the risk factors, including those that are not within the scope of the installing service provider. The bottom line is this: if you don’t manage project risks, you can easily lose control of the project.

This is why a risk officer (or whatever name you use) must be included on the project team, and this individual must not be the project leader or manager.

Approaching Projects Effectively

An effective approach to technology projects takes into account the aforementioned factors and many more. Such key project success factors are identified in the Security Tech Project Survival Test.

Use this checklist to rate your current or upcoming project. If your current project does not rate well, then now is the time to take corrective action. The longer corrective action is delayed, the bigger the risk of project cost and schedule overrun will be.

This Project Survival Checklist is based upon an in-depth study of deployment projects involving today's complex physical security system technologies and documented IT best practices.

Using the Security Tech Project Survival Checklist is easy:

  1. Start by selecting answers for the 36 checklist questions.
  2. Select the project size and complexity factors that apply to your project.
  3. Press the Calculate My Score button to obtain the Survival Test results.
  4. Review the Score Rating and related comments.

About the AuthorRay Bernard, PSP, CHS-III is the principal consultant for Ray Bernard Consulting Services (RBCS), a firm that provides security consulting services for public and private facilities. For more information about Ray Bernard and RBCS go to www.go-rbcs.com or call 949-831-6788. Mr. Bernard is also a member of the Content Expert Faculty of the Security Executive Council. Follow Ray on Twitter: @RayBernardRBCS.