Commentary

Amy DeCarlo
 

Priorities Out Of Order

The beginning of a new year is a perfect time for businesses to assess their objectives and define which projects should take precedence in the coming 12 months. Unfortunately, all too often, IT professionals complain that corporate technology priorities are out of order. In the Systems Management Pipeline poll conducted over several weeks in December, only 18 percent of the respondents said their companies have the right IT projects properly prioritized in their 2006 budget.
The beginning of a new year is a perfect time for businesses to assess their objectives and define which projects should take precedence in the coming 12 months. Unfortunately, all too often, IT professionals complain that corporate technology priorities are out of order. In the Systems Management Pipeline poll conducted over several weeks in December, only 18 percent of the respondents said their companies have the right IT projects properly prioritized in their 2006 budget.More than one-third of the Systems Management Pipeline readers who responded to the poll said that the budgeted 2006 IT initiatives are totally out of synch with what their IT priorities should be. This indicates that as much progress as companies are making to align their IT and business teams, there are still big gaps in both groups' understanding of the other team's objectives.

Others complained less about the way their companies prioritized IT projects than how those initiatives are being funded. Forty-five percent said that while the right projects are being prioritized in 2006, there is not enough money allocated to carry them out properly. Obviously, enterprises have a ways to go before IT and business managers are on the same page. Drop me a line at larsendecarlo@yahoo.com and let me know if your business has its 2006 IT priorities in order.


More Infrastructure Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>


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