As businesses, we all want to build products and services of Salesforce that make a difference to people’s lives. But we often get so caught up in the product itself – the look, the feel, the features, the technology – that we forget about the customer or the people for whom we’re actually designing that product. Who are these users? What is the problem we’re seeking to solve for them, and is there a deeper root cause? Have we considered all possible solutions?

Design thinking pushes us to ask these questions, so that we can create truly targeted solutions that customers love. It’s essentially a creative approach to problem-solving that prompts us to challenge assumptions, redefine the way we think, experiment with solutions, and continuously incorporate feedback. 

At Nlineaxis, design thinking is central to innovation. And in this article, we’d like to show you how we apply this philosophy to build better solutions. We follow a typical double diamond process that involves exploring the human context, converging on a problem statement, developing different ideas, and iterating on potential solutions.

6 Phases of Design Thinking at Salesforce

1. Start With Empathy

At Nlineaxis, TRUST is the number 1 value. We build that trust with end users by cultivating a deep understanding of who they are, including what their goals and motivations might be.

We’ve also noticed that involving ‘humans’ or customers in the process of product development has a long-term business impact. It not only results in higher NPS and CSAT scores, but also helps reduce the volume of service requests.

2. Define The Challenge

We then define high level themes catering to specific business needs. For example, every industry we serve – be it banking, communications, or healthcare – has specific themes identified. These themes are broken down into multiple epics (series of tasks) that focus on solving user needs or problems in a given release.

The key here is to come up with a problem statement synthesizing user needs based on feedback captured in the previous stage. The problem statement should highlight the gaps between current and desired user experiences.

A fulfillment manager needs to view information related to the health and performance of an order management (OM) application and other downstream systems because he can then understand the operational status of the OM.

Next, we generate a few  ‘how might we’ questions to address the problem statement. End users are invited to vote on their favorite questions which are then used in the ideation phase.

For example:

• How might we present data points related to the health and performance of OM applications?
• How might we visualize the data comprehensively? 
• How might we keep the data up-to-date?

3. Ideate On Solutions

At this stage, our design teams conduct co-creation workshops with multiple customer stakeholders from Product, Technology, and Sales. This exercise throws up varied and useful perspectives. Ideas are generated using techniques like ‘crazy 8’s brainstorming’ – eight ideas in eight minutes. The best ideas, as voted by participants, are taken forward to the prototyping phase.

4. Prototype

In every product release, we first create and review low fidelity prototypes (simple, low-tech concepts)  with stakeholders from Product and Technology. Based on their feedback, high fidelity prototypes are created. This iterative process improves efficiency, accelerates time-to-market,  lowers product development costs, reduces redesigns, and ultimately leads to more user-friendly products. 

At Nlineaxis, rapid prototyping can be done right on the Developer Edition (DE) organization – our app creation platform. Once the prototypes are created, it’s time to reconnect with users for their feedback.

5. Build and Roll Out

After the design prototype is shared with the technology team, all insights are put into action. The solution is then built and rolled out to end users as a functional product.

6. Validate and Collect Feedback

At Nlineaxis IT Solution Private Limited, design is never done. The iterative process of listening, collaborating, testing, learning, and growing continues. 

To guard against biases, we capture user feedback regularly through surveys, in-person interviews, and focus groups. We also have an inline feedback mechanism to collect responses to short surveys. Essentially, a lot of evaluative and generative research goes into our products before they’re launched.

That, in a nutshell, is our approach to design thinking.

Conclusion

Salesforce has introduced initiatives for people from any career or educational background to learn about and deliver incredible user experiences. Among these initiatives are the Salesforce Designer role on Trailhead and User Experience Designer certification. The certification is for individuals who want to demonstrate their knowledge, skills, and experience in the following areas: UX Fundamentals, Human-Centered Design, Declarative DesignTesting, Salesforce Lightning Design System (SLDS)

To know more about Salesforce, feel free to reach out to us.