<?xml version="1.0" encoding="UTF-8"?>
<!-- RSS generated by feedland v0.6.43 on Wed, 22 Jan 2025 21:06:48 GMT -->
<rss version="2.0" xmlns:source="http://source.scripting.com/">
	<channel>
		<title>My Feed</title>
		<link>https://blue.feedland.org/?river=http://data.feedland.org/blue/feeds/kencamp.xml</link>
		<description>The feed for my FeedLand notes.</description>
		<pubDate>Mon, 20 Jan 2025 18:09:39 GMT</pubDate>
		<generator>feedland v0.6.43</generator>
		<docs>https://cyber.harvard.edu/rss/rss.html</docs>
		<lastBuildDate>Wed, 22 Jan 2025 21:06:48 GMT</lastBuildDate>
		<cloud domain="rpc.rsscloud.io" port="5337" path="/pleaseNotify" registerProcedure="" protocol="http-post" />
		<source:cloud>http://rpc.rsscloud.io:5337/pleaseNotify</source:cloud>
		<source:localTime>Wed, January 22, 2025 4:06 PM EST</source:localTime>
		<item>
			<description>&lt;p&gt;Strategic Thinking is About Complexity and Options&lt;/p&gt;&#10;&lt;p&gt;Wayne Gretzky once said &amp;quot;skating to where the puck is going to be&amp;quot; was the secret of his success. Often, in the world of technology strategy, we&amp;#39;ve used this same analogy. I&amp;#39;m here to tell you this is flawed, and maps a clear path to failure.&lt;/p&gt;&#10;&lt;p&gt;In hockey, there&amp;#39;s one puck. It will always have one place it&amp;#39;s going to be, based on direction, velocity and any rebounds or interference.&lt;/p&gt;&#10;&lt;p&gt;Enterprise technology is more akin to a game of pool. When you break the rack to start the game, you need to know where 3 solids, 3 stripes and the 8 ball are going to land to form your strategy. And even that&amp;#39;s an oversimplification. Strategy is complex and deep, with a cornucopia of variables. So how do you map a strategy?&lt;/p&gt;&#10;&lt;p&gt;Data Becomes Information Becomes Knowledge&lt;/p&gt;&#10;&lt;p&gt;Gather the facts. Empirical data will always provide a factual foundation to start. This means data gathering. If the data is unstructured, find a structure, or more than one. Extract the facts from the data in context with the subject at hand. Manipulate and massage it until you shake out the nuance and ambiguity. When you see the light, you&amp;#39;re on the right path and getting close. But don&amp;#39;t always be drawn like a moth to the brightest light. Always consider multiple paths.&lt;/p&gt;&#10;&lt;p&gt;Knowledge Becomes Wisdom Through Two Elements&lt;/p&gt;&#10;&lt;p&gt;Experience&lt;/p&gt;&#10;&lt;p&gt;Have you seen a trend or result before that&amp;#39;s similar or related? What have you learned in the past that applies to this scenario? Lessons learned are only that if we actually use what we&amp;#39;ve learned.&lt;/p&gt;&#10;&lt;p&gt;Intuition&lt;/p&gt;&#10;&lt;p&gt;Intuition is beyond simply following your gut. It means collating everything you know from other sources, everything you read (you study the field extensively, right?) and extrapolating possible outcomes. What do the analysts you listen to think? What does industry news say? Where are the vendors leading the space headed? Variables. Ferret out all the variables.&lt;/p&gt;&#10;&lt;p&gt;Then plan for 3-4 potential outcomes. Consider the unexpected. Essentially, wade through a mental library of if-then-else loops. Don&amp;#39;t rely entirely on Plan A. Have as many plans as needed to build a path to success.&lt;/p&gt;&#10;&lt;p&gt;Lastly, monitor progress and always have contingencies percolating for the unforeseen. Rest assured, the unforeseen will occur. Every single time. Even a game of pool is a simple set of variable in comparison to the real world of enterprise information technology.&lt;/p&gt;</description>
			<pubDate>Mon, 20 Jan 2025 18:09:39 GMT</pubDate>
			<link>https://blue.feedland.org/?item=788145</link>
			<guid>https://blue.feedland.org/?item=788145</guid>
			<source:markdown>Strategic Thinking is About Complexity and Options&#10;&#10;Wayne Gretzky once said &quot;skating to where the puck is going to be&quot; was the secret of his success. Often, in the world of technology strategy, we've used this same analogy. I'm here to tell you this is flawed, and maps a clear path to failure.&#10;&#10;In hockey, there's one puck. It will always have one place it's going to be, based on direction, velocity and any rebounds or interference.&#10;&#10;Enterprise technology is more akin to a game of pool. When you break the rack to start the game, you need to know where 3 solids, 3 stripes and the 8 ball are going to land to form your strategy. And even that's an oversimplification. Strategy is complex and deep, with a cornucopia of variables. So how do you map a strategy?&#10;&#10;Data Becomes Information Becomes Knowledge&#10;&#10;Gather the facts. Empirical data will always provide a factual foundation to start. This means data gathering. If the data is unstructured, find a structure, or more than one. Extract the facts from the data in context with the subject at hand. Manipulate and massage it until you shake out the nuance and ambiguity. When you see the light, you're on the right path and getting close. But don't always be drawn like a moth to the brightest light. Always consider multiple paths.&#10;&#10;Knowledge Becomes Wisdom Through Two Elements&#10;&#10;Experience&#10;&#10;Have you seen a trend or result before that's similar or related? What have you learned in the past that applies to this scenario? Lessons learned are only that if we actually use what we've learned.&#10;&#10;Intuition&#10;&#10;Intuition is beyond simply following your gut. It means collating everything you know from other sources, everything you read (you study the field extensively, right?) and extrapolating possible outcomes. What do the analysts you listen to think? What does industry news say? Where are the vendors leading the space headed? Variables. Ferret out all the variables.&#10;&#10;Then plan for 3-4 potential outcomes. Consider the unexpected. Essentially, wade through a mental library of if-then-else loops. Don't rely entirely on Plan A. Have as many plans as needed to build a path to success.&#10;&#10;Lastly, monitor progress and always have contingencies percolating for the unforeseen. Rest assured, the unforeseen will occur. Every single time. Even a game of pool is a simple set of variable in comparison to the real world of enterprise information technology.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;Strategic Thinking is About Complexity and Options&lt;/p&gt;&#10;&lt;p&gt;Wayne Gretzky once said &amp;quot;skating to where the puck is going to be&amp;quot; was the secret of his success. Often, in the world of technology strategy, we&amp;#39;ve used this same analogy. I&amp;#39;m here to tell you this is flawed, and maps a clear path to failure.&lt;/p&gt;&#10;&lt;p&gt;In hockey, there&amp;#39;s one puck. It will always have one place it&amp;#39;s going to be, based on direction, velocity and any rebounds or interference.&lt;/p&gt;&#10;&lt;p&gt;Enterprise technology is more akin to a game of pool. When you break the rack to start the game, you need to know where 3 solids, 3 stripes and the 8 ball are going to land to form your strategy. And even that&amp;#39;s an oversimplification. Strategy is complex and deep, with a cornucopia of variables. So how do you map a strategy?&lt;/p&gt;&#10;&lt;p&gt;Data Becomes Information Becomes Knowledge&lt;/p&gt;&#10;&lt;p&gt;Gather the facts. Empirical data will always provide a factual foundation to start. This means data gathering. If the data is unstructured, find a structure, or more than one. Extract the facts from the data in context with the subject at hand. Manipulate and massage it until you shake out the nuance and ambiguity. When you see the light, you&amp;#39;re on the right path and getting close. But don&amp;#39;t always be drawn like a moth to the brightest light. Always consider multiple paths.&lt;/p&gt;&#10;&lt;p&gt;Knowledge Becomes Wisdom Through Two Elements&lt;/p&gt;&#10;&lt;p&gt;Experience&lt;/p&gt;&#10;&lt;p&gt;Have you seen a trend or result before that&amp;#39;s similar or related? What have you learned in the past that applies to this scenario? Lessons learned are only that if we actually use what we&amp;#39;ve learned.&lt;/p&gt;&#10;&lt;p&gt;Intuition&lt;/p&gt;&#10;&lt;p&gt;Intuition is beyond simply following your gut. It means collating everything you know from other sources, everything you read (you study the field extensively, right?) and extrapolating possible outcomes. What do the analysts you listen to think? What does industry news say? Where are the vendors leading the space headed? Variables. Ferret out all the variables.&lt;/p&gt;&#10;&lt;p&gt;Then plan for 3-4 potential outcomes. Consider the unexpected. Essentially, wade through a mental library of if-then-else loops. Don&amp;#39;t rely entirely on Plan A. Have as many plans as needed to build a path to success.&lt;/p&gt;&#10;&lt;p&gt;Lastly, monitor progress and always have contingencies percolating for the unforeseen. Rest assured, the unforeseen will occur. Every single time. Even a game of pool is a simple set of variable in comparison to the real world of enterprise information technology.&lt;/p&gt;</description>
			<pubDate>Mon, 20 Jan 2025 18:09:21 GMT</pubDate>
			<link>https://blue.feedland.org/?item=788144</link>
			<guid>https://blue.feedland.org/?item=788144</guid>
			<source:markdown>Strategic Thinking is About Complexity and Options&#10;&#10;Wayne Gretzky once said &quot;skating to where the puck is going to be&quot; was the secret of his success. Often, in the world of technology strategy, we've used this same analogy. I'm here to tell you this is flawed, and maps a clear path to failure.&#10;&#10;In hockey, there's one puck. It will always have one place it's going to be, based on direction, velocity and any rebounds or interference.&#10;&#10;Enterprise technology is more akin to a game of pool. When you break the rack to start the game, you need to know where 3 solids, 3 stripes and the 8 ball are going to land to form your strategy. And even that's an oversimplification. Strategy is complex and deep, with a cornucopia of variables. So how do you map a strategy?&#10;&#10;Data Becomes Information Becomes Knowledge&#10;&#10;Gather the facts. Empirical data will always provide a factual foundation to start. This means data gathering. If the data is unstructured, find a structure, or more than one. Extract the facts from the data in context with the subject at hand. Manipulate and massage it until you shake out the nuance and ambiguity. When you see the light, you're on the right path and getting close. But don't always be drawn like a moth to the brightest light. Always consider multiple paths.&#10;&#10;Knowledge Becomes Wisdom Through Two Elements&#10;&#10;Experience&#10;&#10;Have you seen a trend or result before that's similar or related? What have you learned in the past that applies to this scenario? Lessons learned are only that if we actually use what we've learned.&#10;&#10;Intuition&#10;&#10;Intuition is beyond simply following your gut. It means collating everything you know from other sources, everything you read (you study the field extensively, right?) and extrapolating possible outcomes. What do the analysts you listen to think? What does industry news say? Where are the vendors leading the space headed? Variables. Ferret out all the variables.&#10;&#10;Then plan for 3-4 potential outcomes. Consider the unexpected. Essentially, wade through a mental library of if-then-else loops. Don't rely entirely on Plan A. Have as many plans as needed to build a path to success.&#10;&#10;Lastly, monitor progress and always have contingencies percolating for the unforeseen. Rest assured, the unforeseen will occur. Every single time. Even a game of pool is a simple set of variable in comparison to the real world of enterprise information technology.</source:markdown>
			</item>
		<item>
			<description></description>
			<pubDate>Mon, 20 Jan 2025 18:03:00 GMT</pubDate>
			<link>https://blue.feedland.org/?item=788143</link>
			<guid>https://blue.feedland.org/?item=788143</guid>
			</item>
		</channel>
	</rss>
