Comments on: Exploring an IT Operating Model for Enterprise 2.0 – Part 2

By: A Review of this Blog in 2010 « IT Organization Circa 2017

A Review of this Blog in 2010 « IT Organization Circa 2017 — Thu, 06 Jan 2011 11:39:16 +0000

[...] Posts Project vs. Program vs. Portfolio ManagementThe Accidental Project ManagerExploring an IT Operating Model for Enterprise 2.0 – Part 2CIO vs. CTO – What's The Difference?Web-Oriented Architecture: From Push to Pull – So Very 2.0!About [...]

By: Exploring an IT Operating Model for Enterprise 2.0 – Part 4: IT Governance « IT Organization Circa 2017

Tue, 16 Feb 2010 14:05:26 +0000

[...] Personal Value SystemsIT Maturity and the Changing Mix of People, Process and Technology – Part 2Exploring an IT Operating Model for Enterprise 2.0 – Part 2Increasing Maturity by Reducing Complexity The Economy, Information Technology and Opportunity [...]

By: itorganization2017

itorganization2017 — Tue, 09 Feb 2010 18:44:39 +0000

Thanks, Russ. My posts may not be sufficiently explicit on this point, but…

To your desire to begin introducing the IT org to the concepts of living in the cloud and collaborative operations, I’d say the best things you can do quickly and (relatively) easily are to:

1. Make sure you are reviewing the whole “IT operating model”, not just the org design (a point made in this post)
2. Take the IT operating model design activities to the cloud. Use cloud-based mind mapping, process modeling, project management, blogs, wikis, etc. – even if only in the name of an ‘experiment’
3. Via those cloud tools, make the operating model design process as collaborative as it can be. That need not equate to “putting the inmates in charge of the asylum’ (please excuse this crass analogy!) You can reserve the right to make ultimate decisions, once you have engaged your key stakeholders and have heard them on the design intents and issues.

By: Russ Aebig

Russ Aebig — Sun, 07 Feb 2010 01:15:58 +0000

I look forward to the next post in this series. I’ve been looking at IT org design inside my current organization. While traditional approaches have predominated my process to date, and want to begin introducing the IT org to the concepts of living in the cloud, and collaborative operations.
I’m eager to read your next post on the integration of these items.

By: itorganization2017

itorganization2017 — Sat, 06 Feb 2010 11:32:00 +0000

I fully agree, CK, that structure is a highly visible aspect, though mostly to the folks inside the IT organization. In fact, one could argue that other than knowing how to engage IT services, structure should be invisible to the business.

I’d also reinforce your second point, that until you really figured out what “services” you should be delivering, what “processes” will deliver those services, how you will “source” those processes or sub-processes, you cannot really know how to “structure” your resources.

By: C K Venkatraman

C K Venkatraman — Sat, 06 Feb 2010 10:34:15 +0000

Some of reasons companies start with the Organization structrure redesign first is that it is the most visible aspects of IT. Over time, structure influences “the way things get done”. Changing the structure sends a immediate message across the board. Also, it is most easily done. Changing processes is much more diffcult and time consuming.

But, i would agree with Vaughan that structural change must be preceeded y changes in other processes that drive IT. By changing structure and leaving rest to “evolve” is a risky move.