my first question on the list. I´m designing an intranet for a
conservative client who has a strong organisation oriented company
culture. Interviews and surveys with staff mention that an
organisation-structured intranet is the most natural way of using it.
However, my client does not want this, and I don´t want this due to the
administration necessary whenever a reorganisation is made (which is quite
often). The goals of the project are:
-to strengthen the internal image of the company that all employees are
part of a chain (or other similar metaphor) to serve the clients
- to enable more interaction and collaboration between organisational
units in the company
Still it is supposed to be a working tool for the employees.
One way of solving this is a task/process oriented structure, but there is
no time or money to gather all data to do this.
It seems like all my efforts point towards to at least a
semi-organisational structure because most of the tasks people do on the
intranet are department-specific and of no use to other departments.
So, here´s my question: Is this a big no-no or is it unavoidable to be
stuck with organisational-type sections on an intranet?