Intranet

Intranet audio micro-course (transcript)

Three short podcasts about “Intranet”. Listen with the interactive player.

Podcast 1 — Introduction & meaning

Narrator: Intranet. A noun. Pronounced /ˈɪn.trə.net/.

Narrator: Intranet is formed from the Latin prefix intra-, meaning within or inside, and net, short for network. It is consciously modelled on the word internet — the public global network of networks — but with intra- replacing inter-, signalling that this is a network within rather than between. The term emerged in the mid-1990s as organisations began deploying internal networks built on the same TCP/IP protocols as the public internet, but restricted to their own staff and systems.

Narrator: The intranet solved a specific organisational communication problem. Before its arrival, companies relied on paper memos, notice boards, shared network drives, and proprietary groupware systems like Lotus Notes to share information internally. The intranet offered a simpler, browser-based interface that employees already knew from their use of the public web. Suddenly, internal documents, policies, phone directories, and announcements could be accessed through a familiar web browser, from any computer on the corporate network.

Narrator: The intranet quickly became the standard platform for internal corporate communication throughout the late 1990s and 2000s. HR policies, IT documentation, employee benefits, project portals, and news from leadership all moved online. The well-designed intranet became a digital workplace hub — a home page for the organisation's internal life.

Narrator: With the rise of cloud computing and software-as-a-service platforms, the classical intranet has evolved. Tools like Microsoft SharePoint, Confluence, and Notion serve intranet functions while offering richer collaboration features. The intranet concept has not disappeared — it has distributed itself across the digital workplace ecosystem.

Narrator: The intranet also has a security dimension: by keeping sensitive corporate information behind a firewall and accessible only to authenticated employees, it protects confidential data from the public internet.

Narrator: Intranet. The word for the internet that stays inside — the private network that brings the web's ease to the organisation's own walls.

Speaker A: The policy was on the intranet — I checked this morning — but now I can't find where it's been moved.

Speaker B: Classic intranet problem. Everything's on there somewhere but the navigation is a graveyard of old structures.

Speaker A: The intranet that nobody maintains. Every department adds their own section and nothing ever gets retired.

Speaker B: The archaeology of intranets. Layer upon layer of content from different eras of the company's existence.

Speaker A: You find policies from 2009 sitting next to the 2024 ones with no indication of which is current.

Speaker B: The intranet as organisational memory — accurate in places, dangerously out of date in others, and indistinguishable.

Speaker A: A properly governed intranet has content owners, review dates, and an archiving process.

Speaker B: Which takes resource and discipline to maintain. Most organisations do the build and neglect the governance.

Speaker A: So the intranet starts well and gradually becomes the thing everyone searches and nobody trusts.

Speaker B: The intranet's trustworthiness as a cultural signal — it tells you how seriously the organisation takes its own information.

Speaker B: Build a Next.js intranet design and information architecture for an internal communications manager — documenting how to design an effective corporate intranet, reviewing navigation, content governance, and employee experience, generating an intranet design framework, and producing an intranet information architecture corporate guide.

Speaker A: Intranet design documented with information architecture analysis so practitioners explain both the navigation principles — how card sorting and tree testing reveal how employees expect to find information on the intranet — and the governance model: how content ownership, mandatory review cycles, and archiving workflows prevent intranet decay, with the SharePoint and Confluence feature sets that support intranet content lifecycle management.

Speaker B: Design a Django intranet security and zero trust network for a security architect — documenting how intranet security is designed in a zero trust model, reviewing VPN, identity-based access, and microsegmentation, generating an intranet security zero trust framework, and producing an intranet security network architecture guide.

Speaker A: Intranet security documented with architecture analysis so engineers explain both the perimeter security model — how traditional intranets rely on firewalls and VPNs to restrict access to the corporate network — and the zero trust shift: how remote work and cloud adoption mean the intranet perimeter no longer exists, requiring identity-based access control, device trust verification, and microsegmentation regardless of network location.

Speaker B: Create a Svelte intranet analytics and measuring employee engagement for a digital workplace analyst — documenting how to measure intranet usage and employee engagement, reviewing page views, search behaviour, and adoption metrics, generating an intranet analytics framework, and producing an intranet employee engagement digital workplace guide.

Speaker A: Intranet analytics documented with digital workplace analysis so practitioners explain both the usage metrics — how page views, unique visitors, search queries, and time-on-page indicate which intranet content employees actually use — and the engagement interpretation: how raw traffic numbers must be supplemented with search abandonment rates, zero-result searches, and employee satisfaction surveys to assess whether the intranet is meeting communication needs.

Speaker B: Build a Vue intranet versus internet and network topology for a network engineer — documenting the technical differences between intranet, extranet, and internet architectures, reviewing RFC 1918, private addressing, and firewall design, generating an intranet network topology framework, and producing an intranet internet network architecture guide.

Speaker A: Intranet topology documented with network engineering analysis so engineers explain both the private addressing model — how RFC 1918 address spaces allow intranets to use IP addresses not routable on the public internet — and the extranet extension: how controlled access to intranet resources for external partners is achieved through VPN tunnels or reverse proxy configurations, with the firewall policy design that separates intranet, DMZ, and internet zones.

Speaker B: Develop a React Native intranet social features and the digital workplace for a knowledge management specialist — documenting how social intranet features support knowledge sharing and collaboration, reviewing enterprise social networks, communities of practice, and internal search, generating an intranet social digital workplace framework, and producing an intranet social knowledge management guide.

Speaker A: Social intranet documented with knowledge management analysis so practitioners explain both the community features — how profiles, activity feeds, groups, and internal blogging on platforms like Yammer and Viva Engage extend the static intranet into a social knowledge network — and the knowledge capture problem: how tacit knowledge shared in intranet conversations can be made retrievable through tagging, communities of practice pages, and internal search optimisation.