<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Product Docs on Xiangtao's log</title><link>https://www.xiaoxiangtao.cn/tags/product-docs/</link><description>Recent content in Product Docs on Xiangtao's log</description><generator>Hugo</generator><language>en-US</language><managingEditor>15989119660@163.com (Xiangtao XIAO)</managingEditor><webMaster>15989119660@163.com (Xiangtao XIAO)</webMaster><lastBuildDate>Tue, 30 Mar 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.xiaoxiangtao.cn/tags/product-docs/feed.xml" rel="self" type="application/rss+xml"/><item><title>Notes on Requirement Analysis and Management</title><link>https://www.xiaoxiangtao.cn/posts/learning-notes-on-product-requirement-analysis-and-management/</link><pubDate>Tue, 30 Mar 2021 00:00:00 +0000</pubDate><author>15989119660@163.com (Xiangtao XIAO)</author><guid isPermaLink="false">https://www.xiaoxiangtao.cn/posts/learning-notes-on-product-requirement-analysis-and-management/</guid><description>&lt;p&gt;When you&amp;rsquo;re digging into what users actually need, it&amp;rsquo;s rarely something concrete and explicit. There&amp;rsquo;s the old Ford line — &amp;ldquo;if I&amp;rsquo;d asked people what they wanted, they&amp;rsquo;d have said a faster horse&amp;rdquo; — but once you get to actually building the product, you still have to land on something concrete: specific features that satisfy the underlying need. So what I mean by &amp;ldquo;requirement analysis and management&amp;rdquo; here is the whole chain: start from a surface-level ask, dig into the real need underneath it, evaluate it, land on a specific solution, and hand that off to engineers and designers to turn into an actual product. B2B and B2C products differ quite a bit in how this plays out.&lt;/p&gt;</description></item><item><title>Notes on Doing Competitive Analysis</title><link>https://www.xiaoxiangtao.cn/posts/learning-notes-of-competitive-product-analysis/</link><pubDate>Sun, 28 Mar 2021 00:00:00 +0000</pubDate><author>15989119660@163.com (Xiangtao XIAO)</author><guid isPermaLink="false">https://www.xiaoxiangtao.cn/posts/learning-notes-of-competitive-product-analysis/</guid><description>&lt;h2 id="1-why-bother-with-competitive-analysis"&gt;1 Why Bother with Competitive Analysis&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;1. Better decisions.&lt;/strong&gt; Understanding competitors&amp;rsquo; products helps you position your own — and steer clear of the strongest players so you don&amp;rsquo;t wander into a red ocean. It lowers the risk of getting your bets wrong.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2. Learning from others.&lt;/strong&gt; Studying what makes a competitor&amp;rsquo;s product strong lets you build more deliberately: take what works, absorb their strengths, and use it to sharpen your own edge.&lt;/p&gt;</description></item></channel></rss>