Meridian

During stakeholder discussions product managers, marketing leads, dev leads, and the design team will join to discuss and gain insights into:

• The company's vision for the product
• What our users want
• What our technical and resource limitations are
• The milestones and features we must implement for the product's first release

App Layout & Design System

Layout: We conducted a reverse card sorting test to understand where our users will look for a feature. With this we decided on what is the best layout for our app.

Design System: For the design system I setup a style guide and defined all the UI components we needed or will need and established guidelines for the UX, interactions and visual design for other designers and developers to follow.

ITERATIVE PROTOTYPES

Images

Design Sprints

The next task is to break down the features we finalized for Meridian into sub features and assign them to design sprints. In a design sprint I:

• Identify all the use cases for the feature.
• Create wireframes, prototypes, task/user flows and iterate and test them with the team until we capture all cases and achieve the right experience.
• Create the final mockups for QA verifications and Dev reference.
• Write the detailed specifications which are handed over to the dev team to write the technical specification.

Development

The UX Designer - I walk the team through a feature, clarify doubts, resolve any UX problems they come across and ensure the feature is built as per the specification.

A Front-End Developer - I created reusable UI components using Angular 8 and write code and unit tests for functionality that doesn't require heavy logic.

Additionally, I was also responsible for creating the custom CSS framework for Meridian and ensuring that CSS written in Meridian is clean, maintainable, adheres to our style guide and can be reused in our sub products.

Analyze

Usability testing is very important in making sure our product is relevant and useful to the user. At Meridian we test our features by:

• Conducting usability testing on a focus group after milestones are completed.
• Track features using tools such as Indicative to examine how features perform after they are released to production.
• We closely follow support channels for feedback from users.

If our analysis indicates users are having trouble with a feature or any area of the application, we will prioritize it based on our metrics to calculate its priority and assign it to an iteration where we will decide how we can solve the problem.

Pre-Flight

• Walking the marketing and sales team through the work we have done and provide information they can use for any initiatives they might want to take.
• Collaborate with support to review support articles to make sure the users can find the help they need.
• Work with support to add trigger points within the app to help customers reach support when needed.

Post Release

• Meridian successfully replaced the former Meridian Beta app after a few months since its release and after we migrated all our users to Meridian.
• Meridian Beta although had lesser features than the Later Version, had higher sign ups and conversions from existing client since its release.
• Customers found the application extremely easy to use and had very few cases where they needed to reach customer support.