As a developer you hear and witness several different things from users. One thing I've learned over the past 20 years is you must have patience, especially with certain users.
It's amazing how many users are convinced that if something looks different or something "seems" to be missing on their screen that they assume something has changed in the code. One of the comments I get a lot is, "you guys must have changed something in the code."
Well, when you're the only developer at a company you know when something has changed or not changed. I try to explain to these users that "no, nothing has been changed in that program, we haven't made any changes to that in almost 6 months". Then I get responses like, "well I over heard you guys talking about a username being misspelled, and maybe that's what's causing this." My response, "No, that had nothing to do with the program you're in and that was on our test system anyway."
Most of the time in these situations you just have to be patient and let them believe what they're going to believe. When the above example happens it's usually caused by them not having rights to certain features, but they try and convince me they've had the ability to do the feature 5 days ago.
"Hmmmmm, that's funny because when I look at the code it would be impossible for you to have that feature." But again, they're convinced something has changed. Anyhow, you give them the rights, and they "do" have the feature visible to them now.
It's amazing how many users are convinced that if something looks different or something "seems" to be missing on their screen that they assume something has changed in the code. One of the comments I get a lot is, "you guys must have changed something in the code."
Well, when you're the only developer at a company you know when something has changed or not changed. I try to explain to these users that "no, nothing has been changed in that program, we haven't made any changes to that in almost 6 months". Then I get responses like, "well I over heard you guys talking about a username being misspelled, and maybe that's what's causing this." My response, "No, that had nothing to do with the program you're in and that was on our test system anyway."
Most of the time in these situations you just have to be patient and let them believe what they're going to believe. When the above example happens it's usually caused by them not having rights to certain features, but they try and convince me they've had the ability to do the feature 5 days ago.
"Hmmmmm, that's funny because when I look at the code it would be impossible for you to have that feature." But again, they're convinced something has changed. Anyhow, you give them the rights, and they "do" have the feature visible to them now.
Comments
Post a Comment