How to prioritize which data to collect and keep

One of the things that can feel overwhelming for a lot of people, whether you’re beginning to collect data for the first time or you’re trying to clean up a decade’s worth of data, is how to prioritize which data you need.

Of course, there’s data you’re required to collect and keep due to regulations, taxes, grant contracts.

And then there’s the data that you will need in the course of your operations—like where to send donation thank you letters, volunteer contact information, client names, budget totals, event attendees, etc.

But of that second category, which data do you need to keep?

And, if you’re starting out, what data should you collect that would be helpful?

Here’s how I like to answer that question:

A question you can answer using dataWhat action can the organization take based on this data?What data do you have (or can you get) that would be needed to answer this?
Example: Which social media channel generates the most conversions?Example: We can change how much time we spend on various channelsExample: Click through rate
Table to use for prioritizing data to collect

By filling in this table, I can get a lot of clarity on which data is worth keeping or collecting.

First, identify some questions you’d like to be able to answer using data.

These are typically things that might help you make a decision.  For example, is our current marketing strategy working as we’d hoped?  Is our program achieving the intended goal?  Did we budget appropriately for our technology needs? 

Next, determine what actions you could take based on answering that question.

Perhaps you’ll spend more time on your TikTok content than YouTube if that’s what the data proves to be more effective.  Maybe you’ll be able to (combined with demographic data) notice that your program is more effective for certain age groups than for others.  Or you can budget more realistically for your technology needs in the future.

Last but not least, determine what data is needed to answer that question and evaluate whether you can actually obtain that data or whether it would be ethical to collect or keep it.

Of course, there are plenty of things we’d love to be able to answer.  For example, we’d be interested to know what drives those seemingly random donations from new donors.  But maybe it’s really not feasible to obtain that data beyond how they got to our donation page (e.g., from an email vs. social media vs. something else).  Or perhaps we’d like to know how long the effect of our program lasts, but we work with a population that moves frequently. 

Then again, there’s data that is highly sensitive in nature.  Like someone’s undocumented status or the fact that an individual has contacted your organization about services related to intimate partner violence. 

If you are dealing with data that puts your constituents at risk should it end up in the wrong hands, consider whether you actually need this data to fulfill your mission and if so, what steps you can take to minimize data collected, secure it, and carefully discard it as soon as possible. 

NTEN’s Equity Guide for Nonprofit Technology is a great resource to check out for more considerations for your data collection and data management practices.

A Quick and Easy Template for All Your Meeting Notes

My whole life, I have been a note taker – not because I have poor memory, but because it is part of how I process information.  If someone is simply talking at me (not with me), and I am doing nothing with this information, then there’s a good chance I’m not likely to remember any of it.  I have live transcribed interview notes.  I have gotten into sketchnotes the past few years.  I have typed up official minutes and jumped into the beautiful fray of collaborative notes.  Mostly though, I prefer a steno pad and a ballpoint.

Take notes however works best for you.

That being said, there are notes that are for you, and there are notes that are for the creation and sharing of knowledge.  Meeting notes fall into the latter category.

To be useful to other people afterwards, meeting notes require a clear structure.  They require some synthesis of what had been discussed, agreed upon, and what remained outstanding.

To be useful during the meeting to the person taking notes, meeting notes require a template that reminds you of all the types of things you need to capture.

There are a lot of specific and formatted templates out there.  You may have a few or 15 at your organization.  But I find that simple is best.  It means I can easily create it from memory without having to search for the correct template for that particular client or committee or type of project.  Which is really helpful when what was supposed to be a 15-minute check-in with your team turns into an apparently-no-one-renewed-our-domain-registration crisis management session.

Here it is my quick and easy template for all meeting notes:

  • Date
  • Participants
  • Agenda
  • Decisions Made
  • Action Items
  • Notes

Date

Having spent enough time working with global teams and generally communicating with people who are not American, I am getting into the habit of writing dates in an internationally friendly format: Month DD, YYYY.  That’s still rather US centric, if at least clearer, so you and your colleagues might prefer DD Month, YYYY, which is how most (the rest?) of the world formats dates.  If you prefer numerical dates and or will be including this in the filename for chronological sorting, I suggest using the ISO standard of YYYY-MM-DD.

Participants

Who was present at this meeting?  Unless it’s a very small team or very short-term project, I typically include last names so as to maintain clarity for when a second Sanket joins the team.  (Trust me, New Sanket and Old Sanket are NOT good ways to distinguish between them.). If this is a meeting across teams or organizations, I may include which group they’re representing as well. 

Basically, if these notes were shared with you and you were not at the meeting, what might you want to know about who was involved in making the decisions?  What information would you need to follow up with people assigned action items if you have questions?  Relevant details will vary somewhat depending on that context of who’s there and who else will use these notes.

Agenda

Every meeting should have an agenda.  It doesn’t have to be super formal, but there should always be a clear purpose for your meeting. 

Many people list the topics or the speaking order in an agenda, and that’s not wrong—but it’s not as effective as listing your objectives.  How will you know if the objectives of the meeting have been achieved?  How do you know when you’re done talking about a topic or if further discussion is needed?  It’s easier to tell if your agenda lists “Choose venue for teambuilding” instead of “Discuss teambuilding.” Make your agenda your guide.

If this truly needs to be meeting and not an email, this means there is likely at least one decision to be made.  Include any decisions to be made in your agenda.

Decisions Made

This space is for recording decisions that have been made.  Documenting decisions is crucial.  Otherwise, everyone notes what they think they heard to be the group’s decision, and you end up with a game of telephone except that you were all in the room (Zoom or conference) believing you took part in the same conversation.  Spelling out the decision in writing gives everyone a chance to refute or clarify, and helps make sure that you are all agreeing to what you think you are agreeing to. 

Note that this decision can change in the future; you’re simply documenting the decision at this point in time.  For example, that you’re going to have your conference in Baltimore, Maryland, in April 2020.  That decision may have made sense in September 2019 but may not have looked so good in March 2020.  This doesn’t mean you may not plan out your 2022 conference and revisit having it in person.  Documenting your decisions allows people to track what happened when and why things changed.

In the rare instance that no decisions were made* (was this actually a presentation rather than a meeting?), you can always leave this section blank, but it’s a handy prompt.

*If you decided to punt a decision to a later date or separate meeting because, for example, you needed some additional information, or because a key stakeholder wasn’t present—then you made a decision!  Add that here.

Action Items

It is very common that after a meeting, some of the people in the meeting will need to do some things.  Documenting those action items here, along with who is responsible and the due date, is again, crucial as a central source of truth and avoiding those pesky arguments about who was supposed to get your domain registration renewed pronto.

Notes

This is where you take notes on the substantive points of discussion.  Updates shared.  Concerns and considerations that went into the decisions that were made.  Any disagreements and how they were resolved.  Contextual information for those action items.  (If there are any questions that require someone to find something out and let the group know – that’s an action item!)  And anything else worth noting!

If you’re taking notes during the meeting and scrambling to figure out where to put things in the moment, it’s completely okay to put everything that’s not the agenda (which hopefully you have beforehand or create together at the start of the meeting) in the Notes section.  Then you can take a few minutes after the meeting if needed to put the decisions made and action items into their appropriate spots.  Since note taking is often done quickly, I often leave them in the notes as is and then try to rewrite them more clearly to put into the Decisions Made and Action Items sections.

Go forth and take notes!  Drop me a line if this has been useful to you or if you have any suggestions.