Gathering a set of expectations requirements is an important part of making sure that the products we build and design are the right fit for our clients.
Before any design or development starts, we meet with clients to get a good understanding of what they envision for their product.
Needs gathering involves going beyond the features that will be part of the final product. In addition, the team develops a set of desired goals and outcomes for all users interacting with the product that is built.
Based on the information gathering, the team identifies different user roles, workflows, and potential pain points by building out a set of User Experience Personas.
A team of designers and developers spend a week determining the viability and design direction of the potential product by conducting a META+LAB Stunt.
This process is based on the format first included as part of the Google Ventures Sprint, which sets aside specific segments of the creation process to be completed each day within one week.
Over the course of the week, the team members identify all potential features (Map), work individually on different design directions (Sketch), identify and prioritize key features for initial release (Decide), build a functional prototype that demonstrates the general features and workflow (Prototype), and demonstrate the proposed product to the client (Demo).
At this point, if the team decides that the project is viable given the resources available, a project proposal is written up and presented to the client.
The interdisciplinary development teams at META+LAB use a process that is based on the Agile Scrum methodology.
Development is split into week-long sprints, which begin with a planning session to determine the tasks that will be competed by the end of the week.
At the end of every sprint, there is a review that culminates with a deliverable product that can be demonstrated to the client.
These incremental updates allow the client to interact and give feedback throughout the process, while also allowing the team members to review and provide each other feedback based on the completed work.
Together, this gives our teams the opportunity to make appropriate adjustments along the way and grants our clients with a regular set of updates on the progress of the work.
While the development teams are building the application, other members are busy working on a variety of post-launch efforts.
Individuals from the operations team work on developing solutions for services such as deployment, hosting, and support after the product has been released and delivered.
At the same time, individuals from the marketing team interact with the development team, the client, and prospective users to develop strategies for outreach, promotion, and propagation of the product.