<?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 on: Do Product Managers need Domain Knowledge?</title> <atom:link href="http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/feed/" rel="self" type="application/rss+xml" /><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/</link> <description></description> <lastBuildDate>Wed, 23 May 2012 06:12:20 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.1.2</generator> <item><title>By: Melanie Holloway</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-40414</link> <dc:creator>Melanie Holloway</dc:creator> <pubDate>Thu, 12 Jan 2012 00:50:58 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-40414</guid> <description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;RT @onpm: Do Product Managers need Domain Knowledge? http://t.co/eeoLjbQn&lt;/span&gt;&lt;/span&gt;</description> <content:encoded><![CDATA[<p><span
class="topsy_trackback_comment"><span
class="topsy_twitter_username"><span
class="topsy_trackback_content">RT @onpm: Do Product Managers need Domain Knowledge? <a
href="http://t.co/eeoLjbQn" rel="nofollow">http://t.co/eeoLjbQn</a></span></span></span></p> ]]></content:encoded> </item> <item><title>By: Simon South</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-5107</link> <dc:creator>Simon South</dc:creator> <pubDate>Fri, 29 Jan 2010 05:30:43 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-5107</guid> <description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Why product managers need domain knowledge: A tech writer at the now-defunct Delrina writes about his experience there. http://bit.ly/ccRevw&lt;/span&gt;&lt;/span&gt;</description> <content:encoded><![CDATA[<p><span
class="topsy_trackback_comment"><span
class="topsy_twitter_username"><span
class="topsy_trackback_content">Why product managers need domain knowledge: A tech writer at the now-defunct Delrina writes about his experience there. <a
href="http://bit.ly/ccRevw" rel="nofollow">http://bit.ly/ccRevw</a></span></span></span></p> ]]></content:encoded> </item> <item><title>By: OnProductManagement</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-5108</link> <dc:creator>OnProductManagement</dc:creator> <pubDate>Thu, 20 Aug 2009 00:29:07 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-5108</guid> <description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;@rcauvin Domain knowledge is a pre-requisite for good #prodmgmt. See this story for the flip side. http://tr.im/wH52&lt;/span&gt;&lt;/span&gt;</description> <content:encoded><![CDATA[<p><span
class="topsy_trackback_comment"><span
class="topsy_twitter_username"><span
class="topsy_trackback_content">@rcauvin Domain knowledge is a pre-requisite for good #prodmgmt. See this story for the flip side. <a
href="http://tr.im/wH52" rel="nofollow">http://tr.im/wH52</a></span></span></span></p> ]]></content:encoded> </item> <item><title>By: Entrepreneurial Proverbs &#171; On Product Management</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-2583</link> <dc:creator>Entrepreneurial Proverbs &#171; On Product Management</dc:creator> <pubDate>Tue, 05 Aug 2008 04:39:21 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-2583</guid> <description>[...] what you know is another one I agree with. I&#8217;m a big proponent of having domain knowledge for whatever endeavour you embark on. Can you succeed with domain expertise? Certainly, but [...]</description> <content:encoded><![CDATA[<p>[...] what you know is another one I agree with. I&#8217;m a big proponent of having domain knowledge for whatever endeavour you embark on. Can you succeed with domain expertise? Certainly, but [...]</p> ]]></content:encoded> </item> <item><title>By: More Haiku madness&#8230; &#171; On Product Management</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-2582</link> <dc:creator>More Haiku madness&#8230; &#171; On Product Management</dc:creator> <pubDate>Fri, 23 Nov 2007 07:04:32 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-2582</guid> <description>[...] who have no domain knowledge suffer great [...]</description> <content:encoded><![CDATA[<p>[...] who have no domain knowledge suffer great [...]</p> ]]></content:encoded> </item> <item><title>By: Michael Litt</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-2581</link> <dc:creator>Michael Litt</dc:creator> <pubDate>Fri, 26 Oct 2007 22:03:02 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-2581</guid> <description>As the third on the project, I will agree that Delrina FAX was a very good example of the need for all team members to fully understand the market, the customers and the role of the product.  While a lot of what Saeed said is true this was rectified when a mac focused product marketing effort was brought in.  In general product marketing was brought in very late however the team working on the project early on (don and myself) understood and lived up to what people especially folks with fancy MBAs in the 2000s call customer-centricity.  This buzz word is used a lot more in the 2000s but we lived it in the early 90s without knowing it and it was the prime reason for the success of the project. On the other hand I would now argue that Winfax was more product focused. Delrina paid attention to customers but did not have a customer-centric focus.Delrina Fax was not a port of the Windows app, it was developed for the Apple zealots.  Features, manuals, demos, ads, pretty much all of the product was tailored for the Mac audience which was large in the &quot;graphics/publishing ghetto&quot; and an audience that had a large portion of female users.  Our demo was to fax a famous painting (at least I think as I am no art expert) of a young girl in her Sunday dress in a nice summer scene in full grayscale that appealed to graphics folks and to people of the fairer sex.  We compared it to the output from Winfax and our mac competitors and said which painting would you buy. Do you want to fax your work and have it look like Delrina-fax output or the other software.  Worked well with our audience.  Our other test was a picture of a Mariah carey showing some cleavage which would have worked better than a painting if our audience was mainly in prison.I would argue that customer-centricity is what is lost in the PC software of the 2000s whether out of Redmond or Cupertino and is better illustrated by websites such as Facebook, Myspace or Youtube.  One only has to look at Vista and office 2007 to see the lack of customer-centricity.Delrina Fax also is an example of a project that was not driven by marketing.  Delrina Fax was a success and it was not driven by marketing who are supposed to be the only folks who understand the market. Saeed shows that in some cases marketing can be a detriment. Marketing folks need to understand the benefits of educating the full team.The Mac product was a Skunkworks project and like any project, everyone will have a perspective and a memory of a project, however one thing I will agree with Steve Johnson on and I am sure all will agree, we could not have made this up.  The other take home is everyone on a project needs to know the customer, the market and the role of the product.Michael</description> <content:encoded><![CDATA[<p>As the third on the project, I will agree that Delrina FAX was a very good example of the need for all team members to fully understand the market, the customers and the role of the product.  While a lot of what Saeed said is true this was rectified when a mac focused product marketing effort was brought in.  In general product marketing was brought in very late however the team working on the project early on (don and myself) understood and lived up to what people especially folks with fancy MBAs in the 2000s call customer-centricity.  This buzz word is used a lot more in the 2000s but we lived it in the early 90s without knowing it and it was the prime reason for the success of the project. On the other hand I would now argue that Winfax was more product focused. Delrina paid attention to customers but did not have a customer-centric focus.</p><p>Delrina Fax was not a port of the Windows app, it was developed for the Apple zealots.  Features, manuals, demos, ads, pretty much all of the product was tailored for the Mac audience which was large in the &#8220;graphics/publishing ghetto&#8221; and an audience that had a large portion of female users.  Our demo was to fax a famous painting (at least I think as I am no art expert) of a young girl in her Sunday dress in a nice summer scene in full grayscale that appealed to graphics folks and to people of the fairer sex.  We compared it to the output from Winfax and our mac competitors and said which painting would you buy. Do you want to fax your work and have it look like Delrina-fax output or the other software.  Worked well with our audience.  Our other test was a picture of a Mariah carey showing some cleavage which would have worked better than a painting if our audience was mainly in prison.</p><p>I would argue that customer-centricity is what is lost in the PC software of the 2000s whether out of Redmond or Cupertino and is better illustrated by websites such as Facebook, Myspace or Youtube.  One only has to look at Vista and office 2007 to see the lack of customer-centricity.</p><p>Delrina Fax also is an example of a project that was not driven by marketing.  Delrina Fax was a success and it was not driven by marketing who are supposed to be the only folks who understand the market. Saeed shows that in some cases marketing can be a detriment. Marketing folks need to understand the benefits of educating the full team.</p><p>The Mac product was a Skunkworks project and like any project, everyone will have a perspective and a memory of a project, however one thing I will agree with Steve Johnson on and I am sure all will agree, we could not have made this up.  The other take home is everyone on a project needs to know the customer, the market and the role of the product.</p><p>Michael</p> ]]></content:encoded> </item> <item><title>By: Don Agro</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-2578</link> <dc:creator>Don Agro</dc:creator> <pubDate>Wed, 10 Oct 2007 13:22:42 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-2578</guid> <description>As the lead developer on the Delrina Mac Fax project this exchange brings back a flood of memories - most of them good. Saeed and David both remember the same events from slightly differrent perspectives as do I. I have worked at several companies since that time where the Mac culture was secondary to the Windows one and it is no easy feat to accomodate both in a single corporate entity - perhaps this is why so few Windows to Mac ports have been successful.I do know that by the time we got to market - Delrina Fax Pro was a Mac product with the look and feel of a Mac product. The fact that there were bumps and crashes along the way in no way diminishes the hard work or the sense of satisfaction that we all shared.</description> <content:encoded><![CDATA[<p>As the lead developer on the Delrina Mac Fax project this exchange brings back a flood of memories &#8211; most of them good. Saeed and David both remember the same events from slightly differrent perspectives as do I. I have worked at several companies since that time where the Mac culture was secondary to the Windows one and it is no easy feat to accomodate both in a single corporate entity &#8211; perhaps this is why so few Windows to Mac ports have been successful.</p><p>I do know that by the time we got to market &#8211; Delrina Fax Pro was a Mac product with the look and feel of a Mac product. The fact that there were bumps and crashes along the way in no way diminishes the hard work or the sense of satisfaction that we all shared.</p> ]]></content:encoded> </item> <item><title>By: saeed</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-2579</link> <dc:creator>saeed</dc:creator> <pubDate>Tue, 09 Oct 2007 03:08:09 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-2579</guid> <description>David,Thanks for the detailed comment. I’ll reply in kind. :-)Clearly you had quite an emotional stake in Delrina. I&#039;m sure it was a wild ride for those at Delrina, both the ups, and the downs, given the impact of Win95, the layoffs and lawsuits that occurred there in the mid 1990s.To correct one of your points...my tenure at Delrina was not &quot;long before Delrina Fax Pro actually shipped.&quot;  Given that I know precisely when I left and that I completed the documentation project and was there when the product went RTM, it could hardly be called &quot;long before&quot; the product shipped. :-)Thanks for giving me credit for the docs. There were people internal to Delrina who reviewed it certainly, (Vicki who posted a comment was one of them) so it was not 100% a solo effort, but it was my primary deliverable and focus in my time there. I also wrote the balloon help, did a UI review and provided suggestions to improve the usability. An axiom from my tech writing days: If it&#039;s difficult to document, it&#039;s difficult to use.Also, thanks for verifying the fact that at the time, there was little if any Macintosh domain knowledge in the company. Others as well, not simply the PM, had decided that WinFax Mac was to be the original product name. The &quot;wiser heads&quot; you mention were the beta customers who gave negative feedback on the name and thus prompted the search for another name. This despite protestations from those few inside the company who were actually Mac savvy, when WinFax Mac was originally proposed.In those days, for any company to have to wait for beta testers to tell them that Win-anything Mac was not a suitable name for a product, indicates a clear gap in basic domain understanding, which was the whole point of the blog posting.Bringing in &quot;domain knowledge&quot; after the fact would be the correct thing to do, and as you state, that&#039;s what Delrina did. Had that knowledge been there earlier, who knows what decisions would have been made. The original plan had been to create an entire product line for the Macintosh, not simply a single fax product. What happened to that vision? It never materialized.In fact, after Fax Pro was released, Delrina invested in what they knew best -- Windows software. They released WinComm as a standalone product in 1994, WinFax Scanner in 1994, Cyberjack (a Web browser, ftp client and Usenet reader) for Win95 in 1995, and a full communications suite (CommSuite) for Windows, also in late 1995. This suite included TalkWorks, a Windows product based on technology Delrina acquired earlier.There were no other Macintosh communications products released by Delrina in that time. I wonder why, given the &quot;exponential growth of Delrina’s Mac team&quot; during that period.BTW, WRT the product and awards, I never made any aspersions against the product itself if you read what I wrote. I worked closely with the development team and Don and Mike certainly knew what they were doing.In fact, those who were closest to the actual product, myself included, knew that it had  some functional superiority to other products. The grey scale sample image in the original manual was taken from one of my own photographs. But functionality and awards don&#039;t always win markets.In the end, the question comes down to business success. Was the product ultimately financially successful? If it was, and I don&#039;t have data one way or another, it&#039;s interesting that Symantec wasn&#039;t interested. Also, why didn&#039;t Delrina release other Macintosh communication products? Instead they focused on the core Windows business, and then dabbled in screen savers (Dilbert, Bill &amp; Opus), and electronic scrapbook software (Echo Lake).Regardless, thanks for reading the blog, and posting the comment. Constructive comments and clarifications are always welcome. And after 14 years, which in technology is like a few generations in human terms, there will always be several sides to each story.Saeed</description> <content:encoded><![CDATA[<p>David,</p><p>Thanks for the detailed comment. I’ll reply in kind. <img
src="http://onproductmanagement.net/wp-includes/images/smilies/icon_smile.gif?513254" alt=':-)' class='wp-smiley' /></p><p>Clearly you had quite an emotional stake in Delrina. I&#8217;m sure it was a wild ride for those at Delrina, both the ups, and the downs, given the impact of Win95, the layoffs and lawsuits that occurred there in the mid 1990s.</p><p>To correct one of your points&#8230;my tenure at Delrina was not &#8220;long before Delrina Fax Pro actually shipped.&#8221;  Given that I know precisely when I left and that I completed the documentation project and was there when the product went RTM, it could hardly be called &#8220;long before&#8221; the product shipped. <img
src="http://onproductmanagement.net/wp-includes/images/smilies/icon_smile.gif?513254" alt=':-)' class='wp-smiley' /></p><p>Thanks for giving me credit for the docs. There were people internal to Delrina who reviewed it certainly, (Vicki who posted a comment was one of them) so it was not 100% a solo effort, but it was my primary deliverable and focus in my time there. I also wrote the balloon help, did a UI review and provided suggestions to improve the usability. An axiom from my tech writing days: If it&#8217;s difficult to document, it&#8217;s difficult to use.</p><p>Also, thanks for verifying the fact that at the time, there was little if any Macintosh domain knowledge in the company. Others as well, not simply the PM, had decided that WinFax Mac was to be the original product name. The &#8220;wiser heads&#8221; you mention were the beta customers who gave negative feedback on the name and thus prompted the search for another name. This despite protestations from those few inside the company who were actually Mac savvy, when WinFax Mac was originally proposed.</p><p>In those days, for any company to have to wait for beta testers to tell them that Win-anything Mac was not a suitable name for a product, indicates a clear gap in basic domain understanding, which was the whole point of the blog posting.</p><p>Bringing in &#8220;domain knowledge&#8221; after the fact would be the correct thing to do, and as you state, that&#8217;s what Delrina did. Had that knowledge been there earlier, who knows what decisions would have been made. The original plan had been to create an entire product line for the Macintosh, not simply a single fax product. What happened to that vision? It never materialized.</p><p>In fact, after Fax Pro was released, Delrina invested in what they knew best &#8212; Windows software. They released WinComm as a standalone product in 1994, WinFax Scanner in 1994, Cyberjack (a Web browser, ftp client and Usenet reader) for Win95 in 1995, and a full communications suite (CommSuite) for Windows, also in late 1995. This suite included TalkWorks, a Windows product based on technology Delrina acquired earlier.</p><p>There were no other Macintosh communications products released by Delrina in that time. I wonder why, given the &#8220;exponential growth of Delrina’s Mac team&#8221; during that period.</p><p>BTW, WRT the product and awards, I never made any aspersions against the product itself if you read what I wrote. I worked closely with the development team and Don and Mike certainly knew what they were doing.</p><p>In fact, those who were closest to the actual product, myself included, knew that it had  some functional superiority to other products. The grey scale sample image in the original manual was taken from one of my own photographs. But functionality and awards don&#8217;t always win markets.</p><p>In the end, the question comes down to business success. Was the product ultimately financially successful? If it was, and I don&#8217;t have data one way or another, it&#8217;s interesting that Symantec wasn&#8217;t interested. Also, why didn&#8217;t Delrina release other Macintosh communication products? Instead they focused on the core Windows business, and then dabbled in screen savers (Dilbert, Bill &amp; Opus), and electronic scrapbook software (Echo Lake).</p><p>Regardless, thanks for reading the blog, and posting the comment. Constructive comments and clarifications are always welcome. And after 14 years, which in technology is like a few generations in human terms, there will always be several sides to each story.</p><p>Saeed</p> ]]></content:encoded> </item> <item><title>By: David S. Jones</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-2580</link> <dc:creator>David S. Jones</dc:creator> <pubDate>Mon, 08 Oct 2007 22:56:47 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-2580</guid> <description>Unfortunately, this anecdotal account of Delrina’s early 1990’s Mac fax product is based on the author’s short contractual stay that occurred long before Delrina Fax Pro actually shipped, and arrives at completely inaccurate conclusions about Delrina’s marketing savvy. Had the author remained at Delrina, he would have witnessed the arrival of experienced Mac &quot;domain knowledge&quot; and the exponential growth of Delrina&#039;s Mac team in the areas of development, product management, and tech support. He might have shared in the satisfaction of Delrina Fax Pro earning winning product reviews and endorsements from top Mac luminaries including MacWorld columnist David Pogue, former Apple USA president and Mac celebrity Jean-Louis Gassée, and other Mac influencers. He also would have been pleased to see Delrina Fax Pro stocked in all mass retailers and Mac mail-order houses, and selling well to Mac users right up to the moment when Symantec bought Delrina.Delrina Fax Pro was indeed a late entrant into a Mac fax market that was dominated by the DoveFax and Global Village products. However, those bundled hardware/software products suffered two serious weaknesses: their bundled fax software was notoriously unreliable and delivered mediocre quality fax output. In contrast, Delrina Fax Pro was rock-solid reliable and was the only fax software capable of sending ultra high quality &quot;grayscale&quot; faxes—a key feature immediately popular with the Mac graphics crowd. Discontented DoveFax and Global Village users seeking a reliable fax software alternative also discovered that Delrina&#039;s Mac tech support was fast, informed, and friendly. And I must commend the author for creating the top-quality documentation that got a &quot;4 out of 5&quot; for Delrina Fax Pro in that MacUser magazine review.Claiming that Delrina lacked &quot;real domain knowledge or true understanding of the market they were entering&quot; makes for an entertaining case study conclusion almost a dozen years later—but it&#039;s not true. Yes, a WinFax product manager wanted to name the Mac product &quot;WinFax Mac,&quot; but wiser heads prevailed. Yes, Delrina had earlier hoped for OEM bundles with Mac faxmodem makers, but Delrina&#039;s leadership was fully aware that the OEM window of opportunity had closed. A better conclusion grants Delrina some credit for intelligence, and makes the case that Delrina accurately assessed the Mac market at that time.Sales were slowing and margins dropping on faxmodems with bundled &quot;lite&quot; fax software in both the Windows and Mac markets. Conversely, there seemed to be a real market opportunity for feature-rich, high-margin standalone fax software. The success of WinFax Pro proved this proposition in the Windows market, and Delrina reasoned that the Mac market was also ripe for a Mac equivalent to WinFax Pro. Delrina never &quot;misunderstood the dynamics of the Macintosh fax market.&quot; Delrina Fax Pro was an calculated attempt to enter a new market category dominated by no single player, get in quickly with a feature-rich product that defines the category, influence the key Mac influencers and win decisive reviews to win mindshare dominance, ensure that the product was advertised and available in every single Mac sales channel, and employ every trick in the book to promote sell-through.Unfortunately, the terms of the Symantec acquisition didn&#039;t allow Delrina to continue this foray into the Mac fax software market. In fact, the Symantec acquisition of Delrina was the high-water mark of the entire PC fax market, eclipsed shortly afterward by the popularity of Internet-based email. The author says, &quot;Even back then, early in my career, I could see the dark days ahead if I stayed at Delrina.&quot; Too bad he didn’t stick around, because all of us at Delrina enjoyed a wild ride while it lasted—and had a heck of a good time!</description> <content:encoded><![CDATA[<p>Unfortunately, this anecdotal account of Delrina’s early 1990’s Mac fax product is based on the author’s short contractual stay that occurred long before Delrina Fax Pro actually shipped, and arrives at completely inaccurate conclusions about Delrina’s marketing savvy. Had the author remained at Delrina, he would have witnessed the arrival of experienced Mac &#8220;domain knowledge&#8221; and the exponential growth of Delrina&#8217;s Mac team in the areas of development, product management, and tech support. He might have shared in the satisfaction of Delrina Fax Pro earning winning product reviews and endorsements from top Mac luminaries including MacWorld columnist David Pogue, former Apple USA president and Mac celebrity Jean-Louis Gassée, and other Mac influencers. He also would have been pleased to see Delrina Fax Pro stocked in all mass retailers and Mac mail-order houses, and selling well to Mac users right up to the moment when Symantec bought Delrina.</p><p>Delrina Fax Pro was indeed a late entrant into a Mac fax market that was dominated by the DoveFax and Global Village products. However, those bundled hardware/software products suffered two serious weaknesses: their bundled fax software was notoriously unreliable and delivered mediocre quality fax output. In contrast, Delrina Fax Pro was rock-solid reliable and was the only fax software capable of sending ultra high quality &#8220;grayscale&#8221; faxes—a key feature immediately popular with the Mac graphics crowd. Discontented DoveFax and Global Village users seeking a reliable fax software alternative also discovered that Delrina&#8217;s Mac tech support was fast, informed, and friendly. And I must commend the author for creating the top-quality documentation that got a &#8220;4 out of 5&#8243; for Delrina Fax Pro in that MacUser magazine review.</p><p>Claiming that Delrina lacked &#8220;real domain knowledge or true understanding of the market they were entering&#8221; makes for an entertaining case study conclusion almost a dozen years later—but it&#8217;s not true. Yes, a WinFax product manager wanted to name the Mac product &#8220;WinFax Mac,&#8221; but wiser heads prevailed. Yes, Delrina had earlier hoped for OEM bundles with Mac faxmodem makers, but Delrina&#8217;s leadership was fully aware that the OEM window of opportunity had closed. A better conclusion grants Delrina some credit for intelligence, and makes the case that Delrina accurately assessed the Mac market at that time.</p><p>Sales were slowing and margins dropping on faxmodems with bundled &#8220;lite&#8221; fax software in both the Windows and Mac markets. Conversely, there seemed to be a real market opportunity for feature-rich, high-margin standalone fax software. The success of WinFax Pro proved this proposition in the Windows market, and Delrina reasoned that the Mac market was also ripe for a Mac equivalent to WinFax Pro. Delrina never &#8220;misunderstood the dynamics of the Macintosh fax market.&#8221; Delrina Fax Pro was an calculated attempt to enter a new market category dominated by no single player, get in quickly with a feature-rich product that defines the category, influence the key Mac influencers and win decisive reviews to win mindshare dominance, ensure that the product was advertised and available in every single Mac sales channel, and employ every trick in the book to promote sell-through.</p><p>Unfortunately, the terms of the Symantec acquisition didn&#8217;t allow Delrina to continue this foray into the Mac fax software market. In fact, the Symantec acquisition of Delrina was the high-water mark of the entire PC fax market, eclipsed shortly afterward by the popularity of Internet-based email. The author says, &#8220;Even back then, early in my career, I could see the dark days ahead if I stayed at Delrina.&#8221; Too bad he didn’t stick around, because all of us at Delrina enjoyed a wild ride while it lasted—and had a heck of a good time!</p> ]]></content:encoded> </item> <item><title>By: Allen Lau</title><link>http://onproductmanagement.net/2007/10/01/do-product-managers-need-domain-knowledge/comment-page-1/#comment-2575</link> <dc:creator>Allen Lau</dc:creator> <pubDate>Sat, 06 Oct 2007 05:20:21 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/10/01/do-product-managers-need-domain-knowledge/#comment-2575</guid> <description>Very interesting post.  I was one of the Delrina developers on the WinFax side at that time.  Although I don&#039;t know much about the Mac side of things at that time, I did heard about a few funny things about Mac product.  WinFax Mac was one of those :-)</description> <content:encoded><![CDATA[<p>Very interesting post.  I was one of the Delrina developers on the WinFax side at that time.  Although I don&#8217;t know much about the Mac side of things at that time, I did heard about a few funny things about Mac product.  WinFax Mac was one of those <img
src="http://onproductmanagement.net/wp-includes/images/smilies/icon_smile.gif?513254" alt=':-)' class='wp-smiley' /></p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User is logged in)
Database Caching using disk: basic
Object Caching 489/490 objects using disk: basic

Served from: onproductmanagement.net @ 2012-05-22 22:36:13 -->
