9 ms·
In my past experience building internal tools, the customer (colleagues) is one major source of feature requests. It rarely ends well. From their perspective, f
by a_c 3y ago
In my past experience building internal tools, the customer (colleagues) is one major source of feature requests. It rarely ends well. From their perspective, feature requests never get addressed. What was built is rarely what they perceived most helpful. What seemed most helpful was a forever moving target, there are always next most important thing to have.
Without internal tool building, people bend their workflow to suit the tools, have second tier support if any, the tool has no empathy on your particular business context, close to or no involvement on roadmap. But hey, at least less complaint from the people, I mean the colleague
- boxed 3y agoI build internal tools and I regularly build things that, while not what they asked for, the users are glad to get in the end since it was a car and not a faster horse. My biggest problem has always been that users are used to software being "Stone Tablets from the Mountain" and so instinctively work around the tool instead of just asking me to fix it. Which is reasonable mostly since almost all the software they (and me!) have ever used is very much like this. This isn't only a discussion about software though, but about government. The citizens don't even report problems because they assume they will be ignored. So the government stops listening because there is nothing to listen to. Round and round it goes.