Project management in IT companies

I've moved from a consulting company targeting smaller companies to a fairly large global company and it's interesting to watch the differences in IT management. There are a lot of similarities, too.

On the differences:

• Budget: Most of my clients in Seattle had to be convinced, cajoled, or outright pushed to by high quality hardware. In my current company, they are so paranoid about downtime that they through money at redudant hardware that they really, really don't need.
• Schedule: Right now, I was working on an "accelerated" project - I only had three months to plan and deploy it. I don't think I had three months to plan anything with my Seattle clients.
• Turf: There arent't enough people in a small company to really generate big turf wars whereas larger companies can't seem to function without them. There were definately some "I built it, you can't touch it" moments with my Seattle clients but the amount of time spent manging that was quite small compared to now.

Similarities:

• Dithering: When it comes to tech related issues, there are always "what if" dicussions - "what if we build a custom app instead of buying it?", "what if we outsource it", "what if they have a new version?", "what if we using an open source product?", and so on. The amount of time that it takes to explore options, discuss things with leadership, and get approvals for things seem to take the same amount time. Even though my current company is 700 times bigger than my largest Seattle client, they don't actually move noticably slower. I'm actually kind of suprised by that.
• Managing change: It seems that both small and large companies don't do a good job of actually preparing thier employees for major changes. Very few of my clients would send employees to training before pushing a new software (Office, timesheet tracking, or whatever was being deployed). I tried very hard to push for end-user training in my Groove project but it was delegated to local offices instead of being pushed from HQ. And that has devolved to "go read this website" rather than any structured training. And now, I am not surprised that most of the questions I get are "what is this thing and what can I do with it".
• ROI: Both my Seattle clients and current company seems to suffer from an odd approach to new technologies. They seem to start with some big plan that will have some big benefit (new communciation tool, smoother operations, time savings). Then, about half way through the planning process, the technical details take center stage. Whenever there is a hiccup, the project shifts towards ease-of-implementation rather than maxium-user-benefit. It seems that the big picture goal gets forgotten slightly - it's subtle but very noticable.

It's only been a short time, though, so I'll keep an eye on other interesting things as it develops.