You are only as good as what you know, and half of what you know comes from books Truth be told, it's not an original thought - I heard it many years ago, but it rang true for me personally. I still have many of my old college textbooks - engineering volumes bound in impressive faux leather, including a massive, near-mint copy of the CRC Handbook of Chemistry and Physics - 60th edition (note: collectors, make me an offer!). Over the years,…
Previously: Timing The new year approaches, and most IT groups aspire to start out with a completed IT Budget, derived from a well thought out set of short-term Objectives, that align with an IT Strategy - that itself aligns with the overall Corporate Strategy. If your timing is a bit off, and you haven't established these connections with the process yet - where do we begin? In my last post, I talked about Timing: get in the conversation early, take…
In some companies, IT struggles to find a voice amid the other functional areas of the business - Finance, Operations, Sales and Marketing, even Human Resources. "Business Alignment", a regular item on lists of Top 5 IT Concerns each year, pops up because (I believe) it's difficult to glibly draw a line connecting IT systems and projects to the changing priorities of most organizations. I will admit to a small amount of cynicism here - part of the problem is…
Ok, maybe I'm stretching the meaning there, but that's a cool sounding title, and what I see as an interesting phenomenon. People get excited about Large Numbers, and think they have meaning and importance simply because they are Large Numbers. Big Errors For example - years ago, when an application manager was whirling around the office in a minor uproar, worrying that that someone accidentally keyed in a $1B line item on an invoice. That's $1,000,000,000,000 - for the Unit…
Some IT departments prefer chargebacks, while others do not. My own preference is to allocate IT costs to the business units, based on some reasonable balance of simplicity and accuracy. General services could be allocated by headcount, COGs, or revenues, with each business unit taking their proportional share. Some easily identifiable items might be allocated more directly - maintenance costs for specialized engineering, warehouse management, or financial systems, for example, could be allocated more directly to those departments. I've written…
All projects should have a clear objective, a practical plan, and an understanding of the costs and benefits to get the thing done. Easy to say, but a lot of project teams struggle to crisply and clearly define specific business benefits. One way to move the process forward would be to have a clear understanding of the types of business benefits you might claim. Hard benefits come from firm commitments to make measurable differences in the amount of revenue generated…
When someone asks my opinion on their writing, I'll get fairly detailed; I've noted in the past that there is a lot of power and influence in the written word, and it's fairly important to get it done well, or your project proposals just never seem to get off the ground. This particular proposal suffered from a lack of direction; it didn't take the reader (the decision maker) through a clear progression. Admittedly, the subject matter was a bit technical and…
As the new year approaches, debates over the "value" of IT and business projects intensify; it's not holiday stress, but the excitement of the approaching New [fiscal] Year. Lately, I'm hearing more about the struggle to quantify business value, especially when selecting those few projects that will "make the cut". We will definitely iterate on our scoring framework, adding a cost / benefit template to facilitate more apples-to-apples comparisons between projects (yes, don't scoff - it is possible - more…