{"id":19630,"date":"2020-10-29T22:11:00","date_gmt":"2020-10-30T05:11:00","guid":{"rendered":"https:\/\/copperleaf-test.majortom.dev\/how-we-collaborate-in-copperleaf-labs\/"},"modified":"2023-03-16T13:30:59","modified_gmt":"2023-03-16T20:30:59","slug":"how-we-collaborate-in-copperleaf-labs","status":"publish","type":"post","link":"https:\/\/copperleaf-test.majortom.dev\/en\/blog\/how-we-collaborate-in-copperleaf-labs\/","title":{"rendered":"How We Collaborate in Copperleaf Labs"},"content":{"rendered":"

Collaborating with Clients on Innovative Products<\/h4>\n

At Copperleaf, we collaborate<\/a> with our clients to ensure our solutions address their unique business challenges and deliver maximum value. We strongly believe in user-centered design\u2014an iterative process in which our teams focus on the user’s needs in each phase of the design and development process.<\/p>\n

What Does Our Process Look Like?<\/h4>\n

Every successful product organization needs a process in place to incorporate input on features and validate development and design choices. Copperleaf\u2019s process is based on Design Thinking<\/a>\u2014a problem-solving methodology that puts the user\u2019s needs at the heart of the design journey. The process consists of 6 stages:\u00a0\u00a0Understand<\/strong>, Define<\/strong>, Sketch<\/strong>, Decide<\/strong>, Prototype<\/strong>, and Validate<\/strong>.<\/p>\n

\"\"<\/p>\n

1. Understand<\/h4>\n

When we are considering adding a new feature or product to our roadmap, we conduct research to validate it. The first step is to understand who <\/strong>we are designing for and why <\/strong>we are creating the new feature.<\/p>\n

Who<\/strong>: Which organizations and personas will be impacted by this change? Which clients can we interview to better understand the challenges we are trying to solve? Which internal stakeholders should we get input from?<\/p>\n

Why<\/strong>: Why is this feature or product enhancement needed? What is the benefit for the user? What product differentiation can be gained by creating this new capability?<\/p>\n

This stage enables us to explore ideas and broaden our knowledge about the end user\u2019s pain points, the business impacts, and the potential benefits of the change.<\/p>\n

2. Define<\/h4>\n

Now that we have a broad understanding of the problem we’re trying to solve and who will benefit from the change, we can create at least one hypothesis that defines the solution for our clients.<\/p>\n

During this stage, our product teams will narrow our focus to the context, desired outcomes, and potential solutions to the problem. We create goals, success metrics, and signals\u2014using Google\u2019s HEART Framework<\/a>\u00a0to measure user experience based on Happiness, Engagement, Adoption, Retention and Task Success.<\/p>\n

3. Sketch<\/h4>\n

Once we’ve defined our hypothesis, and aligned stakeholder agreement on how to measure success, the next step is to sketch solutions. The goal is to produce as many innovative and desirable solutions as possible. An emphasis on fast iterations and timely reviews allows us to produce a broad set of potential solutions economically.<\/p>\n

4. Decide<\/h4>\n

Having generated a number of ideas, we now have to decide which idea presents the most desirable, viable, and feasible solution to the problem. Sometimes there will be a clear winner, and other times, multiple solutions solve the problem. Regardless, we will need to build and test the potential solutions in the prototype stage.<\/p>\n

5. Prototype<\/h4>\n

The purpose of prototyping is to actualize our design and allow us to test the feasibility of our solutions. Depending on the level of user validations required, the prototyping method will vary. For example, if we are looking to validate a complicated interactivity problem, we would look at a high fidelity, interactive prototype. For a simpler concept, we would choose lower cost options to bring the concept forward to the next stage.<\/p>\n

6. Validate<\/h4>\n

This is the moment of truth\u2014when users get to interact with the prototype! The objective here is to generate statistically\u00a0significant data to validate our assumptions so that we can either move ahead to implementation or regress back to an earlier (define\u00a0<\/span>\/\u00a0understand\u00a0<\/span>\/\u00a0sketch\u00a0<\/span>\/\u00a0decide\u00a0<\/span>\/\u00a0prototype<\/span>) stage.<\/p>\n

Validating our prototypes is key to getting to the right solution efficiently and effectively. The product team decides how best to validate the solution by asking questions like:<\/p>\n