<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Strategy on Konstantin Zavarov</title><link>https://zavarov.com/en/blog/strategy/</link><description>Recent content in Strategy on Konstantin Zavarov</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2026, Konstantin Zavarov.</copyright><lastBuildDate>Mon, 16 Mar 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://zavarov.com/en/blog/strategy/index.xml" rel="self" type="application/rss+xml"/><item><title>Product Strategy ≠ Template</title><link>https://zavarov.com/en/product-strategy/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0300</pubDate><guid>https://zavarov.com/en/product-strategy/</guid><description>&lt;p>The goal of strategy is to move from &amp;laquo;build whatever anyone asks for&amp;raquo; to a deliberate position aimed at creating a better future for both users and the business.&lt;/p>
&lt;p>As much as we&amp;rsquo;d like one to exist, there&amp;rsquo;s no universal product strategy template — honestly, no template at all. The format depends on company and team maturity, team structure, business model, business strategy, and a whole host of other factors.&lt;/p></description></item><item><title>ICE, RICE, DRICE Prioritization Frameworks</title><link>https://zavarov.com/en/drice/</link><pubDate>Thu, 24 Oct 2024 15:17:01 +0300</pubDate><guid>https://zavarov.com/en/drice/</guid><description>&lt;p>Ein, zwei, drei… There are endless ways to prioritize tasks. Every product I&amp;rsquo;ve ever worked on had its own unique ranking method, each with its own quirks. For a quick tour of all the approaches used at major companies, check out &lt;a href="https://www.youtube.com/watch?v=BpXVJByOh8g&amp;amp;t=2421s" target="_blank" rel="noopener noreferrer">Misha Karpov&amp;rsquo;s talk&lt;/a> at Yandex&amp;rsquo;s product meetup [1]. As for me, my personal favorite prioritization methods are the energy-based one — where priorities are chosen based on how you&amp;rsquo;re feeling that day — and the intuitive one, where you simply follow your gut and your heart. Too bad the team rarely agrees to go along with either.&lt;/p></description></item><item><title>The Evolution of Goal-Setting Frameworks: From OKR to NCT</title><link>https://zavarov.com/en/nct/</link><pubDate>Sat, 24 Aug 2024 15:17:01 +0300</pubDate><guid>https://zavarov.com/en/nct/</guid><description>&lt;p>I came across an interesting approach to goal-setting — NCT (Narratives, Commitments, Tasks) by Ravi Mehta [1]. What makes it compelling is that it positions itself as an alternative to OKR and could be genuinely useful for many product teams. Before diving into NCT, let&amp;rsquo;s take a quick look at the history of goal-setting frameworks.&lt;/p>
&lt;p>In 1954, Peter Drucker introduced the concept of MBO (Management by Objectives) in his book &lt;em>The Practice of Management&lt;/em> [2]. The core idea is to set goals at the company level and cascade them down to individuals at each level. Many services within Yandex, for example, still use a similar approach today. There&amp;rsquo;s even a dedicated internal tool for cascading goals called &amp;laquo;Golzyatnitsa.&amp;raquo;&lt;/p></description></item><item><title>The Growth Dilemma of Online Course Economics</title><link>https://zavarov.com/en/edtech/</link><pubDate>Mon, 24 Jun 2024 15:17:01 +0300</pubDate><guid>https://zavarov.com/en/edtech/</guid><description>&lt;p>Comparing the top edTech companies in the Russian internet market, I noticed an interesting scaling problem baked into their course economics — one they all seem to live with. I&amp;rsquo;m not talking about product-driven edTech platforms like Lingualeo, but companies that create educational courses for upskilling or career transitions.&lt;/p>
&lt;h2 id="product-edtech-theorem-1">Product EdTech Theorem #1&lt;a class="heading-anchor" href="#product-edtech-theorem-1" aria-label="Copy link to this section">&lt;svg viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round">&lt;path d="M6.5 9.5a3.5 3.5 0 0 0 5 0l2-2a3.5 3.5 0 0 0-5-5l-1 1"/>&lt;path d="M9.5 6.5a3.5 3.5 0 0 0-5 0l-2 2a3.5 3.5 0 0 0 5 5l1-1"/>&lt;/svg>&lt;/a>&lt;/h2>
&lt;p>&lt;q>The absence of deadlines in an educational course leads to ↑ Revenue and ↓ Completion Rate (COR). Conversely, having deadlines leads to ↓ Revenue and ↑ Completion Rate.&lt;/q>&lt;/p></description></item><item><title>ICE, RICE, DRICE Prioritization Framework Template</title><link>https://zavarov.com/en/template-rice/</link><pubDate>Fri, 01 Jul 2022 12:00:00 +0300</pubDate><guid>https://zavarov.com/en/template-rice/</guid><description>&lt;p>A Google Sheets template for prioritizing product initiatives using three frameworks: ICE, RICE, and DRICE. For a deeper dive into the methods, check out the article &lt;a href="https://zavarov.com/drice/">«ICE, RICE, DRICE Prioritization Methods»&lt;/a>.&lt;/p>
&lt;p>&lt;a class="button" target="_blank" href="https://docs.google.com/spreadsheets/d/1Dm2fcXwwIR70mm2fGExPU0FbYvs_dknu8W8vclFK9yI/edit#gid=0">Download template&lt;/a>&lt;/p>
&lt;h2 id="whats-inside">What&amp;rsquo;s inside&lt;a class="heading-anchor" href="#whats-inside" aria-label="Copy link to this section">&lt;svg viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round">&lt;path d="M6.5 9.5a3.5 3.5 0 0 0 5 0l2-2a3.5 3.5 0 0 0-5-5l-1 1"/>&lt;path d="M9.5 6.5a3.5 3.5 0 0 0-5 0l-2 2a3.5 3.5 0 0 0 5 5l1-1"/>&lt;/svg>&lt;/a>&lt;/h2>
&lt;p>&lt;strong>ICE&lt;/strong> — the simplest prioritization method. Each initiative is scored on three factors from 0 to 10:&lt;/p></description></item></channel></rss>