You are on page 1of 29

Early Visualization

An approach to rapid UI development

Business goals &


User needs
Finding the right balance

Business Goals & User needs

Focus mostly on turnover and saving

Leveraging features to meet user needs

Meeting in the middle

Tactical goals to incorporate


features in a product

Seamless access to the products


and services

Capture Business goals from


stake holders and prioritize them

Strategic goals to
heated competition

Improved User experience and


reduced pain points

Identify target users and their


needs. Tailor the features for
target users

address

Corporate goals to help define


the business of the company

Opportunities to save money

Ensure that the business goals


dont overarch and trumps the
user experience

Involve cross functional team while


defining goals. You dont want
Impossible goals in list

Define metrics and perform


usability testing to ensure
project is in right direction

Prioritize goals to meet time,


budget and technical limitations

Who are your


Users?
More than just age, gender and
income based classification

Representation of your target audience

Of Knowing Your Customer, up close

User research methods

Identify major user groups of


the product

Helps in making decisions on


features to retain, prioritize and
chop off

Leverage information from


stakeholders and brainstorm to
create initial Persona spec

Used to uncover gaps and new


opportunities

Contextual interviews to observe


users in natural environment to
understand behavior

Personas and User segmentation

Identify the needs and issues


of the important user groups
Discover the characteristics,
behavior, expectation and
motivation and goals of users

Try to keep the number of user


groups under 5 and prioritize the
groups

Stakeholders make informed


decisions by empathizing with
the users

Persona identification starts at the


beginning of the project

Survey existing users to


understand their needs and
behavior

Competitive
Analysis

Learning from your competition

BPI

COMPETITIVE USABILITY EVALUATIONS

Define quantifiable and clear goals


before starting

Not just copying but progressive


improvement

More than just debating

Asses if a is design better or


worse than competition

Good initial research activity and


can help define direction for
design and Development

Identify features to compare and


set a scale to rate them

Identify how the same


problem is solved by different
vendors

Identify Risks before investing by


getting insights into features

Invite Users or Usability experts


to perform set of tasks and
collect feedback on usability

Identify what works and what


does not work for competition

Build up on the features that


users are happy with on the
competitions products

Map the ratings on a radar chart


to identify the good performers
across features

Identify the competitors you want


to compare with. 2 to 3 is optimal

Identify the feature or problem to


solve or compare

Trends in Retails Banking

Mobile banking getting more cheaper

Desktop still rules the roost

Most used features

Increased
investment
and
development activity noticed in
mobile frontier in 2015

User awareness and


t acceptance of
mobile banking needs to be
pushed

New deliverable every 3 months to


cater to progressive enhancement

Tablet
penetration
too
is
increasing in the middle and older
age group.

Trends in Retails Banking

This calls for new applications and


features
to
increase
the
engagement with the bank

Millennial generation still rules the roost. However research


suggests offering more valuable features for senior group to boost
engagement

Just Out of the box

Re-Brand the TCMB


label
product
to
standards

white
EWB

Tweak T24 and TCMB to meet


EWB banking processes

Complete redesign of OTB product

Phased delivery via Multiple Sprints

Identify features by analyzing


User
Needs,
Competition's
products and Build to match
Business goals

Deliver Approach 1

Improved User experience and


reduced pain points

TCMB Delivery strategy

Delivery in a single sprint

Two
to
Three
development effort

months

of

Identify features and Build to


match Business goals Prioritize
across multiple sprints
Deliver the enhancements over
multiple sprints

Requires additional effort for


requirements gathering and
prioritization

Scope
out
features
independent apps

Time line can vary from 6 to 10


months depending on features

New deliverable every 3 months to


cater to progressive enhancement

for

TCMB

A hybrid mobile app

EVA Approach
Road to Rapid Prototyping

User Study

Classification

Information provided by
business and marketing team

the

Issues faced by the users

Of the marketing team, IT, business

Issues highlighted by the IT team


and customer support

List for prioritizing


developing prototype

and

for

THE UX DEVELOPMENT PROCESS

26

The STEPS
Prototype
Convert the users description of the solution into mock-ups, factoring in user experience
standards and best practices.

Review
Share the prototype with users and evaluate whether it meets their needs and expectations.

Refine
Based on feedback, identify areas that need to be refined or further defined and clarified.

27

1. Define USER Stories


As A <Type Of User>, I Want <Some Goal> So That <Some Reason>.

Story: Account Holder withdraws cash

As an Account Holder
I want to withdraw cash from an ATM
So that I can get money when the bank
is closed

Scenario 1: Account has sufficient funds


Given the account balance is \$100
And the card is valid
And the machine contains enough money
When the Account Holder requests \$20
Then the ATM should dispense \$20
And the account balance should be \$80
And the card should be returned
28

1. Define USER Stories


As A <Type Of User>, I Want <Some Goal> So That <Some Reason>.

29

2. Define Features
Which main features do you want to expose your users to? List two to
three pieces of core functionality that you will include in the lowfidelity prototype.

The point of rapid prototyping is to showcase how something will work or, in later stages, what the design
will look like, without prototyping the entire product.

A good rule of thumb is to focus on the 20% of the functionality that will be
used 80% of the time.
30

2. DEFINE THE METHOD: HOW WILL YOU


SHOW IT?

31

Low FIDELITY Prototypes

32

Medium Fidelity

33

High Fidelity

34

3. Execute: On Paper

35

4. Evaluation & Review

1. Identify KEY benefits identified by the new feature or change. It


can be an improved usability, Increased competitiveness.
2. Comparative analysis of the multiple solutions to the same
problem
3. Measure emotional reactions of the users on the solution. The
reactions can range from Happy, Bored, Frustrated, Angry.

36

NEXT STEPS

1. Wireframe
Wire framing is an important step in any screen design process. It
primarily allows you to define the information hierarchy of your
design, making it easier for you to plan the layout according to
how you want your user to process the information.
2. Visual design
3. UI Development

37

Agile Iterations

38

You might also like