Rants
Questions
Soapbox
Best Practices
Apply today for a FREE subscription to CIO Magazine!
Tue, Jun 12, 2007 0:11 EDT

|
Posted by: Michael Hugos in Best Practices Topic: DevelopmentBlog: Doing Business in Real Time
Current Rating: |
A recent experience further reinforces my belief that there is one central person who is key to making IT agility happen. That person is the “system builder”. I’ve just finished a 30-Day Blitz with a team of developers at a company and in this case that central person was a manager and senior developer on the client’s IT staff. I coached him on how to employ his talents to fill the role of system builder. He was already good and he caught on fast; the business people really liked the system he and his team delivered.
Successful system builders all have some traits in common. They all understand the specific business issues their system is supposed to address and they find simple and effective ways to use technology to get things done. They are also competent in the six core techniques and they display high levels of skill in five other areas that relate to designing systems and running projects. Using these talents, they become the totally committed, driving force that provides the leadership that makes their projects successful.
Usually the system builder comes up through the technical ranks and learns about business. Sometimes this person comes up through the business side and learns about technology. Either way, the systems builder is a person who can clearly demonstrate talent in five areas. There are other areas where talent is good, but without talent in these five areas, a person cannot succeed as a system builder.
1) Understand the Business Operation – The systems builder needs a good grasp of the concepts and rules that guide the business operation. This means knowing how the operation fits into the overall business, how the work of the operation is performed, and what the cost and profit factors are.
2) Create an Inclusive Process – System builders must be able to consistently produce competent (and sometimes even brilliant) designs in spite of high levels of complexity in both business and technology. Complexity looses much of its power to intimidate and confuse if groups of people with the appropriate skills and experience are brought together in a collaborative process where they pool their collective insights. The systems builder is the one who orchestrates this process.
I really like your point about “Tolerate Not Knowing.” A lot of IT executives fall into the trap of projecting confidence even when they are not sure whether the solution under consideration is the best way to solve the business problem. Their staff soon stops investigating other options because they feel their boss must know what is best and thus investigating alternate solutions is a waste of time. We need to recognize that changing one’s mind when presented with better information is a sign of confidence, not weakness.
Hi Asengupta,
I could not have said this any better than how you have put it. Agility requires that we be committed to delivering effective results and not cling to initial ideas. Since the world constantly changes in unexpected ways agility requires the ability to see a better idea when it comes your way.
It is uncomfortable to not know. Yet by immersion in the situation, by following the process of exploring options and testing out ideas within the constraints of the circumstances you are in, a simple and often elegant answer does emerge.
As Obi-Wan Kenobi told Luke Skywalker, "Close your eyes and let the force be with you..."
Best regards,
Michael
Very interesting that the first characteristic you depict is related to users' business context: "They all understand the specific business issues their system is supposed to address"
It's a kind of the other side of the "Product Owner"
PierG
http://pierg.wordpress.com
Nice post Michael. I think decision technologies have a part to play in this too.
Nice post Michael. I think decision technologies have a part to play in this too.