2. BEA.net
Intranet Background
▪ InSite last redesigned in 2007.
▪ Limited functionality (very static).
▪ Content managed by Web team.
▪ Lacking collaboration tools.
▪ Content in silos – organization based, not
task based.
2
3. BEA.net
Insite: What doesn’t work
▪ Content grouped by
department and subject
can be confusing
▪ Navigation buttons are
overwhelming and not
consistent
▪ Navigation behind the
buttons is not always obvious
3
4. BEA.net
Insite: What are we lacking
▪ Internal communication tools
▪ Document sharing
▪ Accurate search results
▪ Logical Information Architecture
4
5. BEA.net
The Big Issues
▪ New BEAnet Information Architecture
Top tasks
Subject driven
▪ Content management will be at program level
Permission based workflow
▪ Technical improvements
Collaborative tool (OneBEA)
Improved Search
Template driven
Analytics
5
Notes from mtg:
One directional
# of pages and files
ROT
Consistency with design
collaboration with OCIO
Adhoc additions to navigation
A-z search
Why do we need a redesign?
Top accessed pages
Q: How would you find the pay scale?
Improve internal communications – Jim’s list of ideas – blog, wikis, door posters
Collaboration
Content ownership – access to make immediate updates
CARS
Improve calendar of events
Accurate, updated, relevant information
IA – broad and shallow – deep narrow
Task orientated
Consistant in design and navigation
Add example – revisions/proposals – blog/wiki tools for comments, review, knowledge management
Homepage prototype – user centric
List what’s new
Navigation
Task based
Icons on right
HP feeds
Problems finding content
Search problems – HR
Key application – documents
-- organize files (topic or division driven)
-- Tagging
-- Full index searching
-- auto archive and review date
> Next Example of input form
Versioning – maintains history
Review date –relevant
Advertise –
Review and approve
--Multiple workflow sequences – first manager is emailed, second manager notified for approval.
Permissions
--Permission based workflow – define groups and sequence, identify staff to be editors, reviewers, final sign off
Next > permission based content
-- Establish Permission based content
– define groups
--COR agendas, important notices
COR guidelines and info – reduce
Next - calendar
Two content types
- applications and widget
Application types:
Calendar
E-forms
Department homepage
Blogs
Photo libraries
Calendars
-brown bag training
-Staff meetings
-Asd specific events
Next > blogs
Zero based budget
– info in centralized space,
Blog on safety and security
- updated policies on smoking near the building
– announcement of upcoming events,
reduces emails traffic,
Reduce number of meetings
Next > widget example
4 types – simple, social, feed, external
Highlight employees
RSS feed and weather
– good examples used frequently
Daily tips – upcoming reminders
>Next polls
Informal polls
Feedback
Next > – employee hub
--replaces employee directory
-- keywords skill sets
–Centralized space for alerts
– workflow process
-- Training reminders
– feedback on postings
– comments suggestions