top of page
IMG_0321.jpeg

Shram

My learnings from working as a UX Designer at Shram

Introduction

Startup culture in India has always intrigued me. When I came across Shram, a B2B SaaS startup, I found myself interested in the domain of work management. Considering the significant implications of human factors in a product that would be interacted with at the core of a business, the domain is complex. Every workplace is different, and factors such as culture, work, and team size contribute to this diversity.

Building an application to be used by such a diverse group is a significant task, and when I joined Shram, I was impressed by the amount of work the team had already accomplished. During the three months I spent with the Shram team, I had the opportunity to both learn and contribute to the challenge they had taken on.

Learnings

Removing information overload is crucial, as each user is different and the information they require varies depending on their role. Providing continuous access to all information can create confusion. Simultaneously, accurately categorizing the various types of users is another essential task.

Multi-threaded thinking is vital, as some ideas may be excellent but not implementable. I learned that, as a designer, it's crucial to consider factors from all teams and work in alignment with every goal. A good solution doesn't exist in isolation; it should withstand all the constraints and thrive within the broader context.

Adaptability is essential, as every organization has its unique way of working, which influences both the technical aspects and the company's design philosophy. As designers, we need to adapt to the work style and philosophy, ensuring that it benefits all stakeholders.

Understanding technicalities can save time and streamline the design process. Putting effort into learning the technical aspects of how a design is implemented is crucial. While deciding on features or changes, I used to participate in discussions with the backend and frontend teams. These discussions often involved a lot of back and forth as concepts were explained, and their implementation was discussed.

As I gained more knowledge about the technical side, I realized that communication becomes faster when the designer has a basic understanding of how backend and frontend systems work. This understanding enables the designer to anticipate potential challenges and make informed decisions.

Documentation and design systems play a critical role in the design process. The decisions a designer makes are backed by research, and having this process documented for future reference is essential. Over time, the series of documentation can be analyzed to understand the design philosophy that a company follows. I realized how creating these documents aids in both UI and UX design. Additionally, I gained hands-on experience working on a design system.

Adapting the design process according to context is crucial. One significant realization I had was that not everything written in books works in practice. Understanding the concepts and applying them in a real-world scenario is essential. We must be able to assess the unique challenges and requirements of each project and tailor their approach accordingly.


I would like to thank to Jay, Ojasvika, and the entire Shram team for the opportunity and all the valuable learning experiences I've gained.

bottom of page