I think this is a phenomenal idea. The last project I worked on was designed to look good in a demo or on mocks but not really to be usable.
I was constantly asking our designers and PMs to try using our product as a user might. I'd write up little scenarios that I knew our users struggled with and invite people to try them out with our product.
Sadly, I found it impossible to persuade anybody to design for anything except what looks good on a presentation of UX mocks.
I begged to job shadow the future users of my software at my last job and I was told there not enough time.We are all too busy. Keep your head down. Do what you're told.
But I'll be able to understand their job better and what the software really needs to do to make than more efficient and productive. They'll appreciate that and be more likely to buy in and adapt to the product they'll be using.
That's not your job. Your job is to implement the features you're told to implement.
But the users saw those features and said that is not what they asked for.
So? Why do you care if the project fails? It's not on you if it fails. Just do what the BA's said to do.
Boss, they aren't translating the business needs correctly. We have to rebuild features 2 or 3 or 4 times. Is we could see what they do and talk to them it'd only take once. That's happened a couple times during user acceptance. They said that's not what what we asked for. I said what did you ask for? I coded it right there on the spot and they signed off on the user story.
Go back to work. I'm busy. This isn't a productive conversation.
I was constantly asking our designers and PMs to try using our product as a user might. I'd write up little scenarios that I knew our users struggled with and invite people to try them out with our product.
Sadly, I found it impossible to persuade anybody to design for anything except what looks good on a presentation of UX mocks.