Methodology

  1. Business Analysis

    Interviewing key stakeholders and outlining business requirements, including but not limited to, business goals, business objectives, expected outcome, and target audience.

  2. Requirements Workshop

    Collaborative method for fleshing out the project brief. Made by conducting exercises and discussing the project brief with key stakeholders.

  3. Competitive Analysis

    Helps understand the features that are present in competitor products. This is often a good way of understanding users’ expectations and needs.

  4. Context Research

    Involves going out and observing users in the real world. Particularly valuable when multiple channels are involved (offline, online, and more).

  5. Content Modeling

    Description of the activities users perform in order to reach their goals. They help us understand how our product can fit into users’ lives. Typically gathered after a round of usability testing alongside additional user research.

  6. User Journeys

    Ensure that users’ tasks are streamlined and easy to accomplish. Useful when designing the flow of our product. How can we structure our product to ensure key journeys are smooth?

  7. Information Architecture

    Defines the product’s underlying structure. Structures include context consistent naming, grouping, and navigation. Typical IA deliverables are content plans, process flows, and site maps.

  8. Sketching, Wireframes, and Prototypes

    Generating and iterating design ideas in multiple screen sizes before they go into production. To get designs and interactions reviewed, tested, and refined

  9. Usability Testing

    Testing with real users is the best way to find out if our designs work. Conducting a user test will reveal insights we could never have guessed, and suggest improvements that will make our product stand out. Usability testing is easy and need not be expensive, especially if we use light-touch “guerilla” approaches.