<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>

<feed xmlns="http://purl.org/atom/ns#" version="0.3" xml:lang="en-US">
<link href="https://www.blogger.com/atom/11211488" rel="service.post" title="Randy Cronk's Blog" type="application/atom+xml"/>
<link href="https://www.blogger.com/atom/11211488" rel="service.feed" title="Randy Cronk's Blog" type="application/atom+xml"/>
<title mode="escaped" type="text/html">Randy Cronk's Blog</title>
<tagline mode="escaped" type="text/html">&lt;b&gt;Connecting the dots between technology and strategy.&lt;/b&gt;</tagline>
<link href="http://www.greatwriting.com/blog" rel="alternate" title="Randy Cronk's Blog" type="text/html"/>
<id>tag:blogger.com,1999:blog-11211488</id>
<modified>2006-11-17T14:12:04Z</modified>
<generator url="http://www.blogger.com/" version="6.72">Blogger</generator>
<info mode="xml" type="text/html">
<div xmlns="http://www.w3.org/1999/xhtml">This is an Atom formatted XML site feed. It is intended to be viewed in a Newsreader or syndicated to another site. Please visit the <a href="http://help.blogger.com/bin/answer.py?answer=697">Blogger Help</a> for more info.</div>
</info>
<convertLineBreaks xmlns="http://www.blogger.com/atom/ns#">true</convertLineBreaks>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/11211488/116119647117172192" rel="service.edit" title="Popular Topics Outnumber BitPipe Contributors" type="application/atom+xml"/>
<author>
<name>RandyC</name>
</author>
<issued>2006-10-18T14:33:00-04:00</issued>
<modified>2006-10-18T18:48:14Z</modified>
<created>2006-10-18T18:34:31Z</created>
<link href="http://www.greatwriting.com/blog/2006/10/popular-topics-outnumber-bitpipe.html" rel="alternate" title="Popular Topics Outnumber BitPipe Contributors" type="text/html"/>
<id>tag:blogger.com,1999:blog-11211488.post-116119647117172192</id>
<title mode="escaped" type="text/html">Popular Topics Outnumber BitPipe Contributors</title>
<content type="application/xhtml+xml" xml:base="http://www.greatwriting.com/blog" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">
<span style="font-size:130%;">
<blockquote>It's 705 to 181 for white papers less than a year old</blockquote>
</span>Of all the high-tech companies that have published white papers since October 2005, I counted 181 that have posted white papers to <a href="http://www.bitpipe.com/" target="_blank">BitPipe</a> in the 705 topics the site lists as most popular.  BitPipe is the aggregator of IT thought leadership owned by TechTarget.  It describes itself as "the Web's leading online information source for IT professionals who need technology white papers ...."<br/>
<br/>You can find these companies and topics under "<a href="http://www.bitpipe.com/data/web/bp/newsletters/bp_kasignup.jsp" target="_blank">Market Intelligence</a>" on the <a href="http://www.bitpipe.com/about/sitemap.jsp" target="_blank">BitPipe sitemap</a>.  I have listed them <a href="http://www.greatwriting.com/bitpipe.htm" target="_blank">in a single table</a> on my own website.<br/>
<br/>The table was compiled the second week of October by inspecting the titles and authors appearing in each of the 705 topics.  The information is freely available to anyone looking at the BitPipe website.<br/>
<br/>Compared to the universe of IT firms, 181 is a small number.  In fact, it is only about one-quarter the size of the number of "most popular" topics (a subset of <a href="http://www.bitpipe.com/term_list.jsp" target="_blank">all BitPipe topics</a>).  Nor does this fraction reflect the lopsided contribution of a handful of companies whose papers appear over and over again under multiple topics and sub-topics.  If you took out the top 10 companies (in terms of number of white paper listings) you would reduce the number of companies by less than 6%.  But you would reduce the number of recent white paper listings by over two-thirds.<br/>
<br/>It's not just the names of companies that repeat; many of the same titles repeat under different subtopics, and many of the same subtopics repeat under several different topics.  The result is a "perceptual multiplier effect" that makes 181 feel big.  Compounding the effect is the high degree of granularity in the choice of topics and subtopics -- many of which BitPipe differentiates by merely adding qualifiers like "system," "software," and "service" to the same root.<br/>
<br/>This maze makes white papers hard to find -- which may help explain why more companies are not represented.  You don't know what all the choices are until you drill down into all potentially relevant silos and when you do drill down in one it's easy to forget what choices you had in others. At least as an alternative, why not provide a simple list of all companies and all topics?  Also, why not allow for compound searches by right clicking on multiple companies and topics in drop down menus?  Finally, why not make topics less granular?  Serious researchers will still look at both "system" and "software" versions of a topic anyway just to make sure they have covered all the bases.  Why put users through all that work?<br/>
<br/>One other observation: when BitPipe says that there are no documents in a topic, there usually are documents -- which you will miss if you do not click on the topic anyway.<br/>
<br/>No doubt more companies would write white papers if they felt they could get more of an audience -- and a return on their investment.  Making white papers easier to find would help.</div>
</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/11211488/116069087803761698" rel="service.edit" title="Two-Thirds of Tech Companies Don't Do Case Studies" type="application/atom+xml"/>
<author>
<name>RandyC</name>
</author>
<issued>2006-10-12T18:06:00-04:00</issued>
<modified>2006-10-12T22:14:04Z</modified>
<created>2006-10-12T22:07:58Z</created>
<link href="http://www.greatwriting.com/blog/2006/10/two-thirds-of-tech-companies-dont-do.html" rel="alternate" title="Two-Thirds of Tech Companies Don't Do Case Studies" type="text/html"/>
<id>tag:blogger.com,1999:blog-11211488.post-116069087803761698</id>
<title mode="escaped" type="text/html">Two-Thirds of Tech Companies Don't Do Case Studies</title>
<content type="application/xhtml+xml" xml:base="http://www.greatwriting.com/blog" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">
<span style="font-size:130%;">
<blockquote>Only one-third write white papers.  Over half do neither case studies nor white papers.</blockquote>
</span>My survey of high-tech company websites this week reveals that:<br/>
<ul>
<li>31% have white papers</li>
<li>36% have case studies</li>
<li>56% have neither cases nor white papers</li>
</ul>The survey looked at the websites of 100 companies randomly selected from all U.S. firms with 50-999 employees in the <a href="http://www.corptech.com" target="_blank">CorpTech database</a> in the following categories: computer hardware, computer software, telecommunications and Internet.  The sampling error is plus or minus 9%. I actually sampled 120 and threw out 20 that were not appropriate -- for example, the firms might have gone out of business or CorpTech had mislabeled their industries.<br/>
<br/>(Attention marketers:  there were 7007 firms in this particular CorpTech download -- so if you extrapolate that out, i.e., 20 bad names for every 100 good ones, it comes to 5600 firms, or significantly fewer than what you might have expected.)<br/>
<br/>I wasn't completely surprised by the survey's results.  I did a similar survey of tech companies in Massachusetts and New Hampshire about five years ago and found that only about 40% did case histories.<br/>
<br/>This obviously raises a lot of questions about why tech companies don't showcase either their successes or their thinking more than they do.  One thing is clear -- the market for writing services should be a lot more efficient.  Many companies are not getting served because of barriers either real or perceived.</div>
</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/11211488/116041709196377742" rel="service.edit" title="McKinsey Revisits IT's Shopping List" type="application/atom+xml"/>
<author>
<name>RandyC</name>
</author>
<issued>2006-10-09T13:59:00-04:00</issued>
<modified>2006-10-09T18:16:15Z</modified>
<created>2006-10-09T18:04:51Z</created>
<link href="http://www.greatwriting.com/blog/2006/10/mckinsey-revisits-its-shopping-list.html" rel="alternate" title="McKinsey Revisits IT's Shopping List" type="text/html"/>
<id>tag:blogger.com,1999:blog-11211488.post-116041709196377742</id>
<title mode="escaped" type="text/html">McKinsey Revisits IT's Shopping List</title>
<content mode="escaped" type="text/html" xml:base="http://www.greatwriting.com/blog" xml:space="preserve">&lt;blockquote&gt;&lt;span style="font-size:180%;"&gt;"… these two adoption trends indicate that a technology architecture transformation is beginning to take shape …."&lt;/span&gt;&lt;br /&gt;&lt;div style="text-align: center;"&gt;--McKinsey &amp; Company&lt;/div&gt;&lt;/blockquote&gt;When McKinsey &amp;amp; Company published its &lt;a href="http://www.mckinseyquarterly.com/article_abstract.aspx?ar=1745" target="_blank"&gt;IT Shopping List &lt;/a&gt;at the beginning of the year, &lt;a href="http://www.greatwriting.com/blog/2006/03/whats-on-its-shopping-list.html" target="_blank"&gt;I noted that&lt;/a&gt; two items - virtualization and web services -- did not rank near the top of most CIOs' shopping lists.&lt;br /&gt;&lt;br /&gt;The most popular items were more established technologies like ERP, VoIP, business intelligence, and security.  That's true even though McKinsey and almost everyone else acknowledge virtualization and web services are the next big things.&lt;br /&gt;&lt;br /&gt;Perhaps sensing the disconnect, McKinsey focuses squarely on virtualization and web services in its &lt;a href="http://www.mckinseyquarterly.com/article_page.aspx?ar=1780&amp;L2=4&amp;amp;L3=115&amp;srid=17&amp;amp;gp=0" target="_blank"&gt;latest technology article&lt;/a&gt;.   The authors are Kishore Kanakamedala, Vasantha Krishnakanthan, and Roger P. Roberts.&lt;br /&gt;&lt;br /&gt;Citing data from the earlier survey, McKinsey reports that 86% of CIOs "cited progress" in "server consolidation" and that virtualization is the "next natural move."  As for software as service, 38% of CIOs said they plan "to use the software as service approach during the next 12 months."   In addition, "few companies are using software as a service in systems ...  that need a lot of tailoring or customization."&lt;br /&gt;&lt;br /&gt;Translation -- companies are starting to put their toes in the water on both the virtualization and the web services fronts.    A major implementation of either would still, however, be a major news headline or feature story in most IT trade publications.   To use the phrasing of my earlier post -- not all high-tech is equal and where you sit on the innovation cycle reflects to what extent you are a net consumer or investor of innovation.   Virtualization and web services are still net consumers of investment dollars -- i.e., adoption sucks up more cash then it gives back near term.   So adoption is slow in an era of flat IT budgets.  The money to pay for those investments must come from efficiencies gained from the relative "cash cows" of innovation like ERP — technologies on which companies are much more willing to spend money.</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/11211488/115929468889430960" rel="service.edit" title="A Role Model You Won't Find in Business Week" type="application/atom+xml"/>
<author>
<name>RandyC</name>
</author>
<issued>2006-09-26T14:17:00-04:00</issued>
<modified>2006-09-26T18:30:42Z</modified>
<created>2006-09-26T18:18:08Z</created>
<link href="http://www.greatwriting.com/blog/2006/09/role-model-you-wont-find-in-business.html" rel="alternate" title="A Role Model You Won't Find in Business Week" type="text/html"/>
<id>tag:blogger.com,1999:blog-11211488.post-115929468889430960</id>
<title mode="escaped" type="text/html">A Role Model You Won't Find in Business Week</title>
<content type="application/xhtml+xml" xml:base="http://www.greatwriting.com/blog" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">
<blockquote>
<span style="font-size:180%;">"Only a Duraflow distributor can give customers total performance."</span>
</blockquote>
<br/>Unlike iPods, wastewater filtering is not very sexy.  That probably helps if you're looking for companies with the essential DNA to thrive in the climate change bought on by the tech bubble collapse.  With a company like Duraflow Corporation, there's no glitter to distract you from seeing the raw fundamentals.<br/>
<br/>Ten years ago the people at Duraflow had a good business -- it was (and still is) called Compliance and Recycling Corp. (CARI).  It focused on building plants that remove the waste in water used to make circuit boards and other electrical components.  Based in Tewksbury, Mass, the company flourished serving the needs of computer and electronics manufacturers in the U.S. and especially New England.  Today, of course, those kinds of plants are typically built in China -- somewhat removed from the typical CARI service call to, say, Springfield, Mass. or Salem, New Hampshire.<br/>
<a href="http://www.greatwriting.com/blog/uploaded_images/wheel-724997.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}">
<img alt="" border="0" src="http://www.greatwriting.com/blog/uploaded_images/wheel-722991.jpg" style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;"/>
</a>
<br/>But instead of just becoming extinct like a lot of old-line New England companies, CARI gave birth to Duraflow, which has become the largest U.S. supplier of wastewater treatment technology providing total system solutions to Chinese manufacturers.  That includes the latest technology (crossflow microfiltration modules), the chemicals that work with those modules, and the know-how to build and operate systems incorporating those modules.<br/>
<br/>How is that possible?  There are lots of reasons, but probably the biggest was the founders' insight that China needed a scalable solution to its wastewater treatment problem (just as Duraflow needed a scalable solution to its problem of how to reach profitable, but distant, markets).<br/>
<br/>That solution was the Duraflow business model -- to equip and train Chinese distributors to provide everything a customer would need to comply with strict new Chinese environmental regulations.  In other words, Duraflow's "real" business would be to create lots of CARIs, each one locally owed and operated, and each one selling a total solution, not just pieces of it.  Getting all three pieces from a single source -- know-how, modules, and chemicals -- is less expensive for the buyer and more profitable for the distributor.  There is, in fact, sufficient revenue to support the gold standard of compliance Chinese authorities want.<br/>
<br/>The result is a virtuous cycle of profitable distributors, happier officials, cleaner rivers, and more efficient manufacturers.  The fact that Duraflow is helping transfer environmental technology to Chinese nationals, and helping locals build successful companies is their own right doesn't hurt either.<br/>
<br/>(A website transformation reflects the corporate transformation -- compare the <a href="http://www.duraflow.biz" target="_blank">Duraflow</a> and <a href="http://www.cari-usa.com" target="_blank">CARI</a> websites.  The new site was designed by <a href="http://www.greatwriting.com/firms_folder/schenkel.html" target="_blank">Schenkel/Stegman Communications Design</a>.  I wrote the text.)</div>
</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/11211488/115920054671973549" rel="service.edit" title="A Class of Super CEOs" type="application/atom+xml"/>
<author>
<name>RandyC</name>
</author>
<issued>2006-09-25T12:07:00-04:00</issued>
<modified>2006-09-25T16:14:37Z</modified>
<created>2006-09-25T16:09:06Z</created>
<link href="http://www.greatwriting.com/blog/2006/09/class-of-super-ceos.html" rel="alternate" title="A Class of Super CEOs" type="text/html"/>
<id>tag:blogger.com,1999:blog-11211488.post-115920054671973549</id>
<title mode="escaped" type="text/html">A Class of Super CEOs</title>
<content type="application/xhtml+xml" xml:base="http://www.greatwriting.com/blog" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">
<blockquote>
<span style="font-size:180%;">The failures of the tech bubble have received attention disproportionate to the value of the lessons learned.</span>
</blockquote>
<br/>Is there a difference between CEOs who lived through the collapse of the tech bubble and those who did not have to face that challenge?  Asking this question is like looking at the DNA of people infected in an epidemic to see why some got sick but recovered, some died, and some never had symptoms to begin with.  Scientists do that kind of research all the time to see what it is that protects some people -- as well as to see, whatever that agent might be, whether it can be transferred to others so as to protect them as well.<br/>
<br/>I suggest that we may have a new class of super CEOs among us.  These are CEOs who have -- for lack of a better word -- genes that are different from those of the general CEO population.   These are CEOs who know how to recover -- or how not to get "sick" in the first place.  For all its pain, something good that may have come out of the tech collapse was that -- by its very scope -- it provided a large sample of CEOs who were able to do something most high-tech CEOs (and probably most CEOs period) could not.<br/>
<br/>I would suggest that the failures of the tech bubble have received attention disproportionate to the value of the lessons learned.  Bubbles come and go.  They're pretty predictable.  And the causes are well understood.  What's gone relatively under-reported and under-researched are the thousands of "everyday" success stories that seem to fly in the face of these cycles.  These stories are different from the relatively small number of celebrity cases, like Apple Computer, that are constantly getting coverage -- but which most CEOs (or would-be CEOs) would find virtually impossible to emulate.<br/>
<br/>Two qualities distinguish this new class of super CEOs from the celebrities: there are many more of them and their lessons are more transferable. So their impact should be much greater.</div>
</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
</feed>
