Sprih

Building a one-stop platform for carbon management and offset for organizations.

Summary

I spent 15 months designing and strategising the user experience and brand experience for Sprih, an organization deeply committed to combating climate change. In addition to product design work, I also did the branding and brand positioning for Sprih. Within 15 months, there were two versions of the product that were designed, developed and deployed in the market.

Role

Project Lead

User Experience (UX) Researcher

Interaction (IxD) Designer

User Experience (UX) Designer

User Interface (UI) Designer

Brand Identity Designer

Timeline

2021-2023

skills

Product thinking

Interaction design

Market researcher

Accessibility design

Visual design

Brand design

tools

Figma

Miro

Illustrator

Notion

Photoshop

Indesign

*Note

This case study covers only parts of the design process focusing mainly on my role within the project. I have retracted or changed portions of findings to conceal any confidential information.

about SPRIH

In the face of climate change, organizations must urgently prioritise sustainability and accountability for a resilient future.

Sprih, an early player in India, identified the chaos in carbon management and pioneered a user-friendly solution. Their platform not only calculates carbon emissions but also aids in planning and offsetting through in-depth research and data-driven insights.

Seeking a modern, timeless brand identity, Sprih reflects its dedication to a greener future, offering a one-stop solution for simplified sustainability accessible to all organizations.

Project objective

One-stop platfrom

Provide a one-stop platform for organizations, streamlining tracking, calculating, and offsetting with a focus on minimizing the learning curve for seamless adoption.

Scalable platform

Develop scalable and accessible dashboard that can help decision maker and experts take their next step

Community driven

Foster community engagement to create a collaborative ecosystem for shared sustainability goals.

Breaking it down

*Note

Due to the confidential nature of this project under a Non-Disclosure Agreement (NDA) and the inclusion of designs and data pertaining to its forthcoming versions, have retracted or changed portions of findings to conceal any confidential information.

project results

The platform was adopted by more than five large-scale organizations.

The platform rapidly gained popularity during the timeframe my team and I worked on it. The team size also expanded, propelling the project into a fast-paced sprint with a keen focus on outcomes.

Due to confidentiality reasons, further details cannot be disclosed here. If you are interested to know more, feel free to reach out to me directly.

Contact me

Click here to learn more about the company, Sprih.

my learnings

Discussing feature viability should be a collaborative affair.

01

Experts need structure, not simplification

When discussing feature viability, it's essential to involve the UX design team, tech team, and leadership in the conversation. This collaborative approach ensures that all perspectives are considered, leading to well-informed decisions about the feasibility and implementation of new features.

Ask questions.

Since the team was relatively small, I was able to interact with each and every team in the system, enabling me to be more empathetic towards them and vice versa. Anytime there was an overload of information, it was usually forgotten in the span of the day. One of the most important lessons I learned was that it is okay to ask questions and ensure everyone is on the same page, rather than allowing avoidable mistakes to occur.

02

Balancing between users and business.

Designing a product is like a dance, while prioritizing an intuitive and satisfying user experience, it's equally crucial to align with overarching business goals. This synergy ensures that the product not only delights users but also contributes to the overall success and sustainability of the business, creating a harmonious relationship between user satisfaction and organizational objectives.

03

Over-document for easy handoff.

Clear documentation makes lives easier for everyone! I learned the hard way that when you leave room for interpretation, your designs probably won’t be engineered to spec. I had to revisit my designs several times to ensure that component padding, naming conventions, and other forms of documentation were consistent and clear.