[Sigia-l] Help! New job ... terrible knowledge management

[tessa]

Lucie,

> After a year of seeking employment as an IA, I finally did a bit of a
> career switch, and have been hired as a researcher/analyst at a
> government contractor.
Hmm, if you don't mind me asking, what is the job description for your
researcher/analyst position? This may unravel some mysteries as to your
treatment in meetings.

I don't have much advice, but I too just finished a directory project for a
law firm who uses Access and it was awful. The search results for simple
things yielded obscure results all over the board. They don't mind, because
for now, the IT department looks good because they have saved money and can
say that the users just need to be more savvy with computer searches. Their
mantra is, "It is the users fault".

> Everyone here thinks it is just fine, and so far no one wants to listen
> to me when I say there are serious problems. They are just plowing ahead
> creating this massive Access database with totally messed up categories,
> all of which were chosen by the programmer.
An interesting outlook, but one I myself could not get through. Hell, the IT
folks at the law firm told me that metadata was just "frosting", and they
use frames (which is already causing untold problems in the intranet, but
hey, "It is the users fault")....Hmmm, your IT department may be scared for
their jobs and their income, so if this could be true, keep this in mind as
you move through this situation. Scared people will behave differently and
desperately. Pick your allies carefully, and watch those who choose you -
you are the new person on the team, so examine what motives they may have.

> Well, not surprisingly, the system of sharing research & organizing the
> database here is absolutely appalling.
The crew may be in denial. It is the fear-thing again. They are so afraid
that it won't work, they may want absolute control...if they just shared
ideas and the responsibility, could it be better for them?

Anyway, my message to you is that you are not alone, the situation is not
unheard of, BUT it still sucks and it will take a great deal of goodwill,
persistence, patience and understanding. Don't expect this to be solved in
several months, it will take time and strong allies.

In my experience, IT departments have traditionally been given ultimate
control in corporate situations because no one who is NOT in IT can take
much time to understand the situation. So, now anyone who comes in to
challenge them, may be seen as trouble (maybe not, I am playing the devil's
advocate). I would document your research and bind it in with your
deliverables (Tufte comes to mind, here). A formal document such as this can
not be ignored, but you should be careful how, when, why and to whom you
present the finished product (get allies to support you). Mention it to the
team as you are building it and let them know where you have stored it on
the servers (always keep a backup copy). That way you are not viewed as
being covert, but you are also not rubbing their fears into it. You have put
it out there for them. However all this comes back to your stated role in
the project and in your job description.

Break a leg.

Tess