Don't confuse technology with a solution

Just for fun, I am attempting to post while on the rail - Amtrak that is.

It's a familiar refrain, once you get into the business world far enough.  The business needs a solution, but the IT team delivers a technology that doesn't match.  Or reversing the blame, the business asks for a technology (and IT delivers), but that technology doesn't actually "solve" the problems the business confronts.

The June 2008 Communications of the ACM has a teaser of a longer article on the topic, Give Me Information Not Technology by Arik Ragowsky, Paul S. Licker and David Gefen.

Don't confuse technology with business solutions, focusing instead on what users value most - information.

Interesting what they are saying here.  I'll have to pay attention to their upcoming case study that suggests other differences between what IT does and what the business needs.

1 Comment(s)


This is really interesting. In my experience I often see a rush to solution before a problem is properly understood or documented. I know, this sounds an awful lot like "requirements".

Personally I also think a lot of problem solving sessions fall prey to group think. That is, not enough time is spent to ensure that they really understand the problem being addressed. Instead the first proposed solution is jumped on and run with.


Leave a comment

Previous entry: The contemplated action contains the seed of its result

Next entry: Blogging for keeping track of stuff

Picture a steaming coffee cup. Better yet, grab one and have a read!

KJolt Memberships

Follow jackvinson on Twitter

View Jack Vinson's profile on LinkedIn