The IT Journey

A guide to traveling some of the main paths taken to reach IT success.
Travel faster. Avoid wrong turns. Make new mistakes!
Sharing technology details and practices for the journey every IT professional makes to find success.

 

Learn More

Paths to the IT Journey Destinations

(and what to do when you’ve arrived)

Maintain a stable and secure IT infrastructure

Destination:  Reliable and consistent IT resources availability

”Maintain a stable and secure IT infrastructure’ is the destination most stakeholders clearly understand. Building the short, conversational statement that summarizes what you do?  This should be the start of any statement. 

Here’s an example:

Bob, work force consultant:  “So what would you say …. you do here?”

You:  “I maintain stable and secure IT infrastructure by <fill in whatever it is that you do here>”

Learn More

Create an IT infrastructure that pays for itself

Destination:  An IT infrastructure that offsets through increased productivity and reduced risk more expense than IT services cost

Being clear about how the IT infrastructure pays for itself.  the most horrifying task an IT professional must do.   

Name the main reason to develop something or buy and put something new in place.  That is easy.  The main reason, as well as the whys and benefits, is obvious (at least to the IT professional).  How to pay for it . . . well, that requires some thought.

The most frequent reason that a technology caught our eye?  It is cool.   IT professionals would NEVER say that out loud, except, perhaps, to each other.  Mature IT people will deny this, but that feeling still gently nudges them. 

Our eyes go out of focus when we talk about it.  We talk about how it would take care of ‘X’ – ‘X’ being the frustrating problem of the moment.  We scour the internet and forums for more information about it.  We watch YouTube demonstrations of it, some of which aren’t even in a language we speak. 

But there you are:  the money has to come from somewhere. 

.

Learn More 

Build using what others have done

Destination:  Lower cost for new and improved IT services that implement faster with less disruption

Technology must advance and change to make a difference in an organization’s performance. Software becomes easier to use. Hardware becomes faster. Incorporating those advances raises productivity. The challenge is how to build the changes into the IT services structure.

I have experienced a frequent and expensive strategy. It is a nasty and widespread tendency to disregard using what others have done. This is especially noticeable in new IT team members.

Why propose replacing rather than modifying what is already in place? The dominant reason given: replacing it is faster. The truth behind proposing replacement most often comes from technological bias rather than speed. Almost always the complete replacement is not quicker or cheaper. The organizational impact cost wrought by the technology flip can be much higher.

Learn More

Make changes small and quick

Destination: Steady increase in overall productivity supported by IT with less disruption from change

American spiritual leader John Maxwell posited a development concept.  He said you should ‘fail early, fail often, but always fail forward’.  I would add ‘fail cheaply’.  Silicon Valley companies embraced this with gusto.  Software or infrastructure systems, doing smaller increments is great cost containment.  It can also avoid the lessons born of catastrophe.

The Agile concept of a Minimum Viable Product embraces getting changes in place.  Those changes at least do something.  In software development, Scrum amplifies the intended quick movement to something visible and viable. 

‘What small changes can I make that may accumulate to a spectacular outcome?’ Asking yourself this question is tough.  Not a lot of visible glory in it. So how do we get from the today state to this destination?  How can we claim what the organization needs quicker, more precisely and at the lowest cost?

Learn More

Communicate What IT is Doing

Destination: Increased satisfaction with IT efforts through better understanding

Lack of communication can be the great punisher of IT professionals. We can include ‘not involving others’ as a variant. When looking for scapegoats, or an area to cut expense, IT is one of the easiest places to go.

When something goes wrong with IT services, a frequent question is ‘what are they doing?’

Sometimes that is the question even when nothing has gone wrong with IT services. Technology has some inherent mystery in it. In the blame shifting game, the mystery makes IT a convenient target. The thought is ‘I guess its possible that what you did just disappeared‘. And it is possible – but not likely.

The question ‘what are they doing?’ is a good and legitimate one. The challenge is how to make the question less frequent and less charged. Meeting the challenge requires communicating well both reactively and proactively. The risk in that is much less than the alternative of communicating solely on demand.

Learn More

Follow mission with IT investments

Destination: IT changes with the most impact for the investment by improving what brings the most value to an organization’s customers

An organization’s mission drives the organization’s investment in IT.  Or at least it should.   You had better know what the mission is.

Amounts spent on IT are investments.  IT pay, hardware outlays, and software costs are expenditures.  Its no different than spending for inventory, buildings, labor and staff, and marketing.   

All organizations need basic IT services.  The basic services enable:

  • taking and fulfilling orders,
  • invoicing and collecting from customers, and
  • paying employees, suppliers and government entitles. 

The IT infrastructure that enables those services must be stable and secure.  Beyond the basic, where do organizations direct their IT investments?  The next level IT purpose:  move an organization from good outcomes to great performance.

Learn More

 

 

Recent Post

Cheap-Fast-Good for Doable Requirements

 

Probably every IT person collecting new project requirements has at least said this in their head.  The three alternatives contain a basic truth about balancing resources.  There is a way to use the relationship to set better requirements.  The best kind of requirements:  requirements that get you the resources you need to satisfy them.

Read How

 

The results:

  1. I get what I need on the front end for successful completion

  2. I enjoy acceptance on completion.”

Contact

Want to investigate how to make the most of your IT journey?

Contact