Enterprise 2.0 in 2007: Wikis, Collaboration, and the Social Workplace

Enterprise 2.0 brought the participatory mechanics of the public web inside the organization. In 2007, wikis, blogs, profiles, tags, shared workspaces, and activity feeds promised to turn institutional knowledge into something employees could find and improve rather than repeatedly recreate.

The knowledge-management problem

Companies already had document repositories, intranets, email, and collaboration suites. The problem was that formal systems required someone to anticipate a taxonomy, assign ownership, and publish a finished artifact. Much of the organization’s useful knowledge lived in inboxes, project folders, and the memories of experienced employees.

Enterprise 2.0 tools inverted the model. They allowed useful structure to emerge from ordinary work: a team edited a shared page, employees tagged material using language they actually searched, and subject-matter experts answered questions in a space others could later discover.

Adoption was organizational before it was technical

Installing a wiki was easy. Creating the conditions in which people trusted it was harder. Employees needed clarity on which content was authoritative, what could be shared, who moderated disputes, and whether contributing would be recognized as work. Without leadership participation and usable search, collaboration platforms quickly became another abandoned information silo.

Security teams also had legitimate concerns. Open contribution inside a company still required identity, access control, retention, legal discovery, and protection for confidential information. Successful deployments combined low-friction participation with explicit content boundaries.

The architecture underneath collaboration

Enterprise 2.0 accelerated demand for single sign-on, directory integration, APIs, search indexing, and event-driven updates. Those integration requirements foreshadowed the modern digital workplace. Today’s employee experience platforms, team chat, collaborative documents, and enterprise knowledge assistants inherit the same basic objective: make distributed knowledge available at the moment of work.

The enduring lesson from 2007 is that knowledge platforms succeed when contribution is easier than withholding. Technology can create that path, but governance, incentives, and information architecture determine whether people use it.

This article is part of the restored Gain America Technology Archive. Originally published in 2007; editorially restored and updated in 2026.