<?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: Should We Use Cookie Cutters?	</title>
	<atom:link href="https://mikebonem.com/should-we-use-cookie-cutters/feed/" rel="self" type="application/rss+xml" />
	<link>https://mikebonem.com/should-we-use-cookie-cutters/</link>
	<description>consultant, coach, speaker, author</description>
	<lastBuildDate>Tue, 10 Jun 2014 15:20:37 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Silas		</title>
		<link>https://mikebonem.com/should-we-use-cookie-cutters/#comment-77</link>

		<dc:creator><![CDATA[Silas]]></dc:creator>
		<pubDate>Tue, 10 Jun 2014 15:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://mikebonem.com/?p=1761#comment-77</guid>

					<description><![CDATA[This is a tension that I am frequently struggling with. I am naturally a change-agent who thinks of how to improve things and break boxes. But sometimes I am hesitant to make change in some environments if it will mow people down. Using cookie cutters is very much contextual: some environments sniff the usage of the cookie cutter and believe that it is &quot;unoriginal&quot; and thus not authentic, resulting in low trust. I work in an organization that values high transferability, but once a generation has passed and the new generation has low buy-in on the transferred cookie cutter methods, then they chuck it out and try to do their own thing all over again.
I think we live in a culture that values originality rather than cookie cutter approaches (the people). The corporations and organizations value cookie cutters, but then over-use and abuse them into robotic mechanisms. Take this for example https://twitter.com/russmartin/status/474956361500200961 . Somehow there&#039;s gotta be a balance?
You&#039;re right that we all make mistakes in both sides. How does one develop the wisdom to know when to employ a specific technique?]]></description>
			<content:encoded><![CDATA[<p>This is a tension that I am frequently struggling with. I am naturally a change-agent who thinks of how to improve things and break boxes. But sometimes I am hesitant to make change in some environments if it will mow people down. Using cookie cutters is very much contextual: some environments sniff the usage of the cookie cutter and believe that it is &#8220;unoriginal&#8221; and thus not authentic, resulting in low trust. I work in an organization that values high transferability, but once a generation has passed and the new generation has low buy-in on the transferred cookie cutter methods, then they chuck it out and try to do their own thing all over again.<br />
I think we live in a culture that values originality rather than cookie cutter approaches (the people). The corporations and organizations value cookie cutters, but then over-use and abuse them into robotic mechanisms. Take this for example <a href="https://twitter.com/russmartin/status/474956361500200961" rel="nofollow ugc">https://twitter.com/russmartin/status/474956361500200961</a> . Somehow there&#8217;s gotta be a balance?<br />
You&#8217;re right that we all make mistakes in both sides. How does one develop the wisdom to know when to employ a specific technique?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
