<?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 for mike.trachta</title>
	<atom:link href="http://mike.trachta.org/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://mike.trachta.org</link>
	<description></description>
	<lastBuildDate>Tue, 19 Jan 2010 21:06:29 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on SSIS: Returning NULL in a conditional statement by stevet</title>
		<link>http://mike.trachta.org/archives/4/comment-page-1#comment-80</link>
		<dc:creator>stevet</dc:creator>
		<pubDate>Tue, 19 Jan 2010 21:06:29 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/2007/10/22/ssis-returning-null-in-a-conditional-statement/#comment-80</guid>
		<description>Stumbled upon this one myself.  To expand on this anser, one can use the straight NULL(DT_STR,27,1252) by itself, but will have to prefix when in a conditional statement</description>
		<content:encoded><![CDATA[<p>Stumbled upon this one myself.  To expand on this anser, one can use the straight NULL(DT_STR,27,1252) by itself, but will have to prefix when in a conditional statement</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Verisign Powers iPhone Two-Factor Authentication by mike.trachta &#187; Facebook to Support OpenID</title>
		<link>http://mike.trachta.org/archives/39/comment-page-1#comment-69</link>
		<dc:creator>mike.trachta &#187; Facebook to Support OpenID</dc:creator>
		<pubDate>Wed, 29 Apr 2009 12:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=39#comment-69</guid>
		<description>[...] Now I&#8217;ll be able to log on to Facebook using my iPhone as a virtual token. [...]</description>
		<content:encoded><![CDATA[<p>[...] Now I&#8217;ll be able to log on to Facebook using my iPhone as a virtual token. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Verisign Powers iPhone Two-Factor Authentication by Eric</title>
		<link>http://mike.trachta.org/archives/39/comment-page-1#comment-61</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 10 Apr 2009 18:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=39#comment-61</guid>
		<description>What a great app. Who wants to carry extra key fobs around!? I hope we see more web sites participate in this. I remember reading an article about Blizzard (http://ow.ly/2yna) offering a token device to further secure the user&#039;s account. Why haven&#039;t our banking websites offered this?</description>
		<content:encoded><![CDATA[<p>What a great app. Who wants to carry extra key fobs around!? I hope we see more web sites participate in this. I remember reading an article about Blizzard (<a href="http://ow.ly/2yna" rel="nofollow">http://ow.ly/2yna</a>) offering a token device to further secure the user&#8217;s account. Why haven&#8217;t our banking websites offered this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Good Technical Sales Person, Defined by Sales_Engineer</title>
		<link>http://mike.trachta.org/archives/33/comment-page-1#comment-59</link>
		<dc:creator>Sales_Engineer</dc:creator>
		<pubDate>Thu, 02 Apr 2009 18:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=33#comment-59</guid>
		<description>The combination of abilities needed in a good technical salesperson is not easy to find. He or she must have sufficient technical knowledge of the product or service to be able to discuss complexities but they must also have the skills and motivation of a capable salesperson so that they fail to close available business. Such people do exist, but they aren&#039;t common. 

There is a comprehensive source of information about what makes a good technical sales person and how to go about hiring one at &lt;a href=&quot;how-to-hire-a-good-technical-salesman-manual.htm&quot; rel=&quot;nofollow&quot;&gt;How to Hire a Good Technical Salesman&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>The combination of abilities needed in a good technical salesperson is not easy to find. He or she must have sufficient technical knowledge of the product or service to be able to discuss complexities but they must also have the skills and motivation of a capable salesperson so that they fail to close available business. Such people do exist, but they aren&#8217;t common. </p>
<p>There is a comprehensive source of information about what makes a good technical sales person and how to go about hiring one at <a href="how-to-hire-a-good-technical-salesman-manual.htm" rel="nofollow">How to Hire a Good Technical Salesman</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Good Technical Sales Person, Defined by leo</title>
		<link>http://mike.trachta.org/archives/33/comment-page-1#comment-58</link>
		<dc:creator>leo</dc:creator>
		<pubDate>Thu, 26 Mar 2009 11:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=33#comment-58</guid>
		<description>wat does a technical salesperson do usually?
can deliver d answer to my email?thx ya~</description>
		<content:encoded><![CDATA[<p>wat does a technical salesperson do usually?<br />
can deliver d answer to my email?thx ya~</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What Makes A Good Technical Sales Person? by mike</title>
		<link>http://mike.trachta.org/archives/25/comment-page-1#comment-31</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Tue, 14 Oct 2008 14:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=25#comment-31</guid>
		<description>I guess I never thought about it from a reporting/metrics perspective.  I might have to add a comment about that to my response.</description>
		<content:encoded><![CDATA[<p>I guess I never thought about it from a reporting/metrics perspective.  I might have to add a comment about that to my response.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What Makes A Good Technical Sales Person? by Rod</title>
		<link>http://mike.trachta.org/archives/25/comment-page-1#comment-30</link>
		<dc:creator>Rod</dc:creator>
		<pubDate>Tue, 14 Oct 2008 13:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=25#comment-30</guid>
		<description>My personal view for a tech sales person (TSP), is that they main job should be to control user expectation.  Yes, you want the user to be excited about your product, and that&#039;s the sales persons job; but you don&#039;t to sell the customer an F-16 when you make Chevy&#039;s.  

I don&#039;t want to say he is there to keep the sales person honest, but I would say that is their first job.  

Second, I would say that their job should be to make POC&#039;s as close to production settings as possible.

But, now that I think about sales and tech sales, the problems really come down to compensation and who they report to.  Obviously, the sales person is on commission and reports to the VP of Sales, but who should the tech sales person report to?  If they report to the same person, they will be judged by the same metrics of how many sales, but quality of sale needs to be accounted for as well.  

A TSP should report to engineering and represent them.  So, if the quality of customer is bad, they can show the POC&#039;s to the engineers, and the they should know if the TSP is being honest or showing hacks.

This is where the problems come in, teaming a SP with a TSP, that have the same metric and managers, are more dangerous than SP alone.  Now you have a SP with a partner that can tell him how to hack the system to make it do some cool fragile and complicated stuff.</description>
		<content:encoded><![CDATA[<p>My personal view for a tech sales person (TSP), is that they main job should be to control user expectation.  Yes, you want the user to be excited about your product, and that&#8217;s the sales persons job; but you don&#8217;t to sell the customer an F-16 when you make Chevy&#8217;s.  </p>
<p>I don&#8217;t want to say he is there to keep the sales person honest, but I would say that is their first job.  </p>
<p>Second, I would say that their job should be to make POC&#8217;s as close to production settings as possible.</p>
<p>But, now that I think about sales and tech sales, the problems really come down to compensation and who they report to.  Obviously, the sales person is on commission and reports to the VP of Sales, but who should the tech sales person report to?  If they report to the same person, they will be judged by the same metrics of how many sales, but quality of sale needs to be accounted for as well.  </p>
<p>A TSP should report to engineering and represent them.  So, if the quality of customer is bad, they can show the POC&#8217;s to the engineers, and the they should know if the TSP is being honest or showing hacks.</p>
<p>This is where the problems come in, teaming a SP with a TSP, that have the same metric and managers, are more dangerous than SP alone.  Now you have a SP with a partner that can tell him how to hack the system to make it do some cool fragile and complicated stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Who Else Hates POCs? by The Most Magical Bullet &#171; Identity Blogger</title>
		<link>http://mike.trachta.org/archives/20/comment-page-1#comment-29</link>
		<dc:creator>The Most Magical Bullet &#171; Identity Blogger</dc:creator>
		<pubDate>Wed, 08 Oct 2008 17:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=20#comment-29</guid>
		<description>[...] IdM POCs are &#8220;difficult&#8221;. Mike Trachta follows up with why the successful POCs cause headaches for the SIs that have to produce the wonderful scenarios shown in the POCs. Both of these posts are [...]</description>
		<content:encoded><![CDATA[<p>[...] IdM POCs are &#8220;difficult&#8221;. Mike Trachta follows up with why the successful POCs cause headaches for the SIs that have to produce the wonderful scenarios shown in the POCs. Both of these posts are [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Who Else Hates POCs? by Rod</title>
		<link>http://mike.trachta.org/archives/20/comment-page-1#comment-28</link>
		<dc:creator>Rod</dc:creator>
		<pubDate>Tue, 07 Oct 2008 13:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=20#comment-28</guid>
		<description>I hate POC&#039;s.  Being in the web world, I don&#039;t get as many &quot;functional&quot; POC&#039;s as much as I get wireframe mockup&#039;s from graphic designers.

Yeah, they look pretty, but nonsensical links, missing functionality, and perfectly text limited user comments, drive me crazy.  

They always forget the logout button and create expectation and functionality that the customer expects now.

Customer: &quot;Where is that link?  Its in the mock up&quot;
Me: &quot;What is that link supposed to do?&quot;
Customer: &quot;I don&#039;t know, but the graphic designer made it and it looks pretty and I WANT MY LINK!&quot; 
Customer: Proceeds to lay on floor and throw a fit.
Me: Gets to create a link.</description>
		<content:encoded><![CDATA[<p>I hate POC&#8217;s.  Being in the web world, I don&#8217;t get as many &#8220;functional&#8221; POC&#8217;s as much as I get wireframe mockup&#8217;s from graphic designers.</p>
<p>Yeah, they look pretty, but nonsensical links, missing functionality, and perfectly text limited user comments, drive me crazy.  </p>
<p>They always forget the logout button and create expectation and functionality that the customer expects now.</p>
<p>Customer: &#8220;Where is that link?  Its in the mock up&#8221;<br />
Me: &#8220;What is that link supposed to do?&#8221;<br />
Customer: &#8220;I don&#8217;t know, but the graphic designer made it and it looks pretty and I WANT MY LINK!&#8221;<br />
Customer: Proceeds to lay on floor and throw a fit.<br />
Me: Gets to create a link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An Elevator Pitch for Identity Management, part 2 by Orhan Osmani</title>
		<link>http://mike.trachta.org/archives/11/comment-page-1#comment-27</link>
		<dc:creator>Orhan Osmani</dc:creator>
		<pubDate>Sun, 05 Oct 2008 08:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://mike.trachta.org/?p=11#comment-27</guid>
		<description>Mike,

Before you do the pitch on IAM or any product/service. Do the study of the client/customer. I usually try to understand three things about customer when I try to sell IAM.

I always remember - I-S-B - If you understand the (I) issues they have - you can pitch the (S) solution and then you can clearly relate the (B) benefits they can draw out of it.

IAM pitch should different to every customer is you know the ISB of the person/organization you are talking to.

IAM definition/s and pitches do not address pains of those listening, you have to break it down into pieces and explain in layman language.

There is not and should not be defined iam pitch. Be practical and come up with pitches that make sense to the customer environments and needs they have. 

Regards,
Orhan</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>Before you do the pitch on IAM or any product/service. Do the study of the client/customer. I usually try to understand three things about customer when I try to sell IAM.</p>
<p>I always remember &#8211; I-S-B &#8211; If you understand the (I) issues they have &#8211; you can pitch the (S) solution and then you can clearly relate the (B) benefits they can draw out of it.</p>
<p>IAM pitch should different to every customer is you know the ISB of the person/organization you are talking to.</p>
<p>IAM definition/s and pitches do not address pains of those listening, you have to break it down into pieces and explain in layman language.</p>
<p>There is not and should not be defined iam pitch. Be practical and come up with pitches that make sense to the customer environments and needs they have. </p>
<p>Regards,<br />
Orhan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
