I felt it first when I introduced our product to Anand. Though I was proud of the work I do at Tars, I wasn’t so happy about its looks. I had worked with Anand earlier in building products; even though our product failed to deliver value, it was aesthetically pleasing.
Our startup is bootstrapped and profitable since we took the interface route instead of pursuing the AI/ML hype. As our customers matured, there was no end to future requests. Most of them were great features that could save people time, effort and money. But they remained in words, moving from Google Docs to Jira to Notion.
Some of which got implemented after a lot of effort and time. Though it was functional, the experience got sacrificed for deliverability. Building software takes time, and I honestly started losing patience since my dream product seemed far away.
One evening as I was writing code to optimize WhatsApp Campaigns, I had a realization. I took a cab to Vinit’s place, and told him “I can’t do this anymore”. During the conversation, he told me “Why don’t you start a design team in this company?”
My heart started racing faster, life started to get exciting. We started small by taking part of the product and incrementally revamping it. It took us two weeks to hire interns. Sameer’s design stood out, and Priyamwada’s design case study was top-notch among 100s of applicants.
Though I had conducted design thinking workshops in my early 20s, they were not related to visual or UX design. It was more about empathizing with the user’s problem and finding affordable solutions. Later presenting the solution, taking feedback and improving the solution iteratively.
I set up a similar process here.
Conduct interviews with customer success team Identify and prioritize pain points Competitive research Prototype Present & Take Feedback Iterate Following the process is not the difficult part. You might end up making things cool but it need not work. It’s easy for us to get lost on thing that don’t even matter while being blind spotted to obvious and neccessary concerns.
Good design is more than making things look cool. It’s about building interfaces that are not ambiguous, providing actionable insights and empowering your customers to explore the product to its fullest. Such interfaces can be built only when the design team can empathize with the perspectives of different kinds of people.
Our customer success team significantly contributed to identifying interface barriers between the product and the user.
Ish brought a different perspective altogether. His common questions includes: “Why?”, “But, what do I do with it?”, “This part is not clear. Does it do this or does it do that?”.
Vinit understood the suitable threshold of elements that can go in the interface and get too overwhelming.
I made my team understand multiple perspectives, clarifyed intentions and explained technical jargons. Vinit also contributed to this. Slowly I could see Sameer and Priyamwada becoming more independent. My next focus is identifying common patterns in perspective and making them part of the design review process. Hence reducing the feedback loop and design rework.
Shipping things out on a deadline isn’t easy. Emmanual and Ankit significantly contributed to implementing the design without compromising the quality.
Yes, to the question, how can someone pull that off without experience in design?
Well, it’s less about me and more about an environment that’s set for growth.
It’s about the leaders who put faith in you when you want to do something in the company that has never been done before.
It’s about our then interns (now FTEs) who are open to constructive feedback and has the curiosity to learn things.
It’s about our colleagues who genuinely want the product to make our customers successful.
We are hiring good people, join us.