Comprehensive field guide
The Employee Intranets Field Guide
This field guide brings the main employee Portal & Intranet Development decisions into one place: how to read the symptoms, protect the current state, choose a scope, compare paths, and verify an outcome that matters to organizations centralizing policies, forms, training, announcements, and internal workflows.
Read the situation before naming the solution
Begin with employees cannot find the current policy, who experiences it, and what changed before it appeared. Distinguish the visible symptom from the system boundary that may involve single-sign-on and access planning.
- Employees cannot find the current policy
- Important updates disappear in email
- Departments maintain conflicting documents
Protect the current state
Confirm ownership, access, backups, and a recovery path before changing production. Preserve exact errors and timestamps because they may disappear after a restart or update.
- Access owner
- Current backup
- Restore method
- Change history
Define the smallest useful result
Frame the first scope around employee home pages and announcements and one observable acceptance journey. Keep department and staff directories as a later phase unless it is a true dependency.
- Employee home pages and announcements
- Policy, form, and document libraries
- Department and staff directories
Compare repair, extension, and replacement
Repair fits when the core remains sound; extension fits when the boundary is understood; replacement fits when ownership, architecture, or operating risk prevents responsible change.
- Time to value
- Data risk
- Reversibility
- Maintenance ownership
Plan implementation and launch
Sequence work around searchable content architecture, protect users affected by new-hire resources are fragmented, and define the point at which rollback is safer than continuing.
- Searchable content architecture
- Role and department permissions
- Forms, approvals, and notifications
Verify and hand off
Repeat the original journey, test a nearby failure, document the result, and make responsibility explicit. A successful handoff leaves organizations centralizing policies, forms, training, announcements, and internal workflows able to understand what changed and what happens next.
- Acceptance evidence
- Current documentation
- Monitoring owner
- Prioritized next step