Learning to See the Whole System

Learning to See the Whole System

I did not learn systems thinking from a diagram.

I learned it on a factory floor.

The journey began years earlier, when I was sixteen and discovered that business made sense to me in a way few subjects did. I was fascinated by how value was created why people chose one product over another, how trust influenced decisions, and how a business transformed an idea into something people were willing to pay for.

Yet when it was time to choose a career, another world was calling me: design.

I dreamed of working at Condé Nast. I imagined creating work for the magazines I admired and perhaps, one day, working in the orbit of Anna Wintour. I studied graphic design and eventually created work for globally recognized publications and brands, including ELLE DECOR, Vogue, GQ, Architectural Digest, Condé Nast Traveller, and the Vogue Wedding Show.

In many ways, I had arrived exactly where my younger self had hoped to be.

I was surrounded by beautiful photography, celebrated brands, and opportunities to create. I learned to develop visual concepts, tell stories through design, and adapt ideas across campaigns and platforms.

I enjoyed the work, but beneath that enjoyment was a question I could not silence:

What happened after the design left my screen?

Did someone act because of it?
Did it solve a meaningful problem?
Did it build trust?
Did it generate revenue?
Did it make something difficult easier?

I no longer wanted only to make things look compelling. I wanted to understand whether they worked.

That restlessness eventually led me away from the world I had once dreamed of entering and toward a place I never imagined would transform me: a small manufacturing business in my hometown.

The company produced flexible veneers for international B2B customers. It had limited brand materials, no established design system, and a basic website that neither answered customers’ most important questions nor generated meaningful leads.

I joined as the company’s only designer.

I arrived expecting to design.

Instead, I discovered how little I knew.

I could not responsibly communicate the value of a product I did not understand. I could not design a useful website without knowing how customers evaluated the material, how the company fulfilled an order, or what could go wrong between an initial inquiry and a successful delivery.

So, before opening my design software, I was told to step onto the factory floor.

For the next two months, the business became my classroom.

I worked alongside the people manufacturing the veneers and learned how the material was made. I observed the process, asked questions, and began to understand the skill and variability involved in producing something by hand.

Then I moved to the warehouse.

The company offered more than 46 product varieties, each with its own name, appearance, properties, and applications. I learned how they were classified, how they differed, and how they were stored.

From there, I followed the product into packing and logistics.

Because each sheet was produced individually, shipments could vary in weight. That variation affected packaging, freight calculations, delivery costs, quotations, and customer expectations. I learned which materials protected the products, how different orders were packed, and what was required to transport them safely across countries and continents.

Every answer revealed another dependency.

A product decision affected packaging.
Packaging affected weight.
Weight affected freight.
Freight affected the quotation.
The quotation affected the customer’s decision.

What appeared to be a simple product was part of an interconnected system.

Eventually, I reached the sales office the place where these operational realities met the customer.

I sat with the sales team and listened. I studied how they introduced an unfamiliar product, which questions customers repeatedly asked, what caused hesitation, and what information helped people feel confident enough to buy.

I then travelled to international trade shows, where I could observe customers encountering the product for the first time.

That experience changed me.

Only a small percentage of the target market understood what flexible veneer was. Customers touched it, bent it, questioned its durability, and tried to imagine how they might use it. Their confusion was not resistance. It was evidence that we had not yet explained the product in a way that connected with their world.

Because only a few people in the company spoke English fluently, I began communicating directly with customers from China, Dubai, Switzerland, France, Hungary, and other international markets. I listened to their concerns, answered technical questions, and learned how expectations varied across customers, projects, and regions.

As my understanding grew, so did my role.

I learned about quotations, negotiations, international commercial terms, shipping bills, accounting processes, letters of credit, and cross-border payments. I worked with banks to understand how international customers could pay us and with shipping providers to determine how freight should be calculated. Whenever a decision affected another part of the business, I consulted the people closest to it from manufacturing and packing to logistics, sales, and marketing.

There was no large product team waiting to translate this complexity into a neat set of requirements. We did not have product managers, researchers, or business analysts assigned to define the experience.

I had to help create that clarity.

I gathered information from customers and employees, traced how decisions moved across departments, identified gaps, documented requirements, and returned to the relevant teams to validate my understanding.

Then I translated what I had learned into an e-commerce experience.

I hired and collaborated with an external development team, coordinated content and operational inputs, and led the website work from discovery through execution. The website could not simply display attractive photographs. It had to explain an unfamiliar material, anticipate customer questions, communicate technical information, support international purchasing decisions, account for complex shipping conditions, and earn the trust of buyers who might never visit our factory.

Every screen represented decisions made far beyond the screen.

The product information came from the factory.
The language reflected customer conversations.
The purchasing journey reflected the sales process.
The payment experience depended on banking requirements.
The shipping logic depended on packaging, weight, and geography.

I began the journey believing my responsibility was to design a website.

I came to understand that I was designing the digital expression of an entire business.

Over five years, I grew from the company’s sole designer into someone who could work across design, sales, marketing, manufacturing, logistics, and international business. I participated in high-stakes customer conversations and contributed to the negotiation of a ₹4 crore agreement with a Chinese buyer.

But the greatest outcome was not a website or even a commercial agreement.

It was a new way of seeing.

Years later, I discovered names for many of the things I had learned to do instinctively. Working beside employees in their environment was contextual inquiry. Listening to customers was user research. Following an order across departments was journey mapping. Translating operational knowledge into requirements was product discovery. Understanding how one decision affected manufacturing, sales, payments, logistics, and the customer experience was systems thinking.

I had not known the vocabulary.

But I had learned the practice.

That experience taught me that meaningful design rarely begins with a screen. It begins with curiosity and the humility to enter an unfamiliar world, listen to the people who understand it, and remain there until its hidden connections become visible.

A digital product is never only a digital product. Behind it is a living system of people, incentives, processes, constraints, promises, and consequences. If we design only what appears on the screen, we risk solving the most visible part of the problem while ignoring everything that created it.

I once believed I had left business to pursue design.

In reality, my career was guiding me toward the place where the two meet.

The factory floor, the warehouse, the sales office, the trade-show conversations, the shipping documents, the negotiations, and the e-commerce platform were all part of the same education. They taught me to move beyond creating what looks right and begin asking what works, for whom, and within what larger system.

People often say that business cannot be fully learned inside a classroom.

I understand that now.

Some of my most important lessons came without lectures or textbooks. They came from workers explaining their craft, customers revealing their doubts, teams articulating their constraints, and real decisions carrying real financial consequences.

I entered that company as a designer who wanted her work to create an impact.

I left knowing how to find the system behind the design.