Product Design at BigCommerce
Our process begins with empathy. The first step to a creating a successful experience is to develop a deeper understanding of our user. What problems are they trying to solve? What motivates them? What tools are they currently using? Are there UX gaps or opportunities not currently being addressed?
Engaging with our users can take various forms depending on the type of information we are looking to gather. The most common form of qualitative user research we conduct at BigCommerce are 1:1 interviews.
When we begin a project we set up a number of these interviews to help us identify user needs and identify opportunities. Once interviews are completed, the research is synthesized and a report is generated. Insights are garnered, initial assumptions can be validated or disproved.
Competitive Analysis is another method we use during the discovery phase. How is our competition attempting to solve problems similar to our own? What feature sets do they offer? Are there opportunities in the market for us to capitalize on.
As part of this process we map the journeys of our competitors and conduct an evaluation based on Nielsen's Usability Heuristics for Interaction Design. A set of criteria that allows us to evaluate an experience without having to account for aesthetics or personal tastes.
The results of this evaluation are then rendered in a “rainbow plot” to allow us to easily identify trends and spot opportunities for improvement within our own product.
Once we have a sufficient amount of background, we begin the process of partnering with Product and Engineering to help Define the Problem.
This is the most important part of a product designer’s job. Far too often product organizations fall prey to the trap of "institutional knowledge”. Stakeholder interviews are a valuable source of knowledge, but cannot be the only source of input. Beware the product owner that says “I know what our users want.” Many engineering hours have been wasted building features users don’t want and didn’t ask for. Taking the time to validate assumptions with users pays exponential dividends.
What problem do these 3 people share?
Most people will answer “They need an umbrella.” This is an example of jumping to solutions.
The problem statement is: “They are wet.” An umbrella is a solution, like a raincoat, or an awning.
A Discovery Canvas are a tool we use to kickoff projects with our partners in product and engineering. This series of whiteboard, post-it note, and small group exercises is a way for team members to share knowledge and perspective, and allow for the team to align around the keys aspects of the project including, definition of problem, value proposition, targeted users, and metrics for determining success.
The output from the Discovery Canvas should be a clear understanding of the Objectives and Key Results we hope to accomplish from this project.
With our OKRs in hand, we are ready to begin solutioning! Ideation begins with How might we…? questions based on the insights generated during our Discovery phase.
Our Discovery Workshop has helped us define an MVE (Minimal Viable Experience) for the project. An MVE is the first incremental improvement towards a grander vision for an experience.
In this phase, development of one or more concepts begins. Design team members partner with Product and Engineering to define timelines and deliverables. Information architecture and wireframe explorations begin.
Validation of our hypotheses begin via rapid prototyping. Low fidelity prototypes are tested with coworkers or friends and family. With the team sufficiently confident in a direction, higher fidelity prototypes are created and real users are recruited for user testing. These tests are ideally conducted in person and recorded. A user is asked to complete a series of tasks and articulate their experience/thoughts etc. Feedback is gathered and adjustments to the experience are made.
With our prototype testing well with users, we are ready to move on to Delivery. Design team members meet more regularly with Engineering counterparts as they prepare to hand off production files. Our team at BigCommerce has been hard at work developing our Design Language System called BigDesign.
Along with principles and guidelines for designers, we have partnered with our engineering team to create a React Component Library in order to streamline the design to developer handoff and help standardize our interface patterns and behaviors.
With production code being developed, Designers and researchers begin recruiting users based on targeted cohort group. Users join a closed beta and are introduced to the feature. After several weeks our team conducts a follow up interview to gauge the success of the feature.
Once results have been deemed satisfactory, the feature is move to open beta, and available for all users to opt in. Feedback from users is encouraged through contextual prompts. Engineering and product prioritize bugs as the team meets with the Product Marketing Team to discuss got to market plans.
Do It Again
Our feature has achieved General Availability within the product and is now available to all users. But, our journey is just beginning. The design team partners with product and engineering on a post-launch roadmap to plan the next wave of feature development. We gather new data points from users as they interact with the feature, we discover new opportunities for improvement, and the cycle begins again.