<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Justin Schaeffer on Medium]]></title>
        <description><![CDATA[Stories by Justin Schaeffer on Medium]]></description>
        <link>https://medium.com/@justinschaeffer?source=rss-bc902288eb0d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Wp6ENxXp7O66YHq_wjYQtw.jpeg</url>
            <title>Stories by Justin Schaeffer on Medium</title>
            <link>https://medium.com/@justinschaeffer?source=rss-bc902288eb0d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:26:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justinschaeffer/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I Built an AI System That Reads 20+ PM Newsletters For Me (And Why Most “Staying Current”…]]></title>
            <link>https://medium.com/@justinschaeffer/how-i-built-an-ai-system-that-reads-20-pm-newsletters-for-me-and-why-most-staying-current-61795f3a51ed?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/61795f3a51ed</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 19:37:31 GMT</pubDate>
            <atom:updated>2026-01-19T19:37:31.744Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I Built an AI System That Reads 20+ PM Newsletters For Me (And Why Most “Staying Current” Advice Doesn’t Work)</h3><p>A 90% time reduction, 7 specialized AI coaches, and a systematic approach to closing competency gaps</p><p>—</p><p><strong>The problem with staying current as a PM</strong>: Everyone tells you to “read newsletters and listen to podcasts,” but nobody tells you <strong>which ones</strong>, <strong>how to filter signal from noise</strong>, or <strong>how to actually retain and apply what you learn</strong>.</p><p>I was subscribed to 8 newsletters and 8 podcasts. Some weeks I’d spend 2+ hours reading everything. Other weeks, nothing. Even when I did read, I wasn’t retaining much. No system, no tracking, no way to prove I was actually getting better.</p><p>Then I realized: <strong>I was trying to solve a curation problem with willpower.</strong> That doesn’t scale.</p><p>So I built an AI-powered system that handles the curation for me. Here’s what happened.</p><p>—</p><h3>Part 1: Diagnosing the Real Problem (It’s Not What You Think)</h3><p>Before building any system, I needed to understand what I was actually trying to solve.</p><p><strong>The 9-Signal Competency Framework</strong></p><p>I started by doing a rigorous self-assessment using the <strong>9-Signal PM Competency Framework</strong> (created by Jackie Bavaro and Gayle McDowell, the folks behind “Cracking the PM Interview”).</p><p>The framework scores you 0–2 across 9 competencies:<br>- 0 = Not demonstrated<br>- 1 = Emerging (some experience, but gaps)<br>- 2 = Mastered (strong track record, can teach others)</p><p><strong>The 9 competencies</strong>:<br>1. Product Development<br>2. Data Science &amp; Analytics<br>3. Influence &amp; Presence<br>4. Technology Strategy<br>5. Business Fundamentals<br>6. Finance &amp; Funding<br>7. Leadership &amp; Team Building<br>8. Information Management<br>9. Innovation &amp; Digital Trends</p><p><strong>Total score interpretation</strong>:<br>- 0–6: IC level (L3-L4)<br>- 7–12: Senior/Lead level (L5-L6)<br>- 13–18: Executive level (L7-L8)</p><p>My Results: 11/18 (Promotable Range)</p><p><strong>My strengths (s</strong>cored 2):<br>- <strong>Product Development</strong>: Led iterative shipping at Bossa Nova (grocery inventory robotics/AI), achieved 4+ scan rate from 63% → 79% in 11 weeks<br>- <strong>Data Science &amp; Analytics:</strong> Built comprehensive KPI trees, ran cohort analyses, tracked leading/lagging indicators</p><p><strong>My gaps</strong> (scored 1):<br>- Business Fundamentals<br>- Finance &amp; Funding<br>- Technology Strategy<br>- Influence &amp; Presence<br>- Leadership &amp; Team Building<br>- Information Management<br>- Innovation &amp; Digital Trends</p><p><strong>The insight</strong>: I wasn’t just “generally trying to improve.” I had 7 specific competency gaps that were holding me back from L6-L7 roles.</p><p>This changed everything.</p><p>—</p><h3>Part 2: Why Traditional “Staying Current” Advice Fails</h3><p>Once I knew my gaps, I looked at what I was actually consuming:</p><p><strong>My newsletter subscriptions</strong>:<br>- Lenny’s Newsletter (product strategy, growth)<br>- Reforge (product-led growth, retention)<br>- Product Talk (continuous discovery)<br>- Substack PM newsletters (3–4 random ones)<br>- TLDR Product, TLDR AI (tech news)<br>- Mind the Product, ProductPlan newsletters</p><p><strong>My podcast subscriptions</strong>:<br>- Lenny’s Podcast<br>- Product Therapy (SVPG)<br>- The Product Podcast<br>- The CPO Club Podcast<br>- The Product Experience<br>- Masters of Scale<br>- How I Built This<br>- Product Talk</p><p><strong>The problem</strong>: Most of this content focused on Product Development and Innovation — my strongest areas. I was consuming content that reinforced what I already knew while ignoring my actual gaps.</p><p>Even worse:<br>- No filtering: I was reading everything or nothing, no in-between<br>- No application: I’d read something, think “that’s interesting,” and never use it<br>- No tracking: I couldn’t prove I was getting better at anything<br>- No artifacts: Nothing to show in interviews or portfolios</p><p>I needed a system that:<br>1. ✅ Automatically filtered content by my competency gaps<br>2. ✅ Reduced time investment (2+ hours → manageable)<br>3. ✅ Tracked progress systematically<br>4. ✅ Generated portfolio artifacts<br>5. ✅ Balanced gap-closing with strength-maintaining</p><p>— -</p><h3>Part 3: Building the System (Three Attempts, One Success)</h3><h4>Attempt 1: “I’ll Just Read More Strategically” (Failed)</h4><p>The plan: Manually scan newsletters, only read ones relevant to my gaps.</p><p>What happened: Lasted 2 weeks. Too much willpower required. Fell back to reading randomly or not at all.</p><p>Lesson: Behavior change without system change doesn’t work.</p><p>—</p><h4>Attempt 2: Notion Database + Manual Curation (Failed)</h4><p>The plan Forward newsletters to Notion database, manually review weekly.</p><p>What happened:<br>- Zapier automated the forwarding (worked great!)<br>- But full newsletter text was 40,000+ words per week<br>- Took 30+ minutes just to scan through everything<br>- AI tools couldn’t process the database (too much data)</p><p>Lesson: Automation without data reduction doesn’t solve the problem.</p><p>—</p><h4>Attempt 3: AI Summarization + Weekly Pages (Success!)</h4><p>The breakthrough: Use AI to summarize newsletters at ingestion, not at analysis.</p><p>The architecture:</p><p>INPUT LAYER (Automated)<br>├─ Newsletters arrive at Gmail<br>├─ Zapier detects label “PM Newsletters”<br>├─ AI summarizes (2000 words → 300 words)<br>├─ Appends to Notion weekly page<br>└─ Result: 85–90% data reduction</p><p>ANALYSIS LAYER (15–20 min/week)<br>├─ Part 1: Web search digest (5 min)<br>│ └─ AI searches trends in my gap areas<br>├─ Part 2: Newsletter analysis (5 min)<br>│ └─ AI reads summaries, filters by priorities<br>├─ Part 3: Podcast curation (5 min)<br>│ └─ AI recommends 2–3 best episodes<br>└─ Part 4: Learning Log (5 min)<br> └─ Document insights, map to competencies</p><p>OUTPUT LAYER (Portfolio &amp; Growth)<br>├─ Weekly: Learning Log entry<br>├─ Monthly: Deep dive + artifact<br>└─ Quarterly: Competency reassessment</p><p>This worked. Here’s exactly how.</p><p>—</p><h4>Part 4: The Technical Implementation (Copy This If You Want)</h4><p><strong>Step 1: Automated Newsletter Collection with AI Summarization</strong></p><p>Tools: Gmail (free) + Zapier (free tier: 100 tasks/month) + Notion (free)</p><p>Setup (15 minutes):</p><p>1. Gmail: Create label “PM Newsletters”<br>2. Gmail filters: Auto-apply label to your newsletter sources<br>3. Zapier Zap(3 steps):<br> — Trigger: New email with label “PM Newsletters”<br> — Action 1: AI by Zapier — Generate Text<br> — Action 2: Notion — Append Block to Page</p><p><strong>The critical part — AI Summarization Prompt</strong></p><blockquote>Summarize this product management newsletter in 200 words maximum.</blockquote><blockquote>Newsletter content: [Gmail Body Plain]</blockquote><blockquote>Focus on:<br>- Key frameworks or methodologies mentioned (name them specifically — e.g., “The Three Bets”, “Pyramid Principle”, “North Star Framework”)<br>- Case studies or real examples with company names (e.g., “How Stripe built…”, “Airbnb’s approach to…”)<br>- Strategic insights for product managers at L5-L7 level<br>- Actionable takeaways with specific next steps</blockquote><blockquote>Skip:<br>- Generic productivity advice<br>- Promotional content<br>- Basic PM 101 concepts<br>- Content without concrete examples</blockquote><blockquote>Format: Concise bullet points with specific names of frameworks, companies, and technologies.<br>```</blockquote><p><strong>Why this works</strong>:<br>- Explicit instruction to name frameworks = credibility and searchability<br>- Focus on L5-L7 level = filters out junior content<br>- “Skip basic PM 101” = prevents noise<br>- Result: 2000+ word newsletter → 300-word summary with high signal</p><p><strong>Example output </strong>(real from my system):</p><blockquote>## Gemini Personal Intelligence 🤖, OpenAI + Cerebras $10B 💻</blockquote><blockquote>**From:** TLDR AI<br>**Date**: Thu, 15 Jan 2026</blockquote><blockquote>Summary:<br>- Gemini’s Personal Intelligence: Beta feature connecting Google apps<br>- Character.ai Improvements: Techniques that doubled inference speed through GPU optimization<br>- Universal Commerce Protocol (UCP): Co-developed by Shopify and Google to streamline AI agent transactions<br>- Emerging ‘Vibe Graphs’ Concept: Trillion-dollar market focusing on organizational sentiment</blockquote><blockquote>Resources:<br>1. Gemini Personal Intelligence: <a href="https://blog.google/">https://blog.google/</a>...<br>2. UCP Announcement: <a href="https://shopify.engineering/UCP">https://shopify.engineering/UCP</a></blockquote><p><strong>Cost</strong>: Free tier handles 20–30 newsletters/week (each newsletter = 3 Zapier tasks: trigger + AI + append)</p><p><strong>Time saved</strong>: Reading 20 newsletters manually = 2+ hours. Reviewing 20 summaries = 10 minutes.</p><p>—</p><p><strong>Step 2: AI-Assisted Weekly Analysis (The Monday Workflow)</strong></p><p>Every Monday morning, I run three prompts with Claude (my “PM Coach”). Total time: 15 minutes.</p><p><strong>Prompt 1: Web Search Digest (5 min)</strong></p><p>I paste this prompt, and Claude searches current trends:</p><blockquote>Weekly staying-current digest customized for my development needs.</blockquote><blockquote>Use web search to research and analyze:</blockquote><blockquote>HIGH PRIORITY — CLOSE GAPS (60% of focus):<br>1. Business Fundamentals &amp; Finance<br> — Investment case frameworks (e.g., how Stripe/Amazon PMs build business cases)<br> — P&amp;L literacy for product managers<br> — Unit economics (CAC, LTV, payback period)<br> — Build vs. buy decisions with TCO analysis</blockquote><blockquote>2. Technology Strategy<br> — Strategy memo examples (e.g., Shreyas Doshi’s “Three Bets” framework)<br> — How companies set technical direction (e.g., Staff+ engineer decision-making)<br> — Examples of hard trade-offs and what NOT to build</blockquote><blockquote>3. Influence &amp; Executive Presence<br> — Pyramid Principle (Minto Method) applications<br> — Stakeholder management without authority<br> — BLUF (Bottom Line Up Front) communication</blockquote><blockquote>MAINTAIN STRENGTHS — DON’T FALL BEHIND (40% of focus):<br>4. Product Development Evolution<br> — Advanced methodologies (e.g., continuous discovery, dual-track agile)<br> — Emerging frameworks changing the field</blockquote><blockquote>5. Data Science &amp; Analytics Advances<br> — New metrics thinking (e.g., Time-to-Value replacing Activation Rate)<br> — Advanced experiment design<br> — Causal inference in product analytics</blockquote><blockquote>FORMAT:<br>- Top 2–3 insights for gap areas with specific framework names<br>- Top 1–2 insights for strength areas (only if cutting-edge)<br>- Name companies/PMs doing this well<br>- Link to sources</blockquote><blockquote>Filter out: Generic advice, PM 101, buzzwords without substance</blockquote><p><strong>Key design choice</strong>: I explicitly ask for framework names (Three Bets, Pyramid Principle, TCO Analysis) and company examples (Stripe, Amazon, Airbnb). This makes the insights concrete and verifiable.</p><p><strong>Real output example</strong> (from my first run):</p><blockquote>&gt; **Business Fundamentals**:<br>&gt; — Unit economics beyond PMF: Post-PMF products need ongoing unit economics views focusing on efficiency of growth, not just initial CAC/LTV. [Source: [Productify Substack](<a href="https://productify.substack.com/p/p-and-l-management-for-product-leads">https://productify.substack.com/p/p-and-l-management-for-product-leads</a>)]<br>&gt;<br>&gt; **Technology Strategy**:<br>&gt; — North Star + OKR shift: Industry moving from SMART goals to OKR frameworks. North Star Framework aligns teams on what matters. [Source: [25 Product Management Frameworks](<a href="https://www.saasfunnellab.com/essay/product-management-frameworks/">https://www.saasfunnellab.com/essay/product-management-frameworks/</a>)]<br>&gt;<br>&gt; **Influence &amp; Presence**:<br>&gt; — Influence without authority data: Organizations with strong executive presence outperform by 47% in leadership effectiveness and achieve 32% higher stakeholder trust. [Source: [Rework.com — Executive Presence Framework](<a href="https://resources.rework.com/libraries/organizational-competencies/executive-presence">https://resources.rework.com/libraries/organizational-competencies/executive-presence</a>)]</blockquote><p>See the difference? Not “be strategic” or “communicate better.” Specific frameworks with sources.</p><p>—</p><p><strong>Prompt 2: Newsletter Analysis (5 min)</strong></p><p>I copy my Notion weekly page and paste with this prompt:</p><blockquote>Analyze my weekly newsletter summaries from Week of [Date]:</blockquote><blockquote>[PASTE NOTION CONTENT]</blockquote><blockquote>ANALYZE with this prioritization:</blockquote><blockquote>PRIMARY (Close gaps — 60%):<br>- Business Fundamentals &amp; Finance<br>- Technology Strategy<br>- Influence &amp; Presence</blockquote><blockquote>MAINTAIN (Defend strengths — 40%):<br>- Product Development — flag HIGH-SIGNAL only (advanced techniques, field-changing practices)<br>- Data Analytics — flag HIGH-SIGNAL only (new approaches, not standard metrics I know)</blockquote><blockquote>PROVIDE:<br>1. Top 3 insights for gap areas (specific frameworks or techniques)<br>2. Top 1–2 insights for strength areas (only if genuinely advanced)<br>3. Which newsletters are worth reading fully and why<br>4. Patterns across multiple sources (e.g., “3 newsletters mentioned outcome-based roadmapping this week”)<br>5. What to skip and why</blockquote><blockquote>Be ruthless: Don’t surface basic content I likely already know. Focus on L6-L7 relevant insights.</blockquote><p>Why the 60/40 split matters: I can’t only focus on gaps. My strengths (Product Dev, Data Analytics) are my competitive advantage. If I ignore them, I’ll fall behind. But I don’t need basic content in those areas — only cutting-edge stuff.</p><p><strong>Real insight from Week 1:</strong></p><blockquote>&gt; **Product Development (Strength Maintenance)**:<br>&gt; — Time-to-Value (TTV) replacing Activation Rate: New benchmark is &lt;1 hour for B2B SaaS. Leading PMs track TTV by cohort and optimize onboarding specifically for it. This is an evolution beyond activation thinking.<br>&gt; — Application: In interviews, I can say: “Activation rate is table stakes, but L6+ PMs optimize for TTV and segment by cohort to find friction points.”</blockquote><p>This is gold. It shows I’m staying ahead in my strong areas, not resting on past performance.</p><p>—</p><p><strong>Prompt 3: Podcast Curation (5 min)</strong></p><blockquote>Analyze recent episodes (last 2 weeks) from my podcast subscriptions using web search.</blockquote><blockquote>My podcasts:<br>- Lenny’s Podcast<br>- Product Therapy (SVPG)<br>- The Product Podcast<br>- The CPO Club Podcast<br>- The Product Experience<br>- Masters of Scale<br>- How I Built This<br>- Product Talk</blockquote><blockquote>PRIORITIZE episodes for my competency gaps:<br>- Business Fundamentals &amp; Finance<br>- Technology Strategy<br>- Influence &amp; Presence<br>- Leadership &amp; Team Building</blockquote><blockquote>FOR EACH RELEVANT EPISODE:<br>1. Title and guest<br>2. Key frameworks/topics covered (name them specifically)<br>3. Why relevant to my gaps (be explicit)<br>4. Should I listen? (Yes/Maybe/Skip)<br>5. Key takeaways if I skip it</blockquote><blockquote>Recommend 2–3 episodes max that are highest value for my time.</blockquote><blockquote>Also note any frameworks mentioned repeatedly across podcasts.</blockquote><p><strong>Result</strong>: Instead of listening to 8 podcasts × 3 episodes/week (24 hours of content!), I listen to 2–3 carefully curated episodes (2–3 hours).</p><p>— -</p><h4>Part 4: Learning Log Update (5 min)</h4><p>I document insights in a structured format (Obsidian note):</p><blockquote>Week of Jan 13, 2026</blockquote><blockquote>🔥 Close Gaps</blockquote><blockquote>1. Investment Case Framework (Business Fundamentals)<br>- Source: Lenny’s Newsletter — “How Stripe PMs build investment cases”<br>- Key Takeaway: Always lead with payback period for CFO audience. Structure: Problem → Solution → ROI (payback + NPV) → Risks → The Ask<br>- Competency: Business Fundamentals (Gap — scored 1/2)<br>- Application: Could retroactively build investment case for Bossa Nova metrics initiative (est. $2M revenue impact from 63% → 79% 4+ scan rate, 6-month payback)<br>- Next Step: Create investment case artifact with Business &amp; Finance Coach agent</blockquote><blockquote>2. The Three Bets Framework (Technology Strategy)<br>- Source: Lenny’s Podcast Ep 247 — Shreyas Doshi on Strategy<br>- Key Takeaway: Strategy is saying “no” as much as “yes”. Three Bets forces prioritization. Non-goals section is most important part — explicitly list what you will NOT do.<br>- Competency: Technology Strategy (Gap — scored 1/2)<br>- Application: Could reframe Human Interest retirement plan selection project as strategy memo: Bet 1 (Ease of Use), Bet 2 (Trust Signals), Bet 3 (Speed to Decision). Non-goal: Comprehensive education features.<br>- Next Step: Write strategy memo using Strategy &amp; Vision Coach agent</blockquote><blockquote>💪 Maintain Strengths</blockquote><blockquote>1. Time-to-Value (TTV) Evolution (Product Development)<br>- Source: Lenny’s Newsletter — “2025 PLG Benchmarks”<br>- Key Takeaway: TTV is replacing activation rate as key metric. Benchmark: &lt;1 hour for B2B SaaS. Leading PMs track TTV by cohort and optimize onboarding for it.<br>- Competency: Product Development (Strength — scored 2/2)<br>- What’s New: TTV wasn’t emphasized at prior companies. This is next-level activation thinking.<br>- Application: Interview talking point — “Activation is table stakes, but L6+ PMs optimize for TTV by cohort”</blockquote><blockquote>📊 Competency Progress This Week<br>- Business Fundamentals: +1 framework (Investment Case), can now articulate ROI structure<br>- Technology Strategy: +1 framework (Three Bets), ready to practice with agent<br>- Product Development: Updated on PLG evolution, maintaining competitive edge</blockquote><blockquote>🎯 To Explore Deeper<br>- Investment Case framework → Monthly deep dive, create portfolio artifact<br>- Three Bets → Write strategy memo for past project</blockquote><blockquote>💡 Portfolio Artifact Ideas<br>1. Investment case for Bossa Nova metrics shift (show $2M impact, 6-month payback)<br>2. Strategy memo using Three Bets for Human Interest project<br>3. Rewrite existing case studies using Pyramid Principle/BLUF</blockquote><p><strong>Why this structure works</strong>:</p><p>✅ Specific frameworks named: Investment Case, Three Bets, TTV, Pyramid Principle<br>✅ Mapped to competencies: Every insight addresses a scored gap or strength<br>✅ Application to real work: Uses my actual projects (Bossa Nova, Human Interest)<br>✅ Next steps defined: Create artifacts with specialized agents<br>✅ Interview-ready: Can pull these examples directly into interview answers</p><p>— -</p><h4>Part 5: The Secret Weapon — Specialized AI Coaching Agents</h4><p>This is where the system gets really powerful.</p><p>The Learning Log identifies what I need to learn (frameworks) and how to apply them (portfolio artifacts). But I don’t have to figure this out alone.</p><p>I built <strong>7 specialized AI coaching agents</strong> — each an expert in a specific domain:</p><p>1. Data Analytics Coach<br>Focus: Metrics, KPI trees, experiment design, cohort analysis<br>When I use it: Stay sharp on analytics (my strength), learn advanced techniques<br>Example: “Help me design a KPI tree showing how product metrics connect to business outcomes”</p><p>2. AI Product Specialist<br>Focus: AI features, LLM products, prompt engineering, Day 2 ops<br>When I use it: Build AI product portfolio pieces, stay current on AI PM practices<br>Example: “Help me write a PRD for an AI-powered feature with WISER prompts”</p><p>3. Career Strategist<br>Focus: Interview prep, portfolio building, resume optimization, L5→L6 transitions<br>When I use it: Mock interviews, refining stories, building case studies<br>Example: “Run a mock L6 PM interview focused on business fundamentals”</p><p>4. Executive Communication Coach<br>Focus: Pyramid Principle, BLUF, executive presence, stakeholder management<br>When I use it: Eliminate hedges, practice signposting, polish presentations<br>Example: “Critique this memo using the Pyramid Principle — where am I burying the lead?”</p><p>5. Strategy &amp; Vision Coach<br>Focus: Strategy memos, The Three Bets, technology direction, hard trade-offs<br>When I use it: Write strategy artifacts, practice strategic thinking<br>Example: “Help me write a 2-page strategy memo using The Three Bets framework for [project]”</p><p>6. Business &amp; Finance Coach<br>Focus: P&amp;L literacy, unit economics, investment cases, build vs. buy, ROI<br>When I use it: Learn financial frameworks, create business case artifacts<br>Example: “Help me calculate unit economics and build an investment case for [past project]”</p><p>7. Product Launch &amp; GTM Expert<br>Focus: Go-to-market strategy, positioning, pricing, sales enablement<br>When I use it: Build launch plan artifacts, practice GTM thinking<br>Example: “Help me create a positioning statement and launch plan for [product]”</p><p>— -</p><p><strong>How the Agents Integrate with the Learning Log</strong></p><p>Here’s the workflow:</p><p><strong>Monday</strong>: Learning Log identifies “Three Bets framework” as worth learning<br><strong>Tuesday</strong>: Work session with **Strategy &amp; Vision Coach**<br>- Coach explains The Three Bets (what it is, why 3 specifically, why non-goals matter)<br>- We apply it to my Human Interest project retrospectively<br>- Coach critiques my draft, helps me refine<br>- O<strong>utput</strong>: 2-page strategy memo for portfolio</p><p><strong>Result</strong>: I didn’t just “learn about” The Three Bets. I have a portfolio artifact demonstrating mastery.</p><p><strong>The key insight</strong>: The agents turn passive learning (reading newsletters) into active skill-building (creating artifacts). This is the difference between “I learned about X” and “I can show you how I applied X.”</p><p>—</p><h4>Part 6: What I’d Do Differently (And What You Should Steal)</h4><p><strong>What Worked Exceptionally Well</strong></p><p>1. AI Summarization at Ingestion</p><p>Don’t try to have AI analyze full newsletters. Reduce the data first.</p><p>The math:<br>- 20 newsletters × 2000 words = 40,000 words/week<br>- 20 summaries × 300 words = 6,000 words/week<br>- <strong>85% reduction, preserves high-signal content</strong></p><p>This made the whole system viable. Without this, AI tools hit processing limits.</p><p><strong>2. Competency-Based Filtering</strong></p><p>Having 7 specific gaps changed everything. Instead of “help me be a better PM” (vague), I could say:</p><blockquote>“Filter for Business Fundamentals, Technology Strategy, and Influence &amp; Presence. Skip Product Development basics — I’m strong there, only show cutting-edge content.”</blockquote><p>Specificity = better AI curation.</p><p><strong>3. 60/40 Gap-to-Strength Balance</strong></p><p>I almost made the mistake of focusing 100% on gaps. That would have let my strengths atrophy.</p><p>The 60/40 split means:<br>- 60% of weekly insights address gaps (Business, Strategy, Influence)<br>- 40% maintain competitive advantages (Product Dev, Analytics)</p><p><strong>Example</strong>: Learning that Time-to-Value is replacing Activation Rate keeps me ahead in Product Development. If I’d ignored that because “I’m already strong there,” I’d fall behind.</p><p><strong>4. Artifact-Oriented Learning</strong></p><p>Every Learning Log entry has an “Application” field and “Next Step” field. This forces connection to real work and portfolio creation.</p><p>Without this, I’d just consume content endlessly without demonstrating mastery.</p><p>—</p><h4>What I’d Change</h4><p>1. Start with Fewer Newsletters</p><p>I started with 10+ newsletters. After Week 1, I unsubscribed from 2 TLDR newsletters (kept TLDR Product and TLDR AI).</p><p>Lesson: 5–8 high-signal sources &gt; 15 mixed sources. Quality &gt; quantity.</p><p>2. Simpler Notion Structure</p><p>I tried:<br>- Attempt 1: Database with multiple properties (too complex)<br>- Attempt 2: Weekly pages (perfect)</p><p>Lesson: Choose the simplest structure that works. Don’t over-engineer.</p><p>3. Acknowledge Technical Constraints Upfront</p><p>I learned the hard way that:<br>- WebFetch has context window limits in long conversations<br>- Large Notion databases exceed AI processing limits<br>- Summarization must happen at ingestion, not analysis</p><p>Lesson: Test technical feasibility before committing to architecture. I should have done a proof-of-concept with 5 newsletters before building the full system.</p><p>— -</p><h3>What You Should Steal</h3><p>If you want to build this system, here’s the minimum viable version:</p><p><strong>Week 1 — Automated Collection (2 hours):</strong><br>1. Gmail label “PM Newsletters”<br>2. Zapier: Gmail → AI Summarization → Notion weekly page<br>3. Test with 5 newsletters first</p><p><strong>Week 2 — Weekly Workflow (2 hours):</strong><br>1. Create Learning Log template (use mine above)<br>2. Run Monday workflow once<br>3. Document 2–3 insights</p><p><strong>Week 3 — First Artifact (3–5 hours):</strong><br>1. Pick 1 framework from Learning Log<br>2. Research it deeply (use ChatGPT/Claude to guide)<br>3. Apply it to a past project<br>4. Create 1–2 page artifact</p><p><strong>Week 4 — Consistency (30 min):</strong><br>1. Run Monday workflow again<br>2. Update Learning Log<br>3. Identify next artifact</p><p><strong>Total investment: 10–12 hours over 4 weeks<br>Ongoing commitment: 15–20 min/week</strong></p><p>If you do this for 12 weeks, you’ll have:<br>- ✅ 12 Learning Log entries<br>- ✅ 30–40 frameworks documented<br>- ✅ 2–3 portfolio artifacts<br>- ✅ Interview story about systematic self-development<br>- ✅ Proof of competency progress</p><p>That’s a competitive advantage most PMs don’t have.</p><p>— -</p><h4>Part 7: Why This Actually Matters for Your Career</h4><p>Most PM career advice sounds like this:</p><blockquote>“Network more. Get better at storytelling. Read Lenny’s newsletter. Be strategic.”</blockquote><p>That’s not actionable. Here’s what is:</p><p><strong>The L5 → L6 Gap</strong></p><p>L5 PMs: Execute well, deliver features, work with their team<br>L6 PMs: Set direction, influence stakeholders, think strategically, demonstrate business acumen</p><p>The gap isn’t “be more senior.” It’s specific competencies:<br>- Can you write a strategy memo?<br>- Can you build an investment case?<br>- Can you influence without authority?<br>- Can you set technical direction?</p><p>These are learnable skills with named frameworks:<br>- Strategy memos: The Three Bets, Pyramid Principle<br>- Investment cases: ROI structure, TCO analysis, payback period<br>- Influence without authority: Stakeholder mapping, RACI, executive presence<br>- Technical direction: ADRs, Tech Radar, outcome-based roadmapping</p><p>This system helps you learn these frameworks <strong>systematically</strong>, not randomly.</p><p>—</p><h4>Part 10: What’s Next (For Me and For You)</h4><p><strong>My Roadmap</strong></p><p>W<strong>eeks 5–12</strong> (remaining first quarter):<br>- Run Monday workflow consistently (target: 10/12 weeks = 83%)<br>- Complete 2 monthly deep dives<br>- Create 2 portfolio artifacts (strategy memo + investment case)<br>- Practice explaining system in mock interviews</p><p><strong>Month 4 </strong>(first quarterly review):<br>- Reassess 9-Signal competencies<br>- Identify which gaps are closing (1 → 1.5 or 2)<br>- Update priorities for Q2<br>- Optimize system based on learnings</p><p><strong>Long-term</strong> (12+ weeks):<br>- Demonstrate movement on 2–3 competencies (from “emerging” to “proficient”)<br>- Have portfolio of 4–6 artifacts<br>- Master 5–7 frameworks (from 🟡 to ✅)<br>- Use this system as interview story and proof of systematic development</p><p>— -</p><h4>Your Roadmap (If You Want to Build This)</h4><p><strong>This week:</strong><br>1. Do a self-assessment (use 9-Signal or any competency framework)<br>2. Identify 3–5 specific gaps you want to close<br>3. Audit your current newsletter subscriptions — which ones address your gaps?</p><p><strong>Next week</strong>:<br>1. Set up Gmail + Zapier + AI Summarization + Notion<br>2. Test with 5 newsletters for one week<br>3. See if the summaries are useful</p><p><strong>Week 3</strong>:<br>1. Run your first Monday workflow<br>2. Create a Learning Log entry<br>3. Document 2–3 insights mapped to your competencies</p><p><strong>Week 4</strong>:<br>1. Pick one framework from your Learning Log<br>2. Do a 2-hour deep dive<br>3. Create a simple artifact (1–2 page memo, case study, or framework explanation)</p><p><strong>After 4 weeks</strong>, decide:<br>- Is this valuable? (Are you learning systematically?)<br>- Is this sustainable? (Can you maintain 15–20 min/week?)<br>- Is this demonstrable? (Can you show artifacts and Learning Log in interviews?)</p><p>If yes to all three, keep going. If not, iterate or abandon.</p><p>—</p><p><strong>Thanks for reading.</strong> If you build this system, I’d love to hear how it goes. And if you have improvements, even better — systems should evolve.</p><p>Now go build yours. 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61795f3a51ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Considerations for AI/ML in Power Plants - Predictive Maintenance and Part Replacement]]></title>
            <link>https://medium.com/@justinschaeffer/considerations-for-ai-ml-in-power-plants-predictive-maintenance-and-part-replacement-f2051e18c51a?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2051e18c51a</guid>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Mon, 23 Nov 2020 23:44:24 GMT</pubDate>
            <atom:updated>2020-11-23T23:44:24.932Z</atom:updated>
            <content:encoded><![CDATA[<p>As I work my way through my current job search, I find myself having many interesting conversations about technologies and industries. Many of these conversations have left me exploring the ideas further. Once I put my product management hat on, it’s difficult to take off.</p><p><em>Disclaimer: The work produced here is not exhaustive or extensive. It is the product of 2–3 hours of research exploring a topic, using prior experience, and building a basic outline around a solution. It is intended to fulfill the requirements that one might see in an interview case study or homework assignment. The output of this work could be seen as the playbook for building a case for various ideas with many details left to be filled in and assumptions to be validated.</em></p><h3><strong>Background</strong></h3><p>One of the more interesting topics that I have explored recently is that of the world of inspection and maintenance in heavy industry. In particular, I have focused on energy and energy generation facilities (power plants), as I have some limited experience in the field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*fkn2j18q0-uJmdez.jpg" /><figcaption>Brunner Island Power Plant — via mcall.com</figcaption></figure><p>About 10 years ago, I was lucky enough to land a Mechanical Engineering Co-op at Pennsylvania Power and Light (PPL) where I split time between two of their coal-fired electrical generation facilities and their corporate headquarters. During my time there, my responsibilities included</p><ul><li>shadowing project management to understand equipment maintenance and replacement schedules,</li><li>making recommendations to reduce wear and tear/extend the useful life of piping systems,</li><li>and performing failure analyses to determine the cause of failure and prevent future failures.</li></ul><p>You can only get so much experience via an internship, but this internship proved very useful to my career. It helped me to determine that engineering wasn’t for me, but living at the intersection of engineering and other business units was incredibly interesting. Ultimately, this was one of the triggers that put me on the path into product management.</p><h3><strong>Problem Background</strong></h3><p>As I had conversations with various companies, I was reminded of a major problem in electrical generation: the plants can’t go offline. To do so would mean the possibility of hundreds of thousands or millions of people going without power. Depending on the severity of the problem, a plant being offline can also lead to safety concerns for the and the surrounding area.</p><p>Electric utilities and power generators have fail-safes and redundancy in these scenarios. Utilities can purchase power from other generators on the grid. Generators will build plants with multiple units capable of generating the appropriate power needs so that some units can be offline at any given time. But going offline is still not an ideal situation to be in.</p><p>As such, it’s important for power generators to regularly power down and inspect their equipment to ensure that it is still in working order and not in danger of malfunction. Scheduled maintenance is good — as it can be planned for. Unscheduled failure can put lives at risk and cost the company millions of dollars.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*IzA7ak7A5zGwqprH.jpg" /><figcaption>via greenplumbingNJ.com — Creator: PaulTessier</figcaption></figure><h3><strong>Solution</strong></h3><p>The need for inspection and maintenance has led to a growing industry of technology solutions that enable power generators to carry out inspections. Here, I would like to propose a new application (though it may not be new) — the use of Machine Learning to build predictive maintenance and part replacement schedules.</p><p>In current processes, the power generators or 3rd parties, have to carry out inspections to get the relevant data, analyze said data, and make recommendations based on it. During this process, the equipment must be shut down, costing the generators millions of dollars. If the analysis reveals the possibility of imminent failure and requires equipment replacement, the generator has to remain shut down until such a project can be completed.</p><p>An AI solution could help by:</p><ul><li>analyzing the results of inspections and predicting the remaining useful life of the equipment</li><li>recommending optimized maintenance schedules which could extend the life of the equipment</li><li>recommending equipment replacement schedules.</li></ul><p>In this post, I would through the basics of a business case for this solution and steps to develop and implement it.</p><p><strong>Benefits</strong></p><p>Customer Benefits</p><ul><li>Plants can be proactive in their equipment maintenance and replacement processes. They don’t need to react to bad news from inspections but can plan and prepare for replacement.</li><li>Optimized maintenance schedules. Where the system can confidently predict that maintenance is not needed, plants can save costs. Where the system predicts required maintenance, companies can extend the useful life of their equipment. In both cases, accurate predictions will increase employee safety, which should be paramount.</li><li>Minimize downtime, minimize costs, minimize safety risk</li></ul><p>Company Benefits — A company offering this system could:</p><ul><li>Gain recurring revenue through long-term inspection schedules, with built-in increasing frequency of inspection towards equipment end-of-life.</li><li>Increased customer loyalty</li><li>Ability to use data generation to build partnerships with equipment manufacturers</li></ul><p>Benefits - next steps</p><ul><li>Validate assumptions above</li><li>Calculate approximate savings and revenues from such a system.</li></ul><p><strong>Risks</strong></p><ul><li>The cost of increased maintenance outweighs the benefits of extended equipment life, increased employee safety, and shorter equipment replacement projects (in terms of downtime).</li></ul><p><strong>Development and Implementation</strong></p><p><em>I won’t walk through the full details of design and implementation here, but I’ll note some important points to consider.</em></p><p>The implementation and development of a new AI/ML system carries a lot of risks and uncertainty. Any company looking to implement such a system needs to be ready for long project cycles and ROI timelines. Culturally, the company has to be ready to accept the risk of failure and uncertainty and buy in for the long term. 87% of AI projects never make it to production (<a href="https://venturebeat.com/2019/07/19/why-do-87-of-data-science-projects-never-make-it-into-production/">VentureBeat</a>). Such a company also needs to have a mature data and analytics infrastructure, including but not limited to:</p><ul><li>data collection</li><li>data storage</li><li>data pipelines</li><li>data preparation</li><li>traditional analytics</li></ul><p>A new AI/ML implementation is not the time to build out and test data infrastructure.</p><p><strong>MVP</strong></p><p>The first step in the process is to identify a reasonable MVP. Something that may prove the concept and deliver value. The MVP may not even be an AI product but could be based on simple models or heuristics. What is important to identify, however, is a well-defined problem with real-world data that can be used to generate the desired outputs.</p><p>In the case of predictive maintenance at power plants, there is any number of inputs to such a model. It is important to identify a specific set of inputs to prove the concept. Some things to consider include:</p><ul><li>The specific type of equipment</li><li>Material specifications</li><li>Coatings or treatments used</li><li>Type of material flowing through the system (and the purity of said material)</li><li>System specifications — pressure, temperature, flow rates</li><li>Cycle times and uptimes</li><li>Age of the equipment</li><li>Regulatory requirements</li><li>Current maintenance schedule and specifications</li><li>Environmental/weather considerations</li><li>Failure parameters (corrosion, thermal stress, mechanical stress, upstream/downstream faults, etc.)</li><li>etc.</li></ul><p>In the MVP, it will be important to specify and constrain the inputs to remove uncertainty and variability from the training sets.<em> An important note here is that the models will need to be debugged and re-trained as you expand the data to include new inputs.</em></p><p>Decisions will also need to be made about the type of model to use. Here, it is helpful to focus on similar models. In predictive maintenance, there are two main options:</p><ul><li>Classification models — which determine the possibility of failures in N-cycles.</li><li>Regression models — which determine the time left before failure (Remaining Useful Life)</li></ul><p>Regression models can provide more information about when the failure may happen, but require more information. Classification models only give a yes/no answer but can be more accurate with less data. For the MVP case, a classification model probably makes sense.</p><p>Another consideration is the training data available for an MVP. In some cases, there may be some data readily available if the company is already involved in the inspection process. There are also some challenges to consider:</p><ul><li>amount of data available for this specific MVP case</li><li>the willingness of the customer to share data (especially historical data)</li><li>the willingness of the customer to partner to increase data generation (this will increase downtimes in the short term while providing long term benefits)</li><li>the need for education with the customer (and internally) to know that data generated will only apply to this specific scenario.</li></ul><p>It is important to make sure that real data pairs can be used. If the system is going to look at corrosion and wall thickness, we should know the actual measurements and time to failure after those measurements were taken in real-world scenarios.</p><p>Manufacturing data could be an issue here. Even if the company could build a test facility to simulate corrosion, there is likely to be enough difference in other variables that such data would lead to inaccurate outputs.</p><p>The MVP should make considerations for the important factors that go along with the output of the model:</p><ul><li>Accuracy and reliability — In this case, accuracy is paramount. If the model predicts a remaining life of 1 year, and the equipment breaks down after 6 months, the company would be responsible for significant safety hazards and unexpected downtime. It will be important to set up a system to validate the accuracy of the outputs through more traditional analysis until confidence levels are high.</li><li>Speed of the system — In some cases, like autonomous driving, the system must be able to make immediate decisions to avoid accidents. But in this case, the equipment in question should already be inactive. It will be important to deliver results in hours rather than days or weeks, but split-second decisions aren’t a factor here.</li><li>Availability — because the model will be running through data alongside the inspections that are taking place, the system must be up and running during projects. But the system shouldn’t be expected to handle the receipt of random data at any time.</li><li>Durability- How often should the model be re-trained? In this case, it will be important to retrain the model frequently, as it is unlikely that each set of data will have identical inputs to the data that the model was trained on.</li><li>Regulatory/legal concerns- In the power generation industry, there will undoubtedly be regulatory hurdles to using AI/ML to make decisions. The outputs of such a system should always be a recommendation and input to decision-making, but ultimately the system should never be making decisions on its own.</li></ul><p>Finally, it is extremely important to prep for post-launch monitoring and evaluation. Debugging and retraining will be necessary as the model is introduced to datasets with expanded inputs. The company would be wise to ensure that traditional analysis is still being done alongside the system to make sure that the outputs are accurate and make sense, especially as new types of data are introduced. It will be important during the development process to spec out the triggers to alarms, retraining, or system shut down, as necessary.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2051e18c51a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Too Many Hats: Managing what you need to do at a startup when what you need to do is all the things]]></title>
            <link>https://medium.com/@justinschaeffer/too-many-hats-managing-what-you-need-to-do-at-a-startup-when-what-you-need-to-do-is-all-the-things-473211cc2ab?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/473211cc2ab</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Sun, 25 Mar 2018 14:31:00 GMT</pubDate>
            <atom:updated>2018-03-25T14:31:00.836Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W2Y5II-mr55GfGdn.jpg" /><figcaption>This picture is overused for this topic. But I’m sorry, it’s hilarious.</figcaption></figure><p>I haven’t posted in a while. Sometimes life gets in the way. And lately, that has come from the age-old startup problem of wearing too many hats. Large companies have separate departments for product, engineering, marketing, sales, customer support, operations and purchasing, finance and accounting, etc. Each of those departments probably has multiple people with even more defined roles. At an early-stage company, you throw in fundraising as an almost full-time job and then you also have employees that have to take on the entire responsibilities of multiple departments.</p><p>Don’t get me wrong, that’s a totally expected part of the job and I absolutely love it. I want to be involved in all of those things and I probably wouldn’t be happy if I only worked on one of them. That was one of my initial draws to product management. Even if you don’t directly work as a marketer or a salesperson, you still need to work very closely with those departments and many others. You need to understand their work, what drives it, and how to best get things done.</p><p>But yeah, it’s gotten to the point where I keep a Google Doc listing my current job responsibilities which I update and re-prioritize weekly. My current, prioritized roles include:</p><ul><li>Ops manager. We just started shipping our first commercial product and I’m in charge of managing component inventory, manufacturing (in-house and outsourced), shipping management and scheduling, and forecasting and fulfilling inventory needs based on our sales pipeline.</li><li>Customer success manager. After deployment, I’m responsible for helping customers reach their intended goals with our product and expand their use in the future. I help solve issues that come up and act as the main point of post-sales contact.</li><li>Marketing manager. We’re at a point where lead generation is getting more and more important. I devised a content/inbound marketing strategy and am the main person responsible for creating interesting and insightful content that drives people to our website and eventually to our sales team.</li><li>Business development. Identify new potential markets for us to expand to, build contact lists, and identify partnership opportunities. A big, planned part of our business relies on partners that see us as a value-add in their work and can help convince clients to pay for it.</li><li>Product manager. It’s a little sad that this is so low right now, but realistically our main goal is shipping the finished product, putting the final touches on our software release, and performing maintenance. But we’re still trying to look towards the future as well. And this means I need to work on our product strategy and roadmap, validating product ideas with customers, conducting user interviews and testing, designing and updating user personas, building product requirements and wireframes, and building business cases for potential ideas.</li><li>Engineering/project manager. We try to run Scrum. I don’t know how successful we are, but we try. I manage this process as Scrum Master and project manager to make sure we can hit our deadlines and deliver to clients.</li></ul><p>In the past, roles also included mechanical engineer, intern manager (which is coming up again this summer), technical sales, and 3D printer technician, among other things.</p><p>I don’t mean for this to be like, “Oh look at all this stuff I do!”. But it’s more like realizing, “Wow, there’s a lot of stuff on my plate. How do I manage all of this while doing good work?”. To be successful, I’ve had to explore ways to manage all the different work required of me and the company in general. That’s what I really want to talk about in this article.</p><h3>Wearing all the hats and still rocking the outfit</h3><p>The key to managing all the different tasks, at least to me, is to start big and go small. Find out what needs to be focused on, and eliminate the clutter so that each day becomes more manageable. Regularly take a step back, take stock of what is important to the company right now and what that means for your role, and re-prioritize as necessary. Don’t be afraid to hit pause on things or throw them out entirely. The sunk cost of work that’s been partially done is nothing compared to the cost of doing the wrong things now and in the future.</p><p>In general, I try to do things that help me manage my week, my day, and each task. Each one informs usually helps inform the next. There are many different ways to manage your time and priorities, but I wanted to share one thing I do for each.</p><h3>Weekly: Prioritize each week with themes</h3><p>The most important thing I try to do is make sure that I give myself enough time and focus to make sure that I can truly make an impact at my work. Yeah, I listed 6 different roles above, but if I spent 1/6th of every day on each role it would be nearly impossible to make tangible progress on anything. Real progress comes from being able to throw yourself at a problem without distractions.</p><p>To help with this I borrow a bit from Scrum philosophy. The building blocks of Scrum are user stories. User stories are self-contained units of work that represent real progress towards a feature or outcome. Typically they are presented as:</p><p><em>As a _(specific type of user or stakeholder)_, I need to _(perform an action)_, so that I can _(gain a specific benefit or achieve an outcome)_.</em></p><p>Sometimes, the goal may be something that can be worked towards through many specific stories. This is where themes come into play. <a href="https://www.scrumalliance.org/community/articles/2014/march/stories-versus-themes-versus-epics">Scrum alliance uses the example of improving the performance of a feature as the theme Performance Tuning</a>. There are several different things that could be done to incrementally improve feature performance, but each represents work in a different area of the project. Several user stories are written and completed during a themed sprint with the aim of improving overall performance.</p><p>As a bonus, themes also <a href="https://medium.com/@jonatisokon/using-themes-in-your-modern-product-management-roadmap-d6fb064df266">appear in product management</a> for road-mapping.</p><h4>Applying themes to work</h4><p>I apply this strategy by beginning each week with a theme assignment exercise. I look at what really needs to be done to create the right outcomes for the company, and I prioritize on one or two areas of focus. That’s not to say that I don’t do work on my other roles for that week, but I pick one main hat to wear and put on the others as needed.</p><p>So one week might be Marketing-themed, where the goal is to create a bunch of content to draw people to the website, work on our monthly newsletter, make website updates, and do some PR outreach. Biz Dev Week means diving deep on research in a few markets, learning how much of an impact we can make on them, finding the right contacts, and exploring partnerships. The past couple of weeks have been Ship Weeks. Above everything else, the focus is on assembling product, testing it, and shipping to customers. When that’s done, other items can be worked on.</p><p>Within the framework of our sprints, I will prioritize my personal backlogs accordingly. I create a to-do list for that week’s theme with items that will drive the business forward in that particular area.</p><h4>Another option: systems thinking</h4><p>I won’t go in-depth here, but another great tool is combining stretch goals with <a href="http://blog.dilbert.com/2013/11/18/goals-vs-systems/">systems thinking</a>. I use this more in my personal life, but it can get frustrating feeling like you never get any closer to that far off goal in the distance. Systems thinking give you things to work on every day, and if you’ve done those things you know you’re progressing towards the goal.</p><h3>Daily: Prioritize each day with the Rule of 3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*PDbX1OXJzVCshZR-.jpg" /></figure><p>So now there’s a plan for the week, but then life happens. Emergencies come up, fires need to be put out, and real work can fall to the backburner. It can be tough to get back to center and tougher to feel like you’re making real progress. One way to combat this is to refocus yourself at the beginning of each day.</p><p>A great way to accomplish this refocusing is by using <a href="https://alifeofproductivity.com/rule-of-three/">the Rule of 3</a>. The Rule of 3 is pretty simple, but can absolutely change your day. It makes it easy to know what you want to do, to feel like you’ve spent the day well, and to say no to the distractions that come up.</p><h4>Applying the Rule of 3 to work</h4><p>To use the rule, you simply:</p><ul><li>Begin each day by reflecting on what to focus on that day.</li><li>Write down three things you want to accomplish <em>today</em>.</li><li>That’s it.</li></ul><p>There are some tricky parts here. First, you need to make sure each task is actually something that can be accomplished in one day. This might mean breaking down larger projects into sub-tasks. You also have to know when each task is complete. Vague things like “work on market research”, don’t lend themselves towards knowing when you’re done. If you define what it means for each task to be complete, you know when you can put it down and work on the next one. Finally, sometimes things come up and you might forget what your 3 tasks are. Make sure to write them down and consistently remind yourself of them during the day. When you ask yourself if you remember what the 3 tasks are, you can also ask yourself if what you’re doing right now is contributing towards them.</p><p>I try to do this every day and write down 3 things to accomplish at work and 3 things to accomplish in my personal life. It’s a great way to keep myself from plopping down on the couch and wasting my night on TV or video games. It’s very helpful towards making progress on my personal goals as well.</p><h4>Another option: whiteboarding the week</h4><p>This ties in with systems thinking, but I find that it’s incredibly helpful to make sure your goals are staring you in the face every day. I use a whiteboard to lay out my systems and then I have a weekly calendar where I check off if I’ve achieved the system task for that day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6CGqBqrpKDaIUc0q.jpg" /><figcaption>Some weeks aren’t the prettiest but that’s okay.</figcaption></figure><h3>Per task: Cut procrastination with the 5-Second Rule</h3><p>No, not that 5-second rule.</p><p>Easily the biggest obstacle to progress for myself and many other people is procrastination. Particularly I struggle with it as a way to deal with feeling overwhelmed. I’m lucky in that I generally deal with stress pretty easily and in healthy ways, but sometimes that best thing to do, when you need to do everything, feels like doing nothing. And these days there is so much happening that procrastinating is easy. In the past couple years, I often find myself looking at political news because there’s bound to be some new big thing that has happened since I last checked 5 minutes ago.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*p9Jx_nEsmXQ_f9NY." /></figure><p>So the key is finding ways to beat procrastination. Finding ways to get yourself started. The 5-Second Rule is great for this. It breaks the typical cycle where you think of something you need to do and then your brain comes up with excuses for why not to do it. It breaks the tendency towards indecision.</p><h4>Applying the 5-Second rule to work</h4><blockquote>“If you choose not to decide, you still have made a choice”</blockquote><blockquote><em>- The Holy Triumvirate</em></blockquote><p>This is pretty straightforward. When you find yourself needing to do something, simply use the “5–4–3–2–1” countdown and then act on it. I like to add “blast off” to the end because it’s fun. The best time to use this is when you realize your brain is starting to come up with excuses to procrastinate more. “Oh I’ll just read one more article and then I’ll get started” turns into “Oh I’ll just — wait, no…..5–4–3–2–1-Go!”. Every day is filled with these moments when you can kickstart yourself. Right now my major application for this rule is trying to get out of bed early instead of snoozing the alarm.</p><h4>Another option: the Pomodoro technique</h4><p>The <a href="https://en.wikipedia.org/wiki/Pomodoro_Technique">Pomodoro technique</a> is a way to keep yourself from burning out, which to me is when procrastination strikes the hardest. The goal is spend 25 minutes in deep work on a task, then take a break. The break lets you step back and reflect (usually subconsciously) and the work and helps you realize the best things to do. It also gives you something to look forward to. I use the <a href="https://tomato-timer.com/#">Tomato Timer</a>!</p><h4>Feedback</h4><p>Hopefully, these have given you some good insight into options that you have. Do you have different strategies that you use to manage your workload and get things done when there’s so much to do? I’d love to hear about them! I’m always looking for new things I can try and improvements I can make.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=473211cc2ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MIT Deep Learning for Self-Driving Cars and the DeepTraffic Project]]></title>
            <link>https://medium.com/@justinschaeffer/mit-deep-learning-for-self-driving-cars-and-the-deeptraffic-project-98fb16605f61?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/98fb16605f61</guid>
            <category><![CDATA[continuing-education]]></category>
            <category><![CDATA[self-driving-cars]]></category>
            <category><![CDATA[autonomous-cars]]></category>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Tue, 06 Feb 2018 21:37:10 GMT</pubDate>
            <atom:updated>2018-02-06T21:37:10.553Z</atom:updated>
            <content:encoded><![CDATA[<p>If there is one technology that I am super excited about, it’s self-driving tech. I think it’s one of the most important techs in terms of the noticeable effects it will have on everyone’s daily life. Machine learning, AI, big data. All of those are important, but to a random person on the street, they either won’t notice the impact or realize the underlying tech that causes it.</p><p>Self-driving cars are not like that. Maybe I’m biased for living in Pittsburgh, where it’s a common sight to see self-driving Ubers (and I even saw an <a href="https://www.argo.ai/">Argo </a>car today). People will get a lot of their own time back as they can immediately get a car and be productive in it. Many people, myself included, base their job choices around a commute. But when your commute doesn’t need to include being aware of traffic, it gets much less bothersome. There will be fewer accidents as cars are able to talk to each other and avoid each other. Inter-car communication networks will also serve to lessen traffic issues as cars will be able to talk to each other and optimize routes.</p><p>From a monetary perspective, Transportation-as-a-Service could have a huge effect on bank accounts. People may be able to save significant money by renting out cars without even needing to drive them or hand over the keys. Neighborhood ride shares may pop up, perhaps where 10 houses agree to split payments on 7–8 cars, which would lower car payments for each. Naturally, if all cars were taken at a given time, the user would still be able to order loaner a car from a nearby dealer lot.</p><h3><a href="https://selfdrivingcars.mit.edu/">Deep Learning for Self-Driving Cars</a></h3><p>The more I thought about it, the more I realized that I needed to put my attention and focus where my mouth is. It’s one thing to announce that self-driving is the most fascinating tech out there now, but it’s another thing to understand it and work towards making it better.</p><p>My interest for autonomous cars does not extend into programming it. My engineering experience lies mostly in mechanical product design and a few dabbles in various programming languages like Javascript and Ruby. But what I wanted was to gain a better understanding of a technology that I’m really excited about. To approach it like I approach other technologies in my professional career as a product manager. To understand enough about how the technology works to be able to speak with engineers and developers but to also be able to use that knowledge to use finding out how it will affect users, to find out what they want from it, and to predict where it will go in the future.</p><p>I found the MIT Deep Learning for Self-Driving Cars class and it was perfect. I will post more about my findings later once I finish the course, but I wanted to share my first project from the class.</p><h3>DeepTraffic Project</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cddTxvw2lOgPfudd.jpg" /></figure><p>The goal of the project is to get your car to navigate through traffic while trying to gain the highest average MPH possible. Safety settings are already built in, so you can’t change those. You can change the following inputs:</p><ul><li>How many lanes to each side the car is monitoring.</li><li>The number of spaces in front of your car being monitored.</li><li>The number of spaced behind your car being monitored.</li><li>The number of training iterations your network goes through.</li></ul><p>There are other, more advanced changes you can make, but for the sake of expedited experimentation, I stuck with just the major inputs. Students in the course need to exceed 65 MPH to pass the project. My goal is to hit at least this much, with a stretch goal of 72 MPH. The <a href="https://selfdrivingcars.mit.edu/deeptraffic-leaderboard/">current leader</a> as of early Feb. 2018 has reached a maximum average MPH of 76.04.</p><h3>Project assumptions and test plan</h3><p>I started with the following assumptions regarding what might optimize for higher average MPH:</p><ul><li>The car needs to see decently far ahead to know what is coming up and how it needs to adjust. If the car can’t see the traffic ahead of it, it won’t be able to respond to it. My initial guess would be at least 2–3 car lengths, though more may be a smart bet.</li><li>The car needs to see what is beside it to know what options it has. Seeing the action several car lengths ahead isn’t as valuable if the car is only seeing what is in its lane.</li><li>The car needs to see behind it in case it is in danger of being passed. Hopefully, that should help the car make decisions based on the traffic it sees ahead of it.</li><li>The more training iterations the better. The default is set to 10,000 iterations, but I decided to 5x it and leave it there. I’d like to have set the number higher, but for the sake of time that wasn’t going to be possible.</li></ul><h3>Project results</h3><p>After trying out a few input combinations, I was able to achieve a maximum average of 71.93 MPH. I think that’s close enough to round up and say I achieved my stretch goal!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/0*11mzBPxu-3S3-XA_.jpg" /></figure><p>Some reflections from the project:</p><p><strong>Data on data on data: </strong>It’s clear that even a basic goal like this requires a ton of data to see real improvements. My relatively small tweaks didn’t do much to change the average MPH, but my last attempt where I greatly increased the amount of data taken in from inputs and the number of training iterations finally resulted in a real change in the result.</p><p><strong>Traffic avoidance: </strong>At some points, the car seems to want to stay in the left-most or right-most lane. I assume that part of this is due to the preference in its programming for avoiding traffic. When the car is all the way at an edge, there can only be traffic to one side of it. This may go back to one of the big points covered so far in the class: you have to be careful how you construct the system because it may find ways to optimize that aren’t realistic in the real world.</p><p><strong>Constant optimization: </strong>When there is minimal traffic, the car will shift back-and-forth between lanes seemingly at random. This is fine when there is no traffic, but sometimes it decides to shift at the last moment into a lane with traffic ahead. I’m unsure of the reasoning behind this. I think if the cars were communicating with each other, some of this problem could be alleviated.</p><h3>Thoughts</h3><p>Overall the project was a really cool way to being to understand what goes into creating neural networks and the benefits/problems we have with their current implementation. It’s clear that even a “simple” model like this requires huge amounts of data to make real improvements so I can imagine what would be required to attempt to autonomously drive a car in the real world. It’s also clear why we’re still at a point where (most) human drivers will likely be safer on the roads right now. I’m excited to finish the class and see what else I can learn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98fb16605f61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Introvert’s Guide to Product Management Leadership]]></title>
            <link>https://medium.com/@justinschaeffer/an-introverts-guide-to-product-management-leadership-c0ada4682cd4?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0ada4682cd4</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[introversion]]></category>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Tue, 23 Jan 2018 14:06:01 GMT</pubDate>
            <atom:updated>2018-01-23T14:06:01.567Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*O89rL9XRHwxpBF8bUl4bMQ.jpeg" /></figure><p>As a product manager, it can often be difficult to blend personality traits with job responsibilities. Many PMs come from an engineering background that keeps them primarily working on individual projects or interacting with a consistent, small team of colleagues. It can be a challenge moving into product management that can have the PM interacting with all facets of the organization — product (duh), design, development, marketing, sales, operations, c-suite, etc. — as well upstream — suppliers, OEMs, etc. — and downstream — customers and other stakeholders. Not only is this a big change, but product managers are supposed to be leaders in all of these capacities as well, usually without formal authority. PMs are counted on for their ability to influence all different types of people without zero or few direct reports.</p><p>I am one of those PMs who was thrown into the role without a true understanding of what it means to be a product leader. That’s not to say that I didn’t know what leadership was, but that I was not exposed to true leadership without formal authority. I did not consider myself to be a leader, as I don’t exhibit the traits of what I thought to be a traditional leader that I had grown up seeing in the media. A dominant, loud personality that knows exactly what to do every time and controls everything that happens beneath him — that was/is not me and is not who I want to be.</p><p>But there I was, a fresh-out-of-college 23-year old handed the keys to developing the strategy, positioning, and messaging for a $10m product line and another high-growth product line that was expected to drive part of the company’s future, as well drive the execution for my product’s engineering and marketing, make decisions on suppliers, assembly and manufacturing, and train a seasoned sales team on my products. I had no formal product management training, I’m shy and soft-spoken, often preferring to let others speak while I consider their opinions and gather my thoughts. My teams were diverse in age and backgrounds, but I was usually the youngest and quietest person (by far, for both) in the room.</p><p>As I’ve grown in my career, I’ve learned more about the subtler aspects of product leadership. I’m still not outspoken or domineering, but I take charge when needed, make decisions, and persuade stakeholders with the best of them. I decided to take a look at more ways to improve my PM and leadership skills. I went through (of course) <a href="https://a16z.com/2012/06/15/good-product-managerbad-product-manager/">Good PM, Bad PM</a>, and books such as <a href="https://www.amazon.com/How-Win-Friends-Influence-People/dp/0671027034">How to Make Friends and Influence People</a>, <a href="https://www.amazon.com/Originals-How-Non-Conformists-Move-World/dp/0525429565">Originals</a>, <a href="https://www.amazon.com/Yes-Improvisation-Reverses-Creativity-Collaboration-Lessons/dp/0062248545">Yes, and</a>, <a href="https://www.amazon.com/Influence-Psychology-Persuasion-Robert-Cialdini/dp/006124189X">Influence</a>, <a href="https://www.amazon.com/Charisma-Myth-Science-Personal-Magnetism/dp/1591845947">The Charisma Myth</a>, <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwjVn-D84-zYAhUpRN8KHWQzDUYQFggpMAA&amp;url=https%3A%2F%2Fwww.amazon.com%2FExtreme-Ownership-U-S-Navy-SEALs-ebook%2Fdp%2FB00VE4Y0Z2&amp;usg=AOvVaw26K7ZevgrX53TqCU3Wvlw8">Extreme Ownership</a>, and <a href="https://www.amazon.com/Quiet-Power-Introverts-World-Talking/dp/0307352153">Quiet</a>, among many others, searching for something that would give me an edge. I took ideas and concepts from each book with me and use them when I can.</p><p>In the rest of this post, I’d like to explore the 7 key leadership principles listed as I’ve read through <a href="https://www.amazon.com/Product-Management-Dummies-Business-Personal/dp/1119264022">Product Management for Dummies</a>.</p><h3>Vision</h3><p><strong>Their take</strong>: Vision means knowing where your product needs to go and creating a strong picture of how to get there. You should be thinking short-term and long-term.</p><p><strong>The introvert take</strong>: For an introvert, having a compelling vision is the building block for everything else you can do. It aids in each of the rest of the principles. You should know, to the best of your ability, what specific things your team will be working on for the next few months and have a strong idea for what may be on the board for the next year or two. These items can absolutely change, but having a plan backed up by true knowledge is essential.</p><p>The key to a vision is being able to explain <em>why</em>. You should know the market, competition, industry, buyers, and users like the back of your hand to the point that you can predict how things will change. You should also be able to talk about technological changes and advances and how they might affect your product and the way customers interact with it in the future (even if that means it becomes obsolete!). The <em>why</em><strong><em> </em></strong>is what gets people on board.</p><h3>Boldness</h3><p><strong>Their take:</strong> Know what you believe in and be willing to fight for it. Be willing to break out of your comfort zone to make things happen. Think outside the box and then turn those ideas into reality.</p><p><strong>The introvert take:</strong> Pick your spots and be able to back it up. You need to be able to <em>confidently</em><strong><em> </em></strong>communicate your ideas. When it’s time to speak up, do it with purpose and assurance, knowing that the data backs up your stance. Being bold doesn’t have to mean being loud and boisterous, but instead is turning knowledge into action and accepting failure as a possibility.</p><h3>Ability to Influence</h3><p><strong>Their take</strong>: You should use logic and emotion to win over many different types of audiences.</p><p><strong>The introvert take</strong>: The key to persuading different stakeholders within your organization is being able to talk to them on their level and clearly articulate the benefits (and have knowledge of the drawbacks) of your decisions regarding your products. The way you pitch to executives should be different from the way you talk to sales, engineering, marketing, etc. You should know the motivations of each group you talk to and be able to justify your decisions on those terms.</p><p>One key that I think is probably the most important leadership ability isn’t reflected in the book’s list so I will include it here. That is the <strong>ability to build trust</strong>. Being able to influence any group of people in your company is founded on the sincere belief that you’re going to act in the best interests of the company. Sometimes this will align with your stakeholder’s belief about what is best for them personally. Other times, you’ll have to explain the benefits of your decision even if they don’t like it, and this will be significantly easier if you’ve built trust. Trust means many things, but can be built by following through on what you say, by being open, honest, and transparent in your communication, and discussing issues when they arise. As a PM, your victories should be credited to your team and your team’s failures should deflect from them and fall squarely on your shoulders. When people know that you’re willing to go to bat to protect them, they will be more willing to work for you.</p><h3>Be an Expert</h3><p><strong>Their take</strong>: You should be an expert in the field of product management and in the market segments that your product is targeting. It is difficult to get others to follow you if you aren’t an expert in the customers, markets, technology, and trends for your product.</p><p><strong>The introvert take</strong>: This is how you back up your vision and decisions. This is how you lead when you’re not the loudest in the room. As a product manager, you should know everything you can about the industry, market, competition, emerging technology, and your buyer and user personas. You should know past information on your product sales, missed opportunities, and avenues for growth and expansion. A mix of qualitative and quantitative data is better than just relying on one or the other.</p><p>This (plus your vision) should give you the confidence to speak up. You won’t always win, but when you back up your opinions with clear, convincing data you will find that often you do. When your decisions go wrong, you’ll be able to back up your choices and make it clear why you made your decision.</p><h3>Enthusiasm</h3><p><strong>Their take</strong>: Being enthusiastic is contagious and will bring your team together. This will get you and your team to a higher level and get people excited about your vision.</p><p><strong>The introvert take</strong>: Enthusiasm doesn’t have to be rah-rah all the time. You can impact your team by consistently bringing positivity, optimism, and confidence. When things go wrong, it is important to be the even keel that your team can count on to right the ship and provide new direction.</p><h3>Tenacity</h3><p><strong>Their take</strong>: You have to be able to keep going despite difficult people and circumstances. Your effort can’t just be a one-time activity or meeting, but should be a driving, ever-present force. Break down seemingly insurmountable challenges into small steps and effect as much change as you can.</p><p><strong>The introvert take</strong>: One of the keys to being tenacious, for me at least, is my unrelenting optimism. Failure in business and in life is inevitable. There will always be missed sales, difficult to reach deadlines, and fire to put out. The best way I’ve learned to deal with it and keep going is to be able to find a bright side to everything. Each result is a lesson that can be applied to future situations.</p><h3>Commitment to Excellence</h3><p><strong>Their take</strong>: Be excellent both in the work you do and in your deliverables. Everything you deliver as a PM should read well and look amazing. You are the center of all aspects of your product and if your work isn’t excellent the effect will ripple into other aspects of your product and organization.</p><p><strong>The introvert take</strong>: The easiest way to commit to excellence is to have a greater, driving purpose behind what you do. Again it’s the <em>why</em> that is important. For example, I used to work primarily with products in the education technology space. I didn’t cry or jump for joy with every thousand dollars made or lost on a sale, but it was easy to remind myself that every product we put into a classroom meant ~30 kids getting a better education. You don’t have to be excited and jump for joy at every aspect of your job, but know that the level of your work will influence the level of everyone else’s work on your product.</p><p>Do you have your own thoughts on the keys to leadership in product management or reflections on the ones listed here? Leave a comment or shoot me an <a href="/service/mailto:justin.michael.schaeffer@gmail.com">email</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0ada4682cd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product-Feature Prioritization]]></title>
            <link>https://medium.com/@justinschaeffer/product-feature-prioritization-de39a2d06605?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/de39a2d06605</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Tue, 09 Jan 2018 02:46:04 GMT</pubDate>
            <atom:updated>2018-01-09T17:10:35.362Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FMmsOYOBkmaWmx7RxIbtwQ.jpeg" /></figure><p>This is the first in a series of blog posts I plan on doing around product management and start-up topics and concepts. In these posts, I plan to study and present my findings on problems that product managers and entrepreneurs can often experience. Some posts will be based on things that I encounter in my day-to-day work at a pre-seed startup company. Others will be based on things I read, with a focus on information gathers from <a href="https://www.amazon.com/Product-Management-Dummies-Business-Personal/dp/1119264022">Product Management for Dummies</a>, <a href="https://www.amazon.com/Product-Managers-Desk-Reference/dp/0071591346">The Product Manager’s Desk Reference</a>, and <a href="https://www.amazon.com/Startup-Step-Step-Building-Company/dp/0984999302">The Startup Owner’s Manual</a>.</p><p>I’ve always found prioritization to be one of the most fascinating and impactful activities that a product manager can engage in. Prioritizing the right features can mean being first to market, delighting customers and users, and shows thought leadership in the industry. Picking the wrong features can mean building products nobody wants, incurring a lot of development cost for a product that doesn’t sell or move the needle, and playing catchup to competitors without releasing anything that users view as new and exciting.</p><p>Because of the impact of this activity, I have spent a lot of time trying out different methods for prioritization. Many methods work and some are better in certain situations compared to others. Based on the type of business and organization, certain methods may be better than others. Below are two of my favorites.</p><h3>Method #1 — Impact vs. Effort</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*59XDRqEkajF5HnaY.jpg" /></figure><p>My preferred method is to measure the impact and effort of a potential feature. From a <a href="https://blog.intercom.io/first-rule-prioritization-no-snacking/">blog post by Intercom and Hunter Walk</a>, the impact vs. effort graph is an easy, simplistic way for a startup or small business to prioritize its efforts. When running a startup, feature requests and ideas can come in from all directions — VCs, team members, early adopters and first customers, etc. Typically startups don’t have a process for handling all of these requests and features just get worked on one after another in almost random order.</p><p>Measuring the impact of a feature against the effort it takes to complete is a good way to pick the right type of work. Early on, there may be a lot of high impact, low effort projects to complete and this is fine. But this type of low hanging fruit does eventually run out. After that, it is important to focus energy on high impact, high effort projects.</p><p>Determining the placement of features on the graph requires some deliberation. Executives and the product team must determine what high impact means for them. The same goes for effort. The team should spend time determining criteria that are important for determining these factors. After creating these criteria (and their relative weight), each product can be ranked accordingly. An example is provided below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0Sr5XZ_kyx0xZw5Y.jpg" /></figure><p>Sometimes the development team can get discouraged if all they get to work on are high effort features. It feels good to ship things regularly and to be able to show the work you have been doing. Because of this, I think it is important to select ideas to work on from each of the Impact vs. Effort quadrants (except for high effort, low impact). Once the list is created graphed, a product manager should use their best judgment to pick and choose how ideas a prioritized for work.</p><p>One consideration that is glaringly missing from this method is Urgency. In the course of business, there will inevitably be fires to put out and directives from the c-suite that have to be worked on ASAP. Urgency can be worked into impact as a criterion — presumably, if a feature or project is urgent, that is because it will have a high impact. Additionally, I think it is always prudent to build some flex time into your development backlog. If something urgent comes up, it’s easy to work in because the team should (hopefully) already have extra time for it. If nothing comes up, then the next item on the list can be pulled in or the extra time can be spent on clean up or administrative tasks.</p><p>This method is ideal for startups and companies using Scrum for product development. The two factors can usually be ballparked pretty quickly if needed and comparing the impact and effort of two ideas can be straightforward without the detailed scoring. Estimated task effort is something that already takes place in the Scrum methodology so it may be more intuitive to measure the effort of a larger idea.</p><h3>Method #2 — Cost vs. Benefit Analysis</h3><p>Similar to measuring impact and effort, Cost vs. Benefit analysis is another good way to prioritize. Again in involves executives and stakeholders meeting to determine what is important when considering potential features. Consider the different levers projects could hinge on. On the benefits side, a company might consider factors like increasing revenue, customer value, and strategic value. Costs include implementation effort (amount of time resources will be occupied and unable to work on other projects), costs, and amount of risk involved with project success. The different features are then ranked for each factor (which may be weighted) and an ultimate score is determined<a href="#_ftn1">[1]</a>. The items with the highest score are the ones the company may want to work on first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ixsSX5kqxN2agMyJ.jpg" /></figure><p><a href="#_ftnref1">[1]</a>This is a variation of the pugh chart decision-making matrix. (<a href="http://www.decision-making-confidence.com/pugh-matrix.html">http://www.decision-making-confidence.com/pugh-matrix.html</a>)</p><p>Cost versus benefit is also ideal because it lends itself directly to $ values. In addition to somewhat qualitative criteria, the revenue and dollar cost impact of an idea can also be estimated and used to judge the value and priority of an idea. In the example above, the revenue category may be something like: 1 — &lt;$50k revenue per year ……. 5 — $10M revenue per year.</p><p>Both methods have their pros and cons. The decision on which one to use, or the choice to use a different method, should be made based on what is best for the person and organization. Do you have another method you like to use? Share it in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de39a2d06605" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Emotional Dunce]]></title>
            <link>https://medium.com/@justinschaeffer/the-emotional-dunce-803a57cb9969?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/803a57cb9969</guid>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Wed, 03 Jan 2018 23:18:28 GMT</pubDate>
            <atom:updated>2018-01-03T23:36:00.672Z</atom:updated>
            <content:encoded><![CDATA[<p>I just finished listening to the audiobook for <a href="http://www.amazon.com/Whole-New-Mind-Right-Brainers-Future/dp/1594481717">A Whole New Mind by David Pink</a> and parts of it were very eye-opening. Pink posits that we are leaving the information age and that we are facing the same dilemma as when we entered it. The main jobs of the age are being phased out as they are either being automated or outsourced overseas. To remain relevant, workers must embrace new skills. This means combining the left-brain skills of the information age with right brain qualities like creativity, inventiveness, and empathy. I do try to focus on skills at each end of the spectrum, but the section on empathy was pretty interesting to me.</p><p>Empathy is the action of understanding, being aware of, being sensitive to, and vicariously experiencing the feelings, thoughts, and experience of another. While it’s useful in many work situations, I was especially intrigued by the discussion about trying to use empathy around difficult coworkers. While it might seem like difficult coworkers are just trying to be confrontational or keep you from getting things done, that’s probably not the case. In reality, they’re most likely trying to do their best to reach the same objective as you. they just go about it differently. It helps to try to understand this mindset and find common ground.</p><p>One way to try to be more empathetic is to try to read the expressions on someone’s face to see what they’re feeling. Particularly of use is the reading of micro-expressions. Microexpressions, first explored by Paul Ekman, are the fleeting, involuntary expressions we make in reaction to events. They’re also a good way to <a href="https://www.ted.com/talks/pamela_meyer_how_to_spot_a_liar?language=en">spot if someone is lying</a> and determine their true emotions. <a href="http://www.microexpressionstest.com/micro-expressions-test/">Take this test</a> and see how good you are at reading expressions! Turns out I’m pretty bad at it, but I’ll get better.</p><p><em>Originally published at </em><a href="https://justinschaeffer.com/2018/01/03/the-emotional-dunce/"><em>justinschaeffer.com</em></a><em> on January 3, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=803a57cb9969" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting SuperBetter]]></title>
            <link>https://medium.com/@justinschaeffer/getting-superbetter-6f81807193e1?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f81807193e1</guid>
            <category><![CDATA[gamification]]></category>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Wed, 03 Jan 2018 23:17:30 GMT</pubDate>
            <atom:updated>2018-01-03T23:35:21.229Z</atom:updated>
            <content:encoded><![CDATA[<p>I just started a new book called <a href="http://www.amazon.com/SuperBetter-Revolutionary-Approach-Stronger-Resilient-Powered/dp/1594206368">SuperBetter by Jane McGonigal</a> and it’s been hard to put down so far. The book is all about how when we play games, we actively seek out and attain psychological benefits that help us achieve our goals. What’s fascinating is that we can take those same rules and methods and apply them to reaching goals in out everyday life. McGonigal references countless studies and even 400,000 SuperBetter players that show that the rules she sets out can be used to tackle real work problems.</p><p>I’m not a much of a gamer (unless you count Sega Genesis and Super Nintendo!), but I love the idea of turning life into a game. Have a big bad boss in your life? Grumpy neighbor? Want to learn a language or run a marathon? Recruit allies to help you develop your ninja skills to achieve your goal! Know that every time you fail you learn a few new tricks, gain insight into what doesn’t work, and get a little better for next time.</p><p>One last thing that I find fascinating is taking concepts from one area of life and using them to solve problems in another. It makes me wonder where else this could be done? Could we make businesses and organizations SuperBetter? What about schools?</p><p><em>Originally published at </em><a href="https://justinschaeffer.com/2018/01/03/getting-superbetter/"><em>justinschaeffer.com</em></a><em> on January 3, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f81807193e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Just do it (or why I wrote a personal manifesto and stopped halfway through)]]></title>
            <link>https://medium.com/@justinschaeffer/just-do-it-or-why-i-wrote-a-personal-manifesto-and-stopped-halfway-through-d199f49cb96c?source=rss-bc902288eb0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d199f49cb96c</guid>
            <category><![CDATA[improvement]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Justin Schaeffer]]></dc:creator>
            <pubDate>Wed, 03 Jan 2018 23:09:13 GMT</pubDate>
            <atom:updated>2018-01-03T23:34:51.578Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Ed. note: This is a repost from 2015 as I migrate some posts over to my new blog.</em></p><p>So back in March I decided that I was sick of declaring I was going to do this or going to do that and never following through. Instead, I was going to put all of my goals and dreams down on paper and share it with someone who could keep me honest. I sat down one night, disconnected from the internet, and started writing.<br> I wrote down my whys for writing the manifesto. I wrote down my purpose. I wrote down my rules for following the manifesto. And finally, I began to list my goals and dreams. The end result is below.</p><p>I took a few nights to go through the process of writing the manifesto. I wanted to make sure I had all of my bases covered. I wanted to list everything that I could possibly think of that I felt needed improvement in my life (at least at the time), so that I could start checking them off. But as I wrote, something funny happened.</p><p>It hit me that while it was great I was writing everything down, it was just another form of procrastination. Another way to keep from doing the actual work, but still feel good about what I’m doing with my life. So I stopped. As you can see, I got through the details on a few goals, but I left the rest blank. It might be more accurate to say that I started. Instead of describing what I was going to do in painstaking detail, I just started doing it. I’m happy to say that I’m almost at my 90 day deadline and I’ve made significant progress on several of these goals.</p><h3>A Personal Manifesto by Justin Schaeffer</h3><p>*Note: I expect this process to take significantly longer than 90 days, even though I do expect I can make great strides by that point. Patience is going to be key. Keep grinding, every day. Even on the bad days.</p><p><strong>Purpose</strong>: I want to change. I need to change. I have some specific areas that I want to improve on in my life, and this document is a way to get all of my thoughts out there. The document will describe each area that I want to change, what my drivers are for changing them, how I plan to make improvements (both in a general overarching sense and on a day-to-day basis), and talk about how I can get unstuck if I fail or become unmotivated. I will break each goal down into a S.M.A.R.T. goal with specific actions and deadlines and I will hold myself accountable to those deadlines.</p><p><strong>Start Date</strong>: March 26, 2015</p><p><strong>End Date</strong>: June 24, 2015</p><h4>Rules for following this manifesto:</h4><ol><li><strong>No Zero Days</strong>: I need to make small, measurable steps towards my goals every day. Every single day, no excuses. I will try to set myself up to succeed in this by not making my goals overwhelming. I will stagger goals so that I am never working on too many things at one time. I will give myself one cheat day per week (optional), to ignore certain goals — some goals will need to be worked towards every day to avoid drastic setbacks.</li><li><strong>Stay positive</strong>: Change is hard enough as it is. It’s damn near impossible if I get negative don’t believe it can happen for me. Small progress is still progress. If I encounter a setback, it is important to remember that the only way that’s even possible is if I have been making progress toward my goal. Have a sincere belief in sincere belief.</li><li><strong>No complaining: </strong>I am deciding to do this, because it is important to me. I love improving, even if it means short-term sacrifice on my end. Even if certain things suck. They will be good in the long run.</li><li><strong>100% all the time</strong>: No half-assing things.</li><li><strong>It’s okay to get discouraged</strong>: That being said, it’s going to be difficult. I’m going to fail at some things. Other things will take longer than expected. I’m going to have bad days. And that’s okay. If I need to take a break that day, it’s okay. I’ll get back to it the next day. <em>Forgive yourself for being human. </em>I know you expect too much out of other people and expect twice as much from yourself, but that isn’t always reasonable.</li><li><strong>Ask for help</strong>: As much as this is a personal thing, you’re going to need help. And you have done a good job of surrounding yourself with a lot of great people who are willing to help you. But you won’t get help if you don’t ask for it.</li><li><strong>Don’t waste time</strong>: Many of these things are going to take a decent amount of time each day to complete. Things like Netflix, Reddit, Facebook, etc. are going to need to take a back seat. They aren’t productive. It’s fine to partake (even every day), but only if the goals are taken care of.</li><li><strong>Don’t be afraid to blow it up</strong>: If something is obviously NOT working, ends up leading down a path that doesn’t end in success, or becomes de-prioritized, don’t hesitate to cut it from your life. Do you really have time to waste on something like that?</li></ol><h4>Staying Motivated</h4><p>Refer back to message from my best friend:</p><p>“That was almost 5 years ago now. I used to have such high hopes and aspirations with what I could offer the world. And they’ve only grown by leaps and bounds since then. I know a lot of people can’t understand why we’re best friends when they first meet us, especially when they meet us separately, but I know you’re very similar in that sense. The personal manifesto you put together last night is impressive, and demanding, but I know you want more out of life so that you can give more back. That’s why I know you can do it. I know you’ll work hard at it. There will be days that you fall off the wagon, and some days I won’t kick your butt to get back on, but the important part, and sometimes the most difficult, is that you do get back on. 🙂 You’re the best best friend I could ask for so I want to see you achieve all that you can. Start kicking ass today, Bambi. :)”</p><h4>Goals:</h4><p><em>General</em></p><p><strong>Get more sleep and get up on time.</strong></p><p>Why: Many of my goals are going to require discipline. One of the factors keeping me from being disciplined is the fact that I am tired a lot. The more rested and alert I am, the better I will be able to tackle what’s in front of me.</p><p>Driver: Accomplishing this goal will help me accomplish my other goals.</p><p>How: Go to sleep every night by midnight, weekends when I’m doing something excluded. This does not mean I need to be asleep at midnight, but by this time, I should turn everything off and be trying to sleep. Get up with my first alarm each morning and DO NOT GO BACK TO SLEEP. No snooze button.</p><p>Staying motivated: Every day is a chance to be awesome, but I can’t be awesome if I’m asleep in bed. I won’t reach my full potential of awesome if I don’t get enough sleep.</p><p>SMART: This goal is a daily goal. Measurable by getting 5.5–7.5 hours of sleep each night.</p><p><strong>Read (or listen to an audiobook. Or both!) every day.</strong></p><p>This is general because it applies to both personal and professional goals. I want to keep improving and one of the best ways to do that is by learning. I want to do this with a mix of professional learning, personal development, and mix in some fiction for leisure as well.</p><p>Driver: Reading is going to help me accomplish other goals. It will also make me a more rounded person and I will have more to talk about.</p><p>How: Listen to audio books every day on the drive to work. Even on the days that I don’t want to. Read at least 10 pages of a physical book or e-book every night.</p><p>Staying motivated: You love reading, you dork! Even more than Netflix!</p><p>SMART: Listen to an audio book for at least 30 minutes each day. Spend 5 minutes recording observations every day when I get to work. Read 10 pages of a physical book or e-book every night. Goal is daily. Deadline is every day.</p><p><em>Professional</em></p><p><strong>Exceed expectations at Black Box</strong></p><p>Why?: Because I hold myself to too high of a standard not to. Don’t just exceed the company’s expectations, exceed my own. Because I’ll learn so much more by doing than I ever could by reading.</p><p>Driver: Doing well at work can only pay off in the long run for my career. I’ll learn new skills that I can use to run my own company someday.</p><p>How: Start things and don’t stop them until they are done. Make mistakes. Fail. Try again. Take on projects I’m not ready for. Complete them anyway. Learn the fundamentals. Find ways to drive more growth. Sustain it. Share my knowledge with others. Listen to those that have knowledge that you don’t (which is everyone).</p><p>Staying motivated: If certain days are overwhelming, it’s okay. It happens. Take a step back and breathe. Remember why you wanted the job in the first place.</p><p>SMART: Create a daily to-do list first thing in the morning. Don’t leave until everything is checked off. Create weekly goals each Monday. Create monthly and quarterly goals (Khorus). Adjust as necessary.</p><p><strong>Build product management skills</strong></p><p>Why: Because I lack formal product management training. Trial by fire is great for learning, but it’s important to know the fundamentals. It will help me deal with situations that I am unfamiliar with. It will help me excel in situations that I have experienced before. It will help me drive change within the company.</p><p>Driver: Being a product manager is like being the CEO of the business at the product level. Everything I learn here can help me to run my own business one day. Until that time, it can help make me the best product manager that I can be.</p><p>How?: Take classes. Read the Product Management Desk Reference. Read other product oriented books, even the ones that don’t apply to my current position. Learn agile and scrum. Learn UX principles. Learn selling techniques and marketing principals. Watch webinars. Read blogs. Ask the other PMs questions.</p><p>SMART: Sign up for and watch 2 webinars per month. If you miss one, watch the recording. Read at least 10 pages of the Desk Reference every day until it’s done. Choose your next book. Search for online classes to take.</p><p><strong>Build software management skills</strong></p><p>Why: Most of the things that I want to be involved in — sports tech, AI, space, clean energy — require some sort of product that involves software. Even if I don’t write code, it is important to be able to manage products involving it.</p><p>How: Learn best practices for software management. Agile. Scrum. Lean methods.</p><p>SMART: You ordered books on lean method and scrum. Read them by the end of summer. Take notes. Continue to work on side-projects that involve some sort of software. Code on your own if you have to. Implement the practices you learn from the books. Find an online class about software management. Take it.</p><p>Other</p><ul><li>Build leadership skills</li><li>Build communication skills</li><li>Work on a side project every day (within reason)</li><li>Find a mentor</li><li>Build relationships with great people</li></ul><p><em>Personal</em></p><ol><li>Be more outgoing</li><li>Make new friends</li><li>Build deeper connections with people</li><li>Forgive other people for being human. Don’t hold grudges. Don’t judge them for making decisions that you wouldn’t. Don’t hold on to the feelings when they hurt you. Let it go.</li><li>Run/do yoga every day</li><li>Get on a regular gym schedule</li><li>Learn to play the ukulele</li></ol><p><em>Originally published at </em><a href="https://justinschaeffer.com/2018/01/03/1-just-do-it-or-why-i-wrote-a-personal-manifesto-and-stopped-halfway-through/"><em>justinschaeffer.com</em></a><em> on January 3, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d199f49cb96c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>