Astronaut loading animation Circular loading bar

Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(7)

Customer Journey(16)

Design(39)

Solar Industry(7)

User Experience(62)

Edtech(10)

Events(34)

HR Tech(3)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(17)

Testing(9)

Android(48)

Backend(32)

Dev Ops(8)

Enterprise Solution(28)

Technology Modernization(4)

Frontend(29)

iOS(43)

Javascript(15)

AI in Insurance(36)

Insurtech(63)

Product Innovation(54)

Solutions(21)

E-health(11)

HealthTech(23)

mHealth(5)

Telehealth Care(4)

Telemedicine(5)

Artificial Intelligence(139)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(17)

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

Platform Engineering: Accelerating Development and Deployment

The software development landscape is evolving rapidly, demanding unprecedented levels of speed, quality, and efficiency. To keep pace, organizations are turning to platform engineering. This innovative approach empowers development teams by providing a self-service platform that automates and streamlines infrastructure provisioning, deployment pipelines, and security. By bridging the gap between development and operations, platform engineering fosters standardization, and collaboration, accelerates time-to-market, and ensures the delivery of secure and high-quality software products. Let’s dive into how platform engineering can revolutionize your software delivery lifecycle.

The Rise of Platform Engineering

The rise of DevOps marked a significant shift in software development, bringing together development and operations teams for faster and more reliable deployments. As the complexity of applications and infrastructure grew, DevOps teams often found themselves overwhelmed with managing both code and infrastructure.

Platform engineering offers a solution by creating a dedicated team focused on building and maintaining a self-service platform for application development. By standardizing tools and processes, it reduces cognitive overload, improves efficiency, and accelerates time-to-market.  

Platform engineers are the architects of the developer experience. They curate a set of tools and best practices, such as Kubernetes, Jenkins, Terraform, and cloud platforms, to create a self-service environment. This empowers developers to innovate while ensuring adherence to security and compliance standards.

Role of DevOps and Cloud Engineers

Platform engineering reshapes the traditional development landscape. While platform teams focus on building and managing self-service infrastructure, application teams handle the development of software. To bridge this gap and optimize workflows, DevOps engineers become essential on both sides.

Platform and cloud engineering are distinct but complementary disciplines. Cloud engineers are the architects of cloud infrastructure, managing services, migrations, and cost optimization. On the other hand, platform engineers build upon this foundation, crafting internal developer platforms that abstract away cloud complexity.

Key Features of Platform Engineering:

Let’s dissect the core features that make platform engineering a game-changer for software development:

Abstraction and User-Friendly Platforms: 

An internal developer platform (IDP) is a one-stop shop for developers. This platform provides a user-friendly interface that abstracts away the complexities of the underlying infrastructure. Developers can focus on their core strength – building great applications – instead of wrestling with arcane tools. 

But it gets better. Platform engineering empowers teams through self-service capabilities.This not only reduces dependency on other teams but also accelerates workflows and boosts overall developer productivity.

Collaboration and Standardization

Close collaboration with application teams helps identify bottlenecks and smooth integration and fosters a trust-based environment where communication flows freely.

Standardization takes center stage here. Equipping teams with a consistent set of tools for automation, deployment, and secret management ensures consistency and security. 

Identifying the Current State

Before building a platform, it’s crucial to understand the existing technology landscape used by product teams. This involves performing a thorough audit of the tools currently in use, analyzing how teams leverage them, and identifying gaps where new solutions are needed. This ensures the platform we build addresses real-world needs effectively.

Security

Platform engineering prioritizes security by implementing mechanisms for managing secrets such as encrypted storage solutions. The platform adheres to industry best practices, including regular security audits, continuous vulnerability monitoring, and enforcing strict access controls. This relentless vigilance ensures all tools and processes are secure and compliant.

The Platform Engineer’s Toolkit For Building Better Software Delivery Pipelines

Platform engineering is all about streamlining and automating critical processes to empower your development teams. But how exactly does it achieve this? Let’s explore the essential tools that platform engineers rely on:

Building Automation Powerhouses:

Infrastructure as Code (IaC):

CI/CD Pipelines:

Tools like Jenkins and GitLab CI/CD are essential for automating testing and deployment processes, ensuring applications are built, tested, and delivered with speed and reliability.

Maintaining Observability:

Monitoring and Alerting:

Prometheus and Grafana is a powerful duo that provides comprehensive monitoring capabilities. Prometheus scrapes applications for valuable metrics, while Grafana transforms this data into easy-to-understand visualizations for troubleshooting and performance analysis.

All-in-one Monitoring Solutions:

Tools like New Relic and Datadog offer a broader feature set, including application performance monitoring (APM), log management, and real-time analytics. These platforms help teams to identify and resolve issues before they impact users proactively.

Site Reliability Tools To Ensure High Availability and Scalability:

Container Orchestration:

Kubernetes orchestrates and manages container deployments, guaranteeing high availability and seamless scaling for your applications.

Log Management and Analysis:

The ELK Stack (Elasticsearch, Logstash, Kibana) is the go-to tool for log aggregation and analysis. It provides valuable insights into system behavior and performance, allowing teams to maintain consistent and reliable operations.

Managing Infrastructure

Secret Management:

HashiCorp Vault protects secretes, centralizes, and manages sensitive data like passwords and API keys, ensuring security and compliance within your infrastructure.

Cloud Resource Management:

Tools like AWS CloudFormation and Azure Resource Manager streamline cloud deployments. They automate the creation and management of cloud resources, keeping your infrastructure scalable, secure, and easy to manage. These tools collectively ensure that platform engineering can handle automation scripts, monitor applications, maintain site reliability, and manage infrastructure smoothly.

The Future is AI-Powered:

The platform engineering landscape is constantly evolving, and AI is rapidly transforming how we build and manage software delivery pipelines. The tools like Terraform, Kubecost, Jenkins X, and New Relic AI facilitate AI capabilities like:

  • Enhance security
  • Predict infrastructure requirements
  • Optimize resource security 
  • Predictive maintenance
  • Optimize monitoring process and cost

Conclusion

Platform engineering is becoming the cornerstone of modern software development. Gartner estimates that by 2026, 80% of development companies will have internal platform services and teams to improve development efficiency. This surge underscores the critical role platform engineering plays in accelerating software delivery and gaining a competitive edge.

With a strong foundation in platform engineering, organizations can achieve greater agility, scalability, and efficiency in the ever-changing software landscape. Are you ready to embark on your platform engineering journey?

Building a robust platform requires careful planning, collaboration, and a deep understanding of your team’s needs. At Mantra Labs, we can help you accelerate your software delivery. Connect with us to know more. 

Cancel

Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top
ml floating chatbot