How much rigor does any decision really need? One clue might be to look at the number of significant digits you will be presenting. Say you are asked to present the cost impact of IT systems on a major acquisition or merger. Based on the context of the conversation - the macro-financials, the pay-back models, and the YOY growth plan for the next five years, you will probably be delivering a single slide that shows $20M in cost and/or benefits…
What can be disrupted? How real is this threat / promise? It's not a deflection tactic - it's more about opening your eyes to the possibilities, and getting focus on the priorities.
A collection of Project Steering Committee discussions from the past, illustrating a few common methods and patterns for PMs. The lessons learned here are applicable to many types of projects (and certainly not limited to technology efforts!)
A simple tactic for fighting the ever-growing list of legacy applications, spreadsheets, reports, customizations, and processes that no one knows how to maintain, but nobody seems to want to get rid of (aka Technical Debt).
I'll tell you about this visualization from a recent internal conversation, but I may end up aggravating some career IT people out there. Yes, I have massively oversimplified things - but I'm trying to develop a broader understanding, and I think it's a good first step. The original question was "How do I manage IT?", but it quickly morphed into "how can I drive / derive value from IT?" (note the powerful difference that a single letter makes - derive sounds sustainable)…
At technology conferences, vendor seminars, and user group, I enjoy the networking conversations - professionals looking to leverage each others' background, experience, and relationships, ostensibly to forward their own careers, but openly trying to solve a problem with a win-win for both sides of the connection. Inevitably, however, the conversations refine and regress down to a common theme - the classic oversimplification "change is hard". Much of the time, I'd wager that change in your organization is comparatively easy -…
Cut to the chase! An effective style of communication is to "run to the bad news"; for time-starved stakeholders, this approach works by focusing the attention on the critical few decision points and issues.
Interesting line of conversation around an internal Help Desk project ... "What exactly is the point of my help desk ticketing system?", posits the hardy IT Tech. "I, like so many other IT technicians, am expected to solve end-user problems quickly with my infinite knowledge of every potential PC / software combination, not to mention a dizzying array of specialty printers, alternative input devices, smartphones, and tablets. And I, like so many other IT technicians, realize that the most capable,…
It's not enough to capture Lessons Learned at the end of your projects; build in a process step to review Learnings from the past, to start new projects off right.
Cloud and open source have been around for some time - long enough for the term "cloud" to [finally] fade away as a differentiator (it's just assumed!). Still, some continue to dismiss these technologies for their corporate solutions - but it's getting tougher to just ignore this stuff ... Scale? Cloud provider Amazon continues to dominate the market, with five times the market share of all of their competitors combined. The breadth, depth, and scale of some of their customers…