Working tech support will tell you what real users are having trouble with and sometime they have really great ideas for features.
402 karma · joined January 22, 2019
Working tech support will tell you what real users are having trouble with and sometime they have really great ideas for features.
Tell your users to call or email of they have questions or problems. Then personally speak with them.
You will find loads of valuable things you can do for them or find significant pain points to address.
As for sorting signal and noise, you have to find generic solutions if possible. Example: if you have any kind of reports or tables etc you will have people asking you to add, remove, rearrange them. Users will get very upset that their "really important" field isn't available. And you could add this field but then the next person will come along. So give them some options to add, remove, rearrange fields so they can get what they need without coming to you first.
What we really need is basic computer literacy since most jobs will use software to accomplish things. Coding skills may help people work with the expert systems they will use at work.
Of course not. It's boilerplate CEO speak. It's a way of "answering" the question without making any commitments and seems to terminate any further discussion.
Joe Rogan and Sam Harris discuss this on Joe Rogans podcast #1241
Making the presenter bring everything needed to have a distraction free conversation is a feature, not a bug.
We were close to finalizing a sale for a huge company before some non-technical exec insisted on using Oracle for the backend. Then it became a huge sticking point. Our cto joked that he must be getting a kickback.