<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Friends of eisokant</title><link>http://disqus.com/by/eisokant/</link><description></description><atom:link href="http://disqus.com/eisokant/friends.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 08 Jan 2009 15:02:26 -0000</lastBuildDate><item><title>Re: 25 Tips for a Better Wiki Deployment + 1 Tip on How to NOT Use Presentations</title><link>(u'http://www.zoliblog.com/2007/12/18/25-tips-for-a-better-wiki-deployment-1-tip-on-how-to-not-use-presentations/',%205639212L)#comment-5639212</link><description>&lt;p&gt;I would characterize you as "way too deeply" interested in wikis. But you criticized the form and not the substance of the presentation, perhaps because, like me, you couldn't find any real substance. It seems to me in their several suggestions for rewards and merit badges the authors were confused about the fact that wikis dissolve voice and authorship. Many of these suggestions are more appropriate for encouraging an internal blogging ecosystem. Wiki's require team incentives and rewards to be effective, rewarding individuals is more appropriate for blog or forum posts where the authorship is clear. They also seem to miss the point completely that the place to start is with frequently updated information that is also frequently accessed. Meeting agendas and minutes (avoiding the bottleneck of the designated note taker and/or overlapping amendments in different e-mails that then have to be reconciled), early and still evolving specifications, and project status in a dynamic environment are much better places to start. At some point in the enterprise world many wikis must be congealed into a document or document set and either archived, frozen as a static HTML tree, or transferred to a content management system where more formal revision and change control methods are more appropriate. Projects end, products are shipped and end of life, problems get solved: unlike Internet wikis, older wikis in the Enterprise are often better preserved as read only archives. I think Wikipedia anchors a lot of expectations in a use case that is rarely appropriate to a team that is not building an encyclopedia.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Thu, 20 Dec 2007 17:44:53 -0000</pubDate></item><item><title>Re: 25 Tips for a Better Wiki Deployment + 1 Tip on How to NOT Use Presentations</title><link>(u'http://www.zoliblog.com/2007/12/18/25-tips-for-a-better-wiki-deployment-1-tip-on-how-to-not-use-presentations/?nucrss=1',%2015818496L)#comment-15818496</link><description>&lt;p&gt;I would characterize you as "way too deeply" interested in wikis. But you criticized the form and not the substance of the presentation, perhaps because, like me, you couldn't find any real substance. It seems to me in their several suggestions for rewards and merit badges the authors were confused about the fact that wikis dissolve voice and authorship. Many of these suggestions are more appropriate for encouraging an internal blogging ecosystem. Wiki's require team incentives and rewards to be effective, rewarding individuals is more appropriate for blog or forum posts where the authorship is clear. They also seem to miss the point completely that the place to start is with frequently updated information that is also frequently accessed. Meeting agendas and minutes (avoiding the bottleneck of the designated note taker and/or overlapping amendments in different e-mails that then have to be reconciled), early and still evolving specifications, and project status in a dynamic environment are much better places to start. At some point in the enterprise world many wikis must be congealed into a document or document set and either archived, frozen as a static HTML tree, or transferred to a content management system where more formal revision and change control methods are more appropriate. Projects end, products are shipped and end of life, problems get solved: unlike Internet wikis, older wikis in the Enterprise are often better preserved as read only archives. I think Wikipedia anchors a lot of expectations in a use case that is rarely appropriate to a team that is not building an encyclopedia.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Thu, 20 Dec 2007 17:44:53 -0000</pubDate></item><item><title>Re: Silicon Valley Arrogance</title><link>(u'http://avc.com/2008/02/silicon-valley/',%20132206L)#comment-132206</link><description>&lt;p&gt;I would think in your business it would be useful to be clear eyed and avoid the Valley centric astigmatism for technology analysis. I really don't understand your complaint. If you wanted to be a well respected pundit I can appreciate how this lack of respect would be grating, but if it's about spotting opportunities for investment that other firms are overlooking, this bias would seem to accrue a number of advantages to your firm.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Thu, 07 Feb 2008 12:35:36 -0000</pubDate></item><item><title>Re: Why I Can&amp;#8217;t Read Novels Anymore</title><link>(u'http://www.leveragingideas.com/2008/02/04/why-i-cant-read-novels-anymore/',%20134265L)#comment-134265</link><description>&lt;p&gt;There is a category of information that hasn't been written down (yet). You might try more reflection and focus on serious conversation to regain your balance. Ultimately gathering all of this information has to be used for a purpose beyond maintaining situational awareness. What kind of know-how do you want to develop? What is the problem you are trying to solve. Neither Google, nor the Blogosphere/, nor the World Wide Web are the world. As Korzybski observed: "The map is not the territory, the word is not the thing it describes. Whenever the map is confused with the territory, a 'semantic disturbance' is set up in the organism. The disturbance continues until the limitation of the map is recognized."&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Fri, 08 Feb 2008 06:21:16 -0000</pubDate></item><item><title>Re: Why I Can&amp;#8217;t Read Novels Anymore</title><link>(u'http://www.leveragingideas.com/2008/02/04/why-i-cant-read-novels-anymore/',%20144807L)#comment-144807</link><description>&lt;p&gt;I am not a venture capitalist but have some experience working with them and I would think much of the key or differentiating information in they rely on is not on the web. It seems to me it's more about being able to judge people rather than encyclopedic knowledge of technology and financial trends. As an analogy: it's the difference between knowing the probability distributions of poker hands--necessary but not sufficient--and knowing how to assess people. The deep trends are visible in the "long nose of innovation." What society will do with them is harder to predict.&lt;/p&gt;&lt;p&gt;The latest data on developing expertise is that it takes approximately 10,000 hours (or 10-12 years) of practice, and actually requires "deliberate practice" so that you don't experience the same year over and over. See for example &lt;a href="http://www.psy.fsu.edu/faculty/ericsson/ericsson.exp.perf.html" rel="nofollow noopener" target="_blank" title="http://www.psy.fsu.edu/faculty/ericsson/ericsson.exp.perf.html"&gt;http://www.psy.fsu.edu/facu...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;I don't fault your goals, but I do question your methods.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Tue, 12 Feb 2008 23:03:02 -0000</pubDate></item><item><title>Re: How to Grow Your Ideas With a Project Incubator</title><link>(u'http://lifedev.net/2008/02/how-to-set-up-and-maintain-a-project-incubator/',%2011002226L)#comment-11002226</link><description>&lt;p&gt;I would think a wiki (say EditMe, PBWiki, CentralDesktop) would give you more flexibility to link between ideas and would be more easier to refactor. You could still have one idea on a page but it would be more straightforward to cross-link and re-factor. The basic suggestion is certainly excellent, at the moment I keep mine in a single large "ideas" file. This post has prompted me to reconsider.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Fri, 15 Feb 2008 22:46:58 -0000</pubDate></item><item><title>Re: Why Not To Do A Startup</title><link>(u'http://mattmaroon.com/?p=340',%20244492L)#comment-244492</link><description>&lt;p&gt;We see a lot of bootstrappers who run "small successful" software firms who are about as happy as they would have been in "a real job." Some break out and some fail, but many fall into a fairly large middle ground: they achieve modest success but stay below the radar screen of most observers. It's one of the reasons we facilitate the Bootstrapper Breakfasts &lt;a href="http://www.bootstrapperbreakfast.com/" rel="nofollow noopener" target="_blank" title="http://www.bootstrapperbreakfast.com/"&gt;http://www.bootstrapperbrea...&lt;/a&gt; as a service to the startup community.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Wed, 19 Mar 2008 12:28:58 -0000</pubDate></item><item><title>Re: Founder's Blog - ClutterMe.com</title><link>(u'http://blog.clutterme.com/',%20249973L)#comment-249973</link><description>&lt;p&gt;One point I would add is that a recession can create "involuntary entrepreneurs" who have to do a startup (at least on a consulting model that may or may not lead to a product) because they can't keep telling folks "looking for work" when asked what they are doing. They may also get offered part-time consulting and realize that there is a product or productized service opportunity. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Thu, 20 Mar 2008 19:41:45 -0000</pubDate></item><item><title>Re: Why VCs Aren&amp;#8217;t More Brave</title><link>(u'http://mattmaroon.com/?p=354',%20346013L)#comment-346013</link><description>&lt;p&gt;I agree with our assessment on Google, there just aren't that many companies that get that big that fast, Cisco was probably the last one to do so in Silicon Valley, and their market cap is less than half of what is was a few years ago.&lt;/p&gt;&lt;p&gt;I have a different assessment of Angels, I don't know that they are braver than VC's, but they don't have to invest and they can have a longer time horizon than VC's. Also, in my experience,  Angels would prefer to put the last money in, or at least participate in what is the last round (e.g. via a bridge loan). They don't typically have the wherewithal for follow on rounds. I don't know the breakdown on YC returns is but with a number of early acquisitions they may have backed into this with several of their investments. Also, Angels can have a longer time horizon than the average VC because they don't have to get to a liquidity event within five to seven years from investment (most VC firms raise ten year fund and don't want to return stock in a private firm to their limited partners since it's normally hard to liquidate). &lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Thu, 17 Apr 2008 02:16:51 -0000</pubDate></item><item><title>Re: Central Desktop Takes $7 Million</title><link>(u'http://techcrunch.com/2008/04/16/central-desktop-takes-7-million/',%2071905351L)#comment-71905351</link><description>&lt;p&gt;We have been using CentralDesktop for the last 18 months to collaborate with clients and have been delighted with their service and impressed by how they organize the "honeycomb model" of their workspaces. It works particularly well when you are running several projects in parallel and want to have "firewalls" between them for access: client A cannot see client B's work, and vice versa. They also do a better job of "contention management" than most which is especially important as you are collaborating closely against a deadline. Nothing can shatter team dynamics faster than the ability to inadvertently over-write someone else's work.&lt;/p&gt;&lt;p&gt;@anonyjoe I think we are still close to the 1% point on what small team collaboration environments look like. The "small team moving fast" looks very different outside the enterprise rather than inside the enterprise and is much more empowered by a cloud computing model that allows for easy inclusion of suppliers, customers, and partners.  In particular CentralDesktop's pricing model (based on workspace count not user count) allows us to run more than 100 workspaces at a very effective price point.  As a happy side effect from their perspective, it makes it viral because we are then willing to use them with everyone we collaborate with, some of whom decide to get their own (or transfer ownership at the end of a project).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Thu, 17 Apr 2008 14:26:07 -0000</pubDate></item><item><title>Re: What They Don&amp;#8217;t Tell You About Starting a Startup</title><link>(u'http://adityakothadiya.com/2008/04/what-they-dont-tell-you-about-starting-a-startup/',%206271597L)#comment-6271597</link><description>&lt;p&gt;Probably the best book on entrepreneurial roller coaster is Barry Moltz's "You Have to Be a Little Crazy" which includes an excellent introduction by Howard Tullman that is directly on point to the real issues of entrepreneurship: Identity, Family, and Failure. Tullman notes "Identity is important because entrepreneurs constantly confuse what they do with who they are. We’re all certainly responsible for what we do but failing doesn’t make us bad people and succeeding doesn’t make us omniscient."&lt;/p&gt;&lt;p&gt;Keeping in mind that no one wished they had spent more time at the office on their deathbed, Tullman notes "Family is important because it’s a much more important extension of ourselves than any work we’ll ever do. There’s always more work but you’ve only got one family." which is certainly counter to Currier's approach  of subordinating family to startup.&lt;/p&gt;&lt;p&gt;More on the book&lt;br&gt;&lt;a href="http://www.amazon.com/You-Need-Be-Little-Crazy/dp/079318018X/" rel="nofollow noopener" target="_blank" title="http://www.amazon.com/You-Need-Be-Little-Crazy/dp/079318018X/"&gt;http://www.amazon.com/You-N...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;More on Barry Moltz&lt;br&gt;&lt;a href="http://www.barrymoltz.com/" rel="nofollow noopener" target="_blank" title="http://www.barrymoltz.com/"&gt;http://www.barrymoltz.com/&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Two blog entries I wrote relative to Moltz's book&lt;br&gt;&lt;a href="http://www.skmurphy.com/blog/2006/12/27/you-need-to-be-a-little-crazy/" rel="nofollow noopener" target="_blank" title="http://www.skmurphy.com/blog/2006/12/27/you-need-to-be-a-little-crazy/"&gt;http://www.skmurphy.com/blo...&lt;/a&gt;&lt;br&gt;&lt;a href="http://www.skmurphy.com/blog/2007/10/16/the-challenge-of-advising-entrepreneurs/" rel="nofollow noopener" target="_blank" title="http://www.skmurphy.com/blog/2007/10/16/the-challenge-of-advising-entrepreneurs/"&gt;http://www.skmurphy.com/blo...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Moltz himself observes "Entrepreneurs start businesses because..they have no choice. Passion and energy drive them on good days and sustain them on bad days." I agree with his  assessment: sometimes we pursue our dreams and sometimes they pursue us, but in neither case do most entrepreneurs have a real choice.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Sun, 27 Apr 2008 21:45:34 -0000</pubDate></item><item><title>Re: Ultra-immersive, long-form video games from the past or future</title><link>(u'http://paulbuchheit.blogspot.com/2008/01/ultra-immersive-long-form-video-games.html',%20396010L)#comment-396010</link><description>&lt;p&gt;"We are not human beings have a spiritual experience. We are spiritual beings having a human experience."  Pierre Teilhard de Chardin&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Wed, 30 Apr 2008 01:11:40 -0000</pubDate></item><item><title>Re: Ten Interesting Memes Plucked From The Blogosphere</title><link>(u'http://www.leveragingideas.com/2008/05/06/social-media-memes-twitter/',%20448523L)#comment-448523</link><description>&lt;p&gt;Concept of Singularity was well established prior to Peter Thiel's donation: it was coined by Vernor Vinge in 1993 see &lt;a href="http://www-rohan.sdsu.edu/faculty/vinge/misc/singularity.html" rel="nofollow noopener" target="_blank" title="http://www-rohan.sdsu.edu/faculty/vinge/misc/singularity.html"&gt;http://www-rohan.sdsu.edu/f...&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Mon, 12 May 2008 01:22:53 -0000</pubDate></item><item><title>Re: Facebook viral marketing: When and why do apps &amp;#8220;jump the shark?&amp;#8221;</title><link>(u'http://andrewchen.co/2008/03/05/facebook-viral-marketing-when-and-why-do-apps-jump-the-shark/',%201843609L)#comment-1843609</link><description>&lt;p&gt;Great post, one thing that struck me is that it doesn't capture the "competitive equilibria" issues that may also occur. Your social network isn't the only  one recruiting, so that there is competition for the total carrying capacity. I think there may also be a bandwagon effect, where users depart smaller groups (in the context of a particular demographic/market/segment that you measure with your carrying capacity) for larger ones because they offer more benefits. But I agree with your basic modeling approach.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Mon, 19 May 2008 01:24:22 -0000</pubDate></item><item><title>Re: Who are you? What do you do?</title><link>(u'http://onticoren.com/2008/04/10/who-are-you-what-do-you-do/',%202925980L)#comment-2925980</link><description>&lt;p&gt;Since you are a startup you should focus on what makes you trustworthy and dependable. The biggest question in a prospect's mind is how will you perform when things go wrong. I think too many startup teams stress how smart they are or how many merit badges they have accumulated (degrees, certificates) or almost accumulated (e.g. coursework towards doctorate but no doctorate) instead of projects that they have delivered and value they have created for former partners, customers, etc..&lt;/p&gt;&lt;p&gt;It's a mistake to recycle anything from your investor presentation (fund-raising pitch) into your presentation for prospects. It's two fundamentally different audiences with very different needs and distinct questions about your team and your offering. Steve Blank's "Four Steps to the Epiphany" is a good guide for strategies in the early market.&lt;/p&gt;&lt;p&gt;If you are thinking about including your corporate backgrounder in your demo or presentation...don't, or at least put it at the end after you have demonstrated something directly relevant to the prospect's situation. They may be interested in learning more about you at that point, or they may want to discuss how to get started. See Peter Cohan's "Great Demo!" book for a good methodology.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Wed, 21 May 2008 18:58:09 -0000</pubDate></item><item><title>Re: Creating Passionate People</title><link>(u'http://eisokant.com/2008/07/17/creating-passionate-people/',%20925926L)#comment-925926</link><description>&lt;p&gt;Shouldn't this be discovering and engaging people's passions? I try and keep track of what other folks are looking for or potential solutions to problems that they are wrestling with. But I haven't formalized the process to the extent that you have.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Thu, 17 Jul 2008 17:08:30 -0000</pubDate></item><item><title>Re: Financial crises and forest fires</title><link>(u'http://blog.payne.org/2008/09/30/financial-crises-and-forest-fires/',%20193603983L)#comment-193603983</link><description>&lt;p&gt;Robert Cringely sees the same analogy in "The Cringely Plan: See the Light" &lt;a href="http://www.pbs.org/cringely/pulpit/2008/pulpit_20080926_005422.html" rel="nofollow noopener" target="_blank" title="http://www.pbs.org/cringely/pulpit/2008/pulpit_20080926_005422.html"&gt;http://www.pbs.org/cringely...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;"An unmanaged forest, one without the sort of fire control we attempted to provide, would naturally burn every few years. The undergrowth would build up, reach a critical mass, some source of ignition would come along -- usually lightning -- and all that undergrowth would burn. The redwoods themselves would be scarred but not really threatened, as we could see from the charring that marked them from countless such fires over centuries. Of course burning undergrowth threatened homes and property, too, so there was a natural desire on the part of that community to want the next burn to not come this year, please not this year. So there came a policy of aggressively fighting fires with the result that we eventually faced 60 (now 90!) years of flammable material growth rather than six or eight years. And the probable fire fueled by 60 years of undergrowth would have been so bad that our job changed to one of trying to prevent fires from happening, well, ever. This was an impossible task, of course. Eventually the stars would align the wrong way and the whole place would burn down, we all knew it. Just let it not happen on our watch.&lt;/p&gt;&lt;p&gt;Does this sound familiar?"&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Fri, 03 Oct 2008 03:33:59 -0000</pubDate></item><item><title>Re: Enterprise Software: Focus on User Adoption, Not Features</title><link>(u'http://www.readwriteweb.com/archives/focus_on_user_adoption_not_software_features.php',%20110495856L)#comment-110495856</link><description>&lt;p&gt;Given that Neochange's tag line is "Driving Effective IT Adoption" it's not surprising that they reach this conclusion. It's also a tautology: if enterprise employees are not using the software then it's unlikely you will get additional orders/subscriptions/upgrades. Although the fact that term "shelfware" exists indicates some companies are able to make money selling software that's bought but not adopted. &lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;As to tips and techniques for fostering adoption Peter Cohan's model for collecting user stories by listening to users in a structured and sustained way is an excellent place to start. See &lt;a href="http://www.secondderivative.com/Four_Opportunities_to_Harvest_The_Value_of_Informal_Success_Stories.html" rel="nofollow noopener" target="_blank" title="http://www.secondderivative.com/Four_Opportunities_to_Harvest_The_Value_of_Informal_Success_Stories.html"&gt;http://www.secondderivative.com/Four_Opportunities_to_Harvest_The_Value_of_Informal_Success_Stories.html&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Sat, 18 Oct 2008 01:42:27 -0000</pubDate></item><item><title>Re: Don&amp;#8217;t Mistake Ambition for Entitlement</title><link>(u'http://mattmaroon.com/?p=573',%203279568L)#comment-3279568</link><description>&lt;p&gt;I guess the difference between my 20's and my 40's is that in my 20's I was held back by outside events and the people around me and in my 40's I am held back by my own shortcomings and decisions.&lt;/p&gt;&lt;p&gt;Upon reflection, it was that way in my 20's as well.&lt;/p&gt;&lt;p&gt;It's a crap article full of crap generalizations that are true for every generation: you can find people who feel entitled and people who don't in every generation.  I would encourage you to aim your considerable talents at more worthy targets.&lt;/p&gt;&lt;p&gt;By the way,  the amount of technology change that your great grandparents saw--telephone, telegraph, automobile, antibiotics, television--in terms of its pervasive impact on life and business, is certainly on a par with the last 20 years.&lt;/p&gt;&lt;p&gt;Two quotes from folks born more than 100 years ago to point out that everything old is new again now.&lt;/p&gt;&lt;p&gt;"You get what you settle for." Emyln Williams&lt;/p&gt;&lt;p&gt;"It is a funny thing about life; if you refuse to accept anything but the best, you very often get it. "   Somerset Maugham&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Fri, 24 Oct 2008 14:30:45 -0000</pubDate></item><item><title>Re: Don&amp;#8217;t Mistake Ambition for Entitlement</title><link>(u'http://mattmaroon.com/?p=573',%203281158L)#comment-3281158</link><description>&lt;p&gt;I did say great grandparents to set it one generation back, let's say from 1900 to 1950. The telephone, telegraph, and automobile all transformed the workplace. It takes about 30 years from the time a technology is introduced for it to have a full impact on society (including the workplace).&lt;/p&gt;&lt;p&gt;Paul David's "The Dynamo and the Computer" is good background on how existing capital and infrastructure has to age out before the full impact of a new technology can be assessed. A more recent work is "Technological revolutions and financial capital" by Carlota Perez which details the multi-decade timeline of new technology adoption and impact on a country.&lt;/p&gt;&lt;p&gt;It seems to me that the opportunity is to design new firms and new business models that exploit existing inventions whose full impact has yet to be realized.  Perhaps that's what you are already doing.&lt;/p&gt;&lt;p&gt;I would like to hear more about how you would design new business structures (or adopt proven ones) that avoid some of the challenges you outline with inequitable distribution of effort/contribution and reward. What should real knowledge worker organizations look like, how can they be structured in way that's robust and long term stable in offering employees a career and be competitive in serving their customers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Fri, 24 Oct 2008 15:58:11 -0000</pubDate></item><item><title>Re: The Survival Matrix</title><link>(u'http://avc.com/2008/10/the-survival-ma/',%203327327L)#comment-3327327</link><description>&lt;p&gt;Burn rate is your net cash withdrawal from working capital. If you have revenue in excess of spending then your burn rate is zero because you are not making withdrawals. Seth is suggesting that these startups focus on more revenue now instead of planning to raise another round to stay alive.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Mon, 27 Oct 2008 13:52:11 -0000</pubDate></item><item><title>Re: Announcing VentureBeat&amp;#8217;s roundtable on &amp;#8220;how to manage the downturn&amp;#8221;</title><link>(u'http://venturebeat.com/2008/10/16/announcing-venturebeats-roundtable-on-how-to-manage-the-downturn/',%203345820L)#comment-3345820</link><description>&lt;p&gt;It's interesting that the VC's now want to charge $189 for an audience. Perhaps it's the choice of venue or someone else is brokering the relationship and collecting the cash.  At a Bootstrapper Breakfast ( &lt;a href="http://www.bootstrapperbreakfast.com/" rel="nofollow noopener" target="_blank" title="http://www.bootstrapperbreakfast.com/"&gt;http://www.bootstrapperbrea...&lt;/a&gt; ) you can meet other entrepreneurs who understand how to manage to their cashflow for just the price of your own breakfast and nothing else. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Tue, 28 Oct 2008 14:05:01 -0000</pubDate></item><item><title>Re: The Author’s Dilemma – Why Most Business Books Suck</title><link>(u'http://johngreathouse.com/whybusinessbookssuck/',%20175121539L)#comment-175121539</link><description>&lt;p&gt;I found "Four Steps to the Epiphany" full of practical advice for starting a software company. I do agree that many business books are a good magazine article that's been expanded unnecessarily, this is not one of them. What's strange is that I would be willing to pay the same amount for a much shorter write-up boiled to essentials with a few examples than a 180-250 page book. Perhaps 10-25 pages would do for most.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Tue, 11 Nov 2008 19:28:55 -0000</pubDate></item><item><title>Re: The Twice Shy Entrepreneur</title><link>(u'http://techcrunch.com/2007/12/09/the-twice-shy-entrepreneur/',%2072101861L)#comment-72101861</link><description>&lt;p&gt;What a difference a year makes. Now the "newcomer entrepreneurs" have had the chance to lay employees off and are encouraged by the VC's on their boards to focus on profit and survival instead of bold growth.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Sat, 13 Dec 2008 15:37:37 -0000</pubDate></item><item><title>Re: Default To Public</title><link>(u'http://avc.com/2009/01/default-to-publ/',%204994407L)#comment-4994407</link><description>&lt;p&gt;Wikis dissolve individual authorship into a team or group.  For class assignments that are group projects you might find your students already using wikis:  they are a great way for a small team to reach a working consensus on a document against a deadline.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skmurphy</dc:creator><pubDate>Thu, 08 Jan 2009 15:02:26 -0000</pubDate></item></channel></rss>