![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Okay, so I have an inservice coming up for work on Monday. One of the issues I want to bring up relating to my job is consistent documentation and communication of information.
My job primarily involves organising events. This means keeping track of lots of information in lots of programs.
Currently, I use:
- Two spreadsheets for financial information. I maintain them both, different people have access to each.
- Another spreadsheet for publicity-fu, shared and maintained with Communications.
- A table for more generalised publicity-fu, only some of which is directly related to me. I own the document and regularly issue death threats against five specific people for the information I don't have control over. The updated table gets chucked at Communications on a regular basis.
- Email correspondence in Outlook with anyone who has anything to do with events.
- Internal staff calendars in Outlook, to see who's available for what event and if they're taking 'initiative' and going to events that don't cost anything WITHOUT TELLING ME. These give me a varying quality of information, dependent on how staff manage their calendars.
- Two FileMaker databases which cover overarching information on the events; one is for statistical purposes and the other has more qualitative information.
- Paper files, which contain hard copies of correspondence, and (theoretically) a hard copy table of what I've done for that event. I say 'theoretically' because in practice finding the time to go and dig out the paper file and trawl through all the information from different sources to update it is near impossible. That, and the blind girl in me doesn't like paper files all that much.
Certain things do with events - travel bookings, approval for advertising, overarching changes to our strategic plans - are dealt with by other people and I have to chase them if I need that information.
This means that information is easy to lose track of and can be very fragmented. If I'm asked a simple question like "Are we having a telephone line at Event X?" I have to go through my email correspondence in the appropriate Outlook folder to find out whether I've spoken to the event organisers about it, then through the finance spreadsheets to see if we're processing a payment for it, and then I might double check the paper forms to make sure there aren't any specific conditions on that phone line, such as local calls only. Then I have to chase the person who needed the information urgently because the event is in three days, they're attending but will be out of the office between now and then and they really need to know NOW.
So it's not terribly surprising that I've occasionally wondered if a wiki would solve some of these problems. I could set up pages for each of the events, and possibly general sections on finance and publicity. I could bung in information from emails and letters as I got it without displaying anything confidential. I could link to the appropriate documents - all on file servers - where necessary. The other people concerned could add in questions and data. In the process, we could all stop chasing each other for simple pieces of information.
But it would be a huge undertaking to set something like that up, and I don't have the ability to justify it at this point. Would it be a better system, rather than creating yet more redunancy? How cost effective is it? How hard is it to use a wiki? How secure can the information be made? Could we get formal training for it, or would we have to teach ourselves?
So, what do people think? I'm not going to be putting a full blown proposal up at this inservice, but is it a totally stupid idea to raise in the first place?
My job primarily involves organising events. This means keeping track of lots of information in lots of programs.
Currently, I use:
- Two spreadsheets for financial information. I maintain them both, different people have access to each.
- Another spreadsheet for publicity-fu, shared and maintained with Communications.
- A table for more generalised publicity-fu, only some of which is directly related to me. I own the document and regularly issue death threats against five specific people for the information I don't have control over. The updated table gets chucked at Communications on a regular basis.
- Email correspondence in Outlook with anyone who has anything to do with events.
- Internal staff calendars in Outlook, to see who's available for what event and if they're taking 'initiative' and going to events that don't cost anything WITHOUT TELLING ME. These give me a varying quality of information, dependent on how staff manage their calendars.
- Two FileMaker databases which cover overarching information on the events; one is for statistical purposes and the other has more qualitative information.
- Paper files, which contain hard copies of correspondence, and (theoretically) a hard copy table of what I've done for that event. I say 'theoretically' because in practice finding the time to go and dig out the paper file and trawl through all the information from different sources to update it is near impossible. That, and the blind girl in me doesn't like paper files all that much.
Certain things do with events - travel bookings, approval for advertising, overarching changes to our strategic plans - are dealt with by other people and I have to chase them if I need that information.
This means that information is easy to lose track of and can be very fragmented. If I'm asked a simple question like "Are we having a telephone line at Event X?" I have to go through my email correspondence in the appropriate Outlook folder to find out whether I've spoken to the event organisers about it, then through the finance spreadsheets to see if we're processing a payment for it, and then I might double check the paper forms to make sure there aren't any specific conditions on that phone line, such as local calls only. Then I have to chase the person who needed the information urgently because the event is in three days, they're attending but will be out of the office between now and then and they really need to know NOW.
So it's not terribly surprising that I've occasionally wondered if a wiki would solve some of these problems. I could set up pages for each of the events, and possibly general sections on finance and publicity. I could bung in information from emails and letters as I got it without displaying anything confidential. I could link to the appropriate documents - all on file servers - where necessary. The other people concerned could add in questions and data. In the process, we could all stop chasing each other for simple pieces of information.
But it would be a huge undertaking to set something like that up, and I don't have the ability to justify it at this point. Would it be a better system, rather than creating yet more redunancy? How cost effective is it? How hard is it to use a wiki? How secure can the information be made? Could we get formal training for it, or would we have to teach ourselves?
So, what do people think? I'm not going to be putting a full blown proposal up at this inservice, but is it a totally stupid idea to raise in the first place?
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
From:
no subject
- data quality; someone has to look after all the changes, otherwise rumour etc. start to become fact
- people like to process their stuff in Word and Excel; getting them to something different (especially as different as a wiki) might prove a nigh-impossible task
Not even to mention the access-control nightmare it's gonna be.