<?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: Engineering a New Bedrock</title>
	<atom:link href="http://altitudebranding.com/2009/02/engineering-a-new-bedrock/feed/" rel="self" type="application/rss+xml" />
	<link>http://altitudebranding.com/2009/02/engineering-a-new-bedrock/</link>
	<description></description>
	<lastBuildDate>Tue, 16 Mar 2010 08:35:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Unspoken Role in Community Management &#124; Altitude Branding &#124; Brand Elevation through Social Media</title>
		<link>http://altitudebranding.com/2009/02/engineering-a-new-bedrock/comment-page-1/#comment-6779</link>
		<dc:creator>The Unspoken Role in Community Management &#124; Altitude Branding &#124; Brand Elevation through Social Media</dc:creator>
		<pubDate>Wed, 14 Oct 2009 19:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://altitudebranding.com/?p=497#comment-6779</guid>
		<description>[...] service or marketing or whatever, without taking it to the foundations of an organization and engineering a new bedrock, it&#8217;s all going to fall [...]</description>
		<content:encoded><![CDATA[<div style="padding: 1em">
<p>[...] service or marketing or whatever, without taking it to the foundations of an organization and engineering a new bedrock, it&#8217;s all going to fall [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: susan kuhn frost</title>
		<link>http://altitudebranding.com/2009/02/engineering-a-new-bedrock/comment-page-1/#comment-3505</link>
		<dc:creator>susan kuhn frost</dc:creator>
		<pubDate>Thu, 28 May 2009 19:25:51 +0000</pubDate>
		<guid isPermaLink="false">http://altitudebranding.com/?p=497#comment-3505</guid>
		<description>There is a huge need for this kind of thinking among those working on enterprise transformation projects, and among those starting companies.  Very clearly articulated.

&lt;abbr&gt;&lt;em&gt;&lt;abbr&gt;&lt;em&gt;susan kuhn frosts last blog post..&lt;a href=&quot;http://siteground220.com/~recessi2/2009/03/17/social-sustainable-business-competitions/&quot; rel=&quot;nofollow&quot;&gt;Get in On 2009 Social and Sustainable Business Plan Competitions&lt;/a&gt;&lt;/em&gt;&lt;/abbr&gt;&lt;/abbr&gt;&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>There is a huge need for this kind of thinking among those working on enterprise transformation projects, and among those starting companies.  Very clearly articulated.</p>
<p><abbr><em><abbr><em>susan kuhn frosts last blog post..<a href="http://siteground220.com/~recessi2/2009/03/17/social-sustainable-business-competitions/" rel="nofollow">Get in On 2009 Social and Sustainable Business Plan Competitions</a></em></abbr></em></abbr></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heather Rast</title>
		<link>http://altitudebranding.com/2009/02/engineering-a-new-bedrock/comment-page-1/#comment-2624</link>
		<dc:creator>Heather Rast</dc:creator>
		<pubDate>Sun, 22 Feb 2009 19:20:53 +0000</pubDate>
		<guid isPermaLink="false">http://altitudebranding.com/?p=497#comment-2624</guid>
		<description>Hi, Amber. This post does a good job of bringing some known, but often undiscussed, truths about business and even human behavior: we look for absolutes, we follow routines, and we avoid digging for deeper, more stable solutions because of the upheaval and chaos the process will inevitably bring. Just because something&#039;s always been done one way doesn&#039;t mean it&#039;s the only way, or even the most productive or efficient way. Sometimes those that ask these questions or challenge the norm can find themselves in some crosshairs, though, and that&#039;s a risk.

Process-wise, I&#039;ll throw in one experience-based suggestion that might be helpful to some:  there&#039;s a software development methodology called Scrum.  It&#039;s an agile methodology, which pretty much means it seeks to slice off parts or elements of a whole horizontally in an iterative fashion. Instead of developing a new program or product in it&#039;s entireity (a 2-4 year endeavor for many)to then discover it doesn&#039;t meet consumer needs or it&#039;s flawed, Scrum has companies developing a part of the product or software, releasing it to your customers, and moving on to develop the next part. This allows for some real-application feedback from users (provided you build your cycles that way)and can lead to greater transparency--within a company and via a published product roadmap with external audiences--potentially creating an atmosphere of continuous process improvement. It&#039;s actually a simple process but challenging to indoctrinate because of those inherent, learned behaviors you mention above.

Thanks for the great read!

&lt;abbr&gt;&lt;em&gt;&lt;abbr&gt;&lt;em&gt;Heather Rasts last blog post..&lt;a href=&quot;http://insightsandingenuity.com/2009/02/22/the-content-entanglement-factor-inform-engage-entertain/&quot; rel=&quot;nofollow&quot;&gt;The “Content Entanglement Factor”: Inform, Engage, Entertain&lt;/a&gt;&lt;/em&gt;&lt;/abbr&gt;&lt;/abbr&gt;&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Hi, Amber. This post does a good job of bringing some known, but often undiscussed, truths about business and even human behavior: we look for absolutes, we follow routines, and we avoid digging for deeper, more stable solutions because of the upheaval and chaos the process will inevitably bring. Just because something&#8217;s always been done one way doesn&#8217;t mean it&#8217;s the only way, or even the most productive or efficient way. Sometimes those that ask these questions or challenge the norm can find themselves in some crosshairs, though, and that&#8217;s a risk.</p>
<p>Process-wise, I&#8217;ll throw in one experience-based suggestion that might be helpful to some:  there&#8217;s a software development methodology called Scrum.  It&#8217;s an agile methodology, which pretty much means it seeks to slice off parts or elements of a whole horizontally in an iterative fashion. Instead of developing a new program or product in it&#8217;s entireity (a 2-4 year endeavor for many)to then discover it doesn&#8217;t meet consumer needs or it&#8217;s flawed, Scrum has companies developing a part of the product or software, releasing it to your customers, and moving on to develop the next part. This allows for some real-application feedback from users (provided you build your cycles that way)and can lead to greater transparency&#8211;within a company and via a published product roadmap with external audiences&#8211;potentially creating an atmosphere of continuous process improvement. It&#8217;s actually a simple process but challenging to indoctrinate because of those inherent, learned behaviors you mention above.</p>
<p>Thanks for the great read!</p>
<p><abbr><em><abbr><em>Heather Rasts last blog post..<a href="http://insightsandingenuity.com/2009/02/22/the-content-entanglement-factor-inform-engage-entertain/" rel="nofollow">The “Content Entanglement Factor”: Inform, Engage, Entertain</a></em></abbr></em></abbr></p>
]]></content:encoded>
	</item>
</channel>
</rss>
