para-method
The PARA Method and Building a Second Brain (Forte)
This skill captures the knowledge management framework from Tiago Forte's The PARA Method and Building a Second Brain, adapted for product managers and product leaders. It covers how to organize digital information for actionability, how to capture and retrieve knowledge systematically, and how to turn knowledge into creative output. PARA is not a filing system — it's a decision framework that determines what information deserves your attention, where it lives, and when it becomes useful. Building a Second Brain is the broader system that makes PARA operational through the CODE methodology: Capture, Organize, Distill, Express.
Core Principle
PMs who can't retrieve the right knowledge at the right moment default to recency bias, rebuild context from scratch for every decision, and lose the compounding value of everything they've learned — a Second Brain organized by PARA turns scattered information into a decision-making advantage.
Product managers swim in information: customer interviews, competitive analyses, strategy documents, research papers, Slack threads, meeting notes, conference talks, industry reports. Most of this information is captured once and never seen again. It sits in a folder called "Research" or "Notes" or "Miscellaneous" — organized by topic, not by use. When a decision needs to be made, the PM either remembers the relevant insight or doesn't. Knowledge doesn't compound. Every quarter feels like starting from scratch.
Forte's insight is that the problem isn't capture — most PMs are already saving too much. The problem is retrieval. Information organized by topic (marketing, engineering, design) is organized for a librarian, not for someone trying to ship a product. PARA organizes information by actionability: what are you working on right now (Projects), what are you responsible for ongoing (Areas), what might be useful later (Resources), and what's done (Archives). This means the information you need most is always closest to the surface.
The Second Brain extends this by adding a methodology — CODE — that turns passive information hoarding into active knowledge creation. You Capture what resonates, Organize it by where it's useful, Distill it to its essential message, and Express it as creative output. The goal is not to have a comprehensive knowledge base. The goal is to produce better work, faster, by reusing what you've already learned.
Scoring
Goal: 10/10. When evaluating knowledge management and organizational effectiveness, rate 0-10:
| Score | Description |
More from tomaszstaniak/pm-ai-skills
continuous-discovery-habits
Product discovery framework based on Teresa Torres'' "Continuous Discovery Habits". Use when you need to: (1) build an opportunity solution tree from desired outcomes, (2) identify and prioritize customer opportunities, (3) design assumption tests for product ideas, (4) structure customer interview snapshots, (5) map assumptions to experiments, (6) move from output-driven to outcome-driven product development, (7) map current-state customer experiences, (8) build a weekly discovery habit.
13good-strategy
Strategy evaluation and design framework based on Richard Rumelt''s "Good Strategy Bad Strategy" and Michael Porter''s "What Is Strategy?". Use when you need to: (1) evaluate whether a strategy is good or bad, (2) diagnose the core challenge before proposing solutions, (3) build a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-test strategic plans with pre-mortem analysis, (5) distinguish strategy from goals, ambitions, or wish lists.
10working-backwards
Amazon''s Working Backwards product development method based on Colin Bryar and Bill Carr''s "Working Backwards". Use when you need to: (1) write a PR/FAQ document for a new product or feature, (2) validate an idea by defining the customer experience first, (3) stress-test a proposal with pre-mortem analysis, (4) align stakeholders around a product vision, (5) decide whether an idea is worth building before writing code.
9positioning-and-pitch
Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use when you need to: (1) define or evaluate product positioning using the five-component framework, (2) translate positioning into a compelling pitch for stakeholders or buyers, (3) choose a market category strategy that shapes what you build and how you compete, (4) develop differentiated value claims that connect product decisions to market reality, (5) structure a pitch for exec reviews, board updates, or partner conversations, (6) diagnose why your product story isn''t landing with customers or internal stakeholders, (7) align cross-functional teams around a shared positioning narrative, (8) connect positioning decisions to roadmap priorities and feature trade-offs
6first-90-days
Leadership transition framework based on Michael D. Watkins'' "The First 90 Days". Use when you need to: (1) plan onboarding for a new leadership or management role, (2) build a 30-60-90 day plan, (3) diagnose the business situation you''re entering (STARS model), (4) plan critical early conversations with your new boss, peers, and team, (5) identify and avoid common transition traps, (6) accelerate time to value in a new role.
5escaping-build-trap
Product management framework based on Melissa Perri''s "Escaping the Build Trap". Use when you need to: (1) diagnose whether a team is stuck in the build trap (shipping features without outcomes), (2) shift from output-driven to outcome-driven product development, (3) evaluate product manager archetypes and team maturity, (4) design a product strategy that connects company vision to team-level decisions, (5) run a pre-mortem on a product roadmap to detect build-trap patterns.
5