Building a second brain as a venture capitalist: the five knowledge components that accumulate over an investment career (founder pattern intelligence, market and sector wisdom, investment decision wisdom, portfolio company pattern intelligence, and LP and firm relationship intelligence), the organization that makes each component retrievable when investment and portfolio support decisions require it, and the practices that convert experience into compounding investment judgment.
From Research to Output — A Workflow for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
How product managers should use AI for research: the four-question framework for evaluating any AI research task (is this orientation or conclusion? is this current? is this generalizable or specific? what's the cost of being wrong?), the specific workflows where AI produces reliable PM research value, and the failure modes that undermine PM research quality when AI is misapplied.
How product managers turn research into product decisions: the research-to-output flow from customer discovery through roadmap prioritization to product strategy documents, covering the specific outputs each research type produces, the evidence standards that distinguish good product decisions from opinions with nice slides, and the documentation disciplines that make product reasoning retrievable.
How to build a searchable knowledge base for product managers: the retrieval-first design that makes customer intelligence, competitive research, and product decision history accessible when roadmap decisions require them, the tagging and metadata structures that enable search without browsing, and the maintenance disciplines that prevent knowledge base decay.
Information overload for product managers: how to manage the six competing input streams (customer feedback, stakeholder requests, competitive signals, data and metrics, market intelligence, and engineering and design context) without becoming permanently reactive, with a triage system that routes each stream to the appropriate attention level and protects the synthesis time where product judgment is actually formed.
Managing information overload as a venture capitalist: the six information streams that compete for VC attention (inbound deal flow, market and sector intelligence, portfolio company updates, co-investor and founder network, regulatory developments, and technology trends), the triage protocol that separates investment-critical signal from background noise, and the monitoring structure that keeps investment intelligence current without consuming all available time.
Note-Taking Templates for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
Note-taking templates for product managers: the four templates that structure PM research and decision capture (customer interview notes, competitive intelligence capture, product decision records, and stakeholder alignment notes), the fields that make each template retrievable and useful rather than just filed, and the practices that convert raw note-taking into organized product intelligence.
Note-taking templates for venture capitalists: the four templates that structure VC research and relationship capture (founder meeting notes, market and sector research notes, board meeting notes, and reference call notes), the fields that make each template retrievable when investment decisions and portfolio support require historical context, and the practices that convert raw note-taking into organized investment intelligence.
Reading and research workflow for product managers: a practical system for managing the continuous reading and research demands of the PM role without allowing input consumption to crowd out the synthesis work where product judgment is actually formed, covering the daily, weekly, monthly, and quarterly reading rhythms that keep PM intelligence current while protecting synthesis time.
The research-to-output workflow for product managers: how product decisions — feature prioritization, roadmap planning, product strategy, competitive positioning, and customer research synthesis — are grounded in systematic research and documented in ways that create a clear record of the reasoning behind product choices.
The research-to-output workflow for venture capitalists: how investment decisions — from initial company evaluation through thesis development, deep diligence, investment committee memos, and portfolio company support — are grounded in systematic research and documented in ways that create a clear record of investment reasoning.
Second brain setup for product managers: what the PM second brain actually stores (the accumulated product judgment that makes senior PMs faster and more reliable than junior PMs with the same data), how to structure it for retrieval rather than archiving, and the capture habits that convert daily PM work into compounding career intelligence.
The best note-taking templates for product managers: practical templates for the four contexts where PM notes most directly drive product decisions (customer discovery sessions, competitive observation, product strategy discussions, and cross-functional coordination meetings), with the specific fields that make each template useful rather than just organized.
The best software stack for product managers is the system that converts scattered customer conversations, competitive observations, and market intelligence into organized, retrievable knowledge that drives better roadmap decisions — covering the capture-to-synthesis pipeline, how each tool integrates into the PM's daily workflow, and the common stack mistakes that create knowledge silos instead of accessible intelligence.
The Reading and Research Workflow for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
The software stack for venture capitalists: the tools and systems for managing deal flow, tracking portfolio companies, organizing market intelligence, and building the institutional knowledge that makes better investment decisions — organized around the VC's fundamental information management challenge of processing large volumes of companies and market signals with limited time.
A reading and research workflow for IT managers: the four-tier monitoring structure (daily security and operational alerts, weekly technology and security intelligence, monthly landscape assessment, project-specific deep research), the security compliance calendar that catches patching windows and regulatory deadlines, and the dated capture discipline that keeps security intelligence current.
A reading and research workflow for operations managers: the four-tier monitoring structure (daily operational performance and safety review, weekly improvement and industry intelligence, monthly landscape assessment, project-specific deep research), the regulatory compliance calendar that catches OSHA and quality standard changes before they create compliance gaps, and the dated capture discipline for regulatory and industry intelligence.
A second-brain setup for accountants is a personal system for technical knowledge, CPE learning, and career-spanning research that survives firm changes, unlike a knowledge base that stays behind on a former employer's shared drive.
A second-brain setup for IT managers is the personal professional intelligence system that stores technology expertise, incident pattern recognition, vendor relationship knowledge, security and compliance expertise, and the accumulated architectural judgment from years of IT management — organized so that the institutional knowledge that typically exists only in the IT manager's memory is retrievable when the next incident, technology decision, or audit requires it.
A Second-Brain Setup for Recruiters — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Recruiters.
AI research for accountants works well for drafting memo structure, summarizing regulatory updates, and orienting new research — and fails dangerously when used to source IRC citations, since domain AI tools still hallucinate in 17-33% of cases.