100 Note-Taking Ideas for Data Scientists & Analysts in 2026

Before any stakeholder presentation, note down the primary objective you want to achieve or the key decision you need to facilitate.

Create a quick reference list of technical terms that might need simplification for non-technical stakeholders during a presentation.

Dedicate a section of your notes to clearly list action items, assignees, and due dates as they arise in data review meetings.

Maintain a running log of all significant decisions made during a meeting, including the rationale and who agreed.

Keep a separate section for questions raised by stakeholders, noting if they were answered or need follow-up analysis.

Use stars, underlines, or different colors to highlight critical data points or insights discussed in a meeting.

Designate a 'parking lot' section for ideas or questions that are important but not directly relevant to the current meeting agenda.

Document any hypotheses being tested or assumptions being made during data discussions, especially in requirements gathering.

When reviewing a dashboard, note the logical flow and narrative you want to convey, anticipating potential user questions.

Organize feedback received during a dashboard walkthrough into categories like 'UI/UX', 'Data Accuracy', 'New Feature Request'.

Create a checklist of key performance metrics (e.g., accuracy, precision, recall) to cover during model review sessions.

In model review, specifically note down any identified edge cases where the model performed unexpectedly or poorly.

During any technical discussion, make a note of potential technical debt or areas for future optimization.

If presenting, note down specific questions asked by stakeholders to reflect on how to improve future communication.

When reviewing data, note any questions about data sources, transformations, or lineage for further investigation.

For any proposed change or finding, quickly jot down the potential business impact (positive or negative).

Identify potential risks related to data quality, model deployment, or project timelines, and note down mitigation strategies.

Keep a running list of ideas for future enhancements or analyses that emerge during discussions.

At the end of a meeting or presentation, dedicate a small section to summarize the 2-3 most important takeaways.

Assign a subjective 'confidence score' (e.g., low, medium, high) to key insights presented, indicating the robustness of the data.

Clearly state the primary goal of the experiment and the specific hypothesis you are testing before starting.

Document all critical parameters of your experiment design: sample size, control/treatment groups, duration, metrics.

Detailed notes on where the data came from, any cleaning, transformation, or feature engineering performed.

For ML experiments, record the specific model architecture used and all tuned hyperparameters.

List the primary and secondary metrics used to evaluate experiment success, along with their definitions.

Regularly log the actual results, noting any unexpected deviations from expected outcomes.

Document the p-values, confidence intervals, or other statistical tests performed to assess significance.

Summarize what was learned from the experiment and outline the immediate next steps or follow-up experiments.

If applicable, note down the most influential features identified by the model or analysis.

Document any detected biases in the data or model, and potential strategies for mitigation.

Use version numbers or dates to clearly differentiate between different iterations of an experiment.

Record the specific software versions, libraries, and computational environment used to ensure reproducibility.

Note down any difficulties faced during the experiment, such as data quality issues or model convergence problems.

Jot down ideas for how best to visualize the experiment's results for different audiences.

Always include notes comparing the current experiment's performance against a established baseline or previous model iterations.

For A/B tests or new feature deployments, calculate and note the potential business impact in monetary terms if possible.

Consider and note any ethical implications of the experiment or model deployment, especially concerning sensitive data.

Create a checklist to ensure all necessary components (code, data, environment) are documented for reproducibility.

Document any serendipitous discoveries or unexpected patterns observed during the analysis, even if not directly related to the hypothesis.

After model review, note the team's collective confidence level in deploying the model to production.

For each requirement, write a user story ('As a [user], I want to [action], so that [benefit]') and its acceptance criteria.

As new data elements are discussed, start or update a data dictionary with definitions, types, and sources.

Clearly list any dependencies on other teams or projects, and any potential roadblocks that could hinder progress.

Explicitly define what is IN scope for the project and, equally important, what is OUT of scope.

Document the overarching metrics that will define the success of the entire project, not just individual experiments.

Note down who is responsible for what, especially in cross-functional projects, to avoid confusion.

Document any known technical limitations, such as system performance, data storage, or integration challenges.

If applicable, note down any specific regulatory, legal, or compliance requirements that the project must adhere to.

Keep a high-level overview of project timelines, key milestones, and target delivery dates.

Maintain a dedicated section for unresolved questions that require further investigation or clarification from stakeholders.

When faced with choices, create a simple pro/con list for each option to aid decision-making and document the rationale.

Beyond technical terms, maintain a glossary of specific business terminology relevant to the project for universal understanding.

Describe different scenarios in which the data product or model will be used, identifying user interactions and expected outcomes.

Document how the system should behave when errors occur or if data sources become unavailable.

Note down any specific requirements or concerns related to data security, privacy, and access control.

Keep track of which team members are assigned to specific tasks or components of the project.

Clearly articulate the criteria that must be met for a task, feature, or project increment to be considered 'done'.

After project completion, document key learnings from successes and failures to improve future projects.

For larger projects, keep notes on budget allocations, actual spend, and potential cost overruns.

Outline who needs to be informed, when, and through what channels for different project updates or issues.

Before building, clearly define the primary purpose of the dashboard and its target audience.

List all primary and secondary KPIs that the dashboard will track, along with their definitions and calculation logic.

Document where the data for each visual comes from and how often it is updated.

Note down the reasons behind specific chart types, color palettes, or layout decisions.

Document all available filters, drill-down options, and other interactive elements.

Keep a log of all feedback received during walkthroughs and how it was addressed in subsequent iterations.

If the dashboard includes alerts, document the thresholds and conditions that trigger them.

Document any steps taken to improve dashboard loading times or query performance.

Note down who has access to the dashboard and what level of permissions they have.

List the data quality checks implemented for the dashboard's underlying data sources.

Plan out the story you want the dashboard to tell, guiding the user through key insights.

Map out the possible drill-down paths and which visuals or data points they are linked to.

Establish and note down what constitutes 'normal' or 'expected' performance for each KPI.

Document any assumptions made during data aggregation or calculation that might impact the report's interpretation.

Note down who receives scheduled reports, the frequency, and the delivery method.

If comparing current data to historical periods or benchmarks, note the context and rationale for the comparison.

Anticipate ways the dashboard data might be misinterpreted and plan how to address them in explanations.

Keep a running list of desired features or improvements for the dashboard based on evolving needs.

Note any implications for data governance, such as data ownership, stewardship, or retention policies.

If the dashboard is complex, outline key points for a user training session or documentation.

Document your specific IDE setup, extensions, and any custom environment variables for consistency.

Maintain a personal library of reusable code snippets for common data cleaning, visualization, or modeling tasks.

Whenever you encounter and solve a technical problem, document the problem, the steps taken, and the solution.

For new techniques or models, summarize key papers, their methodologies, and relevant findings.

Write down simplified explanations of complex algorithms or statistical concepts to solidify your understanding.

During initial data exploration, note down interesting patterns, outliers, or potential data quality issues.

When working with APIs, keep notes on endpoints, required parameters, and expected response formats.

Store frequently used or complex SQL queries with comments explaining their purpose.

Track your personal development goals in data science, including resources studied and skills acquired.

When evaluating different tools (e.g., visualization libraries, ML frameworks), note their pros and cons for specific tasks.

Create a checklist of all steps required to deploy a model or data product to production.

Document how a deployed model or dashboard will be monitored for performance degradation or data drift.

Maintain a running list of ethical considerations relevant to your projects, including fairness, transparency, and accountability.

Note down key advice, insights, or alternative perspectives gained from discussions with mentors or peers.

During analysis, jot down ideas for future research, deeper dives, or entirely new projects.

Experiment with and document different frameworks or structures for presenting data-driven narratives.

For critical data pipelines or models, outline scenarios for automated testing to ensure robustness.

Visually map out how different data science concepts, tools, or projects relate to each other.

Note down any personal strategies or tools that help you manage your data science workflow more efficiently.

For potential projects or features, use a simple matrix to quickly assess their potential impact versus the effort required.