Process


UX process

Designthinking is a non-linear process, which follows the product for whole development life-cycle. Each project is different and the milestones can be different. The user experience process should be impartial to complete the project successfully.

agile-uxAgile Development Methodology


Lean UX process with practical approach to the unique business requirement always show a big impact on post-launch measure. User experience design process is an iterative method. We believe in simplified real-life process than theoretic approach of classic UCD. In the process, we go through different stages repeatedly while evaluating or testing and feedback on each stage – Build-Measure-Learn loop.

 


agile-vs-waterfall
In an agile environment the phases run parallel instead of following each other. Building final wireframes are in fact defining requirement and are better than any documentation.

 

Manifesto for Agile Software Development

  • Individuals and interactions are more important than processes and tools.
  • Working software is more important than comprehensive documentation.
  • Customer collaboration is more important than contract negotiation.
  • Responding to change is more important than following a plan.

Minimum viable product (MVP)

A minimum viable product (MVP) is a product with just enough features to satisfy early customers and to provide feedback for future product development. It’s all about building the foundation on which product will be enhanced with iterative development.

Features vs product

Customers don’t care about your product or service’s features. Instead, they want to know how it will benefit them. Users create a cognitive connection between the product and the improved quality of life while using the product – they want to see the value. Many product startups try to build and sell features instead of real products, but there is no guarantee of being in business in the future unless that feature can be translated into a benefit. There might be many competitor products with the same feature and loaded with many other features.

It’s so hard to predict what and why users will like particular features. It’s really hard to design products by focus groups alone as often people don’t know what they want until you show it to them.

Building delightful solutions is a customer-centric approach to design. The software starts to become really useful when each feature complements other features in the program. The feature-creep phenomenon creates a lack of focus. The behavioral design approach creates a minimalist and focused interface. Every micro interaction adds up to how users feel about a particular product, brand, or service.

We begin each project with user research and careful evaluation based on factors like; markets, user stories, use cases, analytics, content, and functionality.

1. Specification (Discover – UX Research)

Identifying project stakeholders for each stage of development, Stakeholder Interviews, requirement gathering, data gathering – market and user through desk and field research, task analysis, user personas, user interviews, empathy, user stories, user/customer journey planning, use cases, scenarios, feature matrix – feature priorities

2. Define and Design (UX)

Ideate, research and competitive benchmarking, branding analysis, brainstorming on how to make feature works with each other in a complementary way, site mapping, information architecture, low – high fidelity prototyping, sketch > wireframes > mockup > prototype along with usability, user testing, and feedback, visual design – pixel-perfect prototype, usability analysis

3. Development (UI – Code)

Code, testing- developers do testing on their own code or functionality, implementation – designers and developers work together for code integration and optimisation

4. Testing (Quality Assurance)

QA testing – The testing team rigorously performs the QA, accessibility review, usability, and user testing activities

5. Release (Launch)

Migrate live to the domain or test server, additional maintenance, bug fixing if any, admin training

6. Evaluate (Support – Maintenance)

Additional maintenance, support, user onboarding, use analysis, future customisation, monitoring, evaluate and advance, review, customer comments, uphold best practices, maintenance schedule, web analytics, content strategy, UX metrics – qualitative and quantitative analysis