Another day of not getting along with technology. Can SOMEone PLEASE fix the frikkin' wireless connection at school???????
I think I understand the whole service-oriented architecture thing, at least conceptually. And I also understand the importance of knowledge management and knowledge exchange. Heck, I'm going to be working at a consulting company, so I get it. We need to talk to each other, we need to share knowledge, and it needs to be a seamless transaction in order to work well.
The part that I still really don't get, though, is HOW this all happens. Over the summer with Deloitte, we tried to compile a comprehensive service delivery model, and the client (the IT department, for the record) couldn't do it. There were just so many different services housed so many different places that it became an exercise in futility. Obviously, this is part of the problem, but I still don't understand what I'm supposed to DO about it.
N may be for knowledge, but at this point N is also for no clue.
Subscribe to:
Post Comments (Atom)
I meant to respond to the last one on this so I'll just post here. I totally am with you Holly. At my last job I purchased a software system that unified several departments information. There is still though, not a single system out there that can cover all areas of a business so my question is - shouldn't they be working on allowing different systems to TALK with each other while still maintaining record privacy? By the time I left we had worked out the talking of two systems, but the third system's director would have nothing to do with the project. Technology is fantastic and does wonders with communication, but it's fascinating to me how that aspect seems to be the last realized.
ReplyDelete