3 ms·
> A business analyst thought that it would solve a session management problem and instead of asking us how to solve the problem, thought that they would prescri
by gregmac 8y ago
> A business analyst thought that it would solve a session management problem and instead of asking us how to solve the problem, thought that they would prescribe this solution to us. ... I really just wanted to call this BA an idiot and bully the problem away, it would have saved a significant amount of time and frustration for multiple parties.
I totally understand your frustration and reaction here, as I've had the same.
I've found the best way to deal with this is right away start reframing this back to a business problem, often in the form of a user story ("As a _____ user, I want to _____ so I can _____"). Keep asking "why" to refine it down to what is really trying to be accomplished. The point is to not get into an argument about a technical implementation with someone who doesn't have the knowledge to argue about it (whether they realize it or not), because it's nearly impossible to not come across as a bully.
In this situation I would almost outright dismiss the suggestion of the right-click, saying something like "Forget the right-click thing for a minute; In business terms, what is it you're trying to prevent and why?". We're both trying to solve a business (or user-facing) problem here, let's make sure we're both on the same page about that before we even begin to discuss how to do it.
I am very up front with people about my process: If you bring me a perceived solution, I'm always going to boil it back to a problem and work from there. Sometimes I -- or more often we, the dev team -- might come to the same conclusion, but I'd say the vast majority of times, in my experience, we will come up with a better implementation that takes less time to implement, has other benefits that are not part of the original objective, and/or avoids a major downside not originally thought of.
Arguing is going to make you seem like a bully; calmly reframing the discussion shows you're trying to work together.