<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: risk</title>
	<atom:link href="http://m.ammoth.us/blog/2010/07/risk/feed/" rel="self" type="application/rss+xml" />
	<link>http://m.ammoth.us/blog/2010/07/risk/</link>
	<description>the herculez gomez of architecture blogs</description>
	<lastBuildDate>Wed, 08 Feb 2012 04:04:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Public vs Private &#8211; Mammoth Blog Quote &#124; Local Sid</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-127756</link>
		<dc:creator>Public vs Private &#8211; Mammoth Blog Quote &#124; Local Sid</dc:creator>
		<pubDate>Sat, 19 Mar 2011 03:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-127756</guid>
		<description>[...] risk – mammoth // building nothing out of something: &#8220;We learn public infrastructure projects are usually beholden to the demand of constituents (voters, special interest groups, chambers of commerce, etc). This generally leads to comprehensive (‘fair’) coverage, yet often inefficient or unreliable operation, as there isn’t much redundancy built into the system because its goal is to cover the most possible constituents at the lowest cost. In contrast, privately developed infrastructures are virtually always in response to market demand (though they may transition to constituent control at some point in their future). Competition among providers will often result in redundant, more reliable networks (as seen in the layout of New York’s subway system, and the overlapping cellular networks in Los Angeles), but access can spread more slowly, with increased coverage occurring in synch with profitability.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] risk – mammoth // building nothing out of something: &#8220;We learn public infrastructure projects are usually beholden to the demand of constituents (voters, special interest groups, chambers of commerce, etc). This generally leads to comprehensive (‘fair’) coverage, yet often inefficient or unreliable operation, as there isn’t much redundancy built into the system because its goal is to cover the most possible constituents at the lowest cost. In contrast, privately developed infrastructures are virtually always in response to market demand (though they may transition to constituent control at some point in their future). Competition among providers will often result in redundant, more reliable networks (as seen in the layout of New York’s subway system, and the overlapping cellular networks in Los Angeles), but access can spread more slowly, with increased coverage occurring in synch with profitability.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markets, constituencies, and infrastructure &#8211; mammoth // building nothing out of something</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-107040</link>
		<dc:creator>markets, constituencies, and infrastructure &#8211; mammoth // building nothing out of something</dc:creator>
		<pubDate>Fri, 11 Feb 2011 17:59:01 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-107040</guid>
		<description>[...] this set of cost/benefit trade-offs between public and private infrastructures is why we&#8217;ve argued in the past that, when discussing the creation and operation of infrastructure, using &#8216;development for [...]</description>
		<content:encoded><![CDATA[<p>[...] this set of cost/benefit trade-offs between public and private infrastructures is why we&#8217;ve argued in the past that, when discussing the creation and operation of infrastructure, using &#8216;development for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: architects without architecture &#8211; mammoth // building nothing out of something</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-27990</link>
		<dc:creator>architects without architecture &#8211; mammoth // building nothing out of something</dc:creator>
		<pubDate>Mon, 13 Sep 2010 21:43:22 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-27990</guid>
		<description>[...] that light, although I&#8217;m tremendously sympathetic to projects like Roger Sherman&#8217;s game theory urbanism as a way of operating within such highly complex environments, the lack of a larger approach within [...]</description>
		<content:encoded><![CDATA[<p>[...] that light, although I&#8217;m tremendously sympathetic to projects like Roger Sherman&#8217;s game theory urbanism as a way of operating within such highly complex environments, the lack of a larger approach within [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: public landscapes of distribution &#8211; mammoth // building nothing out of something</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-21818</link>
		<dc:creator>public landscapes of distribution &#8211; mammoth // building nothing out of something</dc:creator>
		<pubDate>Wed, 11 Aug 2010 04:00:56 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-21818</guid>
		<description>[...] probably recognize Roger Sherman as the author of the chapter before &#8220;Distribution&#8221;, &#8220;Count(ing) on Change&#8221;.  In &#8220;Duck-and-Cover&#8221; Sherman proposes both an architecture and a business plan, [...]</description>
		<content:encoded><![CDATA[<p>[...] probably recognize Roger Sherman as the author of the chapter before &#8220;Distribution&#8221;, &#8220;Count(ing) on Change&#8221;.  In &#8220;Duck-and-Cover&#8221; Sherman proposes both an architecture and a business plan, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cell(s&#8217;) Structure(d) for Counting (on) Change, through sufficient looseness &#171; Thoughts on Everything under the Sun or I am a guilty Secularist</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-19630</link>
		<dc:creator>Cell(s&#8217;) Structure(d) for Counting (on) Change, through sufficient looseness &#171; Thoughts on Everything under the Sun or I am a guilty Secularist</dc:creator>
		<pubDate>Fri, 30 Jul 2010 02:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-19630</guid>
		<description>[...] an interesting video to come across, just in time for my contribution to Mammoth&#8217;s book club, discussion on Cell Structure and Counting (On) Change chapters of the Infrastructural City. Particularly [...]</description>
		<content:encoded><![CDATA[<p>[...] an interesting video to come across, just in time for my contribution to Mammoth&#8217;s book club, discussion on Cell Structure and Counting (On) Change chapters of the Infrastructural City. Particularly [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Hogan</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-19469</link>
		<dc:creator>Mark Hogan</dc:creator>
		<pubDate>Wed, 28 Jul 2010 21:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-19469</guid>
		<description>I think the most common way to deal with risk in an architectural project is to be somewhat vague in the drawings but very specific in the specification. This, of course, can always lead to unfortunate unintended consequences. New methods of more collaborative project delivery could lead to better consequences if architects and contractors had a better and more productive relationship that was focused on solving problems and creating outcomes instead of always trying to shift liability off on the other. Inevitably, the designers will probably have to take more risk but there is also the possibility of seeing greater profits.</description>
		<content:encoded><![CDATA[<p>I think the most common way to deal with risk in an architectural project is to be somewhat vague in the drawings but very specific in the specification. This, of course, can always lead to unfortunate unintended consequences. New methods of more collaborative project delivery could lead to better consequences if architects and contractors had a better and more productive relationship that was focused on solving problems and creating outcomes instead of always trying to shift liability off on the other. Inevitably, the designers will probably have to take more risk but there is also the possibility of seeing greater profits.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: reading the infrastructural city, chapter nine index &#8211; mammoth // building nothing out of something</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-19291</link>
		<dc:creator>reading the infrastructural city, chapter nine index &#8211; mammoth // building nothing out of something</dc:creator>
		<pubDate>Tue, 27 Jul 2010 19:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-19291</guid>
		<description>[...] A pair of posts related to Roger Sherman&#8217;s &#8220;Count(ing) on Change&#8221;: [...]</description>
		<content:encoded><![CDATA[<p>[...] A pair of posts related to Roger Sherman&#8217;s &#8220;Count(ing) on Change&#8221;: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: From Tianguis to Capitalized Urban Space in L.A. &#171; dpr-barcelona</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-19079</link>
		<dc:creator>From Tianguis to Capitalized Urban Space in L.A. &#171; dpr-barcelona</dc:creator>
		<pubDate>Mon, 26 Jul 2010 10:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-19079</guid>
		<description>[...] —– This post is part of The Infrastructural City blogiscussion, now reading Roger Sherman’s “Counting (on) Change”. [...]</description>
		<content:encoded><![CDATA[<p>[...] —– This post is part of The Infrastructural City blogiscussion, now reading Roger Sherman’s “Counting (on) Change”. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-18046</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Sun, 18 Jul 2010 17:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-18046</guid>
		<description>yeah, I think this is absolutely right.  I&#039;m becoming more convinced that some of the most exciting (speaking personally) firms of the future will be, among other things, experimenting with radical new strategies of risk management. 

I think it&#039;s key that we learn not only how to gauge (and accept) risk to our own firms, but also how to accurately quantify and counter risks (perceived and real) to other parties in the deal.  We can never inherit, for example, the risk of increased traffic to neighbors after the completion of an urban infill project, or the risk of experimenting with a new construction technique unless we become contractors as well. But there has to be a better way than adding on the standard 20% contingency price to loans and construction pricing, or increasing the cost of insurance, or just not doing the project at all. I think this is important regardless of who the developer is, whether designer or designer&#039;s client.</description>
		<content:encoded><![CDATA[<p>yeah, I think this is absolutely right.  I&#8217;m becoming more convinced that some of the most exciting (speaking personally) firms of the future will be, among other things, experimenting with radical new strategies of risk management. </p>
<p>I think it&#8217;s key that we learn not only how to gauge (and accept) risk to our own firms, but also how to accurately quantify and counter risks (perceived and real) to other parties in the deal.  We can never inherit, for example, the risk of increased traffic to neighbors after the completion of an urban infill project, or the risk of experimenting with a new construction technique unless we become contractors as well. But there has to be a better way than adding on the standard 20% contingency price to loans and construction pricing, or increasing the cost of insurance, or just not doing the project at all. I think this is important regardless of who the developer is, whether designer or designer&#8217;s client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#8220;anchors in a mutable field&#8221; &#8211; mammoth // building nothing out of something</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-18041</link>
		<dc:creator>&#8220;anchors in a mutable field&#8221; &#8211; mammoth // building nothing out of something</dc:creator>
		<pubDate>Sun, 18 Jul 2010 16:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-18041</guid>
		<description>[...] home // hide asides // links // index.archive // contact us // about     &#171; risk [...]</description>
		<content:encoded><![CDATA[<p>[...] home // hide asides // links // index.archive // contact us // about     &laquo; risk [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rholmes</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-18030</link>
		<dc:creator>rholmes</dc:creator>
		<pubDate>Sun, 18 Jul 2010 15:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-18030</guid>
		<description>In addition to the link between attitudes towards the management of risk and different resulting urbanisms, I also think there&#039;s a strong connection between risk and agency.  In order to expand agency, one must accept expanded risk.  We -- architects, landscape architects -- often step back from expanded agency, because it would increase our financial or legal liability.  This is not an absurd decision (the risks of, say, assuming some of the burden of the developer, are real), but it does have consequences (we cede parts of projects which we might have important things to say about) which are not always positive.</description>
		<content:encoded><![CDATA[<p>In addition to the link between attitudes towards the management of risk and different resulting urbanisms, I also think there&#8217;s a strong connection between risk and agency.  In order to expand agency, one must accept expanded risk.  We &#8212; architects, landscape architects &#8212; often step back from expanded agency, because it would increase our financial or legal liability.  This is not an absurd decision (the risks of, say, assuming some of the burden of the developer, are real), but it does have consequences (we cede parts of projects which we might have important things to say about) which are not always positive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention risk – mammoth // building nothing out of something -- Topsy.com</title>
		<link>http://m.ammoth.us/blog/2010/07/risk/comment-page-1/#comment-17934</link>
		<dc:creator>Tweets that mention risk – mammoth // building nothing out of something -- Topsy.com</dc:creator>
		<pubDate>Sat, 17 Jul 2010 20:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://m.ammoth.us/blog/?p=3057#comment-17934</guid>
		<description>[...] This post was mentioned on Twitter by Ethel Baraona Pohl, Stephen Becker. Stephen Becker said: self link &#124; http://m.ammoth.us/blog/2010/07/risk/ &#124; #mammothbook [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Ethel Baraona Pohl, Stephen Becker. Stephen Becker said: self link | <a href="http://m.ammoth.us/blog/2010/07/risk/" rel="nofollow">http://m.ammoth.us/blog/2010/07/risk/</a> | #mammothbook [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

