Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(8)

Customer Journey(17)

Design(43)

Solar Industry(8)

User Experience(66)

Edtech(10)

Events(34)

HR Tech(3)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(18)

Testing(9)

Android(48)

Backend(32)

Dev Ops(11)

Enterprise Solution(29)

Technology Modernization(7)

Frontend(29)

iOS(43)

Javascript(15)

AI in Insurance(38)

Insurtech(66)

Product Innovation(57)

Solutions(22)

E-health(12)

HealthTech(24)

mHealth(5)

Telehealth Care(4)

Telemedicine(5)

Artificial Intelligence(143)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(19)

FinTech(51)

Banking(7)

Intelligent Automation(27)

Machine Learning(47)

Natural Language Processing(14)

expand Menu Filters

Me vs Client – My Very first Client Meeting

By :
4 minutes read

Remember the feeling that comes when you think you wrote all the right answers in the exam but when you are handed the mark sheet and you barely passed?

I am sure most of us have gone through that. 

Well, I experienced almost the same feeling in my early days at Mantra Labs.

I had gotten assigned to a new project and was super duper grateful for this big responsibility. I dived right into it and wanted to do all of it on my own. I really thought I did everything perfectly. 

We know what is said about perfection, it is difficult to achieve. 

“In design, there is no perfection, there is just iteration.” (Design Gyaan 001 )

This is exactly what I said to myself when I failed. (Big words)

My client was this really big organization. I was working till the very last minute for the first meeting and thought to give it my best.

I joined the call with all my designs and just assumed all my work and efforts would be well appreciated.

.

.

.

BIG FAIL

The 2 words that best fit the first client meeting. It was everything I had not anticipated. 

There were almost 15 top management people present from their end. 

(Nervous alert – the feeling you get when you see the exam paper and know nothing). 

I suddenly realized I was not clear on how to introduce my concept and present my design. All the keywords in my brain seemed to have gone on vacation at that moment. 

(That’s how I wrote my exam answers. Not just me, most of us did.) 

Also, it wasn’t all my unpreparedness and nervousness that led to the downfall of that meeting. They had a very direct approach and their feedback was also not very clear.

I came out of the call almost in tears and was extremely put off.

UPSET

.

.

.

That was the emotion I felt after it and thought I wasn’t ready for this big transition. Felt even worse thinking that all my hard work was for nothing.

The next day I got back to work. With the help of my managers, we changed our strategy for approaching the project. We did a brainstorming (whiteboarding) session with not just the design team, but also with project managers, marketing, and the business team. We scrapped all of our old designs and came up with 3 unique design ideas and iterated on these. 

I aligned the design process to match the client’s requirements and my company’s standards and prepared for the next meeting.

BIG PROGRESS

.

.

.

Changing the strategy played into our hands and we were more confident with our new versions of designs. I understood where I faulted earlier and prepared for my meeting before. I made a small set of key pointers that helped me drive the conversation and explain my designs easily. 

“Always make notes before the exam for revision” (Design Gyaan 002 )

In the next meeting, the clients realized I had understood the assignment and we had a more fruitful discussion. We showed them our designs with the new strategies implemented and they reciprocated positively. We cracked the design pitch meeting in the second call and had a path to move forward.

I walked out of the second meeting with a big smile on my face. (It was like getting straight A’s)

I did realize the places where I was lacking and needed to work on and since then I have started to maintain all these as part of my practice.

NOW FOR THE …..REPORT CARD

1. Agenda: Innovate and not just design

All the research, competitor study, beautiful elements, and trending UI styles didn’t work. While approaching a project it’s the innovation behind it that stands out and makes it work and not the research combined with beautiful design. New ideas don’t exist, until you come up with one.

2. Notebook: Writing in a notebook helps.

The old-fashioned pen-paper approach is key. Writing down keywords for your design that will help you in explaining your audience about it will make it easier for you. It helps you put all your thoughts in place and you won’t miss out on the important things you need to convey. Also, don’t make the mistake of doing this in your Notes app on the laptop because mostly you will be sharing your screen. 

3. Pointers: Prioritise Goals

Make a list of all the tasks in your bucket and choose the top 5 tasks to complete. For that particular day, you can prioritize 3 tasks, one simple, one major requirement, and one that interests you. Do the simple one first and this will help you check one off and give you a sense of accomplishment. Then take up the major one and then the last one. You would have completed a major task and also be happy at the end of the day with doing the one that interests you.

4. Subject knowledge: Know your tool properly to be the best!

I learnt greatly more about the tool Adobe XD and its features while working on the design pitch. I learned how to organize my files to make the workflow efficient. Also, I learned more about how to present my design screens. 

5. Co-curricular:

Don’t forget to charge your laptop before any important call and to keep the charger handy. Also, close all your Google chrome tabs, you don’t want them to peak at your mess. Another interesting thing is to try to document your design progress. I maintained this in the Miro board application. This has helped me to view my progression from the first design and see how much I have improved.

.

.

.

PASSED…

About the Author:

Diya is an architect turned UI/UX Designer, currently working at Mantra Labs. She values designing experiences for both physical and digital spaces.

Want to know more about designing?

Read our blog: Designing for Web 3.0

Cancel

Knowledge thats worth delivered in your inbox

Why Netflix Broke Itself: Was It Success Rewritten Through Platform Engineering?

By :

Let’s take a trip back in time—2008. Netflix was nothing like the media juggernaut it is today. Back then, they were a DVD-rental-by-mail service trying to go digital. But here’s the kicker: they hit a major pitfall. The internet was booming, and people were binge-watching shows like never before, but Netflix’s infrastructure couldn’t handle the load. Their single, massive system—what techies call a “monolith”—was creaking under pressure. Slow load times and buffering wheels plagued the experience, a nightmare for any platform or app development company trying to scale

That’s when Netflix decided to do something wild—they broke their monolith into smaller pieces. It was microservices, the tech equivalent of turning one giant pizza into bite-sized slices. Instead of one colossal system doing everything from streaming to recommendations, each piece of Netflix’s architecture became a specialist—one service handled streaming, another handled recommendations, another managed user data, and so on.

But microservices alone weren’t enough. What if one slice of pizza burns? Would the rest of the meal be ruined? Netflix wasn’t about to let a burnt crust take down the whole operation. That’s when they introduced the Circuit Breaker Pattern—just like a home electrical circuit that prevents a total blackout when one fuse blows. Their famous Hystrix tool allowed services to fail without taking down the entire platform. 

Fast-forward to today: Netflix isn’t just serving you movie marathons, it’s a digital powerhouse, an icon in platform engineering; it’s deploying new code thousands of times per day without breaking a sweat. They handle 208 million subscribers streaming over 1 billion hours of content every week. Trends in Platform engineering transformed Netflix into an application dev platform with self-service capabilities, supporting app developers and fostering a culture of continuous deployment.

Did Netflix bring order to chaos?

Netflix didn’t just solve its own problem. They blazed the trail for a movement: platform engineering. Now, every company wants a piece of that action. What Netflix did was essentially build an internal platform that developers could innovate without dealing with infrastructure headaches, a dream scenario for any application developer or app development company seeking seamless workflows.

And it’s not just for the big players like Netflix anymore. Across industries, companies are using platform engineering to create Internal Developer Platforms (IDPs)—one-stop shops for mobile application developers to create, test, and deploy apps without waiting on traditional IT. According to Gartner, 80% of organizations will adopt platform engineering by 2025 because it makes everything faster and more efficient, a game-changer for any mobile app developer or development software firm.

All anybody has to do is to make sure the tools are actually connected and working together. To make the most of it. That’s where modern trends like self-service platforms and composable architectures come in. You build, you scale, you innovate.achieving what mobile app dev and web-based development needs And all without breaking a sweat.

Source: getport.io

Is Mantra Labs Redefining Platform Engineering?

We didn’t just learn from Netflix’s playbook; we’re writing our own chapters in platform engineering. One example of this? Our work with one of India’s leading private-sector general insurance companies.

Their existing DevOps system was like Netflix’s old monolith: complex, clunky, and slowing them down. Multiple teams, diverse workflows, and a lack of standardization were crippling their ability to innovate. Worse yet, they were stuck in a ticket-driven approach, which led to reactive fixes rather than proactive growth. Observability gaps meant they were often solving the wrong problems, without any real insight into what was happening under the hood.

That’s where Mantra Labs stepped in. Mantra Labs brought in the pillars of platform engineering:

Standardization: We unified their workflows, creating a single source of truth for teams across the board.

Customization:  Our tailored platform engineering approach addressed the unique demands of their various application development teams.

Traceability: With better observability tools, they could now track their workflows, giving them real-time insights into system health and potential bottlenecks—an essential feature for web and app development and agile software development.

We didn’t just slap a band-aid on the problem; we overhauled their entire infrastructure. By centralizing infrastructure management and removing the ticket-driven chaos, we gave them a self-service platform—where teams could deploy new code without waiting in line. The results? Faster workflows, better adoption of tools, and an infrastructure ready for future growth.

But we didn’t stop there. We solved the critical observability gaps—providing real-time data that helped the insurance giant avoid potential pitfalls before they happened. With our approach, they no longer had to “hope” that things would go right. They could see it happening in real-time which is a major advantage in cross-platform mobile application development and cloud-based web hosting.

The Future of Platform Engineering: What’s Next?

As we look forward, platform engineering will continue to drive innovation, enabling companies to build scalable, resilient systems that adapt to future challenges—whether it’s AI-driven automation or self-healing platforms.

If you’re ready to make the leap into platform engineering, Mantra Labs is here to guide you. Whether you’re aiming for smoother workflows, enhanced observability, or scalable infrastructure, we’ve got the tools and expertise to get you there.

Cancel

Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top
ml floating chatbot