They came together to confront the most pressing challenge facing the world.

Not geopolitics.
Not economics.
Not technology.
Not climate change.

It was silos. and it was there as a part of deliberate design - what if we did not want to remove the silos? what if they were there for a reason?

Across industries, across nations, across institutions—the same pattern kept surfacing.

People, teams, and systems highly capable in isolation, yet unable to operate effectively together.

The constraint was not intelligence.
It was not resources.

It was fragmentation.

Humanity will survive this—as it has survived every era before.

But the real question is not survival.

It is cost.

How much potential is lost?
How much progress is delayed?
How much value quietly erodes—simply because we fail to function as one?

Chapter 1 — The Energy Before Structure

The session did not begin with theory. It began with observation. As the room settled, there was already movement—small clusters forming, side conversations happening, uneven attention across the space. Some participants were engaged, others distracted, a few preoccupied with something as simple as breakfast. What could have been dismissed as noise was instead reframed as signal.

The facilitator pointed directly at this. Not to correct it, but to highlight it. The room was already demonstrating the reality of teamwork: uneven energy, fragmented focus, informal groupings. Before any formal definition of “team” was introduced, the participants were already living inside its complexity.

This set the tone. The session would not be about idealized models. It would be about reality—messy, inconsistent, and human.

Instead of moving into frameworks, the facilitator shifted the lens. The topic was not operational excellence, as some expected. It was something more foundational: how people actually work together. The decision to focus on teamwork was not incidental. It was corrective. Because most teams fail not at execution, but at interaction.

The structure of the session was outlined simply: understand what a X-functional team is, explore why it matters, identify what makes it durable, and finally confront how to make it work in practice. But even in this structure, there was an implicit warning—this would not be a surface-level discussion. It would require going beneath roles and into behavior.

Before any definitions were given, the facilitator made one thing clear: many people talk about X-functional teams as if they understand them. In reality, for most, it is just language. A label. Meetings across departments. Conversations without consequence. The word exists, but the substance is missing.

The session would attempt to close that gap.

Chapter 2 — Trust as the Hidden Foundation

The first real question was not about teams. It was about trust.

“Have you trusted someone? And has that trust been broken?”

The shift was deliberate. Instead of asking participants to define teamwork, the facilitator asked them to recall something personal. Almost everyone had experienced trust being broken—personally or professionally. Many had even reached the point of deciding not to trust again.

This was not framed as weakness. It was framed as conditioning. People are taught, often from a young age, to be cautious, to protect themselves, to distrust. These lessons accumulate over time and eventually become default behavior in professional environments.

The group was then asked a simpler question: “What is trust?”

The answers came quickly—transparency, honesty, reliability, belief. On the surface, these seemed aligned. But when tested against reality, the alignment broke down. When participants were asked to rate how much these qualities actually existed in their teams, the scores dropped significantly. Transparency was partial. Honesty was low. Reliability fluctuated. Belief was uncertain.

The contrast was immediate and uncomfortable. People knew what trust should look like, but they were not experiencing it consistently.

This gap became the central insight.

Trust is not a concept problem. It is an execution problem.

Further, not all aspects of trust are equal. Some elements—like transparency and reliability—can be observed and measured. Others—like honesty and belief—are subjective, shaped by perception and personal interpretation. This creates friction. Two people can operate with the same intent but arrive at completely different judgments about trust.

In a team environment, this becomes amplified. Misalignment is not always about disagreement. Often, it is about different internal definitions of what is acceptable, what is true, and what is reliable.

The facilitator illustrated this with a personal example: long-standing relationships where perception diverged over time. Even after years of familiarity, people could hold conflicting views of each other. Not because of facts, but because of interpretation. His Professor on Industrial Psychology had once said - Familiarity infact breeds contempt. So the deeper you think you know them - the more you take for granted.

This is the same dynamic that exists inside teams.

Trust is not binary. It is layered, unstable, and constantly renegotiated.

And without addressing it, no structure—no matter how well designed—can function effectively.

Read More on Trust on some of the social experiments done

Mindset First (The Edu-Whiz)

S1.C45 — TRUST - a journey of awareness and response

Read more

3 months ago · 1 like · 2 comments · Fundamental Decisions

Chapter 3: When Teams Meet Reality

Once the group aligned on what trust should look like, the consultant shifted the room into discomfort—toward reality.

He began probing experiences.

Not theory. Not frameworks. Real situations.

The responses came quickly.

One participant described a familiar tension: one department pushing in one direction, another pulling in the opposite. There was no alignment, only parallel intent.

Another highlighted something more subtle but equally destructive: too many voices. Not disagreement—but an inability to converge. Consensus became an endless loop.

A third experience cut deeper. Being placed in a new environment, working across teams, but never fully accepted. The label was unspoken but clear—outsider.

These were not edge cases. They were patterns.

The consultant did not interrupt. He allowed the accumulation.

What emerged was not a list of problems—it was a map of friction:

• Misalignment of goals

• Fragmented communication

• Identity barriers

• Lack of ownership clarity

• Decision paralysis

At this point, something important became visible.

None of these were structural issues.

Every participant was technically part of a “team.” Roles existed. Meetings happened. Tasks were assigned.

Yet, the experience of working together was broken.

This is where the session quietly shifted.

From “what is a x-functional team” to:

Why do they consistently fail despite being correctly formed?

Chapter 4: The Hidden Cost of Disconnection

Instead of answering directly, the consultant told a story.

Not about corporations or processes—but about a village in the mountains near Hanoi.

At first glance, it had everything: natural beauty, cultural depth, and a headline attraction—the longest glass bridge in the world.

Yet something was off.

Tourists arrived, lingered briefly, and left. The place felt hollow. The potential was visible—but not experienced.

Then night came.

The same village transformed. A market came alive—hundreds gathering, drawn into games, music, movement. Energy surged through the space.

Two realities coexisted:

Untapped potential by day.
Explosive vitality by night.

The question was unavoidable: why?

The answer wasn’t infrastructure. It wasn’t funding. It wasn’t capability.

It was fragmentation.

The village was divided across three distinct ethnic groups. Each functioned well within itself—but not with the others.

Projects were introduced, but executed in silos. Even when groups were mixed, collaboration remained surface-level. Coordination existed. Integration did not.

There was no shared ownership. No collective identity. No unified intent.

The consequence was not abstract.

It was measurable—an estimated $50 million in lost value annually.

Not because the opportunity wasn’t there.

But because the system could not operate as one.

The consultant paused.

The point had landed.

This was not a story about a village.

It was a mirror.

Organizations behave the same way. Teams perform within boundaries but fracture across them. Capability exists—but coherence does not.

And the cost remains hidden—until it compounds.

This is not just stagnation. It is regression.

When systems fail to integrate, they don’t hold steady—they decay. Trust erodes. Alignment weakens. Effort fragments.

The natural state is not collaboration. It is division.

Which raises the real question:

Why is it so difficult to work as one?

Structure alone cannot solve this. It can arrange people—but it cannot align them.

What’s required is deliberate design:

Design of trust.
Design of ownership.
Design of interaction.

A participant finally asked, “So how do we see this clearly?”

The consultant nodded.

“Use a system that makes consequences visible.”

He pointed to the DuPont Analysis—developed in the 1920s. One of the crudest system.

“Not 2.3,” he added, glancing at the room. “Sounds the same when you say it fast”

A brief pause. A few laughs.

“Every decision you make doesn’t act locally. It rolls through the system—changing margins, efficiency, and returns in different ways.”

He paused again.

“When you can see how value is created—and where it breaks—you stop managing parts.”

“You start managing the whole.”

Chapter 5: Beyond Structure — Toward Real Collaboration

With the story anchored, the session returned to the room.

The earlier examples now carried more weight.

Misalignment was no longer a minor inconvenience—it was a structural risk.

Lack of clarity was not just confusion—it was wasted capacity.

Being an outsider was not just uncomfortable—it was a barrier to contribution.

The consultant began drawing threads together.

A X-functional team, in theory, is simple: bring together different functions to achieve a shared goal.

But in practice, it demands something far more complex.

It requires individuals to operate beyond:

• Their functional identity

• Their personal biases

• Their historical experiences of trust

This is where most teams break.

Not because they cannot collaborate.

But because they choose not to fully engage across boundaries. Comfortable in our own shoes.

The earlier trust exercise now returned with new meaning.

Transparency, honesty, reliability, belief—these were not abstract values.

They were operational requirements.

Without them:

• Information is filtered

• Intentions are questioned

• Commitments are doubted

• Decisions are delayed

And slowly, silos reform—even within “X-functional” structures.

The consultant emphasized one critical shift:

That difference includes:

• Conflicting priorities

• Different success metrics

• Varied communication styles

• Unequal power dynamics

Managing this is not a process problem.

It is a behavioral one.

Toward the end, the focus moved toward implementation.

Not everything can be fixed at once. The instruction was clear:

Pick one or two elements. Make them work. Build from there.

Because sustainability—what he referred to as “stickiness”—does not come from theory.

It comes from repeated, consistent behavior.

Closing Reflection: The Real Work of Breaking Silos

The session began with energy—casual conversations, informal interactions, natural engagement.

Ironically, that initial moment reflected the very thing organizations struggle to create intentionally.

As the session unfolded, it became clear that breaking silos is not about introducing collaboration.

It is about removing the barriers that prevent it.

The participants did not leave with a checklist.

They left with something more uncomfortable—and more useful.

A recognition that:

• Trust is fragile and often low

• Alignment is harder than assumed

• Collaboration exposes underlying human dynamics

And most importantly:

Structure alone does not create teams.
Behavior does.

The village in the mountains, the disconnected departments, the outsider experience—all point to the same conclusion.

Cross-functional success is not built on intention.

It is built on the willingness to engage, to align, and to trust—despite past experiences suggesting otherwise.

That is the real work.

And it does not happen in a workshop.

It happens after.

Mindset First (The Edu-Whiz)

S1.C47 — Decision Making

This article centers on decision-making as a function of mindset, bias, learning capacity, and strategic judgment. It argues that most decision failures are not due to lack of tools, but due to psychological and behavioral constraints that distort how individuals interpret information and act on it …

Read more

3 months ago · Fundamental Decisions

Participants left the session with a stronger sense of clarity and ownership.

They better understood:

• The purpose and value of X-functional teams in driving aligned, sustainable outcomes

• The distinction between project teams and X-functional teams

• Their own role using systems like RACI, recognizing they are always part of it

There was also increased awareness of:

• The importance of communication, clear roles, and collaboration

• The need to take greater accountability

• The role of X Teams in bringing energy and inspiration into the organization

Overall, the shift was from passive participation to a more informed, responsible, and engaged mindset, with underlying passion emerging.

A group of curious thinkers has taken up this challenge. They do not carry maps or compasses; instead, they carry questions. Why do businesses fail even when they appear to have resources? Why do supermarkets, with their supposed economies of scale, sometimes sell products at higher prices than small shops? Why is operational excellence so critical to survival? Why do people, even when they share the same vision, struggle to work together?

Their journey began in Vietnam and now continues in Indonesia. Along the way, two powerful metaphors have emerged to guide their thinking: the squeaky wheel and the silo cracker. These metaphors capture the essence of the obstacles they see again and again—the cracks in processes that erode value and the silos that block collaboration.

Instead of a dry conference or a standard workshop, the team designs their journey as an immersive adventure, with missions, challenges, and reflections. Over three days, participants step into character roles, confront inefficiencies, break silos, and build sustainable solutions. By the end, they don’t just learn new concepts—they carry home mindset reports that reveal their own traits and behaviors, showing them how to function at their best in complex ecosystems.

The Squeaky Wheel: Cracks in Process

Every organization has its squeaky wheels. They show up as recurring problems that demand attention: a shipment that is always delayed, a supplier who never delivers on time, a machine that breaks down every few weeks, a customer complaint that refuses to go away. At first, the squeak seems small. Someone patches it up. A manager approves overtime. Extra resources are thrown at the problem. For a while, the squeak goes quiet.

But then it returns. Again and again. Until eventually, the squeak becomes part of the rhythm of the business. Business Leaders stop asking “Why does this wheel keep squeaking?” and start asking “How do we manage the noise?”

This is what the team calls cracks in the process. These inefficiencies don’t remain isolated—they spread. A textile workshop in Vietnam wasted fabric in production but shrugged it off as “the cost of doing business.” A food distributor lost a third of its produce to spoilage but accepted it as unavoidable. A mid-sized manufacturer in Indonesia repeatedly failed to meet delivery deadlines, layering supervisors and buffer stocks to mask the issue rather than fixing its scheduling cracks.

The tragedy is not only financial but cultural. Once inefficiencies are normalized, they fade into the background—no longer seen, no longer questioned. The urgency to fix them disappears. Over time, they silently erode capability, shrink margins, and undermine trust. The end result is an ecosystem unable to achieve the structure needed for lift-off, leaving communities and industries decades behind their true potential.

But here lies the insight: the squeaky wheel is not a nuisance to be managed; it is a signal to be decoded. Each squeak reveals where capability is missing, where processes are weak, and where growth is possible. Treating inefficiency as a teacher—rather than a shame to be hidden—is the first step to resilience.

The Silo Cracker: Breaking Invisible Walls

If squeaky wheels represent cracks in process, silos represent the walls people build around themselves. Silos are not always physical or structural. Often, they are invisible—psychological, cultural, or political.

Farmers sell produce separately, losing bargaining power, even when joining forces could strengthen them all. Departments within the same company hoard information, fearing loss of control, even when sharing data could accelerate innovation. Logistics providers, distributors, and retailers fail to coordinate, leaving farmers with unsold crops rotting in the fields.

The result? Potential gets trapped. Knowledge stops flowing. Collaboration stalls. Opportunities slip away. While AI steadily builds collective intelligence, we fail to recognize the strengths in one another. Instead, we fixate on weaknesses, and from fear arises our tendency to compartmentalize. In doing so, we limit our true potential and fracture the very synergy that could propel teams and ecosystems forward.

The team calls this section the silo crackers because they believe the first step to sustainability is breaking these unnecessary walls. In Vietnam, they watched how small producers—once locked in fierce competition—learned to collaborate. Farmers pooled resources, cooperatives formed, and distribution improved. Each member retained independence but gained strength from shared effort.

Silo cracking is not about flattening diversity or forcing artificial unity—it’s about weaving strengths together. Where one actor is weak, another may be strong. Each member is unique; the challenge lies in fitting those pieces together. When the best of each is added into the collective equation, the entire ecosystem rises.

So how do we begin? Where does the journey start? Here’s the blueprint of an adventure—one you’re welcome to explore, should you choose to step in.

Click the image to explore the Team FD website — or simply continue reading below

Day 1: The Broken Map

In Indonesia, the program begins with arrival, check-in, and character selection. Participants don’t just register names; they choose roles—entrepreneur, supplier, distributor, regulator, or customer. This immersive role-play ensures that when they face challenges, they see them from multiple lenses.

The welcome briefing sets the tone: “Every business has cracks in its map. Our job is not to hide them but to find them.”

The first mission, The Broken Map, confronts participants with a simulated business ecosystem riddled with inefficiencies. Logistics collapse, communication falters, resources leak value. Their task: diagnose the inefficiencies, listen to the squeaky wheels, and uncover deeper issues.

Midway, a Mystery Divergence Card is drawn. It introduces AI-driven scenarios, forcing participants to confront the paradox: machines learn from negatives, but humans tend to cover them up. Do they trust AI, resist it, or blend it carefully with human judgment?

The day ends with evening reflection, where participants share: What squeaks did we find? Why do we normalize them in real life?

Day 2: The Twist & The Truth Map

The second day is about building. If Day 1 diagnosed cracks, Day 2 designs solutions. The mission is called The Twist & The Truth Map.

Teams must redesign the ecosystem, transforming inefficiencies into strengths. The silo cracker metaphor comes alive: no single role can solve problems alone. Entrepreneurs need suppliers, distributors need regulators, and everyone needs trust.

A mid-level boss challenge interrupts: Interdependency Thinking. Teams must merge heritage (local wisdom and traditions), AI (technology), and innovation (new models) into one coherent system. They learn that sustainability is not about replacing the old with the new but weaving them together.

The day ends with a celebration dinner and awards ceremony, where creativity, courage, and collaboration are recognized. The message is clear: cracking silos creates strength.

Day 3: The Final Mission

The final day is the climax. The final mission challenge demands that participants bring everything together—diagnosing inefficiencies, breaking silos, and blending heritage, AI, and innovation—into one coherent design. The goal: a sustainable and scalable business model.

The tension is real. Some solutions look brilliant on paper but collapse under questioning. Others, simple and unpolished, reveal deep sustainability potential. Teams must wrestle with trade-offs: short-term profit versus long-term resilience, control versus collaboration, efficiency versus inclusivity.

By the closing ceremony, the lesson is clear: sustainability is not an abstract SDG or a corporate slogan. It is the lived practice of fixing squeaky wheels and cracking silos—day after day, decision after decision.

Departure comes in the evening or the next morning. Yet participants leave not only with memories but also with personal mindset reports—detailed reflections captured across traits essential to their roles. These reports become mirrors, showing them how they handle inefficiencies, how they collaborate across silos, and how they can function at their very best in real business ecosystems.

And for those who choose to subscribe, these reports can continue to be evaluated and refined through activities for up to six months after signing in.

The Adventure Ahead

This three-day journey in Indonesia will be more than a workshop. It would be a story - a conversational journey—a lived metaphor. The squeaky wheel teaches us that inefficiencies are signals of growth, not inconveniences to be silenced. The silo cracker reminds us that true sustainability emerges when walls are broken and strengths are shared.

By turning the program into missions, challenges, and role-play, participants don’t just talk about sustainability—they experience it. And by receiving their mindset reports, they leave with something rare: a personalized compass for growth.

As they return to the real world, the true adventure begins. They carry with them two powerful tools: the courage to listen to the squeaks and the wisdom to crack silos. Together, these tools form the foundation of resilient, sustainable ecosystems. And, importantly, they also gain a deeper understanding of how technology—and AI in particular—can be harnessed to strengthen capabilities and accelerate growth.

Like all great adventures, this one doesn’t end at departure. It lives on—in every decision made, every collaboration sparked, every crack revealed, and every silo broken. After the three days, we remain connected virtually through technology.

Remember: technology and AI do not reject the negative—they learn from it. Yet AI cannot truly create something new; it is still learning to improvise. That means we still hold the edge in how it is used. And that is where our true responsibility begins: to improve ourselves while leveraging technology responsibly and sustainably, for the benefit of all connected ecosystems. Technology is only an enabler. The real engine—the true chip that powers the ecosystem—is in us - the human mind.

If you’re ready for a challenge—or if you want to improve your company’s performance, strengthen your team, or simply push yourself to the next level—we welcome you to join us on this journey.

To know more, contact our team in Indonesia:
📞 +62 813 5756 5429
📧 silvia@y-lab.co | mail@fundamentaldecisions.com

previous cases :

1. What surfaced when we really looked?
Beyond the views, the real story revealed itself—one detail at a time.

In a sleepy town in Asia, 14 local businesses paint a picture of a fragmented ecosystem—yet one brimming with untapped potential. This is the story of how D and his crew rallied a group of explorers to uncover the gaps, connect the dots, and reveal the hidden treasures buried within the system.

A. The Cafe Chronicles

In the quiet heart of Northern Vietnam lies Mộc Châu — a mist-draped town famous for its tea hills, homestays, and seasonal charm. But beneath the postcard surface, something was broken. Not just one thing — but a network of interlocking inefficiencies, siloed ambitions, and unrealized potential.

That’s where D and his crew stepped in - Cloudy, An, Cozy, Mason and Phuong Anh.

Armed with a tool they called “The Broken Map” — a set of special hint cards designed to detect operational cracks and mindset misalignments — the crew began their quiet excavation. Their target that day? A popular local coffee shop perched above the town.

What looked like a bustling hub on the outside was, in fact, a microcosm of larger issues. D’s team observed, interviewed, listened, and — most importantly — asked the questions no one else was asking.

Step 1: Unearth the Obvious
The first card flipped revealed the Staffing Dilemma. The café couldn't hold onto staff. Not because people didn’t want to work, but because no one saw this place as a long-term home. The seasonal nature of Mộc Châu’s tourism — low from May to September, high from October to April — left employees drifting in and out.

In high season, cafés scrambled. In low season, they vanished. There was no loyalty. No system. No structure. Just rushed survival.

Step 2: Follow the Cracks
The second card hinted at a deeper wound: Training Fatigue. Even when staff were available, owners had stopped investing in them. “What’s the point?” they said. “They’ll leave anyway.”

Without training, service became purely transactional — no warmth, no pride, no hospitality. The café didn’t just lose staff. It lost soul.

Step 3: Expose the Illusion
A third card landed: Community Mirage. Some cafés claimed to “engage the local community” — but it was surface-level. Hiring locals without equipping them. Organizing events without designing for impact. What looked like collaboration was really outsourcing, cloaked in convenience and probably with the hope that community sourcing would work.

Step 4: Map the Systemic Blind Spots
As they moved through other shops — a homestay, a barbecue café, a tea vendor — D’s team saw the same patterns:

• One-time investors treating cafés like ATMs rather than living businesses

• No process innovation: No QR codes, no ordering systems, poor layouts

• Misaligned capacity: Venues built for 300 people serving 3

• Minimalist visions with no operational depth: Style without substance

• Siloed behavior: Owners competing instead of collaborating, fearing shared events or bundled services

Step 5: Reveal the Core Questions
By the end of the mission, the Broken Map didn’t just reveal problems. It framed two core questions:

1. What will keep these businesses alive — and thriving — in the long run?

2. How can operational excellence be restored when even the ambition to improve feels lost?

As they packed up for the day, D turned back to the café — quiet again as rain started to fall. "There’s treasure here," he said, almost to himself. "But they’re digging in the wrong place. Or worse — they’ve stopped digging altogether."

And so once again the Broken Map stayed open, its final card waiting for someone brave enough to ask:
What if we built this town differently — not from capital, but from strategic pruning?

B. The Homestay Chronicles

It had all the makings of a perfect escape.

A wooden cabin by the water. Mist rolling off the hills like silk. Lanterns flickering in the breeze.
The kind of place you see on Instagram with the caption: "Lost in nature ✨."

But D wasn’t lost. Neither was his crew.

An, Mason , Cozy and Phuong Anh had arrived with a mission — and with the Broken Map tucked in D’s satchel, ready to unfold at the first crack in the façade.

What followed wasn’t a vacation.
It was a quiet investigation.

Step One: The Warning in the Wood

They hadn’t even dropped their bags when Cozy let out a yelp.
A nail, poking out from a weathered stair plank, had found its mark. A scratch, nothing major — but enough to remind them: beauty can be skin-deep.

Inside, the charm wore off fast.

The room? Cramped. No space for bags. One bedsheet for six people. No towels.
Phuong Anh squinted: “Are we camping… or checking in?”

And then the kitchen. Let’s just say even Captain Cloudy, usually unshakable, raised an eyebrow.
Dusty. Disorganized. Nothing labeled. “Where’s the water?”
“Maybe under the optimism,” muttered An.

Step Two: Snapshots Without Soul

From the outside, everything looked ready for a film crew.
But from the inside?

No rhythms. No rituals. No welcome card saying, “Here’s what to explore.”

D flipped over the first card on the Broken Map: “Built for the camera, not the human.”
Nailed it.

The team split up to explore the guest experience. Cozy followed a couple hoping to visit a nearby café. Closed. No notice.
Lin interviewed a guest wandering around. “There’s no guide, no map. I just… walk?”

It felt immersive — until you looked closer. Then it felt hollow.

Step Three: A Town That Didn’t Talk

One café didn’t know the guest came from a nearby homestay.
The homestay didn’t know the guest had planned to hike.
The hike group had canceled last-minute — and no one had told the guests.

There were no QR codes, no suggested routes, no activities posted on walls.
No partnerships. No playlists.
Just politely confused staff and politely disappointed guests.

And no one seemed to be asking the most obvious question:
“What would make this better?”

Step Four: A System Frozen in Season

Staff came and went like clouds in the valley.
“Just for the summer,” one smiled. “Then I’m off.”

The crew nodded — they’d heard this before.

Without consistency, there was no training.
Without training, no ownership.
Without ownership, no experience worth returning for.

During high season, the place was bursting at the seams.
During low season, it whispered like an empty shell.

The structure couldn’t flex. Couldn’t breathe. Couldn’t scale.
And still, the owners held tight to the hope that charm alone would carry them through.

Step Five: A Place Designed Without Dialogue

No guestbooks.
No surveys.
No “How did you hear about us?”

D opened the final card from the Broken Map deck:
“No questions being asked.”

It landed like a quiet thud on the wooden table.

The crew stood in silence, the sun dipping behind the hills.

This place wasn’t failing from lack of effort.
It was drifting from lack of design.
It didn’t need a better view. It needed a better strategy.

But Here’s the Twist...

Not all was lost.

The guests still came.
The photos still popped.
The potential still buzzed, just beneath the surface.

So the crew asked:

What if the owners here could flip the script?

What if cafés and homestays joined forces — shared their guest lists, cross-promoted events, bundled weekend experiences?

What if guests arrived to a welcome map, complete with:

• "3 Hidden Cafés You Can’t Miss"

• "Sunrise Yoga at the Waterfall"

• "Book a Local Photographer (Scan Here)"

• "Explore the Hmong Village with Our Guide, Ms. Thao"

What if feedback wasn’t feared — but invited?
What if the seasonal flow became a designed rhythm — with flexible staffing, community-sourced talent, and year-round micro-events?

What if every guest became an ambassador — not just for a homestay, but for an ecosystem?

Final Panel: The Broken Map Never Lies

As the crew packed their bags, Cozy looked out the window.

“It’s not a broken place,” she said. “Just an unfinished one.”

D smiled, tucking the Broken Map back into his coat.
“We came looking for cracks. We found building blocks.”

And as the fog rose again over the hills, the mission was clear:

Don’t just build spaces.
Design stories worth staying for.

read more for further details …

C. The Restaurant Chronicles

It was lunchtime, but something was off.

The town, despite its scenic charm and scattered signs of prosperity, felt… flavorless. Not in taste, but in identity.

So D and his crew — Cloudy, Cozy, Mason, An and Phuong Anh — pulled out the Broken Map again, this time flipping open the “Cuisine & Culture” quadrant.

Their mission: uncover why the restaurants here felt more like rooms serving food than spaces serving experience.

Act 1: The Search for Flavor

They started hungry — not just for food, but for something real. A local specialty. A family secret dish. A story on a plate.

But what they found was… generic.

Big spaces with no warmth. Cafés that looked like they were copied from Pinterest.
Menus that repeated the same five dishes, no matter where they went.
“Puncha?” Cozy asked one waiter. “Yes,” he nodded. “But we outsource it.”

An scribbled in his notebook:

"No house recipes. No regional signatures. No story. Just service."

Even when they found a roadside gem — a tiny local joint with fried grubs and wild herbs — the team had to rely on instinct, not signage or curation.
“There’s no way to know what’s authentic unless you stumble upon it,” said Lin.

Act 2: The Illusion of Hospitality

Some restaurants were clean. Polished, even.
But sterile.

There were no managers greeting guests. No warmth. No “welcome back!” moments.
Everything felt siloed, robotic, purely transactional.

One place had beautiful woodwork but no staff who could recommend a dish.
Another had outdoor seating and music — but no soul.
As Phuong Anh put it:

“They’re serving food. But they’re not hosting an experience.”

And worse — not one restaurant told them why they existed.
What they were proud of. What they were known for. Whats the speciality.

“Without story,” said D, “it’s just food to fill the belly.”

Act 3: Disconnected Dishes, Disconnected Futures

The team dug deeper.

Behind the kitchens, they discovered the staffing struggle:

Seasonal burnout.

No career path.

Family-run businesses where the next generation had already opted out.

One elderly couple admitted they were tired. “We’ve been cooking for years,” they said. “Our kids want city jobs.”

Worse yet, the restaurants weren’t part of a system. No linkages with local farms, homestays, or activity centers.
No QR codes. No vouchers. No events.
Everyone cooked in isolation.

“It’s a town of individual pots,” Cloudy remarked, “boiling without ever blending.”

Act 4: What’s Missing?

No seasonal menus.

No local chef stories.

No evening tasting tours, cooking classes, or cross-promotion with artisans.

No sense of place in the plate.

Even ingredients — like herbs and leaves — were poorly washed.
Presentation? Standard.
Specialty? Unclear.

“What is this town’s signature dish?” D finally asked.

Silence.

That was the problem.

Act 5: The Menu of Possibility

But D didn’t come just to critique. He came to imagine.

And so, the crew gathered around the table and flipped the Broken Map to its final card:
"How do we bring restaurants back to their life?"

Closing Panel: More Than a Meal

As the sun began to set, the team sat down for one last bowl of something warm — not because it was special, but because they knew it could be.

“There’s so much flavor here,” said Cozy. “They’ve just forgotten how to plate it.”

D closed the Broken Map, looked at the quiet restaurants around them, and smiled to the team - perhaps….. he replied.

“We’re not here to judge,” he said. “We’re here to ask one thing:
What if your next dish… was the beginning of a story worth coming back for?”

2. What are the opportunities for the ecosystem?

Mộc Châu's Tourism Revenue Reached $118 Million in 2023

According to official tourism reports, Mộc Châu’s economic impact in 2023 was substantial. The Mộc Châu National Tourism Area recorded approximately 2.5 million visitors, generating over VND 3 trillion in revenue — equivalent to $118 million USD.

This achievement positioned Mộc Châu as the leading tourism revenue generator in Sơn La province, contributing roughly 60% of the region’s total tourism income.

The $118 million figure represents the Gross Regional Domestic Product (GRDP) from tourism for the year, anchored in verified visitor numbers and expenditure metrics

1. Mindset & Ownership Gaps

Short-term thinking: Businesses operate with a survival mindset, especially during the low season. No vision for sustainability or long-term community growth.

Lack of pride or emotional investment: Staff (and sometimes even owners) treat their roles as stopgaps, not vocations. There's little intrinsic motivation to elevate the experience.

Abandoned ambition: Many owners have lost the will to improve, assuming change won’t be worth the effort.

2. Service & Experience Gaps

Transactional service, not hospitality: No greetings, no recommendations, no memory-making moments. Staff are not trained to host.

No rituals or emotional anchors: Whether in cafés, homestays, or restaurants, there’s no warmth, rhythm, or thoughtful welcome—just functionality.

Experience not designed: Beautiful settings are undercut by clunky flows, poor layouts, and awkward visitor journeys.

3. Product & Offering Gaps

No story behind the product: Menus are generic. Dishes lack local narrative. Rooms lack personalized touches. Everything blends into sameness.

Poor curation: Visitors can’t easily find unique, authentic experiences—they must stumble upon them.

Missed creative formats: No tasting menus, photo packages, activity kits, welcome maps, or curated itineraries to guide or delight guests.

4. Operational & Process Gaps

No guest journey planning: No signage, no QR codes, no guides, no shared schedules. Guests are left to figure things out themselves.

No systems for continuity: Staff turnover leads to constant retraining. Many places have no documentation, SOPs, or workflow systems.

No quality control: Inconsistency in cleanliness, food prep, customer handling—even basic amenities like towels or clean herbs are overlooked.

5. Community & Collaboration Gaps

Everyone is working alone: Homestays don’t know which cafés are open. Cafés don’t cross-promote treks. Restaurants don’t partner with farms or guides.

No shared platforms or joint offerings: There’s no ecosystem thinking—just isolated players missing out on synergies.

Fear of cooperation: Business owners fear losing competitive edge if they collaborate or share traffic.

6. Innovation & Design Gaps

Design without feedback: No guestbooks, no surveys, no data collection. No mechanism to hear from customers or evolve with them.

Stuck in seasonal traps: Businesses shut down mentally and operationally during low seasons, missing opportunities for deeper engagement.

No adaptive design: Spaces aren’t flexible to weather, group sizes, or activity types.

7. Cultural & Identity Gaps

No clear local signature: There is no flagship dish, experience, or ritual that anchors Mộc Châu in guests’ memories.

Surface-level “local flavor”: Local identity is often used decoratively—through visual aesthetics—but not embedded meaningfully in food, service, or storytelling.

Youth disengagement: The younger generation doesn’t see a future in these businesses and opts out of inheriting them.

In Summary:

The region isn’t broken—it’s disconnected.
Each business has potential, but without coordination, mindset shifts, and a shared narrative, they remain scattered. The true value lies in weaving them together.

3. How can we help the ecosystem ? Our Proposal

PROCESS - PEOPLE - TECHNOLOGY

While the gaps are many, so too are the hidden treasures. Beneath the surface of disconnection lies a vibrant ecosystem waiting to be awakened—not through massive investments, but through strategic alignment, storytelling, and community redesign.

Here’s what’s possible:

1. Transform Low Season into Loyalty Season

• Design seasonal experiences: Instead of shutting down emotionally during slow months, use this time for curated events—like mindfulness retreats, journaling workshops, rainy day rituals, or storytelling nights.

• Micro-seasons = micro-campaigns: Break the year into emotional chapters. Let each one carry a mood, a theme, a message.

• Bring in Mindfulness sessions for corporate tourists and educational bootcamps for the school holidays.

• Build local roots: Incentivize residents with midweek discounts, loyalty cards, and “locals-first” previews.

2. Activate Experience-Driven Hospitality

• Train staff as storytellers, not servers: Every member becomes an ambassador for the region—able to share history, recommend hidden spots, and create warmth.

• Curate not just service, but memory: From photo-print stations to welcome cards, craft moments that people share—and remember.

• Design flow, not just space: Improve physical layouts and guest journeys so they feel intuitive, seamless, and cared-for.

3. Build a Shared Identity & Destination Narrative

• Create a regional signature: Develop a flagship drink, dish, or ritual that defines “the taste of Mộc Châu.”

• Curate discovery trails: Bundled café + homestay + hike + local art tours. Let guests experience the town as a story, not a series of dots.

• Design “Welcome Maps” for every guest: QR codes, printed mini-guides, suggested itineraries—turn every check-in into an onboarding moment.

4. Foster Collaboration Between Business Owners

• Build an alliance, not a marketplace: Homestays, cafés, restaurants, and artisans can co-create bundled experiences and shared calendars.

• Cross-promotion channels: Cafés can offer discounts for guests from partner homestays. Restaurants can promote local events. Everyone wins when guests move smoothly between touchpoints.

• Host townhall-style ecosystem meetups: Monthly co-learning or co-design sessions help break silos and build shared strategy.

5. Strengthen the Next Generation’s Role

• Youth-led experiences: Let young locals design their own weekend tours, lead storytelling walks, or run pop-up drink counters.

• Create micro-apprenticeships: Train teens and students in hospitality, digital marketing, and sustainable tourism through real-world engagement.

• Build ownership pathways: Offer revenue-sharing for staff-led innovation, turning jobs into entrepreneurial journeys.

6. Embrace Technology for Visibility & Feedback

• QR codes & digital storytelling: Let every product, drink, or flower garden tell its story digitally—via short videos, voice notes, or photo archives.

• Feedback loops = growth signals: Use simple guest surveys, review prompts, and data dashboards to continuously evolve.

• Build an online brand for the region: Not just listings—but curated content that captures the heart of Mộc Châu in images, words, and guest stories.

7. Reframe Hospitality as Healing

• In an age of noise and burnout, Mộc Châu offers something rare: stillness.
  Frame the region not as a tourist stop—but a space for renewal.

Let cafés become sanctuaries.
Let homestays feel like a hug.
Let meals be served with stories.

To know more on how we can help with the transformation,

Break Silos. Fix Processes. Unleash Potential.

Join the Order of Divergence in a transformative 3-day immersive experience designed to challenge norms, rebuild collaboration, and drive operational excellence.

Set in the scenic hills of Mộc Châu, this isn’t just a workshop — it’s a mission-based adventure. You’ll assume character roles, battle bureaucracy, decode inefficiencies, and co-create solutions with fellow changemakers.

Register here

B. DAILY JOURNALING

1. DAY 1 - 11 Jul, 2025: The Squeaky Wheel

1.1 When the Rain Falls, the Game Begins

At 6:00 a.m., under a drizzle that refused to quit, a handful of dreamers huddled in Mộc Châu to begin something that barely looked like a “program.” With the clouds low and doubts high, the first words weren’t about grand plans or deliverables—they were about why anyone was still here.

The room was half-filled, the energy uncertain, and the mission unclear—except to one person. "I would rather that you stay back here," DAV79 began. "Let them be ground." This wasn’t a motivational speech. It was a surrender to grit, not glory. The show, as he said, must go on.

1.2 Redefining the Purpose: It Was Never Just a Workshop

Lin91 almost didn’t come. She thought it might be a waste of time. Cloudy was adrift, unsure how to steer a ship with almost no sailors. But somewhere between the unfinished plans and scattered expectations, something began to crystallize: this wasn’t about a perfect workshop. It was about building resilience from scratch.

The real objective wasn’t financial. The bootcamp wasn’t about profit—it was about building capability, courage, and a new community of changemakers. And that mission couldn’t be paused just because the weather said no.

What emerged next was a raw and honest reset. “I've been running this bloody show for eight years,” he admitted, voice laced with exhaustion. “If I stop, I die.” This wasn't metaphor—it was purpose made flesh. Because when your work becomes your oxygen, stopping isn’t rest—it’s erasure.

He spoke of fatigue, of carrying burdens that felt too big. But he also spoke of faith—in experiments, in young minds, in trying even when outcomes are unclear. This wasn't a business training. It was a lab for human potential.

The true mission revealed itself: to build a tighter, smarter, more useful team. A team capable of going beyond plans and deliverables—one that could adapt, problem-solve, and evolve under pressure. The bootcamp wasn’t designed to showcase skills. It was meant to sharpen them.

This wasn’t about a successful event. It was about building resilient humans.

1.3 What is “problem” and Why Start With the Problem?

“You must want something in order for it to be a problem.”

This became a philosophical anchor for Day One. The first task wasn’t to solve—it was to identify the problem. Because without a clear understanding of what’s broken, how could you ever hope to fix it?

Participants began by asking:

• What do I want?

• Why don’t I have it?

• What stands in the way?

Even abundance was revealed to be problematic. Comfort, when unchecked, leads to entitlement. As one shared, “Too much sugar can still kill you.” Entitlement deadens curiosity. It disconnects people from struggle—and struggle is the birthplace of transformation.

So the challenge was laid out clearly: don’t just solve the problem. Understand it, name it, and own it.

1.4 The concept of “Kintsugi” from Japan: Fixing the Cracks with Gold

In a quiet moment of reflection, DAV79 recalled a story about his father, a man who kept old screws for years just to one day fix something right. “If something is broken,” his father used to say, “make it better.” And maybe, that’s the ultimate mission of Divergence—to turn breaks into beauty, wounds into wisdom, and lost paths into gold-threaded maps of possibility.

This was echoed in the ancient Japanese philosophy of Kintsugi—the art of mending broken pottery with gold. In Kintsugi, the cracks are not hidden; they are highlighted. They become part of the object’s identity, increasing its value rather than diminishing it.

The lesson was clear:

Fixing isn’t just about restoring function. It’s about elevating meaning.
Pain, when processed with care, becomes purpose.

This was the spirit the bootcamp demanded—not just to repair the businesses of Mộc Châu, but to repair how we see brokenness itself.

1.5 The Bootcamp’s Objective: What Does the Squeaky Wheel Need?

The metaphor for day 1 was simple: the squeaky wheel. A system that grinds, stutters, or stalls is crying for attention. But how do you know what it needs? Oil? A new part? A reinvention of the whole?

The bootcamp’s task was to explore:

• What’s squeaking in local systems and businesses?

• What makes things run?

• How can roles, synergy, and strategy come together to move beyond survival to transformation?

Each participant had to engage not just with local business case studies, but with themselves.

With 13 “broken maps” of local businesses ready for exploration, it was time to assign roles—not by expertise, but by character. And so, characters were assigned—not job roles, but archetypes:

• The Inspector – Notices cracks and blind spots

• The Tinker – Tries new tools, tests fixes

• The Challenger – Pushes boundaries and norms

• The Bridge Builder – Connects siloed groups

• The Diplomat – Smooths friction and encourages dialogue

• The Integrator – Seamlessly brings everything together

Everyone had to choose one. Not to define themselves, but to play it, to try it on. This wasn’t about fixed identities. It was about learning how to move differently.

Thirteen local businesses were handed over—each one imperfect, incomplete, a “broken map.” The mission? Dive in. Role-play. Identify the gaps. Build from the broken. But do it with care, with intelligence, and above all, with purpose.

And in between the tasks, came the lessons—unexpected, philosophical, and piercingly real.

What is a problem? Simply put: it is the gap between what we want and what we have. But sometimes, abundance is a problem too. Like a nation rich in resources but poor in drive. Like a generation that has too much and hungers for nothing.

That’s why we’re here, he said—not just to fix problems but to find meaning in them.

As the rain fell, participants huddled in pairs, drawing plans, debating roles, and choosing who they would be—not just for this bootcamp, but perhaps, for their lives ahead.

Because in this wild, experimental theatre of change, there are no scripts—only choices. You don’t get points for sitting still. You grow by stepping in. By getting wet. By choosing discomfort. By daring to care.

And so, under a gray sky and on damp soil, Divergence Bootcamp began—not with clarity, but with courage.

Let the games begin.

1.6 Pairwork - the 13 broken maps

Rain poured steadily across the landscape like a curtain drawn between intention and action. The original plan—to hit the streets and dive into local business interviews—had to be shelved. But if Divergence had taught the team anything by now, it was this:

When you can’t move forward physically, you dig deeper mentally.

The base camp turned into a simulation zone.

The team split into pairs:

• An teamed with Phương Anh

• Mason partnered with Cozy

Their mission: rehearse interview scenarios through roleplay. If they couldn’t get into real businesses yet, they could still prepare to meet them—confident, observant, and sharp.

Each duo took turns pretending to be business owners and consultants, toggling between empathy and inquiry. But before anyone could hit the road, they had to pass through one last checkpoint: Lin91.

Lin91’s question was deceptively simple: “What part of this are you most confident with? And what’s your weakest link?”

An responded first, with sincerity:

“I can start a conversation. I can make people feel comfortable. I believe they’ll be willing to talk to us. But… I don’t know how to find the problem.”

That, right there, was the truth. Not just for An—but for many in the room.

Lin91 leaned in with calm clarity.

“Then don’t start with analysis. Start with description.”

The room nodded slowly.

“Collect raw information. Don’t rush to interpret. Just observe.”

So, what will you observe in a local business? Responses trickled in:

• Are staff working independently or do they need reminders?

• Do customers seem comfortable? Are there any?

• Is the environment clean? Well-arranged?

• What’s the most popular item?

• How long have products been on the shelf?

Now, a basic framework was taking shape. Lin91 stepped into the simulation herself, playing the business owner. Mason took the interviewer role. He started strong—friendly, polite, clear about why he was there. But as the questions came, he faltered. He didn’t know what to ask next. Worse, it showed.

“You came to interview a business,” Lin91 pointed out, “but you didn’t learn anything about it beforehand?”

The discomfort in Mason’s expression said it all. He nodded.

“I realize now—if I walk in without preparation, it’s disrespectful. I’ll waste their time.”

Now the roles flipped.

Lin91 became the interviewer again. An stepped into the shoes of a cautious, resistant business owner. His task? Say No to every request—and explain why. The result was eye-opening.

An hesitated. He squirmed a little. It wasn’t natural for him to create tension. But that was the point.

Because in the real world, not every conversation is easy.
Not every answer is yes.
And sometimes, asking the hard questions is the breakthrough.

1.7 Rain Stops. Wheels Roll. The Field Awaits.

By late afternoon, the rain began to lift. And with it, the team’s inertia.

Two motorbikes roared to life.

The boys—Mason and An—climbed on behind their drivers, awkward and slightly uneasy. But comfort wasn’t on the itinerary. Growth was. The streets of Mộc Châu waited. No more simulations. The next questions they asked would be to real owners, with real challenges.

And from that moment forward, everything counted.

1.8. Return from the Field: Nerves, Noise, and New Skin

The skies had cleared, but the uncertainty hadn’t.

The motorbikes pulled back into base camp with splashes of mud and silence in tow. The pairs had done it. They had stepped into real conversations with real business owners—uncertain of what they’d find, but determined to try.

Still wrapped in his blanket of recovery from a relentless stomach bug, DAV79 looked up and offered the most human of questions: “How do you feel?”

Mason didn’t mince words. His face crumpled slightly, and he said softly: “It’s… very not OK.”

The room laughed gently, recognizing in his words the discomfort that comes not from pain—but from growth.

An, in contrast, was all smiles—even if the nerves hadn’t quite worn off: “I was so nervous to talk to strangers,” he admitted, eyes wide with both relief and pride.

That moment—two truths, side by side—captured what Divergence is really about.

Growth doesn’t look the same for everyone. For one, it feels like collapse. For another, it feels like flight. But for both, it means you did the thing you didn’t think you could do.

That’s the win.

The interviews were not perfect. Questions were missed. Observations were thin in places. But they had crossed a threshold. From roleplay to real-world. From theory to tension. From being “told” what to do to doing it themselves.

And that shift? That’s where transformation begins.

1.9 Dinner, Debrief, and the Real Work Begins

Evening settled over Mộc Châu with the scent of chicken hot pot and grilled fish wafting through the air. For a moment, it felt like the team had earned some rest. But Divergence Bootcamp has a habit of serving reality alongside every meal.

As the steam rose from the table, Lin91 delivered the next course—not food, but fire.

“You need 10 problem statements for each business you studied.”

The room paused. Ten?

Not one. Not three. Ten.

“Because the first five are obvious,” she explained.
“If you stop there, you’re just repeating what everyone can see or what the business owner told you.”

And that’s not value.
That’s not analysis.
That’s not why they came here.

So the challenge was laid down:

• Go deeper.

• Don't just collect noise—extract insight.

• And above all, ask “Why?” five times, at least, for every problem you think you've found.

Suddenly, the evening turned from cozy to clinical.

Participants looked at their “problem” lists with fresh eyes—and growing doubt. Most of what they had captured were symptoms:

• Slow service

• Few customers

• Old décor

• Inconsistent pricing

But why was the service slow?
Why weren’t customers returning?
Why hadn’t anything changed?

The difference between symptom and system started to emerge.

By now, no one was sleepy. The rain, the ride, the nerves—all of it faded. What remained was a growing awareness: they weren’t thinking deep enough yet. They had been scratching the surface.

And so, they stayed up late—heads down, voices low, notebooks open. Trying to earn the right to call something a real problem.

Because in Divergence, you don’t stop at what’s seen.
You dig until it hurts.
And then, you keep digging.

1.10 Ending Day One: Sweat Over Sleep

The night ended not with a wrap-up but with a warning:

“Good effort tonight,” Lin91 thought. “But what comes next will ask more of you.”

The message was clear. Going from observation to insight would take more than good intentions. It would take logic, empathy, persistence—and real thought.

And so, Day One drew to a close not with closure, but with conviction.

Tomorrow, they'd have to defend every one of those problem statements.
Live.
Under fire.
With business owners watching.

And tonight?
They weren't ready yet.
But they were willing.

And sometimes, that’s where real transformation begins.

While the others wrestled with “why” after “why,” Cloudy was in the background—planning for the next day, adjusting schedules, double-checking logistics.

But even she wasn’t fully sure of what lay ahead.

One agenda item stood out—something she had included without entirely understanding it. Normally, she’d lean on DAV79 for clarity. But he was still down, worn from illness, and unreachable for guidance.

It was a strange moment: the person holding the logistics wasn’t confident in the plan, yet the day still had to run.

It was a moment of truth—not about knowledge, but about mindset.

And in doing so, she mirrored the very spirit of Divergence itself:

You don’t need all the answers.
But you do need the courage to keep the mission moving.

The day ended under dim lights and tired eyes. Conversations softened, but the questions still lingered. Tomorrow would come early—and it would come harder.
Because Day Two would open with the debate.
Each team would have to stand by their problem statements, defend them, and face the heat.

There would be no hiding behind good intentions. Only clarity—or correction.

Leave a comment

Persona Cards are generated daily, capturing each member’s evolving mindset and skillset in action.

Leave a comment

2. DAY 2 - 12 Jul, 2025: The Silo Cracker

Mộc Châu, 6:30 a.m.
The sun hadn’t yet burned off the damp chill of the morning, but the air inside was already heating up. Not from the weather, but from the tension. The quiet murmur of participants scrambling to finalize their work was interrupted by a calm but pointed warning:

2.1 “You complete it, or you get a bad name. Your choice!”

This wasn’t a punishment—it was a reminder. Here, at Divergence, your report card wasn’t a private number on a school portal. It was a public reflection of your preparedness, your thinking, and your courage to act.

2.2 Rewinding Day One: Lessons from the Field

Before diving into Day Two’s agenda, the room circled back to what Day One had revealed.

• An reflected on his interviews, sharing insights from her community host while being reminded to clarify her thoughts and avoid ambiguous storytelling. He rated his teammate highly: for being hardworking, fearless, and skilled at initiating conversations—but acknowledged that her mentor’s shyness and lower English proficiency created occasional hurdles. When asked how many business problems he identified, he answered confidently: six out of six. But DAV79 reminded that identifying symptoms isn’t the same as identifying root causes.

“Let’s now find out whether it’s a real problem, a symptom, or just noise.”

A similar arc played out with Mason, who shared that he had studied seven businesses and believed he’d identified problems in each. His feedback about his teammate was honest and balanced—highlighting her social energy and intensity, but also noting moments where pressure led to rushed decisions or unclear communication.

The room appreciated the rigor. Feedback, here, wasn’t sugar-coated. It was mutual. Reflective. Relentlessly real.

Then came the women’s reflections. They shared with depth, vulnerability, and a surprising clarity of self.

Phuong Anh spoke of waking up unsure, fearful even—uncertain why she was here. But through using the “broken maps” and engaging in structured reflection, she felt herself begin to shift. By the end of the day, she realized she had not only conducted interviews—she had taken a first, bold step into discomfort.

Cozy, who had emerged as a natural driver of the group, offered a complex inner monologue. She spoke of pressure—both internal and external—and how she often masked it behind smiles and energy. She spoke of struggling to align her emotional depth with professional expectations, yet recognized that this tension was the very source of her power.

“I’m not here just because I study language,” she said. “I’m here because I’m learning how to balance emotion and contribution.”

She also reflected on working with quieter teammates—how she learned to tune into their slower rhythms and found insight in their cautious observations. There was pride, too, in how others began stepping up

2.3 Preparing for Fire: Today’s Mission Unveiled

Then came the real announcement. Day Two would not be gentle.

“You’re going to be ridiculed. We will tell you your work is useless. And it will be aired.”

Participants were to finalize their problem statements, turning “broken maps” into crystal-clear diagnoses. At 10 a.m., the Debate Round would begin. Business owners and sustainability officers would be invited to join. Cameras would roll. Nothing would be filtered.

The pressure wasn’t performative—it was preparatory. In real-world consulting, criticism doesn’t come wrapped in kindness. It arrives fast, firm, and in public.

The team was instructed to:

• Defend their problem diagnosis

• Estimate potential value impact (even without hard numbers)

• Be ready for pushback, skepticism, and questions from the businesses themselves

“If you want to solve something, you need common sense,” they were reminded. “And common sense is what we’re testing today.”

The distinction between problem, symptom, and illusion was central. AI can throw big words at business failures, but it can’t walk the muddy lanes of Mộc Châu and ask, “What’s really going on here?”

And that’s why the bootcamp matters.

Here, every participant is a detective-in-training. Looking not for fast fixes, but for subtle signals. Reading not just data, but people. Every click of insight must be earned—not borrowed from Google, not scraped from ChatGPT.

2.4 Humor, Humanity, and Hygiene: The Late-Night Tale

But before the day could begin in full, there was one last story.

A late-night misadventure of DAV79 involving stomach troubles, hungry and naughty dogs, and midnight “gossip” became a lighthearted cautionary tale. With laughter echoing off the walls, the message still landed:

“Keep the doors closed. Go to bed early. Or tomorrow will eat you alive.”

It was funny. But it was also a metaphor. You never know what’ll enter through an open door—be it doubts, distractions, or literal dogs. So stay alert. Stay prepared.

2.5 Let the Fire Begin

As breakfast was served and teams readied their charts, the tone had shifted. Day Two was no longer theoretical. It was a test. Not just of business analysis, but of communication, confidence, and clarity under pressure.

Later today, Mộc Châu’s own community members would arrive—ready to listen, question, and challenge. And in the night market, some of these same projects might be pitched in public.

“You survived Day One,” they were told.
“Day Two will be harder. Day Three will be shorter—but sharper.”

In Divergence, every day adds more heat. Not to burn you, but to temper you. Because what’s being forged here is not a polished pitch.

It’s a mindset. A movement. A team that doesn’t crack under pressure—but shines like gold in the cracks.

Here come the real “grill” time!

2.6 The tight simulation

• Team 1: Cozy & Mason – A Hard Fall

They went first. Eyes forward, voices steady—but the cracks showed quickly. Their first business case fell apart under pressure. The problem statements didn’t hold up. The logic was thin. Their questions hadn’t cut deep enough.

“Where’s the real problem?”
“What’s the underlying cause?”
“Why should anyone care?”

The room didn’t attack—but it didn’t rescue either. This wasn’t cruelty. It was the cost of clarity.

• Team 2: An & Phuong Anh – A Glimmer of Direction

Team 2 stepped up next, holding their nerves with a bit more composure.

Their first business analysis showed progress—two valid problem statements emerged. Still basic, still cautious, but at least anchored in reality. It wasn’t brilliant, but it was honest. And that counted.

Then—Redemption. Team 1 returned for their second case.

This time, they came sharper. More grounded. They didn’t try to impress. They tried to understand and connect. And in that shift, the room shifted too. They delivered three valid problems, each more refined than the last.

It wasn’t a comeback—it was a recalibration.

Team 2, inspired or perhaps challenged by the shift, came back once more with a new case and fought hard for clarity. They managed to surface one more valid problem—less than expected, but still a win in the learning arc.

It was a tough simulation.

Voices cracked. Feedback hit hard. Somewhere between the lines and logic, tears fell.

But they didn’t last.

The room was too hot.
The pressure too real.
The transformation too near.

So the tears dried fast—and turned into something better:

Understanding.
Ownership.
A quiet but unmistakable rise.

No one walked out untouched. Because the debate wasn’t just about ideas.
It was about identity.
About learning what it takes to be taken seriously—not just by others, but by yourself.

3. DAY 3 - 13 Jul, 2025: The Final Mission

3.1 Morning Detour and an Unexpected Plan

(to be updated)

3.2 A Conversation That is Meant to Happen

Before deciding to embark on the journey, Lin91 sent a sharp message to Dav79: “I need 1,000 active users for Tap Tap by end of December. If your team can help, I’ll come.” A few minutes later, Dav79 replied, “I think they can.” That quiet exchange set the tone. This was no longer a simulation—it was real. The only task left for the team was to interview Lin91 as a business owner and apply everything they had learned over the last three days to support a real mission.

But just as the team was about to begin, things broke down.

Cozy, visibly drained, let out an exasperated, “Oh my god, interviewing again? I’m tired of it.” That moment shifted the mood. What was meant to be a straightforward interview turned into something else—a reckoning. She voiced a stream of frustrations: that Dav79’s tone had drained her, that Cloudy kept changing plans, that there were no confirmed registrations, that everything felt rushed and stressful. And then came the sharpest cut: “I’ve learned a bit, but it’s not worth it. I don’t want to continue.”

The reaction from Lin91 was swift—and surgical. “Hard words are part of the reality of work. They're meant to build you up, not break you down. This is still a light simulation. If you sat with me for 20 more minutes, you'd know what ‘hard’ actually means.”

She didn’t stop there. Point by point, Lin91 dismantled Cozy’s complaints—not with emotion, but with perspective.

“You’re upset the location was changed? Fine. Tell me—if we stuck with the first venue, how many business owners could you guarantee would show up?”

Cozy and Phuong Anh responded, “We invited them. They said yes… but we can’t guarantee.”

“Exactly,” Lin91 continued. “If you bring zero, then Cloudy has to optimize. She wasn’t just thinking about your one variable. She had to manage cost, support, outreach—more than what you saw. If you had stepped up and said, ‘Don’t change location, I’ll bring five people,’ we wouldn’t be here. But you didn’t. So Cloudy had to carry more.”

And then came a deeper cut: “If you think sending a message or a post online is all you can do, then why did the team invest time, effort, and money to bring you here? If your contribution is something a kid could do, do you think we’re stupid? No. The real reason you’re afraid of them complaining about the venue isn’t logistics—it’s fear of losing face. You didn’t put in the effort to be valuable enough that people would show up because of you.”

Cozy then added, “Even without registrations, Cloudy just told me to invite businesses—but they don’t need to join a program like this.”

Lin91, now tightening her tone, fired back: “So you reached out blindly? You didn’t check if they needed it? You didn’t think for a second who this would help? That’s brainless work. And yes, I’ll say the word—brainless. If you’re working without thought, that’s not professional, that’s irresponsible.”

At this point, Phuong Anh stepped in: “But the plan wasn’t clear. There was no professionalism.”

Lin91 looked straight at her: “You’re right. It was designed that way. Deliberately broken. Because we wanted to see—would anyone stand up and lead? You say you recommended changes. But did you take over? Did you say, ‘Let me handle it’? Leadership here doesn’t mean holding a title. It means triggering others to do better—stepping up without being asked.”

Cozy, still grappling with the discussion, asked, “Then what’s the role of a leader?”

And Lin91 closed that moment with clarity: “Here at teamFD, the role of a leader is to provoke growth—to take over when no one else does. If you wait to be given the perfect conditions, you’re not ready. If you choose to be a follower, then yes, you’ll do what others ask. But if you want to lead—you create change, not consume it.”

The room fell silent. It was no longer about interviews or schedules or venue changes. The question that lingered for each team member was painfully personal:

Why are you here? Do you actually have a goal—or did you just show up hoping not to lose anything?

This was the real test—and only those who could transform discomfort into ownership would move forward.

C. WHAT’S NEXT

D. BEHIND THE SCENE

Leave a comment

Nothing was working. Absolutely nothing.

Emails flew. Executives barked. Clients threatened to pull out. There were talks of regulatory risks, lawsuits, and millions lost by the hour. The CIO issued a statement: “We are working around the clock to restore full functionality.”

But under the gloss of corporate speak, panic reigned.

No one knew where the failure began.

Team Atlas (Infrastructure Ops) insisted everything was fine on their end.

“All servers are green. No anomalies in our dashboards.”

Team Beacon (Data Engineering) threw their hands up.

“Our ETL jobs ran successfully last night. If the downstream’s broken, talk to Catalyst.”

Team Catalyst (Business Automation) pushed back hard.

“No, no, this smells like a legacy issue. Talk to Delta.”

Team Delta (Legacy Systems) wasn’t sure.

“Let us… check with our experts. Some of those modules were touched years ago.”

Team Echo (Integration and APIs) said flatly:

“We’ve had zero deployments in the last 10 days. Must be upstream.”

And on and on it went.

"Whose problem is it?"

No one knows.

Fingers were pointing everywhere.

Each team dug in. Meeting invites flew like confetti. People stopped explaining and started defending. Screensharing became a ritual of helplessness. Audit logs were dissected. Flowcharts were redrawn. Emergency calls went out to vendors. Still, nothing worked.

This wasn’t just a glitch. It wasn’t a routine outage. It was the complete, unexplainable failure of one of the largest integrated IT systems in the world. A company known for its flawless backend operation, lauded in case studies, worshipped in enterprise circles, and trusted by governments and Fortune 100s alike—brought to its knees in a single night.

Log files yielded no clues. Servers showed green, but processes refused to sync. Scheduled tasks vanished. Critical data pipelines were frozen. From payroll to procurement, marketing to manufacturing, the arteries of the organization were blocked.

Someone muttered, “We need a root cause, not more screenshots.”

In the corner, a senior infrastructure expert—Jørgen, a quiet Norwegian with three decades in systems—rubbed his temples. He hadn’t spoken in hours. But now, he leaned back in his chair, eyes distant.

“Maybe they shouldn’t have fired him,” he said softly in frustration.

A few heads turned.

“Who?” asked Rina, a site reliability engineer from Kuala Lumpur.

Jørgen didn’t look up. “You know. That guy… the one from Integration Support. Quiet. Never escalated anything. But things just… worked when he was around.”

There was silence. Then someone murmured, “Oh—Ravi?”

Yes. Ravi.

The man who had kept the weird glue logic functioning. The undocumented exception handler. The person who connected what no one else bothered to understand.

But he was gone.

Four Weeks Earlier

Ravi had always been the last to arrive but also the last to leave. His cubicle—tucked away on Level 11, near the server access room—was modest, half-filled with mechanical pencils and handwritten notes. No fanfare, no corporate lingo, no LinkedIn thought leadership posts. Just quiet diligence.

He wasn’t flashy. He didn’t have a booming voice or a confident swagger. But his code? Impeccable. He knew the invisible plumbing of the system better than anyone—not because someone asked him to, but because he cared.

But caring wasn’t enough.

Ravi’s manager, Parth, had slowly begun reshaping the team. It started subtly—reassignments, new hires, more meetings held in closed rooms. Ravi had sensed the shift. The team lunches grew quieter. Messages went unanswered. His responsibilities were diluted. And then, one rainy Thursday, the calendar invite came: "1:1 – Parth and HR."

Ravi sat across from them, a beige folder on the table.

“It’s not performance, Ravi,” Parth had said, not meeting his eyes. “This is just about... synergy. Team fit. We were also given your name on the table - seems the work you do does might undergo significant change in the future for automation”

“I see,” Ravi had replied quietly.

“You’ve been a valuable asset,” the HR rep chimed in. “But we’re moving toward a new model.”

They offered him a severance package. A modest one. It was wrapped in generic gratitude and carefully-worded legalese.

Ravi didn’t argue. He packed his things in silence. On his way out, he stopped at the vending machine in the basement, bought a bottle of water, and stood for a long moment looking at the flickering floor directory.

No one saw him leave.

Back to the Present

“They called him useless,” Jørgen continued. “Said he wasn’t strategic enough. Not agile. Not dynamic.”

“Wasn’t he the one who handled cross-system workflows with all the other guys bridging and connecting them?” asked another engineer.

“Yes. And undocumented interfaces. And those ‘one-off’ edge cases that magically worked somehow.” He looked up now. “He kept the weird stuff running. The glue.”

Now the pieces began falling into place. That strange workflow with the finance engine? The odd script that adjusted daylight savings time for five continents in one sweep? The failover config that no one could find in the wiki?

Yep ! All Ravi.

Everyone had assumed these things just ran. They didn’t know they were held together by a man who had no audience, no clout, and apparently, no protection.

Meanwhile, Ravi

Ravi wasn’t watching the news. He had spent his days reading, walking along the lake, and re-learning the art of doing nothing. For the first time in years, his shoulders felt light. He didn’t miss the politics. He didn’t miss pretending.

A former colleague messaged him: “Dude… I think they finally realized what you were doing. Whole thing’s crashed. Total chaos.”

Ravi smiled, but said nothing. He knew this would happen - but he just wanted to be alone. Not because he wanted revenge, but because systems that ignore people eventually implode.

The boss never took back what he cast aside. Fueled by ego and a hunger to stay in control, he watched everything unfold—hidden behind the very people he’d positioned in the field.
Unable—or unwilling—to grasp the lesson Karma was already delivering.
He viewed his team through a biased lens, quick to define an inner circle.
To him, everyone else was just a commodity: used, then discarded—unless they belonged to his chosen few.Not every stone is visible. Some lie buried beneath the wall, unglamorous and unacknowledged—but remove them, and everything falls.

Value isn’t always loud. It doesn’t always speak in strategy decks or KPI charts. Sometimes, value sits in a quiet cubicle, solving problems no one else even sees.

Until it's too late.

Each conversation devolved into a deeper blame game and misdirection. Meetings stretched for hours without answers. People stopped talking in full sentences—just acronyms, logs, and panic. Senior VPs were roped into war rooms. Directors scrambled to find people who had once worked on now-forgotten scripts.

And still, the systems refused to move.

The irony was bitter. Ravi’s workspace hadn’t even been reassigned yet. His scripts lived on—disjointed, uncommented, custom—but no one knew how they worked. His hand-drawn mind maps had been binned by janitorial staff. His quiet genius had left no one to translate it.

The issue hasn’t gone away. Why? Because it was never about the solution—it was always about protecting vested interests.

Sad - but a reality.

For the senior management or for those who face such issues at the workplace , here is a question for you, what do you think we can do about this, how can we improve the work place.

1. How do we ensure that every team member, regardless of their position, feels valued and integral to our organization's success?

2. In what ways might our leadership practices inadvertently overlook the 'tiny stones'—the subtle yet crucial elements—that hold our organizational structure together?

3. How can we cultivate a culture that identifies and nurtures the often-unseen efforts that are vital to our resilience and growth?

Leave a comment

Introduction: Cracking the Invisible Silo

Not all silos are built between departments. Some are built in silence — between a leader and their team, between daily tasks and true purpose, between expectations and ownership. These invisible silos are the most dangerous. They create dependency, drain energy, and hide behind high performance.

This story is about Peter — a high-performing leader unknowingly trapped inside a silo of his own making. His team was skilled, but stagnant. He was admired, but emotionally drained. The real issue? A culture fueled by passive execution and unspoken expectations. On top of that, another department had mastered the art of deflection — offloading inefficiencies onto Peter’s team while hijacking the credit for every success. When things went right, they stepped forward. When things went wrong, all eyes turned to Peter. He wasn’t just carrying his own weight — he was shielding his team from crossfire they didn’t deserve.

Through his journey, we explore how silo-cracking isn’t about restructuring teams — it’s about reengineering energy, trust, and distributed leadership. This is not just a leadership story. It’s a blueprint for breaking internal silos, reigniting collective fire, and building a culture where leadership is not held — but shared.

Chapter 1: The Burnout No One Saw

Peter was the kind of leader everyone admired. Sharp suits, sharp words, and even sharper strategies. By 30, he was already leading one of the fastest-growing creative teams in his firm. Young, vibrant, and endlessly competent, Peter had always been the type who seemed born for leadership.

But lately, something was off.

His morning coffee didn’t taste the same. Meetings, once vibrant, now felt like he was dragging deadweight across the floor. The team’s energy was down, and even his once-frequent brainstorms had turned into silent stares and forced ideas.

He wasn’t just tired. He was exhausted. Not physically, but emotionally. Worse, he couldn’t pinpoint why. It was fire everywhere.

Chapter 2: The Mirror Conversation

It was Sarah — the HR business partner and an old friend — who finally broke the silence.

“Peter, when was the last time you really looked in the mirror?”

He gave a tired chuckle. “Not this week. Should I brace myself?”

“Yes. You’ve been physically here, but mentally checked out. Something’s off.”

Peter leaned back, exhaling hard. “I swear, I wish I was on a beach somewhere. The fire’s gone, Sarah. I’m burning out. And the team? They’re stuck. They wait, they hesitate — I have to spark every move. Meanwhile, John’s team is making us look like the weak link. I just… I wish my guys were more proactive. But there’s too much. I’m stretched thin.”

Sarah didn’t flinch. She leaned forward and said quietly, “Hmm... maybe the problem isn’t just the team. Maybe it’s you. You’ve been the flame too long, Peter. Maybe it’s time to build a fire that doesn’t need you to burn.”

Chapter 3: The Shift in Mindset

That night, Peter stared at his ceiling. The idea stuck: build a fire that doesn’t need me to burn.

What if leadership wasn’t about being the engine, but about designing systems of motivation that ran without constant fuel? What if he stopped trying to be the inspiration and started building it into the culture - and measuring it?

He began jotting down ideas:

• Create micro-challenges weekly.

• Empower team members to own initiatives.

• Introduce daily reflection habits.

• Celebrate behaviors, not just outcomes - measure and provide some form of dashboard that others could see and motivate.

• Build Environments where the team members could interact and feel proud of working with other departments.

But he knew ideas weren’t enough. The real work was emotional and it needed followup.

Chapter 4: The Week of Small Fires

On Monday, Peter walked into the office with a mission.

He didn’t announce a grand new vision. Instead, he gave each team a question:

"This week, what’s one thing you want to fix in our client experience? You own it. You test it. You report it."

He also posted a note on the wall:

Small fires build warm rooms.

Every morning, he shared a 2-minute audio note: a story, a struggle, a shout-out.

By Friday, something had changed.

Janice redesigned their onboarding email with more empathy. Marcus rewrote an old campaign brief with humor that nailed a client's brand voice.

No one asked for permission. They just moved.

Chapter 5: Reigniting the Self

Still, Peter knew: if the team was catching fire, he needed to catch his own again.

So, he made a list of challenges for himself:

• Mentor a rising team member he never worked with.

• Host a monthly live AMA (Ask Me Anything).

• Deliver a talk at a nearby university - or an institution - or join a program that helps the members see the value.

Each of these scared him slightly. That was the point.

By stepping into discomfort, he found his own pulse again.

The AMA? Terrifying at first. But it reminded him why he started. The mentorship? Turned into a two-way exchange of insight and energy.

He realized leadership was never just about others. It was about continually evolving alongside them.

Chapter 6: The Culture Rebuilt

Six weeks in, the team looked different.

They didn’t need Peter in every meeting. They started meetings without him. They set goals, created learning pods, and ran feedback circles.

He started seeing behaviors that mirrored his best instincts — without his prompting.

Sarah dropped by again.

“You’re glowing.”

Peter smiled. “They are, too.”

“What changed?” she asked.

“I stopped trying to lead everything. I started building an ecosystem where leadership could emerge everywhere.”

Chapter 7: The Five Flames of Leadership

Peter eventually distilled everything he’d learned into five principles — his "Five Flames":

1. Energy Transmitter — Recharge others with presence, not pressure.

2. Strategic Simplicity — Strip complexity to amplify focus.

3. Empowering Builder — Grow people into decision-makers.

4. Self-Challenger — Never stop daring your comfort zone.

5. Reflection Facilitator — Create space for awareness and renewal.

Each team member received a card outlining the Five Flames — along with personalized upgrades tied to the mindset shifts Peter had envisioned for their roles. These weren’t rules. They were seeds. A quiet challenge. A signal that leadership was no longer top-down — it was a game he had just set in motion, designed to ignite ownership, inspire initiative, and spark a new kind of momentum.

Leave a comment

Hanoi, late afternoon. The sun was dipping low behind a row of cafes, casting long shadows over the sidewalk. Inside a quiet coffee shop — one far more expensive than it should’ve been — the setup for a community event was nearly done. The chairs were arranged. The flyers laid out. But the air was heavy, not just from the heat, but from something else: disconnection.

A lone organizer from LightUp Collective was finalizing the room, adjusting banners, checking the time again and again. He had searched, negotiated, and finally booked this overpriced space — all alone. This wasn’t supposed to happen. The city was full of options, we can choose to support who need help, and dozens of local members were on the team. Yet when support was needed to find a venue, no one responded. Everyone stayed silent. No one moved.

The organizer recalled the team chat just days ago. A call for help. Simple help — finding a café, making a phone call, checking a location. And yet, no response. The thought was sharp: Is this what a community looks like? Is this what shared vision means — help only when it’s convenient?

What began as frustration slowly turned to something heavier. A dull ache of loneliness masked under duty. The feeling of carrying a team on one’s back when no one else feels the weight. And underneath it all, a growing question: What are we even building if no one feels responsible for it?

Silo 1 — “A myth: Volunteer = when I’m Free”
Volunteering, for many, had become a side activity — conditional, optional. The sense of ownership and commitment was absent. People floated in and out, offering help only if schedules were clear and personal lives undisturbed. No preparation. No planning. Just passive attendance. The mission blurred into background noise.

Silo 2 — “It’s Not My Money”
The budget for the event was managed from a shared pool — contributions from members, meant for shared growth. But with no personal stake, care dissolved. Community members, who could have secured a much cheaper venue or negotiated better terms, stayed on the sidelines. The expense was absorbed. The lack of financial ownership was loud, though no one spoke a word about it. Integrity didn’t disappear — it was simply not activated. When you spend from your own pocket, you tend to be cautious. When spending from the organization’s funds, that caution should double or triple — because it’s not just money, it’s trust. And if you're the one with access to those shared funds, therefor others can not, your responsibility multiplies exponentially. So why is it that the opposite often happens?

Silo 3 — “Not My Job”
Events happened. People showed up. But connection didn’t. New members came in and left just as easily. There were no proactiveness, no desire for connection, no follow-ups, no bridges built between names and faces. Each team member played their role, then disconnected. The result: repetition without momentum. Events became isolated acts instead of stepping stones toward something greater.

In another part of the world, people were crowded in coffee shops in Starbucks , Mc D, KFC …… Can we work on this together on a project? asked a member of the team who was engaged in discussion with the unit in Hanoi….

Silo 4 — “Acting busy only lah!”

Soulless people—like zombies—kept tapping away at keyboards. Routine tasks, mindless SOPs from a bygone era, soon to be devoured by AI. Yet they appeared busy.

When invited to contribute or join something meaningful, the default response—especially if there was no immediate monetary reward (often given to them without lifting a finger)—was, “I work, busy now lah.”

But ask: What exactly are you working on? Few could give a clear answer.

For someone already juggling 100 tasks, adding 101 is no big deal. But for those whose hours are empty, even a small shift feels unbearable.

Silo 5 — “Kiā-su - Kiā-kóng” (惊输) – afraid to lose/ overly competitive

When people work together, it doesn’t take long for someone to seize control—locking the group into rigid routines and resisting change. Structure is useful at first, but once the growth curve flattens, it often turns into a plateau of boredom. Ironically, the very people who built the system now find it too dull to lead—yet they expect everyone else to follow without question.

And here’s the twist: these same people who shy away from change do so not out of humility, but because they fear being challenged. They don’t want anyone disrupting what they've built—so they avoid collaborators who might think differently. Better to work with followers than risk losing face.

IN SINGAPORE , we say

“Eh sai kang, ai chhìu-kong, everything also must go through them.”
(They act capable, but just want control. Everything must go through them.)

Silo 6 — “Now or Never: The Impatiently Entitled One”

Some only step in when results are guaranteed — and instantly. They chase instant dopamine, not depth. “If this doesn’t work in a week, I’m out.” They plant seeds but refuse to water them. Ideas are pitched, half-started, and left to rot when growth doesn’t come fast enough. Their restlessness kills momentum. Their lack of patience robs the team of long-term vision. Instead of building together, they bounce — leaving others to clean up after their urgency fades.

Silo 7 — “NATO - No action - Talk only”

“Yo bro, long time no see! Easy lah — we can totally make this happen.”
The energy is high, the words flow confidently, the dreams sound big. But when it’s time to commit — to show up, to deliver, to face the grind — they vanish. These are the ones who romanticize purpose but flee from process. They hijack enthusiasm with empty affirmations, making every idea sound achievable... until execution begins. When the rubber meets the road, they’re nowhere to be found. Excuses replace effort. Vision turns into vapor. And the team is left chasing shadows, cleaning up the gap between hype and reality.

The Core Truth

When no one feels responsible, everything becomes someone else’s job. A team without ownership becomes a machine of moving parts — functional, perhaps, but soulless.

Volunteering becomes a hobby, not a commitment (Silo 1).

Shared money becomes no one’s money — and thus, no one’s responsibility (Silo 2).

Tasks get done, but connections don't — there is no glue, no growth (Silo 3).

People appear busy, but produce little — “busy” becomes the perfect excuse to stay uninvolved (Silo 4).

Collaboration is avoided out of fear of losing face or control — structure replaces innovation (Silo 5).

When patience runs dry, those chasing instant success disappear before anything meaningful can take root (Silo 6).

And the loudest voices — full of promises and inspiration — never show up when it matters (Silo 7)

Community cannot thrive on passive attendance.
It thrives on presence.
On initiative.
On care.
On energy.
On the quiet courage to keep showing up — not because it’s easy, but because it matters.

Reflection

This isn’t a failure of strategy or skillset. It’s a failure of mindset. The cost wasn’t the overpriced café — it was the invisible cost of disengagement, of lost potential, of people showing up without showing up.

If you are part of something bigger — a team, a cause, a community — look closely:
Are you in?
Or just around?

Because real change begins not with better tools, but with better ownership.

Leave a comment

I pulled into a quiet villa by the lake, drawn by the promise of coffee and conversation. The café was a maze of charm—garden chairs under trees, cozy corners inside, balconies that kissed the breeze, and even a patch of sand beneath low tables. I wandered, early as usual, scouting the perfect spot.

Upstairs, I caught a glimpse of the host—meticulously adjusting a projector in a small, dim room. What a pity, I thought. So many beautiful spaces, and we’d be tucked away in a “formal” box.

Still, something about the care in their setup held my attention. I slipped into a balcony seat downstairs, laptop open, tying up another meeting. But my mind stayed with that quiet room upstairs. I had a feeling that space—small as it was—might be where something bigger would begin

From Frameworks to Friendships

In a time when workplace collaboration depends more on emotional intelligence than formal authority, the question “How can we be liked effortlessly?” holds a certain weight than ever. In a session hosted as part of the After Hour series, professionals of different generations, in different industries gathered not to network, but to reflect, laugh, challenge norms, and reveal what makes humans connect as part of the way of working.

• Do you have authority over your team?

• Would you like to make a deeper impact on your team?

Notably, the session emphasized that to move people up this ladder, the Friendship Formula can be intentionally applied. It’s not just about being around—it’s about how you’re around.

The Icebreaker: Cake, TikTok & Korean Dramas

The session opened with a standing-sitting activity. Participants were shown visual prompts—if they loved what they saw, they stood; if they hated it, they sat.

• The first was a toilet paper roll being sliced by a knife—only for it to reveal itself as a hyperrealistic cake. Just one person stood: “I like it because it goes against the norm and it made a surprise”. She appreciated its twist on expectations. The others recoiled: “It looks smelly,” “Why cut it off-center?” “It felt wrong from the beginning.” “It’s not a proper methodology to deal with it, who on earth uses a knife to cut the paper.”

• TikTok? Surprisingly, zero participants stood up. Enough said.

• Korean dramas sparked more reflection. Two admitted their love for it—one for the emotional drama and ideas for storytelling; another, more candidly, shared that growing up, Korean dramas were all there was on TV, and they liked it because “the girls were pretty.”
  Meanwhile, another participant said they preferred peaceful, reflective content—not the melodrama of most K-dramas. Someone quipped: “I like watching Korean actresses, but not the drama. It’s too over the top.” “I used to watch K-drama before, but not now because it’s too lengthy, and now there are movie recap on social media that I can know about movies without watching them all” “I prefer drama at work than Korean drama ahaha”

It wasn't just a game—it was a social scan. Reactions weren’t just about personal taste. They revealed decision-making styles, emotional biases, and generational contrast. And it leads to another thought “Do not just love and hate, define it! Do we have the same definition of love and hate?”

Love, Hate, and Everything in Between

As the conversation deepened, the group was asked to define love and hate. It opened a floodgate of raw, thoughtful reflections.

One participant shared:

“I don’t often hate. I might dislike something, but I only hate when someone does real harm to me.”

While another asked: “If there are 2 teams working well internally, but the 2 teams don’t like each other. Will you be mixing them up or you keep them separate?”

And on love?

“It’s like caring for a flower—you nurture it, protect it. Liking something is just admiring the flower in a vase.”

“If someone loves me, I ‘ll love them, regardless of whether we share opinions”

- “But how could you know if they love you or not?”

That contrast was striking—and led to a collective realization: we use emotional words daily without ever defining them clearly. Someone remarked:

“We use emotional words daily without ever defining them clearly. Turns out we all have our own definitions. But until we articulate them, we can’t expect others to understand or connect.”

Likability is Not a Gift—It’s a Science

The session opened with a bold declaration: “To be liked is not luck. It’s science.”
Drawing from the Friendship Formula, a behavioral model famously used by the FBI and U.S. military in high-stakes negotiations, the speaker introduced the four core elements that drive likability:

1. Proximity – How physically or virtually close you are to others.

   We are hardwired to like what’s familiar. Physical closeness—be it seating arrangements or shared environments—creates a sense of trust.

   "Eat with your team. Sit with your team. Familiarity breeds connection."

2. Frequency – How often you engage or are visible to someone.

   Seeing someone regularly increases comfort. But visibility alone isn't enough. You must also ensure positive interactions occur. The speaker quoted:

   "It takes 8-9 positive interactions to balance one negative one."

   One member raised a question: “Do you think “frequency” is enough? In my team, when new member joins and is asked to join lunch everyday with the team, they don’t feel so comfortable”

   The host quickly responded: “You are right. Because it’s missing the most important element: Meaning. We will come to that shortly” :)

3. Duration – The long you spend together.

   Time matters, but time must be pleasant. Long hours without meaning drain connection. The tip: design team interactions that are both extended and enjoyable—through trips, games, or shared rituals.

4. Meaning – How meaningful your interactions are - The Magic Ingredient

   The formula revealed that it’s not charisma that builds trust—it’s consistent, purposeful engagement.

Do these elements resonate with you? Are they enough? Share your thoughts—and let’s co-create a refined formula that truly works for our unique workplace culture.

Leave a comment

Eye Contact, Seating, and Design Thinking in Action

A question was raised:

“Does eye contact make people closer?”

The host replied, “It depends.” Between men, too much eye contact can feel confrontational. But if I maintain eye contact with a woman, it’s often received differently—more as attentiveness or confidence. Still, it’s important to be aware of how we hold that gaze. Personally, when I make eye contact, I use a rhythm: I meet the gaze, look away briefly to the side or downward, then return. I never stare too long or look down submissively. It creates a balance—engaged but not intrusive
“Just don’t look down,” he added. “Keep your gaze up.”

The participant then pointed out a design flaw in the room—rows of chairs meant participants couldn’t see each other’s faces, it blocked interaction. That led to an impromptu seating change: chairs were rearranged into a U-shape. Instantly, the atmosphere shifted. Conversations flowed. Laughter became shared. The Friendship Formula was already applied and brought in action.

This change isn’t just about comfort—it’s behavioral design in action. Eye contact works best when supported by body position, openness, and proximity. If we want connection, everything—from where you sit to how you look—matters.

Generational Gaps in Building Connection

The session reached a high point when some members dissected how different generations connect, regarding the question asked by the host: “What brings someone closer to you?”

“Drink. Talk. Everything flows.” — said the 7x–8x generation.

A younger participant shared a revealing insight:

“When team-building is organized by Gen Z for Gen Z, it always works. But when Gen Y or older plan it—even with the best intentions—something always feels off in one or another way.”

Another added:

“I used to struggle with the Gen Z members in my team. I eventually hired another Gen Z to work with them. They instantly bonded—and took care of each other. Problem solved.”

“If we have the same enemy, we will work harder together and get close to each other naturally.” “Simple example, if boss hired new member, published high salary and the new member is not that talented to worth the paid, other members will form a stronger team than ever”

And the Host simply shared: “Survey your team!” Yes, it’s about building up connection, by showing your team how you care.

How Much Time Do We Need to Build Rapport?

One exchange that stood out:

“What’s the ideal time to build rapport?”
“Just one hour,” said a participant. “Enough to break the ice and explore one topic—without dragging.”
“Then how do you make that time last longer?”
“Start with coffee, end with dinner. Few people say no to food.”
“Or maybe it depends on how the conversation makes us feel,” someone else offered.

Others shared tactical time frames:

• “It takes me 30 minutes to get close to a teammate.”

• “Just 10 minutes of talk is enough to tell—but that doesn’t mean real connection.”

• “For us, only when conflict comes, we will know. So conflict is the real test. We often stage minor crises to see how people react, like an experiment. It reveals their integrity, resilience, and purpose. Everything, for us, is a mindset experiment.”

• “Few mins to interact but maybe few years to really know who they are…”

A Question That Disarmed the Room

“So… can I assume that one of the biggest problems PMs face is that they’re not liked?” “

The room burst into laughter—for such a naive, silly yet straightforward question. But the question is actually about "Why do you come up with the idea of How to be liked effortlessly?”. The host replied honestly:

“Because no one teaches us this. I’m a coach, and many people were asking me the question. We’re trained in frameworks, metrics, and delivery models—but not in connection. And when people leave jobs, they rarely leave because of the process. They leave because of people.” He paused before finishing: “If we take care of our teams, they’ll take care of our customers. Likeability isn’t about being fake. It’s about being human.”

Another question was raised: “Will the Friendship Formula work if we apply it upward—to higher-tier managers or leaders in the hierarchy?”

It was a moment of truth—and strategy. The host responded with nuance:

“It can—but not everyone will be open to it. Some may perceive likability as a threat, especially if they’re insecure or territorial. That’s a risk we can’t always control.”

But the message was clear: likability isn’t about pleasing—it’s about positioning. When practiced with intention, the formula can still unlock access, trust, and influence—even in top-down structures.

Another participant confessed: “Actually I was expecting to play some games in the event today”. And many others agreed with the statement. The host smiled—and pulled out one called “What do you bring to the party”. Everyone is excited, one brings a friend, another ones bring a problem :))), a phone, a fresh mind, a solution, a coffee and a fresh mind. The game just helped to wrap up the session nicely.

The Spirit of After Hour

The session formally ended—but the real magic happened after. People lingered. Conversations deepened. Small groups formed. New friendships sparked. And suddenly, we all looked at each other and said, with a smile: “This is the real spirit of After Hour.”

Final Thought

Likability isn’t performance. It’s behavioral design.
It’s not about being nice. It’s about being seen, shared, and remembered.

The Friendship Formula—proximity, frequency, duration, and meaning—worked that night not as a theory, but as a living experience. Energetically shared by host, few mindset in action are observed:

1. 1. The Host: Attentive, adaptive, human-centered.

Mindset: Servant leadership in action—prioritized connection over control, theory over ego, and turned feedback into flow.

2. “The Cake Rebel”: Nonconformist, expressive, open to surprise.

Mindset: Challenges norms; sees creativity in the unexpected.

3. The K-Drama Admirers: Sentimental, expressive, nostalgic.

Mindset: Values emotional richness; draws identity from formative experiences.

4. The “Conflict as a Test” Strategist: Analytical, observant, psychologically sharp.

Mindset: Sees life as experiment; trusts behavior over words.

5. The Eye-Contact Analyst: Detail-oriented, socially aware.

Mindset: Observes micro-behaviors to build macro-connections.

6. The Team Survey Advocate: Systems thinker, inclusive.

Mindset: Believes co-creation is the fastest path to cohesion.

7. The Gen Z Translator: Bridging, empathetic, practical.

Mindset: Solves friction through cultural decoding.

8. The “Just One Hour” Reflector: Minimalist, high-trust, efficient.

Mindset: Prioritizes quality over quantity in connection.

9. The Unexpected Game Requester: Playful, spontaneous, honest.

Mindset: Seeks joy, values lightness as a form of engagement.

For me personally, in a room full of introverts and quiet thinkers, all it takes is one curious voice—ask just enough, or maybe even something a little silly—and suddenly, questions start flowing. That’s the spark. That’s how connection begins.

The Assignment Divide

The room buzzed with quiet determination as five students huddled over their laptops, scattered notes, and textbooks. It was crunch time for the team’s group assignment, and Maya, the team leader, was at the center of it all, organizing chaos into order.

Maya was known for her meticulous nature. She had spent the night before outlining the task into manageable sections, assigning parts based on each member’s strengths. While not perfect, the team’s plan seemed solid. Sophie, a bright yet unpredictable teammate, had been given a simpler section to ensure everyone stayed on track.

"Everyone clear on what they’re doing?" Maya asked, her voice steady but firm.

Nods and murmurs of agreement followed. Sophie smiled brightly, "No problem! I’ll finish my part and help if anyone needs it."

Promises Made, Promises Forgotten

True to her word, Sophie finished her section early, but instead of helping, she switched on her gaming console, headphones wrapped snugly around her ears. As the hours ticked by, Maya and another teammate, Ethan, dove into reviewing everyone’s contributions.

“Can you believe this?” Ethan muttered, frowning at an inconsistent citation. “We’ve been fixing these for hours.”

Maya sighed, rubbing her temples. “I know. But we can’t submit something half-baked. Let’s just get it done.”

Sophie occasionally glanced over but made no move to join them. When Maya asked her to double-check a paragraph, she waved it off. “That’s your part, right? You’re the leader.”

Despite the imbalance, Maya and Ethan powered through the corrections. By midnight, the assignment was polished, cohesive, and ready to submit.

The Aftermath

The next morning, the team gathered to review their completion percentages. Maya had kept track of each person’s contributions, noting the effort spent beyond their initial tasks. Ethan, who had stayed up late helping, received high marks. The others, who had followed through on their sections without much assistance, earned respectable scores.

Sophie, however, didn’t take the results well.

“Why is my percentage lower than Ethan’s?” she demanded, arms crossed.

Maya looked up, surprised. “It’s based on effort. Ethan helped me fix the passages and followed up with the other teammates.”

“I said I wanted to help!” Sophie argued.

“Yes, but when there was work to review, you didn’t join in,” Maya replied calmly. “I gave more to those who actively helped.”

Sophie’s voice rose. “That’s unfair! You’re favoring Ethan over me!”

“Favoring Ethan?” Maya blinked, struggling to remain composed. “Ethan earned those points by taking initiative. Did you help any teammates with their sections?”

Sophie faltered, unable to respond. Instead, she accused Maya of deliberately underestimating her abilities and intentionally excluding her from important tasks.

“No one excluded you,” Maya said firmly. “But being part of a team means stepping up when needed, not just when it’s convenient.”

Breaking the Silos

As Sophie stormed out, the remaining teammates exchanged glances. It wasn’t just Sophie’s outburst that stung; it was the unspoken realization that their group operated in silos. Each member had treated their assigned part like an isolated task rather than a piece of a collective whole.

Later, Maya called a team meeting to address the underlying issues. “I think we need to rethink how we work together,” she began. “This assignment showed me something: we’re too focused on just doing what’s assigned. Why do we feel so limited by these boundaries? If we see a gap, we should fill it. If a teammate needs help, we should offer it, even if it’s outside our ‘responsibilities.’”

The team nodded thoughtfully. Ethan added, “I get it. I stuck to corrections because I thought that’s what Maya needed from me, but maybe we can all do more to support each other next time.”

Even Sophie, though initially defensive, reflected on her role. She realized her reluctance to participate beyond her assignment came from a desire to avoid blame for errors. “Maybe I could have jumped in, even if it wasn’t clear what exactly needed doing,” she admitted.

Questions for Thought : here are 3 questions - we would love to hear your responses.

1. Why do some people feel entitled to equal recognition even when their effort doesn’t match others in the team?

2. What holds individuals back from stepping outside their assigned roles to contribute more to the bigger picture?

3. How can teams foster a culture where members feel motivated to take initiative without waiting for explicit instructions?

Let us know which question you'd reflected on when share your thoughts on the comment section!

Tintin, joined by his friend Lee and her lively dog Woof, explores a mysterious café in Hanoi. Lee encounters a cold response when ordering, and the café's odd, restrictive rules become clear when Hui, a friendly waiter, is reprimanded by the stern owner for chatting with customers. Intrigued by the strange atmosphere, Lee recalls a similar experience with a man named Octavio, hinting at the insecurities that can come with authority. Tintin, ever the detective, leaves the café with Lee and Woof, wondering about the deeper mystery behind its silence and the owner's rigid control.

Subscribe now

Leave a comment

Leave a comment

Subscribe now