The Systems Builder as Leader

Computerworld - In my column last month , I defined systems builder as a person who is central to the success of any systems development project. This person
possesses skills in two main areas: designing systems and leading projects to build systems. I then looked at the five basic skills needed for designing systems. This month, I'll discuss the six practices that are the basis for success in leading projects.
In my years of experience in developing systems and watching others do so, I have found these skills to be the essence of project leadership. The more accomplished the systems builder is in these areas, the higher the success rate.
1. Be an effective communicator and negotiator. The systems builder as designer collaborates with others to create a compelling system vision. The systems builder as leader communicates this vision in a way that attracts people and motivates them to act. This means clearly describing a system's features and benefits to a business and a technical audience and showing how development will progress from vision to reality. Systems builders may not all be great public speakers or have outgoing personalities, but they find ways to use the talents they do have to get the message across and win support.
2. Set high standards and great expectations. People want to participate in projects that they believe will improve their skills and bring them recognition and rewards. So the systems builder sets high standards for performance and helps people to attain them. The systems builder also paints a picture that highlights all the great things the project will bring about. As Daniel Burnham, the great Chicago architect, said, "Make no small plans. They have no magic to stir men's blood."
3. Delegate, delegate, delegate. All well-defined projects have a set of objectives or milestones that must be reached in order to finish the project. The systems builder delegates the accomplishment of these objectives to the qualified people who have been attracted to the project. (If no qualified people have been attracted, then stop the project.) Along with delegating responsibility to achieve objectives, the systems builder also works to provide people with the resources they need to do their jobs. In this respect, the systems builder becomes the servant of the people working on the project.
4. Be available. Delegating work does not mean delegating ultimate responsibility for the project. Systems builders stay actively involved. They hold regular, weekly project meetings that are a forum for honest discussions about issues, and they have an open-minded approach