<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: A High-tech Entrepreneur&#8217;s Guide to Surviving Technical Due Diligence</title>
	<atom:link href="http://blog.pasker.net/2007/08/28/a-high-tech-entrepreneurs-guide-to-surviving-technical-due-diligence/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pasker.net/2007/08/28/a-high-tech-entrepreneurs-guide-to-surviving-technical-due-diligence/</link>
	<description></description>
	<lastBuildDate>Thu, 09 Apr 2009 09:44:13 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: rbpasker</title>
		<link>http://blog.pasker.net/2007/08/28/a-high-tech-entrepreneurs-guide-to-surviving-technical-due-diligence/#comment-16</link>
		<dc:creator>rbpasker</dc:creator>
		<pubDate>Thu, 30 Aug 2007 19:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://theabstracttruth.wordpress.com/2007/08/28/a-high-tech-entrepreneurs-guide-to-surviving-technical-due-diligence/#comment-16</guid>
		<description>Depending on how much chutzpah you have, you should be able to keep the conversation steered in the right direction. Your people, at least, should be trying to keep the discussions on track, but you can&#039;t always control the rest of the people in the room. --bob</description>
		<content:encoded><![CDATA[<p>Depending on how much chutzpah you have, you should be able to keep the conversation steered in the right direction. Your people, at least, should be trying to keep the discussions on track, but you can&#8217;t always control the rest of the people in the room. &#8211;bob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NC</title>
		<link>http://blog.pasker.net/2007/08/28/a-high-tech-entrepreneurs-guide-to-surviving-technical-due-diligence/#comment-14</link>
		<dc:creator>NC</dc:creator>
		<pubDate>Wed, 29 Aug 2007 19:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://theabstracttruth.wordpress.com/2007/08/28/a-high-tech-entrepreneurs-guide-to-surviving-technical-due-diligence/#comment-14</guid>
		<description>I&#039;ve been through two tech due-diligence meetings, both of which had me acting as the semi-technical CEO flanked by our CTO and lead developers.

I found the biggest challenge was keeping the conversation on topic.  Their biz guys were dominating the room with questions that weren&#039;t very relevant, and their tech guys wanted to argue the finer points of multi-threaded server architecture rather than dig into what we had built.

My agenda must have been weak, because it was constantly being derailed. My tech guys were just as guilty, by engaging all the tangents.. and were defensive every time unknowns were brought up.

It was 2000, and we were demonstrating group video conferencing using Flash. It was a first. We had no idea how well it would scale. We had no idea what would happen if we threw it on some great hardware.  And there was no reason for the techs to get defensive -- because it was really cool, and we were there to talk about how Macromedia might take the project off our hands and make it into something bigger.

Looking back, I should have spent more time prepping the developers before the meeting -- and should have done a better job at moderating the meeting...

But how much of that onus should be on the company being &quot;interviewed&quot;? If the the interviewers can&#039;t keep on point, are you doomed walking in the door?  And how often is this the case that the interviewers are scattered and unprepared?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been through two tech due-diligence meetings, both of which had me acting as the semi-technical CEO flanked by our CTO and lead developers.</p>
<p>I found the biggest challenge was keeping the conversation on topic.  Their biz guys were dominating the room with questions that weren&#8217;t very relevant, and their tech guys wanted to argue the finer points of multi-threaded server architecture rather than dig into what we had built.</p>
<p>My agenda must have been weak, because it was constantly being derailed. My tech guys were just as guilty, by engaging all the tangents.. and were defensive every time unknowns were brought up.</p>
<p>It was 2000, and we were demonstrating group video conferencing using Flash. It was a first. We had no idea how well it would scale. We had no idea what would happen if we threw it on some great hardware.  And there was no reason for the techs to get defensive &#8212; because it was really cool, and we were there to talk about how Macromedia might take the project off our hands and make it into something bigger.</p>
<p>Looking back, I should have spent more time prepping the developers before the meeting &#8212; and should have done a better job at moderating the meeting&#8230;</p>
<p>But how much of that onus should be on the company being &#8220;interviewed&#8221;? If the the interviewers can&#8217;t keep on point, are you doomed walking in the door?  And how often is this the case that the interviewers are scattered and unprepared?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
