4 ms·
I work in professional services for a large IT vendor (and before that I worked for a place that used that vendor’s products) and I can tell you we spend a huge
by freehunter 6y ago
I work in professional services for a large IT vendor (and before that I worked for a place that used that vendor’s products) and I can tell you we spend a huge amount of time working with our customers to help them fit their workflow to our tools. Because there is no way we can engineer our tools to fit or enable every workflow.
Some companies have the skill and desire to build their own tools over our products so they can use their pre-existing workflows, but inevitably the abstractions start to leak and they almost always end up hiring us to train them on how to use the tool the way it was meant to be used.
- luckydata 6y agoSure but how much you gotta change is the difference between a successful implementation and a failure. Good tools are already close to what people do.
- wtetzner 6y ago> Good tools are already close to what people do. I’m not sure I agree. I think good tools represent the problem space well, and provide powerful ways of manipulating/interacting with it. That may or may not be what people are already doing. I’d say solving a problem well is orthogonal to what people are actually doing.
- trentnix 6y agoI'm living that now a little bit. New tools and processes are discussed and evaluated based on how easily they can be customized, perverted, and eventually bastardized. More frequently than you could imagine, people and organizations jump to how they are going to implement something before they define what they want to implement. And when the effort fails, the technology is blamed and they start all over again.
- Aeolun 6y agoA lot of organisations make the mistake that they think they can fix a garbage process with more technology. They end up finding that garbage in = garbage out