The role of Business Analyst in designing UI/UX prototypes

''What is the role of business analyst in designing UI (User Interface) /UX (user experience) prototypes?' This was an interesting question asked of me to answer by a student. After responding, I thought of writing a detailed blog on this topic to cover many aspects of UI/UX design, as it is one of the most interesting but least visited topics. 

Most of the time, UI and UX are used interchangeably, however, they represent different areas. Let’s take a few minutes to understand and differentiate between them. 

User Interface (UI): User interface design focuses on better interaction with solutions and the design may focus on the placement of menu, look, and feel of the page. 

The goal of user interface design is to make the user's interaction as simple and efficient as possible, in terms of accomplishing user goals (user-centered design). Good user interface design facilitates finishing the task at hand without drawing unnecessary attention to itself. 

User Experience (UX): UX focuses on optimization of a software solution in terms of users' experiences and their feelings associated while interacting with the solution or product. It is human-computer interaction in a useful and meaningful way. For example, effortless identifying of the menus, flexible font size, usage of white space to declutter the website (and readers' minds), or using a familiar color (logo color) to enhance the product ownership. 

UI/UX Design Life Cycle.

User Need: This is an initial activity when need is identified. Business Analyst will understand the user problem or an opportunity. For that, business analyst will refer current state and other relevant documents to understand the current design and related issues and the focus area for proposed solutions.

Elicitation: There are no specific standards available for preparing the UI / UX designs. However, the business analyst can use standards that are specific to the project, their comfort level, and consideration of the internal and external usability standards that may be applicable. The requirements are split into requirements (descriptive text) and model/design (descriptive pictures/models). These are mentioned in IIBA's BABOK Guide version 3 You can use the same standards or customize as needed. 

Business analysts can elicit these requirements through design or models in collaboration with stakeholders and users. The business analyst can provide the details in the form of: 

Requirements: Functionality, features, and data needed in designing UI/UX Design. In addition, the user inputs these and validations needed for the same are also elicited. 

Organization policies and standards (internal and external): Internal policies will include the organization’s standards or policies for creating the UI and usability standards; for example, using colors, fonts, placement of items such as logos and menus, and so on. It will also include menu style, pagination, and navigation across sub-pages. While the external standards will include the standards specified by web browser (Safari 9.1.3 or Internet Explorer 10.0 etc...) operating system (Windows, Mac etc...), external agencies to whom you are sending or receiving feeds, and other requirements... These details need to be part of the requirement and provided to the designer for preparing the prototypes/wireframes. The design style will include menu style, pagination, and navigation across sub-pages. You can use a template/excel sheet to describe the details (for example: first name, input box, size, position) and provide them the basic design in MS Visio.

UI/UX Approach

Design/Prototype Approvals: Once the designs are prepared, the business analyst can use these designs/prototypes and the supporting materials (such as the excel sheet that was provided to technical person to create the prototypes) as a requirement to complete a mock-up and communicate them to the stakeholders. The stakeholders will review both the design and the supporting documents, and provide their feedback to improve, if needed. Once the changes are made and the designs are presented, they are required to verify and validate before starting the approval process. These designs and supporting documents become your verified and validated requirements for UI/UX.

At the end, the stakeholder preference will overrule all other standards in defining the UI/UX design. For example, do stakeholders prefer to follow industry standards such number of clicks for a functionality or detailed functionality, standard placement of menu over customized menu, and more.

User Acceptance (Validation): Ensure that all the windows are prepared and connected; i.e., the flow of the requirement screen by screen using all the flows mentioned in the FRD (basic flow, alternate flow, and exceptions). Some business analysts are creating this type of wireframe. But it is an option, as they can get these completed by the technical person.

Deliver: These approved designs are delivered along with supporting requirements to the technical team to develop. Once the development is completed, they are tested and deployed.

Enrich and Enhance: Once the solution settles in user community (production environment, website, or product delivery/acceptance) with no new bugs or issues reported, the enrichment and enhancement will begin as needed. UI/UX is most dynamic interface in comparison  to other part in solution architecture.  

Principles of UI/UX Design:

UI/UX design principle

Consumer apps can be trendy and catchy to appeal to the customers and business analyst can expect fewer formalities or standards used in these types of apps.

Summary: The UI/UX designs depend on the types of app or solution and stakeholders or user preference.

The designs are presented, reviewed, and confirmed before they enter into the development phase.