some call it not taking ownership
Sep. 24th, 2007 07:27 amAs some of you well know…
(“Huh oh… Serge is going to launch into a Science lecture.”)
Am not.
(“Are too.”)
Really, I’m not. I’d have to think I know much about Science before I start a lecture. There are plenty of times I’ve made a fool of myself because I went in thinking I knew what I was talking about. Why then would I do something that I know I know nothing about? So, no, there will not be any lecture.
(“Go ahead. Knock yourself out.”)
Thanks.
As some of you know, one of the office projects that has consumed quite a few of our team’s waking hours(*) is the setup of a backup server for our programs. So, should our main server go belly up, or croak, or burp, or hiccup, we could switch over to the backup fairly quickly and keep our team’s business going. One of the project’s elements that has been my sole responsibility is the setup of file transmissions. For every file sent to our main server, I’ve been working with each file’s provider so they would also send that file to our backup server. That, unlike other aspects of the project, is pretty much on schedule and will be completed before the end of October. Huzzah and all that.
One of those files has been a bit problematic though because its provider said in late August that they would not have the resources to work on this. As a result, I wrote an email describing the situation and possible alternatives and sent that to my team, which is 1100 miles away. One team-member wrote back right away, seeing problems with what I felt was the best option. I agreed that there were indeed problems, and wrote back to the whole team, saying that I was aware of the disadvantages of my preferred solution, and asked them for other possibilities. That was on August 27. In the weeks that followed, since nobody had written back, I asked them again a few times, and never heard back. This week, when I mentioned this to my manager, she said that, unless I write to a specific team-member, nobody will respond because that’d mean they’re taking ownership of the situation. I call that not being dutiful team-members no matter how far away people are physically, but I didn’t say so to my manager. I took her at her word and, on Friday, wrote specifically to the programmer who had had problems with my initial proposal, and asked him outright about alternatives. He wound up agreeing with my original idea of 4 weeks before, provided certain conditions were met. As those were indeed met, I sent an email to the whole team delineating what I’d do. And right away another team-member wrote back saying NO-YOU-CAN’T-DO-THAT. Too bad she took so long in doing so. Now, I’m back to square one, sort of, and wrote to that file’s providers to ask if they really can’t spare the resources for this new file transmission.
Oh well...
----------
(*) And of few of our not-so-waking hours. And some of the waking kind that happened on my birthday.
no subject
Date: Sep. 24th, 2007 03:50 pm (UTC)(On the other hand, I walked into my office this morning to find a fluorescent light fixture dangling by my desk. Had I been sitting at it, I would have been seriously injured by the light fixture coming off one of its supports.)
no subject
Date: Sep. 24th, 2007 04:03 pm (UTC)no subject
Date: Sep. 25th, 2007 12:18 am (UTC)Serge - You know, that's exactly the sort of job security a person doesn't want. Ugh.
no subject
Date: Sep. 25th, 2007 12:26 am (UTC)no subject
Date: Oct. 28th, 2007 05:20 am (UTC)Happy belated birthday!
no subject
Date: Oct. 28th, 2007 11:41 am (UTC)As for the birthday wishes, thanks. One year older, one year wiser. A tiny bit wiser.
no subject
Date: Oct. 28th, 2007 11:46 am (UTC)no subject
Date: Oct. 28th, 2007 11:53 am (UTC)no subject
Date: Sep. 25th, 2007 03:18 am (UTC)no subject
Date: Sep. 25th, 2007 03:34 am (UTC)Ow!
I should be more careful next time I pat myself on the back. I just dislocated a shouyler.
no subject
Date: Sep. 25th, 2007 03:39 am (UTC)no subject
Date: Sep. 25th, 2007 01:30 pm (UTC)no subject
Date: Sep. 25th, 2007 01:56 pm (UTC)