Commentary

Amy DeCarlo
 

Money Matters

Recently, I was talking to a network manager who had survived a terrible VoIP implementation, if just barely. The deployed system failed to scale, and as a result, the mortgage company he worked for suffered through numerous outages, poor voice quality, and a lack of functionality on even the best day. The implementation was such a disaster, the network manager abandoned the incumbent VoIP solution and installed another, far more scalable and proven IP telephony system which had been his initial first choice. So why didn't he go with his first choice initially, and avoid months of pain for his organization? Money, of course.

Recently, I was talking to a network manager who had survived a terrible VoIP implementation, if just barely. The deployed system failed to scale, and as a result, the mortgage company he worked for suffered through numerous outages, poor voice quality, and a lack of functionality on even the best day. The implementation was such a disaster, the network manager abandoned the incumbent VoIP solution and installed another, far more scalable and proven IP telephony system which had been his initial first choice.

So why didn't he go with his first choice initially, and avoid months of pain for his organization? Money, of course.The IT manager was struggling with the same budget constraints everyone deals with, and so he opted for a cheaper solution, and in his case, got exactly what he paid for, unfortunately. Money makes many IT decisions, and too many of those are regrettable.


More Infrastructure Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Other IT managers often pay a premium, and also are unhappy. The product may work just fine, but the price cuts too deeply into the IT spending budget and doesn't yield enough benefits over the long term to justify the expense. But as long as customers are willing to pay the price, all the grumbling in the world will do nothing to change the vendors pricing policies.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links