Tuesday, July 22, 2008

Technology Teams

I work with technology. But the more I work in technology, the more time I spend working with people. We have the all these great systems in place, but they are nothing if you have not built the following soft human aspects into them:

1) business intelligence or rules built into your code
2) some kind of UI for human beings to access your great box
3) processes for managing change

And in almost all cases, you can assume that everyone thinks they have steps 1 through 3 locked and sealed, but they always don't. I forgot the author, but s/he posited that the web's ease of use made everyone think they're an expert and that any change is a piece of cake. Result: CHAOS. And you have no infrastructure to support building intelligence into your technology because it's all assumed.

How do you manage change?
In larger, more mature organizations, you already have systems in place, but what about smaller groups? Smaller groups remind me of the primordial soup theory where you hope to god some lightening bolt hits your content group or some business users in the ass, and you'll some emergent process or organization. Nah, in reality, you need to reach out to people and effect change by shifting attitudes. Sans technology. By changing attitudes and perceptions you can put in the foundation of a functioning IT or technology group.

Links for your edification:
Life Soup

2 comments:

kbell said...

As a member of the content group, I just hope the lightning bolt doesn't hurt.

cottonmather said...

Thanks for your comment, KB. I'm referring to a nerf lightening bolt.