GOOD ARCHITECT | BAD ARCHITECT

​Over 15 years ago Ben Horowitz wrote “Good Project Manager/Bad Project Manager” as a training document.
We have adapted his concept to create “Good Architect | Bad Architect” as a guide for our firm. 

Good architects know the scope and process of the project. They clearly lay out who is involved and what entities they need approval from.
 
Bad architects make excuses for poor design. They blame the client, the city, or the engineers. Bad architects push their agenda, instead of having empathy for the clients’ wishes, and have the ability to communicate a better solution.
 
Good architects manage their time and their team’s time as it relates to the phase they are in. They work efficiently and seek out solutions. They are not afraid to ask or call people for answers. They manage the slowest leg, i.e. civil, structural, etc. and give them the information and the drawings they need. Good architects meet or beat the deadline.
 
Bad architects do the wrong thing first, waste time on unimportant details. Bad architects don’t communicate quickly, don’t bill on time, and make excuses.
 
Good architects perform after project reviews. They work on improving the process. They create new tools, features, and training. They help their peers willingly. They collaborate to solve the problem.
 
Good architects know their stuff. They study code, understand the basics of other disciplines, know materials’ properties, building cost, and cultivate good resources/relationships while growing their knowledge. An architect can perform basic structural floor, walls, beams, and column calculations.
 
Good architects take on more responsibility leading to more rewards. They create through their hard work, talent, and dedication, and receive great reviews from clients and people they work with. They learn from past mistakes. They help their clients, contractors, city staff, and profession create a better world to live in.