The second Claude Bloom event was redesigned after feedback from the first session. Instead of repeating material people could hear online, the team focused on deeper offline conversation, concrete AX cases, and the question of how organizations actually become AI-native.

1. How Feedback Changed the Second Event

The first event drew interest but also clear criticism: why sit offline for ninety minutes to hear what could be delivered online? The organizers accepted the feedback and redesigned the second gathering as a smaller, community-oriented format.

AB180 provided a space and catering suited to small-group conversation, while MyRealTrip prepared a more specific account of its internal AX transformation.

2. The Second Event's On-Site Response

The event felt stronger because it used the offline setting better. People could ask sharper questions, exchange context, and compare the messy reality behind AI adoption.

At the same time, the recap notes that there is still room to improve the format. The value of IRL events depends on depth, not ceremony.

3. A Bigger Ambition: Global Channels

The organizer also sees potential for English meetups and expansion into Japan and Singapore. The idea is to create a global channel for practical AI-native work, not just a local event series.

4. Sungpil Nam's Greeting: Inspiration Comes from People

AB180's Sungpil Nam emphasized that inspiration ultimately comes from people. Even in an AI-heavy event, the human network and shared energy mattered.

5. Donggeon Lee's Mobile Trauma

MyRealTrip's Donggeon Lee described a painful lesson from missing the mobile transition. That experience created a strong desire not to miss the AI transition in the same way.

The lesson is that imagination matters. Leaders must picture how a platform shift could reshape the company before the evidence feels comfortable.

6. Shipping Within 48 Hours After GPT-3.5

After GPT-3.5, MyRealTrip moved quickly and launched within 48 hours. But early excitement also produced churn when the first version did not fully satisfy users.

The story shows both sides of speed: fast shipping creates learning, but the organization must be ready to absorb and improve from the result.

7. Four Years of Changing Execution Structure

The deeper transformation was not one product launch. It involved AI labs, AICX, AI champions, and changes to how roles collaborate.

The important shift was from using AI as a tool to redesigning the way work itself flows.

8. What It Means to Be AI-Native

An AI-native company is not simply a company where employees use AI tools. It is a company whose operating system changes around AI: evaluation, ownership, tooling, and learning loops all adapt.

The standard becomes whether AI changes real execution, not whether it appears in a slide deck.

9. Seven Real Cases

The event shared practical examples, including non-engineers building tools and leaders creating internal systems themselves. These cases made the message concrete: the person closest to the problem can now often build the first version of the solution.

10. The AI Lab Lesson

One organizational lesson was that centralized AI labs can fail if they separate problem owners from solution builders. A better structure lets the person who recognizes the problem participate directly in solving it.

11. Q&A Realities

The Q&A surfaced grounded constraints: the CEO can become a bottleneck, recovery may matter more than pre-approval, and training must arrive at the right moment.

Conclusion

Claude Bloom 2 argued that the value of AI adoption is organizational, not just technical. The hard part is designing a structure where problems, tools, and responsibility meet quickly enough to change how work actually gets done.