Index_O

O

offline/online intranet access, see remote access.

open source CMS packages, 169

PostNuke, 169

open source portals/blogs, 84

developing intranet using, pros & cons, 84

listing, 85

OpenOffice

non-HTML intranet contributions, handling, 146

organization-specific applications, 13

OS (operating system), choosing, 42

Linux/BSD, pros & cons, 43

Windows, pros & cons, 42

overgrown intranet, occurring, 245

as dispersed/uncontrolled intranet, 246

rather frequent occurrence, 249

evolution, case study charting, 246

time T/T+1/+2/+3/today stages, 246–48

symptoms, listing, 253

reasons for, 249

implementing new CMS, 250

inexistent publishing controls, 250

intranet NOT regarded as strategic resource, 251

management's lack of interest, 250

meaningless directories/filenames, examples, 253

organic growth, 249

random menu navigation system changes, 252

sub-brand site ownership, 249

overgrown intranet, re-developing, 254

advantages, 254

business objectives, supporting, 255

business-oriented info, providing better, 256

communication, accelerating, 256

employee advantages, 256

employee induction process, accelerating, 256

internal service, improving, 255

on-line community, using as, 257

organizational development initiatives, reinforcing, 256

user-centric intranet, developing, 255

navigation re-development, 276

access permissions list, example, 276

global menu presentation, guidelines, 277

guidelines, 280

needs-based site structure/access hierarchy, following, 281

pilot sites & feedback, using, 281

security vs. ease of access, 276

silo menus, negative case study, 279

silo menus, user-oriented ones replacing, 278

planning/marketing, 259, 266, 271, 273

announcing planned changes, 260

costs & ROI, determining, 267

positive case study, 267

design vision required, 260

existing perceptions, challenging, 273

expectations, managing, 264

feedback, obtaining, 262

guidelines, 261, 266, 271

new CMS advantages, popularizing, 273

single/distributed servers choice, pros & cons, 268

standards, considering, 274

strategy NOT fix, creating, 262

users/stakeholders, involving, 271

ways of, 273

workshops/brainstorming sessions, running, 260

researching user requirements, 257

guidelines, 257

portal improving navigation, example designing, 258

transition strategies, 275

controlled flexibility required, 275

navigation re-development, 276

new microsites, handling, 282

revising strategy for change, benefits, 275

user expectations, researching/considering, 279

user/stakeholder support/involvement, 263, 265, 269, 274

'ambassadors'/developers, 272, 274

guidelines, 269

management interference, negative case study, 263

management restricting input, negative case study, 270

resistance to change, handling, 265, 272

'difficult' owners/'sub-branders', 272

senior managers, 272

ownership, web pages

establishing, maintaining intranet, 154