User Experience Design

Thats me

- Entrepreneur, Programmer, Product Designer, YouTuber and Salesman

 

-  Fullstack developer (Android, Java, Spring, Angular, React,  IoT and Blockchain)

 

- Startup Founder

What do you think ?

UXD - why, what, where and how ?

Lets Use

your understandings, conceptions and thinking

Laptop Renting App

  1. Create user profile
  2. User Login
  3. Showing laptop list
  4. Online payment system
  5. Filters on the basis of price range, brand and user reviews
  6. Book a laptop
  7. Register a issue for laptop
  8. etc

Training Institute Management

  1. Branch manager login
  2. statistics  for most selling courses, course of the months
  3. statistics for total revenue collection, remaining fees
  4. Candidate search
  5. Displaying full resume of candidate
  6. Course and Fee information for particular candidate
  7. etc

Agile Product Development

User Stories,planning, daily scrums, Review and retrospection

journey : Backlog to Design

  • Business Analyst
  • User Experience Designer
  • User Interface Designer
  • Programmer
  • Quality Analyst
  • SEO People
  • Product Owner
  • Product User
  • Sales Person

What UX is exactly ?

it is about user

User Experience

User (mostly) is human and experience is feeling or emotion.

And There is no DEFINITION ..

It is the process of enhancing user satisfaction by improving the usability, accessibility, and pleaseure provided in the interaction between user and product

The Elements of User Experience” book written by Jesse James Garrett

UX Elements

Worst food ever

  • Blame to cook
  • Blame hotel management staff
  • Blame to water
  • etc

I DON'T know, how to send

  • I must literate myself about this feature 
  • I might have made mistake
  • Where to find that ?

Our products are human too

make positive emotional connection

User Centric Design

  • A philosophy of product development
  • Product is not end 
  • Product is a means towards the end of providing good experience for user
  • methods that emphasize on people rather than technology  

User Experience

  • How product behaves and used in real world
  • Beyond the product to its context in people's lives
  • Incorporates diverse range of factors 

Surface

Skeleton

Structure

Scope

Stratergy

Communication Gap

  • Developers doesn't understand design terms
  • Designers doesn't bother about technical terminologies
  • Different people have different approaches to looking towards product
  • Web as a information source
  • Web as application 

Basic Duality

STRATEGY Plane

  • User Needs, what product must do for people who use it
  • Product Objectives, what product must for the people who build it

User Needs

  • Fundamentally user needs product that work,  they can use, meet their expectations 
  • Most are specific to your users and your product

User Research

  • Best way to discover user needs
  • There are many techniques like surveys, interviews, in person meetings, environment analysis, show them sketches etc

User segmentation

  • Dont say my product is for everyone, Identify user needs more manageable 
  • Break your audience down into segments based on shared characteristics 

Personas

  • Characteristics  sketches based on user research 
  • Extrapolate general set of characteristics to specific case 

Product Objectives

  • Often formed in the business terms business goal, drivers and requirements
  • Should be specific to product
  • Independent of your organizations other activities

Success Metrics

  • What difference your product has made ?
  • Closely tied to your product objectives

Scope plane

  • Functional Specifications, application features that product must include, product as functionality
  • Content Requirements, content element product must have, product as information.

Functional Specification

  • What application features will fulfill user needs ? 
  • Focus on what it does, not how it works , and what it does not do ? 
  • Be specific, don't dictate the system design

Content Requirement

  • What information use
  • What form should it take ?
  • Where will it come from ?
  • Who is responsible ?
  • Define element according the purpose.

Keeping Documentation

  • Docs are waste of time
    • No one reads them
    • they are never up to date
    • they are too much trouble to maintain
  • Time spent on planning is directly proportional to productivity 
  • Integrate documentation in to the process, instead of making it separate step

Structure plane

  • Interaction Design, how user moves from one step in a process to next step. 
  • Information Architecture, how user moves from one content element to next.

Interaction Design

  • Actions the user can take with the system
  • Actions the system can take it in response to user

Information Architecture

  • Defines conceptual relations between content element 
  • Reflects the way user thinks about subject matter
  • Often hierarchical, but necessary not

Top down vs Bottom Up

  • Top down starts with categories and puts content into them
  • Bottom up start with content and builds categories

Documenting Structure

  • Visual representations tends to work best
  • Diagrams can be simple or complex as you need

SKeleton Plane

  • Information Design, facilitates understanding of system
  • Interface Design, facilitates user input and system output
  • Navigation Design, facilitates movement through product

Information Design

  • How can we present this information so that people can understand and use it?
  • Communicate relative importance of different pieces of information
  • Guide the user from one piece to the next
  • Draw attention to important details
  • Communicate relationships between elements

Interface Design

  • Provides a means for users to interact with application functionality

Navigation Design

  • Communicates choices available to user
  • Facilitates the movement
  • Different designs have different effects

WireFrames

  • Brings all skeleton issues together into one highlevel sketch
  • Illustrates relative priorities of page elements
  • Suggests the page layout approaches

Surface Plane

  • Visual Design, Look and feel
  • Usually this part is web design or App Design
  • Its more than aesthetics 

Nine Pillars 

User Research

  • Foundation of user centered design
  • Informs all strategic decisions
  • Primary responsibility for identifying user needs
  • Roles
    • User Researcher
    • Usability Analyst

Site Strategy

  • Primarily responsible for defining product objectives
  • Decides priorities and success metrics
  • Roles
    • Business Analyst
    • Product Manager
    • Executive Producer

Technology Strategy

  • Primarily responsible for functional specification
  • Decides technical platform and standards to adopt
  • Roles
    • Senior Engineer
    • Development Manager
    • Technical Lead

Content Strategy

  • Primarily responsible for content requirement
  • Decides appropriate format and subject matter
  • Roles
    • Content Strategist 
    • Content Editor
    • Editor in Chief

Abstract Design

  • Turns strategy into design concepts 
  • Responsible for structure plane
  • Sometimes responsible for scope and skeleton plane 
  • Roles
    • Information Architect
    • Interaction Designer
    • UI Specialist 

Technology Implementation

  • Tactical execution of technology strategy
  • May incorporates many roles
  • Sometimes responsible from coding to interaction to testing
  • Roles
    • Software Engineer
    • HTML Developer
    • QA Tester

Content Production

  • Tactical execution of content strategy
  • Gathering, editing, producing  and deploying content (not just text)
  • Roles
    • Content Producer
    • Writer 
    • Editor

Concrete Design

  • Tactical realization of abstract design
  • Always responsible of surface plane 
  • Sometimes responsible for Skeleton and Structure plane
  • Roles
    • Interface Designer
    • Visual Designer 

Project Management

  • Binds together all tactical competencies 
  • Often neglected in smaller organizations
  • Roles
    • Producer 
    • Project Manager

UX audit

app and web app

Templates

Adapt and Improvise

References

Material Design

Design Language for web and mobile

Lets Build

REDESIGN and Build new

GymApp

  1. Finding nearby Gyms
  2. Gym listing with ratings
  3. User reviews
  4. Gym features and information
  5. Enrollment process
  6. Workout and Diet Plans
  7. Instructor profile
  8. Daily schedule  

BAnk admin dashboard

  1. Login to system
  2. Total deposits, withdrawals. Differentiate by cash, cheque, NEFT, RTGS and UPI
  3. Searching account holders
  4. Account holder profile
  5. Tracing transaction activities
  6. Transaction data pattern in bar chart format

UXD Case studies

Takeaway

Analysis of last 4 case studies

ActiveSG App

  1. Double Diamond
  2. User interviews

Bicycle Renting

  1. User analysis
  2. brainstorming and lateral thinking
  3. What, where, when, why, how, who 

One fit

  1. Focused on pain points
  2. User Interviews
  3. Surveys

Fintick

  1. Double diamond
  2. User Interviews
  3. Surveys

UX Design

By Aniruddha Avinash Kudalkar