I don't think any role will ever be perfect. It's great you work with great people and are rewarded for your work.
On your point regarding user perspective, I'm not sure whether you mean A) validation that the features delivered succeeded in achieving their goal or b) you would like to understand the tangible benefits to the user of the features being proposed before you develop them.
If it's A) there are some great analytics tools out there. I'll be happy to let you know what I use if you'd like.
If it's B), a first step might be to suggest that requirements are written in the form of User Stories, if they're not already, so that developers can understand what value a proposed feature will bring to a user, instead of "feature must do X thing". Beyond that, it's probably a matter of making suggestions to amend the processes, if processes exist, so that developers are more involved in understanding the business and not simply writing code. If no formal processes exist and you would like a bit more structure, why not be the person to float the proposal? ;)
Because you mentioned lacking user perspective, I was more thinking along the lines of validating that value has been delivered to user post-delivery, via heatmaps/analytics/A-B testing and things like that.
I wish you luck with advising on the processes. It can be a rewarding experience - particularly if people start seeing faster deliveries and better deliverables.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for reading :)
I don't think any role will ever be perfect. It's great you work with great people and are rewarded for your work.
On your point regarding user perspective, I'm not sure whether you mean A) validation that the features delivered succeeded in achieving their goal or b) you would like to understand the tangible benefits to the user of the features being proposed before you develop them.
If it's A) there are some great analytics tools out there. I'll be happy to let you know what I use if you'd like.
If it's B), a first step might be to suggest that requirements are written in the form of User Stories, if they're not already, so that developers can understand what value a proposed feature will bring to a user, instead of "feature must do X thing". Beyond that, it's probably a matter of making suggestions to amend the processes, if processes exist, so that developers are more involved in understanding the business and not simply writing code. If no formal processes exist and you would like a bit more structure, why not be the person to float the proposal? ;)
Because you mentioned lacking user perspective, I was more thinking along the lines of validating that value has been delivered to user post-delivery, via heatmaps/analytics/A-B testing and things like that.
I wish you luck with advising on the processes. It can be a rewarding experience - particularly if people start seeing faster deliveries and better deliverables.