When Figma make was introduced, I started working with it from the very beginning. It was the feature I had been waiting for — the missing link in the UX workflow.

For years, I have poured my heart into Figma prototypes, trying to give life to “natural” user interactions. But if we’re being honest, something was always complete. We would prioritise a few key paths, focus on the visuals, and end up with a “point-and-click” experience. The “product life” was missing.

Today, that has changed.

I haven’t stopped my traditional prototyping, I have evolved it. I have a comparably big database of existing Figma designs, and I am now converting that some of those into Figma Make along with all new topics I am working. This allows me to generate prototypes that perform the exact user flow and interaction we plan for the actual product.

Usability testing isn’t just a final check anymore; it’s faster, deeper, and more honest.

My goal isn’t to replace my work with AI, but to integrate it in the spaces required to do a “better job”. I can identify the right problem worth solving before a single developer starts a sprint.

1. The Database as Context: I use my core Figma frames as the “DNA” for Figma Make. By feeding my actual design system into the AI, I ensure the generated flows look and feel exactly like our brand.
2. Adding the Logic Layer: If the topic is greenfield, Once the interactive structure is there, I use the Model Context Protocol (MCP) to bridge the design into my coding environment. Using GitHub Copilot, I add real logic — actual data inputs and functional filters that “fake” prototypes just can’t handle.
3. High-Fidelity Discovery: Because the prototype now behaves like the final product, the user’s feedback becomes the truth. We stop testing “pictures of software” and start testing “software behavior.”

Why the “Fidelity Gap” Matters

People use products for their own wants — not because the product “wants” them to. When we test with static prototypes, we often force users down a narrow path. We say, “Imagine this works,” or “Don’t click that; it’s not connected.” When we do this, we aren’t testing the product; we are testing the user’s ability to follow instructions. We miss the subtle friction points. By using Figma Make to create high-fidelity, functional prototypes, we finally have a mirror that reflects true human behavior.

The era of “imaginary” prototyping is over. It’s time to start making.

Prototyping is often treated as a step between research and development, but in real product teams it does far more than that. In this article, you’ll see how prototypes can help you think more clearly, uncover unknowns early, align cross‑functional teams faster, and reduce delivery risk with less rework.

After years of working on complex enterprise products, one pattern became clear: prototyping is not a phase in the process, it is a way of thinking.

It helps teams see reality sooner, reduce risk earlier, and move from opinion to evidence much faster.

1. Prototyping exposes what you don’t know

Teams often feel confident about a problem, until they try to turn it into a concrete flow.

The moment you start prototyping, hidden dependencies, missing rules, and vague assumptions surface in front of everyone.

On one topic, my team had spent hours discussing a “simple” new workflow, but everything stayed abstract.

A rough 20‑minute prototype made the interactions tangible enough that the architect immediately spotted a key integration gap we had completely missed, saving days of going in the wrong direction.

2. Prototypes create direction before it exists

The best time to prototype is not when everything is clear.

It is when you have the first 5–10% of an idea and want to know whether it is worth pursuing.

Even a rough prototype can answer critical questions:

• Is this idea technically feasible?
• Does it actually address the user problem?
• Is there a credible path to business value?
• Which assumptions are clearly wrong?

Instead of long debates and slides, a scrappy prototype gives the team something concrete to react to and quickly shapes a vague spark into a clearer direction.

3. “Just enough fidelity” as an operating principle

Fidelity is not about low, mid, or high.

In real product work, there is only one useful rule: build a prototype with just enough fidelity to answer the next important question.

That might look like:

• A clickable skeleton to validate data flow and state changes.
• A lightly styled flow to test whether users understand the narrative and trust the solution.
• A more realistic, content‑rich prototype to explore edge cases and error handling with engineers.

This approach has helped me spend the right amount of time at each stage of the design process.

4. Prototypes as the primary communication language

In cross‑functional teams, prototypes communicate faster and more accurately than documents.

They let each role see what matters to them without translation layers.

Over time, prototypes became my default way of communicating with:

• Product owners, to align on scope and trade‑offs.
• Architects and developers, to clarify logic, edge cases, and system behavior.
• Business stakeholders and leaders, to show impact and workflows in real context.
• Users, to observe real behavior instead of collecting opinions.

Replacing slide decks with prototype walkthroughs consistently reduced confusion, shortened discussions, and helped everyone align around the same mental model of the product.

5. Iteration: How products find their own clarity

No meaningful product reaches clarity in a single version.

The number of prototype iterations is often directly linked to the sharpness of the final solution.

Each iteration tends to reveal something different:

• A missing business rule.
• A technical constraint no one mentioned earlier.
• A user expectation that conflicts with current logic.
• A regulatory or compliance requirement.
• A workflow collision with another part of the system.

Iterating quickly, sometimes several versions in a day, lets the product “discover” its own direction.

You stop chasing a perfect first solution and instead build clarity step by step.

6. Prototyping for research and discovery, not just validation

Prototypes are not only for usability tests or final sign‑off.

Used early, they dramatically improve research and discovery.

Before validation, prototypes help to:

• Explore what might be possible within technical and domain constraints.
• Reveal where deeper research is needed.
• Identify information gaps and the most important questions to ask users and stakeholders.
• Map where the biggest risks sit. Whether they are usability, technical, or business risks.

This makes research sessions more grounded: you are not just talking in theory; you are reacting to something concrete and evolving it as you learn.

7. How AI has changed prototyping

AI has radically lowered the cost and effort of getting to a “good enough” prototype.

Instead of starting from a blank canvas, teams can now:

• Turn ideas into wireframes or flows in minutes.
• Generate multiple variations to compare quickly.
• Simulate scenarios and user paths before anything is built.
• Visualise alternatives that would have been too expensive to explore manually.

This shift has made prototyping accessible beyond designers.

Product managers, engineers, and leaders can now create or adjust simple prototypes themselves, reaching clarity faster and making decisions with more confidence.

AI amplifies the speed and depth of exploration.

Designers still provide judgment, prioritise learning questions, and decide which directions are worth turning into higher‑fidelity experiences.

8. Prototyping as a mindset

The most important realisation is this:

Prototyping is not a deliverable. It is a way of thinking and learning.

Prototype to understand.

Prototype to align.

Prototype to discover.

Prototype to communicate.

Prototype to reduce risk.

Prototype to build confidence.

When a team adopts this mindset, prototypes are no longer “extra work.”

They become the default way to think through problems, test assumptions, and bring ideas to life.

Where great products begin

The purpose of prototyping is much bigger than checking if a design “works.”

It is a strategic tool that helps entire product teams move with clarity, speed, and shared understanding.

If there is one principle to carry into every project, it is this:

Prototype early, prototype often, and always use just enough fidelity to answer the next question.

That is where real learning happens.

That is where alignment becomes natural.

And that is where great products truly begin.

After nine years of working with teams across several countries, one lesson became clear. Design does not move in a straight line. Real projects shift. People shift. Priorities shift. And when that happens, the clean structure of design thinking rarely holds its shape.

Early in my career, I tried to follow every stage in order. I treated the process like a checklist. But working with global teams changed that view fast. Sometimes a team wanted clarity before anything else. Sometimes another pushed early into ideas because speed mattered. Sometimes alignment was the priority so decisions stayed tight. These patterns may appear or not, but the point is simple. People, environments, and expectations shape the way problems are approached, and no rigid process can fit every situation.

In most of the products, I worked on from the beginning. Some I entered mid-way when the solution was already taking form. Sometimes we validated before defining. Sometimes we defined before researching. It taught me that design is unpredictable by nature, and trying to force it into one fixed framework misses the point.

The real strength does not come from following a process. It comes from following principles that keep you grounded when the work gets messy.

1. Identify the right problem

If the problem is wrong, the outcome is wrong. Teams may see challenges differently based on their goals or context. Our job is to uncover the core truth behind all those views.

2. Build a product mindset

Value comes first. Visuals, flows, and screens matter only when they move the product forward. A product mindset keeps you focused on impact, not documentation.

3. Work with people, not steps

Success depends on communication styles, expectations, and trust. Adapting to people will move a project farther than adapting to a template.

4. Close the gaps you create

Every designer and PM creates gaps. Strong teams surface them early, clarify them, and fix them without drama.

5. Stay open and ready to adjust

No plan survives the first round of feedback. Flexibility is not a weakness. It is a core skill.

Design thinking, lean UX, or product discovery all aim for the same outcome. They want us to understand the problem, reduce risk, and build something that matters. The frameworks are different routes to the same destination.

From my perspective as a lead product designer, this became the key insight. Design is not about enforcing a process. It is about protecting the value the work must deliver. It is about reading the room, understanding the people, and shaping the path based on what the product needs at that moment. It is about staying grounded in principles so you can flex the process without losing direction.

If there is one idea I would leave to any designer, product manager, or founder, it is this:

Principles will guide you through challenges that no process can predict.

June 2025.
Me and my wife were buzzing with excitement, our Thailand trip was finally happening. 15 days, 3 regions, 1 goal: to explore the full heart of the country. North for the hilly forests and quiet temples of Chiang Mai. Mid for Bangkok’s energy and chaos. South for the beautiful beaches of Phuket.

Simple plan. Until we started booking hotels.

We opened every platform we could — Booking.com, Agoda, Airbnb, MakeMyTrip — juggling tabs, filters, and budget sliders like pros. But soon something odd caught our attention.

In Bangkok, most hotels within our budget had decent ratings 4.2, 4.3, even 4.5. But in Chiang Mai and Phuket? Suddenly, the ratings dropped. 3.6, 3.2, 3.9. At first glance, the numbers screamed “average”.

But the photos told another story — cozy rooms, warm lights, mountain views, beachside breakfasts. Something didn’t add up.

Were we missing something? Were these hotels truly worse, or was there something else behind those numbers?

We did what any confused traveler would do — we dove into the reviews. Comment after comment, from travelers across the world, gave us a glimpse into completely different realities.
Some loved the same hotels others hated. Some complained about things that didn’t matter to us at all. Some cared about Western breakfast; we were craving Thai street food. Some wanted spotless luxury; we wanted comfort and connection.

Still, the ratings made us hesitate. Numbers are supposed to be objective, right?

With mild anxiety and crossed fingers, we finally booked a mix of places — a few with high ratings in Bangkok, and a few “risky” low-rated ones in the North and South.

Fast forward

We land in Thailand, and my first surprise comes in Bangkok.

The “highly rated” hotel? Functional but soulless. Busy lobby. Polite but distant staff. Small room, no warmth. It was fine but not memorable.

Then we moved to Chiang Mai. The “3.5-star” stay? A completely different world. Family-run, cozy, with staff who treated us like friends. They remembered our breakfast choices, shared local travel tips, even helped us plan a temple hike.
The same story continued in the South, our “average” rated beach stay turned out to be the highlight of the trip.

That’s when it hit me.
The numbers hadn’t lied, they had simply told one side of the truth.

The UX parallel

Later, while reflecting, I realised something important not just about travel, but about how we design and make decisions in UX.

We often rely on quantitative data — ratings, metrics, clicks, conversions, engagement scores.
They feel clean. Objective. Reliable.
But behind every number is a human context — shaped by culture, behaviour, geography, and expectations.

A “3.5” in one cultural lens might mean “okay,” but in another, it might actually mean “great value.”
A “negative review” might not reflect bad service, but simply a mismatch in expectations.

When we design or analyse user experiences, data can tell us what is happening.
But only qualitative understanding can tell us why.

In Thailand, I learned this lesson not from dashboards or reports, but from dusty streets, smiling hotel owners, and late-night review scrolls filled with human emotion.

Learning

If UX is about empathy, then empathy can’t live in numbers alone.
We need both — the what and the why.
The data and the story.
The chart and the conversation.Because sometimes, the most meaningful insights hide right behind a 3.5-star review.

It was my raw ideas pencil-shaded UIs on loose sheets that landed me in their tech lab as a front-end developer intern. I began an exhilarating journey, hungry to learn everything: the intricacies of front-end frameworks, the basics of graphic design, bug fixes, and brainstorming.

The opportunity

Soon, I was given a challenge that set my heart racing: create an interactive digital story for autistic children. The canvas? An open source game engine called Godot and Inkscape for the illustrations. As an intern, restrictions were few and creative license was vast. I poured myself into YouTube tutorials, fiddled with Godot code and functionalities, and filled pages with sketches. Names for the story came and went until “Best Friend” struck a cord. Every hour was trial-and-error: storyboarding, coding, drawing, and reworking. I reached out to friends for help and leaned on online forums for answers.

One intense month later, my interactive story app was finally ready — installable on any Linux system. I felt extremely happy. Peer reviews went well, then my manager gave the green light to test in the real school setting.

Curiosity turns to fear

Eager and anxious, I presented the app to the school director. “Looks promising,” she said with a smile, “Let’s test it with the children and see how things will be” My heart thumped as teachers agreed to run the trial.

That night, sleep eluded me. Would the kids enjoy it? Had I made something meaningful? The next morning, I waited at the building’s ground floor, anticipation mounting, from as early as 7 am. When teachers finally arrived, they greeted me with grins

“Bibin, you’ve done a great job! We loved your illustrations, the interactivity, even the story.”

My heart soared. But then came the softly spoken “but…”

The hard truth

“But, Bibin, there’s something you should know,” a teacher continued, her voice gentle but firm. “Our children understand things differently. Some grasp the idea of a friend, but not what a ‘best friend’ means. Some follow the app’s steps, others cannot. Every child is unique — one solution does not fit all. Inclusivity is more nuanced than you think.”

I was recapping- what our school director said initially, “ let’s see how things will be”.

Then teacher nodded, “You should’ve come to see the classroom first. To watch, listen, ask. Then design.”

I wanted to disappear. My efforts felt wasted — good graphics, creative code, but ultimately not usable for the children I sought to help. My “successful” launch was a failure.

The spark of growth

That meeting became the spark for my journey as a user experience designer. I learned — starkly — that creativity and technology mean little without deep empathy for end users. My error wasn’t technical; it was in making assumptions and designing in a vacuum.

I realised that the heart of UX design was understanding real needs, not imagined ones. My failure shaped me in ways a polished launch never could. It was my first true lesson in product design: The most meaningful solutions begin, always, with listening.

Reflection

Looking back, “Best Friend” wasn’t just the name of the story I built — it was also the failure that befriended me with empathy, humility, and the lifelong commitment to design with users, with right understanding.

In the age of technology, it’s no secret that sustainability and environmental consciousness are becoming increasingly important. As companies and individuals alike strive to reduce their carbon footprint and promote eco-friendliness, the role of UX designers is more crucial than ever. With their expertise in creating efficient and user-friendly interfaces, UX designers are uniquely positioned to help shape the future of green IT. In this article, we’ll take a closer look at why UX designers are key players in the movement towards sustainability in the tech industry. We’ll explore how their skills can be utilised to create more eco-friendly products and services, as well as the challenges and opportunities that lie ahead in this exciting field. So buckle up, and let’s dive into the world of green IT and UX design!

What is Green IT and why is it important?

Green IT, also known as sustainable or eco-friendly IT, refers to the practice of designing, producing, and using technology in an environmentally responsible manner. This includes everything from reducing energy consumption and using renewable resources to minimising e-waste and carbon emissions. The importance of green IT cannot be overstated, as the tech industry is one of the fastest-growing and most resource-intensive sectors in the world. According to a report by the Global e-Sustainability Initiative (GeSI), the tech industry accounts for approximately 2% of global greenhouse gas emissions, and this number is expected to rise as digital technologies continue to expand.

The good news is that there are many ways to promote sustainability in the tech industry, and UX designers are uniquely positioned to help. By designing interfaces that are intuitive, efficient, and user-friendly, UX designers can help reduce energy consumption, minimise waste, and promote sustainable behaviour. For example, by creating interfaces that encourage users to turn off their devices when not in use, or by simplifying complex processes to reduce the amount of time and energy required to complete a task, UX designers can make a significant impact on the environment.

Role of UX Designers in Green IT

So what exactly is the role of UX designers in green IT? Put simply, UX designers are responsible for creating user experiences that are both effective and efficient. This means designing interfaces that are easy to use, intuitive, and visually appealing, while also minimising the amount of time and energy required to complete a task. In the context of green IT, this means designing interfaces that promote sustainable behaviour and reduce environmental impact.

In addition to promoting sustainable behaviour, UX designers can also help reduce energy consumption and minimise waste through the use of efficient interfaces. This includes designing interfaces that are optimised for low-power devices, such as smartphones and tablets, and that minimise the amount of data and processing required to complete a task. By doing so, UX designers can help reduce the energy consumption of the devices themselves, as well as the servers and other infrastructure required to support them.

Benefits of integrating UX Designers in Green IT initiatives

The benefits of integrating UX designers in green IT initiatives are numerous. First and foremost, UX designers bring a unique perspective and skillset to the table that can help drive sustainable innovation in the tech industry. By focusing on the user experience and designing interfaces that promote sustainable behaviour, UX designers can help reduce energy consumption, minimise waste, and promote eco-friendliness in a way that is both effective and engaging.

Another benefit of integrating UX designers in green IT initiatives is the potential for cost savings. By designing interfaces that are more efficient and streamlined, UX designers can help reduce the amount of time and energy required to complete a task, which can translate into significant cost savings for both individuals and organisations. In addition, by promoting sustainable behaviour, UX designers can help reduce the environmental impact of the tech industry, which can have both social and economic benefits in the long run.

Finally, integrating UX designers in green IT initiatives can help promote brand loyalty and reputation. As sustainability becomes an increasingly important issue for consumers and stakeholders, companies that prioritise eco-friendliness and environmental responsibility are likely to be viewed more favourably. Designing interfaces that promote sustainable behaviour and reducing their environmental impact, companies can demonstrate their commitment to sustainability and build stronger relationships with their customers and stakeholders.

Challenges faced by UX Designers in Green IT

While the potential benefits of integrating UX designers in green IT initiatives are significant, there are also many challenges that must be addressed. One of the biggest challenges is the need to balance user experience with sustainability. In some cases, designing interfaces that promote sustainable behaviour may be at odds with designing interfaces that are easy to use and visually appealing. UX designers must therefore find ways to strike a balance between these competing priorities and create interfaces that are both effective and engaging.

Another challenge is the need to work within the constraints of existing technology and infrastructure. In many cases, the technology and infrastructure used by organisations may not be optimised for sustainability, which can limit the effectiveness of UX design interventions. UX designers must therefore find ways to work within these constraints and make incremental improvements that can help promote sustainability over time.

Finally, there is the challenge of measuring the impact of UX design interventions on sustainability. While it is relatively easy to measure the impact of interventions on user behaviour and engagement, it can be more difficult to measure the impact on sustainability outcomes, such as energy consumption and waste reduction. UX designers must therefore find ways to develop metrics and evaluation frameworks that can accurately measure the impact of their interventions on sustainability.

How UX Designers can overcome these challenges

To overcome these challenges, UX designers can employ a range of techniques that are specifically designed to promote sustainability in the tech industry. One such technique is the use of design thinking, which involves a human-centered approach to problem-solving that prioritises user needs and perspectives. By using design thinking, UX designers can gain a deeper understanding of the needs and motivations of users, which can help them create interfaces that are both effective and sustainable.

Another technique is the use of data analytics, which can help UX designers identify patterns and trends in user behaviour that can inform the design of more effective and sustainable interfaces. By analysing data on energy consumption, waste generation, and other sustainability metrics, UX designers can gain insights into how users interact with technology and identify areas where improvements can be made.

Finally, UX designers can leverage the power of collaboration to overcome the challenges of promoting sustainability in the tech industry. By working closely with stakeholders across the tech industry, including engineers, product managers, and sustainability experts, UX designers can develop more effective and sustainable solutions that are grounded in a deep understanding of user needs and perspectives.

Conclusion

In conclusion, the role of UX designers in green IT initiatives is more important than ever. By designing interfaces that promote sustainable behaviour and reduce the environmental impact of technology, UX designers can help shape the future of the tech industry and promote a more sustainable and eco-friendly world. While there are many challenges that must be addressed, including the need to balance user experience with sustainability and work within existing technology and infrastructure, UX designers have a range of techniques at their disposal that can help them overcome these challenges and drive sustainable innovation in the tech industry. So let’s embrace the power of UX design and work together to create a more sustainable future for all.,