Implementing Lean Intranet Sharepoint

[orion1]

Hello,

We are going to implement Lean intranet share point in our organization between different plants in order to improve Lean knowledge sharing.

Could you please share your experiences about this topic
( how is organized your share point, content, is it useful, if yes in what extent, who has access to the share in organization, ....)?

Any suggestion would be helpful.

.

Orion

 

[Ronen E]

Hi,

It sounds like you are considering an implementation of an information system.

I recommend that you hire a professional systems analyst (I am not one) to analyse the system and come up with a system requirements specification (that would cover all the topics you listed, and more). Then you can shop around for the best package, either off-the-shelf or customized.

Personally, I have very little faith in intranet systems as means for propagating knowledge.

Cheers,
Ronen.

 

[KnoKsuKaO]

Hello,
I would like to ask you, how a large organization are?
We don't information system, because we have about 40 workers in total and we use systems as (onedrive, google).

Information system is very expensive for us.

 

[orion1]

Hello,

We do not plan to hire some outside of the organization and no information system ( some specific softer for this purpose).

We have intranet with shared folders as well.

Access will be provided for app. 500 people in different plants in final stage.

BR

 

[Pancho]

Hello,

We are going to implement Lean intranet share point in our organization between different plants in order to improve Lean knowledge sharing.

Could you please share your experiences about this topic
( how is organized your share point, content, is it useful, if yes in what extent, who has access to the share in organization, ....)?

Any suggestion would be helpful.

Orion

Hi Orion,

When you say "Lean intranet share point", do you mean, specifically, Microsoft SharePoint software? Or do you mean a generic point on a server to share knowledge?

If the first, imo, Sharepoint is good if you already have a large library of MS Office documents. But it doesn't encourage linking between documents, nor the creation of a small-world network of knowledge, and therefore, accessibility is never so great. Last I checked, it was expensive too.

If the second, I'd recommend trying a wiki. Wikis are web spaces where anyone in your organization can learn from, or contribute to, shared knowledge. They have several features that promote this, such as easy editing, easy linking, accountability, and full and automatic history logging. With basic care, wikis become useful repositories for all of an organization's knowledge. More importantly, they also become little ratchets of improvement, as they are incredibly helpful in closing the often-missed "Act" part of the Deming cycle.

We have had excellent experience using a wiki as point for collecting and sharing knowledge among all our employees in various disperse locations.

 

[orion1]

I mean, a generic point on a server to share knowledge between different plants.

Wiki is new to me, i will get informed about it.

I am interested more in the content of the share point , not in the technical part of the share point.


Thank you.

Orion

 

[pog451]

I have worked for a company where we had good experiences installing "Info Towers" in the production areas. These had a standard rolling "latest news" display, but users could access the quality documentation and to a limited extent production documentation too.

Im a big fan of Wikis, but I haven't actually implemented one in a working environment.

The big thing with all these tools is - Don't let them gather dust. Make sure there are continuous, relevant updates so that the users see its a living system. As soon as things go static, even for a couple of days, the users will start to ignore the system.