“We need business analyst to define the process, at the same
time we need usability person to help him out in smooth user experience”, so
why can’t we have both in one? What is the problem with that apart from big human
ego coming to picture, UX guys saying “why take the headache of getting into
business”, BA’s saying “Boss not my expertise”.
Strange but if you analyze this both have many similarities
in their tasks which they are doing and there is just a thin line of difference
which both can forgo and come ahead. Being an UX person myself, I have interacted
with many product teams and decision makers to understand the in-depth requirement
of the product/app, and many a times I do interact with BA’s and mostly I get
fully equipped with domain and the entire process, which is essential for
usability person to have. Now comes to documentation and process flow
definition which is also one of the step in UCD and we do that. So point has
come wherein Usability Analysts or consultants can take up or can say
automatically converted to Business Analyst, is this overstatement? Some may feel debatable, probably for larger
programs, it may be a tough ask for UX to fit in the role of BA, but for medium
size programs, they can surely put on the shoes of BA.
Now the point is can a BA do a vise versa. Hmmm difficult to
answer that but over a period of time I think it is better for business analyst
to have knowledge of usability jargons, its methodologies, processes, even
though they know all these, but sometimes ignorance or tight schedule keeps
them away from usability.
I am keen to explore on my role as Business analyst as well
as excel in UX as I always try to do.
No comments:
Post a Comment