Case Study 02. IBM Virtual Worlds, Enterprise 3D Collaboration
Industry: Enterprise Technology and Virtual Collaboration. Timeline: 2006 to 2009.
The Problem.
For a company with roughly 300,000 employees spread across the world, bringing people together meant either expensive travel or flat tools like email, phone, and web meetings. None of it recreated the value of actually being in a room together. In 2006, the question my team set out to answer sounded like science fiction: could a shared three-dimensional space let people meet, collaborate, and get real work done without being in the same place? This was years before the word “metaverse” entered common use.
The Solution.
The effort did not start as a mandate from the top. It grew out of the grassroots, from IBMers who were curious about Second Life, the leading virtual world of the day, and wanted to see what it could do. That curiosity became a company-wide initiative, and I led a cross-departmental, international team of ten that built IBM’s first internal 3D business collaboration space.
We had to build the real thing, not a demo. Working with Linden Lab, the makers of Second Life, we ran a private version of their world on a server inside IBM’s corporate firewall, so employees could hold secure virtual meetings in a space we controlled. We worked alongside the people building OpenSim, the open-source platform that recreated that same environment on servers of our own, so standard clients could connect to it. My team gathered several 3D game engines and built the infrastructure to run them at enterprise scale: server queuing, multiple concurrent worlds, redundancy, and digital asset management.
Two pieces of that work were genuinely ahead of their time. Back then, a 3D engine needed every asset loaded before it could render a scene, which made large shared worlds slow and brittle. My team built a way to stream those assets on the fly, so a space rendered in partial form and then sharpened as its models, skins, and graphics downloaded in the background, instead of making everyone wait for the whole world to load. And because we ran collaboration spaces across more than one platform, a 3D game engine as well as Second Life, I built a platform-agnostic engine that shared objects between them, so a piece created or changed in one world could appear in another that otherwise had no way to connect to it.
I was not only building the environment, I was running the work that happened inside it. I set up and facilitated brainstorming and collaboration sessions in the virtual spaces, putting them to use for the structured, cross-team problem-solving they were meant to enable. That part fit me for a specific reason: I was a programmer who had also been formally trained in Creative Problem Solving, through a graduate certificate in creativity studies. Most people on the effort had one side or the other, the engineering or the facilitation. Having both is why I could build the space and also lead the creative work inside it.
The work put us alongside some of IBM’s best, including researchers and the international prototyping group at the Hursley lab in England.
The Outcome.
We proved that three-dimensional collaboration could work inside a global enterprise, not just in theory but in daily practice. The work reduced travel across IBM’s global workforce, and the team’s work produced real intellectual property, including multiple patents filed by its members.
The clearest proof came when IBM held two of its major internal conferences, the Technical Leadership Event and the Academy of Technology gatherings, entirely inside the virtual space we had built. Full company conferences, conducted in a 3D world instead of a hotel.
This was 2006 to 2009, a decade before the rest of the industry rediscovered the same idea and gave it a name. By the time I moved on in 2009, the effort was at an inflection point. The specialized 3D engine work carried forward with one of the team’s engineers, while others were reassigned as IBM pulled back from speculative projects during the downturn of those years. What it represents has not changed: I helped build, and led the team behind, one of the earliest serious attempts to make the metaverse a place where real work happened, long before it was called that.