How to Talk to I.T.

Slowly, with lots of TLAs (three letter acronyms).

The key to talking with IT is to first understand a bit about computers.  Now think through what you you're trying to achieve:

  • What do you want vs what do you need?  The business side typically has a lot of things it's looking for.  What is absolutely necessary for the system to be of value? What would be nice to have?  What is a bit ridiculous to ask for, but might be useful?
  • Separate out the doing from the simple decision-making and the judgment calls.  This will help guide the discussion on complexity and flexibility.
  • Prioritize, prioritize, prioritize.  If everything is a priority, nothing is a priority.  Remember that the more a system is asked to do, the more complex and therefore more fragile, costly, and time-consuming it is.
  • Don't pre-suppose the solution. You may be sure that the solution to your phone problem is to go with a shiny new VOIP (voice over internet protocol, or just internet phone), but are you a telephony expert current on all the latest developments?  Do what you do best, which is to know and articulate your business needs.  Let the tech experts do what they do best: use the appropriate technology to solve technology-appropriate problems.  If you don't have the necessary skill set in-house, either develop it or look for outside resources.

I'm a big fan of obtaining the basic system first and only then adding in the nice-to-have bells and whistles.  This accomplishes a couple of things: it speeds the delivery of the required functionality and allows for the users to get experience with the system and maybe realize some requirements that nobody had thought of before the final development/implementation work is performed.

One final thought, when talking to a salesperson or IT leader:  if they can't explain the computer system and the benefits and ramifications of the options available so that it's understandable to a non-techie, they don't really understand the technology.  It's part of the educational reality that you don't really know something until you've had to teach it.  If one person can't help you understand, find someone who can.

If you have any questions about this article or effective IT communications, or would like to talk about how to get the most for your IT dollar, contact me at  617-855-5439 or jmarcos@complexityclarified.com.

To view or add a comment, sign in

More articles by John Marcos

  • Agile: Revolution or Evolution?

    Agile represents a change for traditional development shops, but is it a revolution or an evolution? While Agile feels…

    8 Comments
  • Mastering Risk: How to Use Risk in Strategic Decision-Making

    Here's the easy part: risk is everywhere - even a decision to not take any risks is risky. Now the hard part: how to…

  • Finding a Great (Banking) Relationship

    Part I: Treasury Services. Treasury is simple, right? It's the mechanics of money in and money out, and it all…

    1 Comment
  • Computers: the Good, the Bad & the Ugly

    Computers can do amazing things, but in fact, they're only good at a few things. Of course, the things that they're…

  • NPV and DCF and WACC, Oh My!

    Net Present Value explained. Which would you prefer someone to give you: one dollar today or a dollar a year from now?…

    1 Comment
  • The Process Engineering Hammer

    Process is a wonderful thing. In moderation.

    5 Comments

Explore content categories