Our developers use one for knowledge capture/transfer. I've thought about using one for project status, but I don't have the audience to justify the effort. We've got a company newsletter that I'm pretty sure most people don't read.
I have heard success stories, using it for PM purposes; company culture plays a role in it. Saving Changes...
Vijay SuryavanshiProject Manager - Engineering| RECARO Aircraft SeatingPlantation, Fl, United States
Hi Jason,
In setting up such a thing, you must see what value it brings in. Internally in my earlier company, we had company intranet site that listed all Engineering tools, best practices in manufacturing, specifications of product and integrator requirements, so on and so forth. A Wiki may be too detailed and may not be as useful (people may get lost in the details or plethora of information) for employees to train themselves or refer internally when required. Aim must be to increase productivity, self train and bring in value.
In other words, Asron's questions makes more sense ? What do you want to do with it ? Saving Changes...
Thanks for the quick responses! I work in Facilities Management at a good sized University. We have over 100 building on campus and my department in total has few hundred staff. While we have records ( reports, receipts, blueprints, manuals etc) its not organized or available in a way front line staff can easily access. It also lacks institutional knowledge ( buildings and systems quirks, why certain things are they way they are etc) about the buildings and systems that exists primarily in mine and my staff heads. My vision is to create a internal wiki containing both of these resources (formal and institutional) where this information can be gathered and made available to our front line staff in a way that isn't available today.
I am very much in the early stages of this and I truly appreciate any and all comments.
Thanks,
Jason
...
1 reply by Aaron Porter
Apr 14, 2023 10:55 AM
Aaron Porter
...
Thank you for the clarification.
When I started with my current employer, our IT team was using a SharePoint Wiki, which can be good if you have a lot of people who need to access it and you need to control who can edit the content.
The team decided they wanted something a little easier, since only IT has access to it. We switched to a OneNote notebook, with a section for each main content area and multiple pages for each section. Our notebook has around 30 sections, but the page content is very specific so it's pretty easy to work with.
Several years ago, I worked at a company that used Confluence pretty extensively. It worked pretty well for the developers, and it was easier to use more than just text than a SharePoint wiki.
You'll want to consider the volume of information, who can add/edit content, do you need an approval process, and how people will search for information, among other things. Our notebook is small enough that if something can't be found with two or three clicks, OneNote's search function is enough. If you want to be able to add keywords to your content and search for keywords, not just words in the content, a real wiki might be better.
Thanks for the quick responses! I work in Facilities Management at a good sized University. We have over 100 building on campus and my department in total has few hundred staff. While we have records ( reports, receipts, blueprints, manuals etc) its not organized or available in a way front line staff can easily access. It also lacks institutional knowledge ( buildings and systems quirks, why certain things are they way they are etc) about the buildings and systems that exists primarily in mine and my staff heads. My vision is to create a internal wiki containing both of these resources (formal and institutional) where this information can be gathered and made available to our front line staff in a way that isn't available today.
I am very much in the early stages of this and I truly appreciate any and all comments.
Thanks,
Jason
Thank you for the clarification.
When I started with my current employer, our IT team was using a SharePoint Wiki, which can be good if you have a lot of people who need to access it and you need to control who can edit the content.
The team decided they wanted something a little easier, since only IT has access to it. We switched to a OneNote notebook, with a section for each main content area and multiple pages for each section. Our notebook has around 30 sections, but the page content is very specific so it's pretty easy to work with.
Several years ago, I worked at a company that used Confluence pretty extensively. It worked pretty well for the developers, and it was easier to use more than just text than a SharePoint wiki.
You'll want to consider the volume of information, who can add/edit content, do you need an approval process, and how people will search for information, among other things. Our notebook is small enough that if something can't be found with two or three clicks, OneNote's search function is enough. If you want to be able to add keywords to your content and search for keywords, not just words in the content, a real wiki might be better. Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
Thank you for sharing input and clarifications. Saving Changes...
Community Champion
