Professional Practice: A Guide to Turning Designs into Buildings

Feeling a bit grumpy today so I'm going to go all frank and honesty. A good summary say, if you're daydreaming, or want to have something to get you started on more targeted research in starting your own practice (you know, like the internet). But it's a bit fluffy overall and I'm mostly disappointed. Conversely, the binding is a bit crunchy. Attempting to get this thing to lie open somewhat flat, the binding broke open like it was made of peanut brittle. Now, the pages are spilling out of a book I would probably never actually use in a professional capacity anyway. Also, I hate the format. One of those books, like much of architecture, that just doesn't want to fit into it's context--at all. If it wasn't so annoying and attention seeking, it'd also be an easily forgotten throw-away book. Final analysis. Wish I had saved my money for a more a useful resource.

This book was very helpful for understanding many of the legal issues which an aspiring architect will encounter. The little stories and anecdotes make the life lessons more palatable and therefore more memorable. Some parts of the book may have an unrealistic bias in the direction of the architect. For example he states clearly that each change order needs the signature of the client, the contractor and the architect. Then, the "Architect's Handbook of Professional Practice" will tell you that often the client will be unwilling or unresponsive to these changes and it may become the only option to document change orders so as to make certain a solid paper trail remains in place. He says when you go to sleep with dogs, you wake up with fleas. He is stating that if you do business with less than terrific clients you may run into trouble. Sadly however some younger or less experienced professionals will not have our pick of the litter with our clients, and therefore may have to get our hands a little dirty from time to time. He implies that each form, document, request etc be on a physical piece of paper. In the twenty first century this should all be done electronically. While this may seem like a small matter, it is my opinion that this way of thinking typifies the attitudes and behaviors which are holding architects back and allowing ground to be lost to engineers and "project managers" He talks about Howard Roark, the protagonist of the classic Ayn Rand Novel "The Fountainhead" as a poor model for architect. I agree that we have to be willing to make some sacrifices and work to make our clients happy. Yet he is dismissive of any practice remotely unfavorable the architect such as GMP cost structures for architects' fees. I argue that if contractors can provide this GMP service should the architect not also strive to? On one hand we can strive for professionalism, but I continue to observe many construction projects executed with vertically integrated design build teams, probably with GMPs and/or Cost plus fee. Sure this is a lean and mean approach to building, but architects are loosing ground big time here on these projects. He suggests that clients be required to submit a minimum initial payment, so as to cover the expenses of the first months operating cost of the practice. This could be difficult for small fledgling practice to expect. Then he suggests that this can be withheld in case of a dispute. Does this mean we just take the clients' money if we don't agree? Still a great book and highly recommended just having a few growing pains here.

This book is listed for ARE 5.0 suggested study materials which is why I bought it but it is extremely outdated.

I bought this as recommended reading for the Programming Planning and Practice division of the ARE, and I just finished reading it, and I would definitely recommend it for the PPP division as well as the con docs and sevices division and for anyone looking for a good book on programming and practice.

I took the class under Professor Segal last semester, and its pretty close to being a word by word translation of what he teaches in his class. Every architecture student should read this. It really gives you a comprehensive view of what the actual profession of being an architect entails. Segal sprinkles a lot of anecdotes and some biases which he openly discloses but they really are there to help you decide in what spectrum of risk, personality and job type you see yourself being in the future. Would highly recommend.

I had to buy the book for class. I thoroughly enjoyed the book. It is a quick read and simplified for anyone to understand. Its also portable which helps especially if you have more textbooks.

This book written by Paul Segal is what he teaches from in his seminars on professional practice. The book is oriented towards Master of Architecture students, and is an attempt to prepare them for the realities of working in an office or running a firm. It is written very much as he speaks, with funny anecdotes and a casual style. Segal has many years of experience working and teaching, but is also current with new trends in the profession. The book covers things like contracts, fees, marketing, and insurance. I found it helpful, and a much less dry read than other books on similar topics (a textbook that reads more like a conversation). The thing I like the most about this book is how he tries to explain how these concepts are relevant, and what the advantages and disadvantages of various business models are for the architect. It's not so interesting however, that I would bother reading this book if I wasn't wanting to become a licensed architect.

It's the textbook.

I studied this book to prepare for my PjM exam. It has very useful information about what the architect is expecting during the different phase of building a project. I advise to use it as a supplementary material but not as main study material. It's very good to learn what this book offer.

After I read a few chapters for my exam, I decided to read the whole book. It so much enjoyable reading the book in languages I can easily understand. I would definitely recommend this book taking ARE and those who plan to manage their own practice in the future.

Feeling a bit grumpy today so I'm going to go all frank and honesty. A good summary say, if you're daydreaming, or want to have something to get you started on more targeted research in starting your own practice (you know, like the internet). But it's a bit fluffy overall and I'm mostly disappointed. Conversely, the binding is a bit crunchy. Attempting to get this thing to lie open somewhat flat, the binding broke open like it was made of peanut brittle. Now, the pages are spilling out of a book I would probably never actually use in a professional capacity anyway. Also, I hate the format. One of those books, like much of architecture, that just doesn't want to fit into it's context--at all. If it wasn't so annoying and attention seeking, it'd also be an easily forgotten throw-away book. Final analysis. Wish I had saved my money for a more a useful resource.

This book was very helpful for understanding many of the legal issues which an aspiring architect will encounter. The little stories and anecdotes make the life lessons more palatable and therefore more memorable. Some parts of the book may have an unrealistic bias in the direction of the architect. For example he states clearly that each change order needs the signature of the client, the contractor and the architect. Then, the "Architect's Handbook of Professional Practice" will tell you that often the client will be unwilling or unresponsive to these changes and it may become the only option to document change orders so as to make certain a solid paper trail remains in place. He says when you go to sleep with dogs, you wake up with fleas. He is stating that if you do business with less than terrific clients you may run into trouble. Sadly however some younger or less experienced professionals will not have our pick of the litter with our clients, and therefore may have to get our hands a little dirty from time to time. He implies that each form, document, request etc be on a physical piece of paper. In the twenty first century this should all be done electronically. While this may seem like a small matter, it is my opinion that this way of thinking typifies the attitudes and behaviors which are holding architects back and allowing ground to be lost to engineers and "project managers" He talks about Howard Roark, the protagonist of the classic Ayn Rand Novel "The Fountainhead" as a poor model for architect. I agree that we have to be willing to make some sacrifices and work to make our clients happy. Yet he is dismissive of any practice remotely unfavorable the architect such as GMP cost structures for architects' fees. I argue that if contractors can provide this GMP service should the architect not also strive to? On one hand we can strive for professionalism, but I continue to observe many construction projects executed with vertically integrated design build teams, probably with GMPs and/or Cost plus fee. Sure this is a lean and mean approach to building, but architects are loosing ground big time here on these projects. He suggests that clients be required to submit a minimum initial payment, so as to cover the expenses of the first months operating cost of the practice. This could be difficult for small fledgling practice to expect. Then he suggests that this can be withheld in case of a dispute. Does this mean we just take the clients' money if we don't agree? Still a great book and highly recommended just having a few growing pains here.

This book is listed for ARE 5.0 suggested study materials which is why I bought it but it is extremely outdated.

I bought this as recommended reading for the Programming Planning and Practice division of the ARE, and I just finished reading it, and I would definitely recommend it for the PPP division as well as the con docs and sevices division and for anyone looking for a good book on programming and practice.

I took the class under Professor Segal last semester, and its pretty close to being a word by word translation of what he teaches in his class. Every architecture student should read this. It really gives you a comprehensive view of what the actual profession of being an architect entails. Segal sprinkles a lot of anecdotes and some biases which he openly discloses but they really are there to help you decide in what spectrum of risk, personality and job type you see yourself being in the future. Would highly recommend.

I had to buy the book for class. I thoroughly enjoyed the book. It is a quick read and simplified for anyone to understand. Its also portable which helps especially if you have more textbooks.

This book written by Paul Segal is what he teaches from in his seminars on professional practice. The book is oriented towards Master of Architecture students, and is an attempt to prepare them for the realities of working in an office or running a firm. It is written very much as he speaks, with funny anecdotes and a casual style. Segal has many years of experience working and teaching, but is also current with new trends in the profession. The book covers things like contracts, fees, marketing, and insurance. I found it helpful, and a much less dry read than other books on similar topics (a textbook that reads more like a conversation). The thing I like the most about this book is how he tries to explain how these concepts are relevant, and what the advantages and disadvantages of various business models are for the architect. It's not so interesting however, that I would bother reading this book if I wasn't wanting to become a licensed architect.

It's the textbook.

I studied this book to prepare for my PjM exam. It has very useful information about what the architect is expecting during the different phase of building a project. I advise to use it as a supplementary material but not as main study material. It's very good to learn what this book offer.

After I read a few chapters for my exam, I decided to read the whole book. It so much enjoyable reading the book in languages I can easily understand. I would definitely recommend this book taking ARE and those who plan to manage their own practice in the future.

Decent outline and supportive material. It's difficult to write this kind of book since covering the entire practice of architecture is impossible. The industry is ever evolving and to present relevant, intelligent and useful information needs to be updated regularly. Hope to see future versions.

I very much enjoyed Paul's clear and concise pro practice guide. It works perfectly to compliment more technical and difficult ARE study materials. Lots of helpful examples given. Packed with information. Thanks Paul, wonderful read.

Compared to other sources I consulted while studying for exams, this book contains an equal amount of pertinent information and it is very easy to ready. The writers style is more conversational compared to other technical resource and made the topics easier to understand.

A must have companion for every project/construction manager

This book is well written and very easy to comprehend. I feel that is really captures the industry in the simplest sense possible. I feel it was a good resource for studying for my AREs. Definitely recommend.

I really like this book; its easy to read without too much filler. Covers the subject well and I think a must read for any Senior level person in Architecture.

Very clear, practical and applicable advice. Have given it to several other people in my firm (including the office manager… who loved it). Definitely recommend!

It's a good read for PCM part of ARE exams.

A good overview for the project management exam. It’s a good starting point

helped me study for my ARE exams! easy to read and carry around