Mr Richards on technology, information, and people

Sometimes I think posturing, or "to act in affected or artificial manner," can be one of the most dangerous threats to a software development project. Especially one that deals in the public sector. In the Federal government space, where there are numerous agencies, regulatory bodies, contracting companies, management consultants and bureaucrats working towards implementing a software solution of exceeding complexity, to act in affected or artificial manner can go a long way towards threatening the success of the project.

Consultants may posture and bristle at other consultants encroaching on their turf, with no less aggression than a gang-banging Crip making the wrong turn into Blood territory. Contracting firms will posture to ensure the sale of their labor and services, and will play politics to obtain lucrative contracts. And bureaucrats will posture to best exude their seniority and expert position, to make that final determination that the technical solution is befitting of their blessing, and avoid the whole "working together" concept.

Of course this type of artificial stance only seems to be there for offensive reasons - but it can also be defensive. It could take the form of finger pointing in emails and during meetings - where instead of focusing on how to correct a given problem, precious development time is wasted on determining who is at fault, or responsible, for correcting a potential error. This environment only deters people from sharing problems for fear of losing face, and fosters hostility and mistrust, two things that can slow down and even prevent communication between parties.

Taking responsibility, focusing in issue resolution with posturing, and a strong work ethic are much preferable values to aspire to in one's stance.

Labels: gov 2.0