The FT Word
The FT Word is a free monthly newsletter with support management
tips. To subscribe, send
us email with your email address. The subscription list is
absolutely confidential; we never sell, rent, or give information about our
subscribers. Here's a sample.
Welcome
Welcome to the July edition of the FT Works Newsletter, a
monthly review of trends in the support management arena.In this month's issue:
· ROI -
beyond the snow job for the CFO: creating ROI analyses to determine the
payoff of CRM investments
· Using
your knowledge base as a low-cost training tool
And a reminder that you have a month left (until 8/31/01) to take advantage of
the special $100 price for the new The Complete Guide to Hiring Great
Support Managers". This offer is valid for newsletter subscribers only.
Details at the end of this issue.
ROI - Beyond the snow job for the CFO
I'm somewhat of a skeptic when it comes to ROI (return on
investment) analyses, since many of the ones I've seen have only tenuous
links with reality and seem to be designed with the narrow goal of getting a
specific purchase approved. In fact, a properly done ROI analysis is a great
tool to determine whether a particular project is worthwhile. So let's see
how you can do you can analyze the purchase of a new CRM tool.
The logic behind ROI analyses is to compare the cost of an investment against
the benefits it will bring to the company. The trick is to corral *all* the
costs on the one hand and to assess reasonable benefits on the other. Let's
start with costs. You need to add up:
1) the cost of the software itself (the CFO won't let you forget
that one!)
2) the cost of maintenance and upgrades (you know how important
they are)
3) the cost of the hardware required to run the tool (it could
be zero in the long run if you can reuse machines, but you will want to start
with parallel installations for a while. Be sure to check whether individual
workstations will need upgrading; even adding a little RAM can cost a bunch
if you're outfitting hundreds)
4) the cost of any auxiliary software required (database
software, reporting software)
5) the cost of maintenance and upgrades for the hardware and
extra software
6) the direct implementation costs (out-of-pocket costs paid to
the vendor or a third party). This in itself would deserve a full issue of
the newsletter. Suffices to say that you should always expect to exceed the
quote you have, especially for a long project. Try to get price guarantees
(good luck!) and plan for 10-20% more than the initial quote. Some of my
colleagues cynically suggest doubling the quote, but you should be able to do
much better with good project management.
7) the indirect implementation costs (costs that you will incur
internally). This item is usually neglected, perhaps because it's hard to
figure out. The reality is that internal costs can rival and exceed direct
costs. Think about who will need to work on the project (project manager,
SMEs, testers, etc.) and estimate how much time they will spend on it.
8) training costs, both direct and indirect
Depressed? Hang in there, here comes the best part: benefits.
Include
1) the expected decrease in case volume. It can be a significant
figure if you are supporting low-complexity products and you are installing a
self-service system. In a high-complexity environment, don't get carried
away: a 10% decrease would be great!
2) expected increases in productivity : will the support reps be
able to resolve cases faster with the tool? How much faster? It's often
helpful to segment the cases into easy/medium/complex since new tools
typically don't have much of an impact on complex cases but could make a big
difference for the easier ones. Also think of segmenting electronic cases
versus phone cases. Analyze cases handled by different groups separately. A
finer analysis of the different phases in the life of a case may be required,
for instance to determine savings in the routing phase, or the impact of
being able to deliver status reports through self-service. In any event, your
savings will be contingent on your costs, most of which are people-based and
therefore will match the complexity of the software. Do not use
"standard" costs you can find in overall studies as they are
unlikely to match yours.
3) reduced training requirements: if the current tool is
particularly onerous, or if the knowledge base will replace existing
training, you may find savings here.
4) increased employee satisfaction resulting in reduced
turnover: this one's dicey, but I would allow it if you are currently
experiencing turnover because of poor tools.
5) increased revenue: it's usually very difficult to translate
increased customer satisfaction into revenue (and even harder to sell the
results to an inquisitive CFO) but you should capture obvious benefits such
as being able to check entitlement easily and therefore be able to deny
customers that have not paid for the service, or track service packs better.
If you wish to go further, investigate "avoiding doom" scenarios:
if you ever lost a customer because of a tool failure, that may be the only
justification you need!
Now that you have a full list, it's time to honestly spread out
both the costs (most are upfront) and the benefits (which could come much
later) over time. Despite what the vendors say, very short ROIs (investment
recouped within a few months) are very rare, especially if you support
complex products. So feel free to tinker with the ROI analysis to make it fit
a reasonable time frame, but should feel very proud if you can get to a
ROIs on the order of a year are quite respectable. Yes, everyone tinkers with
ROIs until they fit a reasonable time frame, but
Using your knowledge base as a low-cost training tool
Training can be costly, especially if you have a small group
and/or cannot train more than a handful of people at a time. Here's a
low-cost, high impact idea that can work in all settings, either as the
training solution of choice or as an adjunct to other delivery
mechanisms.
Simply create a training plan, listing the various training activities
required from reading documents, hands-on experimentation, self-paced
training courses, listening to tapes, etc. Suggest appropriate sequencing and
time frames for each task. Place the training plan in your knowledge base. If
your knowledge base system allows, have the training plan point directly to
any knowledge base documents it refers to.
Then, point your staff to the training plan. It's a great way to
demonstrate the value of the knowledge base to newbies or doubters.
FT Works News
SupportWeek published an article about electronic software
delivery entitled The New ESD: FTP grows up on 7/10/01. You can find the text at
http://www.supportgate.com/supportweek/20010710/article2.html
The Service and Support Professionals Association will publish a Common
Sense booklet I wrote on the same topic, Electronic Software
Distribution Management An idea whose time has come this
summer.
A reminder that The Complete Guide to Hiring Great Support
Managers is still offered to newsletter readers (only) for the special
introductory price of $100 through 8/31/01. 40 pages of no-nonsense tips
and 566 pre-tested questions from which to conduct thorough and pointed
interviews. Great for all of you who recruit for support managers and
executives, and perhaps as a job-hunting tool too! Special introductory
pricing of . For more information, including how to order, go
here.
I'm working on a second guide, this time focused on hiring
support reps and support engineers. It should be ready next month.
Curious about something? Send me
your suggestions for topics and your name will appear in future
newsletters.
regards,
Francoise Tourniaire
FT Works
650 559 9826
Subscription Information
To request, modify, or cancel a subscription, please
drop us a note. The
mailing list is confidential and is never shared with anyone, for any reason.
You may
reproduce items in this newsletter as long as you clearly display this entire
copyright notice. Contact us if you have questions about republications.
Back to Newsletter Archive
Home |
About
Us |
Case
Studies |
Clients |
Training |
Tools |
Newsletters |
Contact
Us
© FT Works 2006. Unauthorized
reproduction prohibited.