Building a second brain as a data scientist: the five knowledge components that compound across a data science career (methodology intuition, domain and data expertise, analytical judgment patterns, cross-functional communication intelligence, and career craft knowledge), the organization that makes each retrievable when data problems require experienced judgment, and the capture habits that convert daily analytical work into compounding professional expertise.
Building a second brain as a librarian: the five knowledge components that compound across a library career (source and research landscape expertise, reference interview and patron intelligence, cataloging and metadata judgment, instructional and information literacy expertise, and institutional and professional knowledge), the organization that makes each retrievable during reference work, and the capture habits that convert daily professional work into compounding career expertise.
Managing information overload as a data scientist: the six information streams that compete for data science attention (research literature, practitioner content, algorithmic developments, data and tooling updates, stakeholder requests, and business context), the triage protocol that separates immediately applicable signal from background professional development, and the structured reading rhythm that keeps data science knowledge current without overwhelming daily work.
Managing information overload as a librarian: the six information streams that create professional overload (collection development, professional literature, patron requests, cataloging standards updates, institutional communications, and community resources), triage protocols for each stream, and the organizational structures that keep information manageable while maintaining the awareness that professional reference work requires.
Managing information overload as a translator: the six information streams that create professional overload (source text research, terminology and language developments, subject matter evolution, client communications, professional community, and business administration), triage protocols for each stream, and the workflow structures that protect deep translation concentration while maintaining the professional awareness that quality translation requires.
Note-taking templates for data scientists: four templates that structure the most important data science note-taking contexts (analysis session notes, research literature notes, experiment design and results notes, and domain knowledge notes), with the specific fields that convert raw notes into retrievable methodology intelligence and institutional knowledge.
Note-taking templates for librarians: four templates that structure the most important professional note-taking contexts (reference interaction notes, database and source exploration notes, collection development notes, and professional development notes), with the specific fields that convert professional experiences into retrievable source intelligence and institutional knowledge.
The research-to-output workflow for data scientists: how analytical work converts into the outputs that drive business decisions — exploratory analyses, model development documentation, A/B test designs and analyses, and stakeholder-facing reports — with the documentation disciplines that make each output reproducible, trustworthy, and grounded in transparent methodology.
The research-to-output workflow for librarians: how professional knowledge work converts into the outputs that serve patrons and strengthen the institution — research guides and pathfinders, collection development analyses, instructional materials, and professional reports — with the documentation disciplines that make each output useful, maintainable, and grounded in verified source knowledge.
The research-to-output workflow for translators: how professional knowledge work converts into translation outputs that accurately serve their purpose — project preparation research, terminology research and documentation, subject matter verification, and post-translation knowledge capture — with the documentation disciplines that make translation decisions defensible and professional knowledge compound.
The reading and research workflow for data scientists: four tiers of research engagement (daily monitoring, weekly synthesis, monthly landscape assessment, and project-specific deep research), aligned to the information types that data science work actually requires, with the synthesis practices that convert reading into methodology intelligence and domain expertise rather than consumed content.
The reading and research workflow for librarians: four tiers of professional reading and research engagement (daily collection and patron monitoring, weekly professional literature and source exploration, monthly landscape assessment, and project-specific deep research), aligned to the information work that library service actually requires, with the synthesis practices that convert reading into source intelligence and professional expertise.
The software stack for data scientists: the tools and systems for managing code and experiments, organizing research literature and methodology knowledge, tracking analyses and findings, and building the organized intelligence that lets data science work compound rather than repeat — with a focus on the knowledge management layer that most data science stacks underinvest in.
The software stack for librarians: the four knowledge management problems that professional information work creates (collection organization and access, patron research support, cataloging and metadata workflows, and institutional knowledge management), and the tool categories that address each — building a system that makes information findable, connections visible, and professional expertise retrievable.
The software stack for translators: the four knowledge management problems that professional translation work creates (terminology and glossary management, subject matter knowledge organization, client and project context management, and reference material access), and the tool categories that address each — building a system that makes specialized terminology retrievable, subject knowledge accessible, and translation decisions consistent.
A reading and research workflow for product managers: the four-tier monitoring structure (daily customer signal and competitive monitoring, weekly product and market intelligence review, monthly landscape assessment, project-specific deep research), the practices that keep competitive intelligence current without becoming reactive, and the research calendar that aligns deep research with product planning cycles.
A reading and research workflow for venture capitalists: the four-tier monitoring structure (daily deal flow and market alerts, weekly investment intelligence review, monthly sector landscape assessment, fund-cycle deep research), the research calendar that aligns deep sector work with investment pacing, and the intelligence currency practices that keep market knowledge current in rapidly evolving sectors.
AI research for product managers: where AI tools provide genuine leverage in product research workflows (customer interview synthesis, competitive landscape orientation, PRD drafting, stakeholder communication), where they introduce risk (market size claims, regulatory requirements, customer research as a substitute for actual research), and the verification practices that maintain research quality.
AI research for venture capitalists: where AI tools provide genuine leverage in investment research (sector orientation, deal memo drafting, market trend synthesis, competitor landscape mapping), where they introduce risk (company financial data, regulatory intelligence, founder reference checks), and the verification practices that maintain investment research quality.
Building a searchable knowledge base for product managers: the four knowledge layers (customer intelligence, competitive intelligence, product decision history, and market and industry knowledge), the metadata structure that makes each capture retrievable when roadmap and strategy decisions require customer and competitive context, and the maintenance practices that keep the knowledge base current as the customer base, competitive landscape, and market evolve.
Building a searchable knowledge base for venture capitalists: the five knowledge layers (deal intelligence, sector and market intelligence, portfolio company knowledge, pattern intelligence, and relationship intelligence), the metadata structure that makes each capture retrievable when investment decisions and portfolio support require context, and the maintenance practices that keep the knowledge base current as markets, companies, and investment theses evolve.
Building a second brain as a product manager: the five knowledge components that accumulate over a PM career (customer pattern intelligence, competitive landscape knowledge, product decision wisdom, market and domain expertise, and PM craft knowledge), the organization that makes each component retrievable when product decisions and career challenges require it, and the practices that convert experience into reusable knowledge.