Being a "continously increasing" aknowledge activity, would you use a wiki page to gather all the information of your projects?
Working in a Engineering Company the amount of technical data we share is sometimes ridiculous: a pot where locate all the data is highly requested for a quick and unique reference.
What is your point?
Hugs,
alberto Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
This is Knowledge Management.
Sure, why not. If the platform is available. Your intent is correct .... centralize information and increased accessibility. That said, if you are leading the charge for this to be the practice moving forward, take the time to plan out the process for other's to follow - Content, taxonomy, ....
Remember, its not just dumping information in a central spot, there is the need to consider how people will find the information they might need.
"Get the right information to the right people at the right time, int the right context."
-Good Luck.
...
1 reply by Alberto Tummillo
Mar 24, 2017 7:11 AM
Alberto Tummillo
...
you're right: I am actually dumping the information in a centralized area so everyone will retrieve it upon their needs as I can't be the PA of my colleagues!
Once I deliver the document / technical data / whatever to my relevant colleague, I'd just expect them to process it and return it to my on time - if not on time, I do push.
Then I drop the info in the WIKI for general access, using dedicated tags such as "electrical" or "process" or more peculiar tags such as for Suppliers.
In this way, I don't have to dig in Outlook for "that mail I sent back in..." but just make more responsible colleagues for their jobs.
Sure, why not. If the platform is available. Your intent is correct .... centralize information and increased accessibility. That said, if you are leading the charge for this to be the practice moving forward, take the time to plan out the process for other's to follow - Content, taxonomy, ....
Remember, its not just dumping information in a central spot, there is the need to consider how people will find the information they might need.
"Get the right information to the right people at the right time, int the right context."
-Good Luck.
you're right: I am actually dumping the information in a centralized area so everyone will retrieve it upon their needs as I can't be the PA of my colleagues!
Once I deliver the document / technical data / whatever to my relevant colleague, I'd just expect them to process it and return it to my on time - if not on time, I do push.
Then I drop the info in the WIKI for general access, using dedicated tags such as "electrical" or "process" or more peculiar tags such as for Suppliers.
In this way, I don't have to dig in Outlook for "that mail I sent back in..." but just make more responsible colleagues for their jobs.
Cheers,
alberto Saving Changes...
Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
Feel free to use any system of organization that works for your particular situation - in doing so, you'll often innovate brand new ways to do things. I'm currently using SharePoint to organize data for an IT project, but a wiki might be even better. Thanks for the idea. Saving Changes...
Lisa KomidarService Delivery Manager - Sr. Engagement Manager| Optimum Healthcare ITKane, Pa, United States
For me, I do not like wikis. I find them challenging to control and find the information that I need when I need it. I can use them if I need to use them. I just don't care for them.
Box has provided some good solutions as well. But you don't have an index to quickly see everything. But it has a great tagging and search feature.
What it comes down to is what would be able to be used by everyone involved in the projects. Even a solution such as Google can provide for a common place to develop your project content. Saving Changes...
"Impartial observers from other planets would consider ours an utterly bizarre enclave if it were populated by birds, defined as flying animals, that nevertheless rarely or never actually flew. They would also be perplexed if they encountered in our seas, lakes, rivers and ponds, creatures defined as swimmers that never did any swimming. But they would be even more surprised to encounter a species defined as a thinking animal if, in fact, the creature very rarely indulged in actual thinking."
