British TVs Don’t Stop Crime
How to Prevent Big Losses on Your Compliance Project
How would you feel if you spent billions of dollars on something
that didn’t work? Detective Chief Inspector Mick Neville
knows that feeling. He’s feeling the pain right now,
as his crime fighting cameras in Britain are serving little
more purpose than to catch the interesting behavior of passersby
on tape.
The initial thought was to have them function like a bank
or convenience store security camera – thwarting off
criminal activity by their mere presence. Apparently, a secondary
goal of the cameras was to provide evidence in court so that
more rightful convictions could be realized.
According to the UK
Times Online, Mr. Neville, who is in charge of the Video
Images Identification and Detections Office ( VIIDO ) told
the Security Document World Conference that, “Billions
of pounds have been spent on kit, but no thought has gone
into how the police are going to use the images and how they
will be used in court.” Amazing statement, isn’t
it?
In another comment to the conference he states, “It’s
been an utter fiasco: only 3 per cent of crimes were solved
by CCTV [Closed Circuit Television].” According to Mr.
Neville, the crooks think the cameras are props that don’t
even work! Worse yet, when they are caught on tape, the images’
usefulness as evidence is poor. So much for the conviction
rate.
Let’s take a look at a couple of aspects of this scenario,
and try to set the stage so that you don’t end up taking
big losses on your project. Here’s three key lessons
to keep you from getting burned on your big budget project:
Lesson # 1: Make Return on Investment a Living Estimate
It’s quite alright to spend a billion or more dollars
( or pounds if you will ) on your project, but when you start
getting into those numbers, you really need to monitor your
return. It’s one thing to drop a $100K on something
that didn’t turn out – it’s a whole other
thing to be on the losing side of a $1 Billion investment
that went sour.
To prevent this, understand that your initial Return on Investment
( ROI ) is only an estimate, and probably a bad one. It has
nothing to do with your intelligence or knowledge. It’s
just a fact of progressive elaboration on any project. You
cannot possibly know what your return is going to be, until
you start discovering the reality of the product, through
your project execution.
I’ve seen countless projects setup ROI in the very beginning
to get funding, then never bother to keep it updated as the
project is being executed. This is partly due to execution
style ( see the next lesson ), and partly due to ignorance.
This mistake can be a killer. Return is more of a dependent
variable than Investment, so keeping an eye on your Return,
and updating it throughout your project will keep your ROI
a “living” estimate.
Lesson # 2: Start Realizing Your Return as Early
as Possible
How will you know your real Return, unless you actually deploy
some functionality into the real world? You cannot. That’s
why, it’s better to organize your project in an iterative
fashion that physically deploys functionality on a regular
basis. This has two extremely beneficial byproducts.
Firstly, you can be successful with the above lesson on knowing
your Return metric, and by extension your Return on Investment.
This is vital for keeping control and communicating the truth
about your project, and the product that it’s producing.
Secondly, you’re getting a Return before the project
is over! As the project is executing, you are actually receiving
the ( hopeful ) benefits of prior deployments. This is much
better than waiting until the end of the project, just to
realize that your estimates on Return were grossly inaccurate.
So, to realize your return on a compliance project, you must
be able to identify the relationship between your compliance
objectives, and the monetary benefit to your company. For
example, your compliance objective might be to reduce the
number of SOD ( Segregation of Duties ) violations in your
company. What tangible and monetary benefit will that have
on your company? What is the monetary cost to your company
of each SOD violation? These metrics should be known so that
you can appeal to the real executive issue, “What am
I getting for the money I’m spending.”
Lesson # 3: Test the Effectiveness of Your Controls
Early
Although the goal of you project should be indirectly tied
to some sort of monetary return, chances are on a compliance
project, your output metrics will be more closely tied to
reducing violations, or better yet increasing control. So
remember, a control is no good unless it’s effective.
Mr. Neville’s cameras were intended to be a preventive
control ( thwart crime before it happens ), however it seems
like there’s a secondary corrective control in place
also ( evidence for court hearings ). This alone tells me
there’s a problem with the strategy. They should be
clear on their control objectives, and they should be focusing
on the preventive control ( always the best path ).
I think they were on the right track, but the thieves are
ignoring them. This makes the control ineffective for prevention.
The correct execution would be to test these controls early.
And, if they don’t work, you either seek ways to make
them work, or find another preventive control that might work.
Trying to retool the work as a device for corrective control
is a step in the wrong direction.
Big budget projects don’t have to be scary, but you
must take some precautions to make sure you don’t get
burned like Mr. Neville and his Billion pound camera catastrophe.
Understand how your project objectives link to monetary return,
realize that return early, and adjust your ROI number often
to foster truth in project communication. Also, stick to preventive
controls as much as possible, and test their effectiveness
early and often. It’s never too late to start. If you’re
on a big budget project, and you’re worried about the
outcome, make a quick diversion to deploy something functional
as soon as possible. Then test the effectiveness of your controls,
and your ROI. The results may surprise you.
Better to be surprised now, than $1 Billion from now.
|