Let’s start with the easy ones and move forward into the space of “Architect’s Should.”

Number One  with a Bullet: Be aware of their impact on others. So easy to say. So easy to talk about. Even freaking easy to tell others. But what is your impact? Do people trust you? Do you people respect you? Do people listen to you?

All of those are limiters. They limit the effectiveness of the architect in what-ever scenario the architect is in. Determine your impact as you move forward.

Number two: Architects should have some technical chops but not at the expense of as I stated in September, the business conversation. Its also about having the right conversation at the right time. I met an architect once in the midst of a project meltdown who said “but I told them about this very risk.” He in fact had, what he had done was during a hallway conversation he had mentioned the risks. Hallway conversations are not for discussing risks.

Number three: The limits and the limiters, understand the difference and how deal with each. The reality of the world we are in, everything has a limit. Knowing what those limits are make a huge impact on your project, as you don’t end up in a situation where you have to exceed the limits to succeed. The Limiters are more dangerous. In my personal blog I have discussed (and on the old IASA Blog) the concept of communications patterns and anti-patterns. Beware of the limiters they are a huge communication anti-pattern ready to derail your project.

Number four (last one for this blog): Don’t be bound by technology. The best solution to your problem may be released while your project is going on. If that is the case be agile enough to move with the new solution. Don’t become tied to your solution. Sometimes your solution is an anchor. If you are tied to it, then sadly you go with it when it is tossed off the ship.

Thanks for reading!!!

Scott Andersen IASA Fellow