When I started as an Impact Coordinator at a small local nonprofit, my first task wasn’t to choose software. It was to observe the work, explore what we could measure, and review the information the organization already collected. That starting point shaped everything that followed.

Understand the work before changing the tools

Look at where information begins, who updates it, and who needs it next. A spreadsheet might hold attendance while another file tracks services and a staff member’s inbox holds important follow-up. Before bringing those records together, understand the purpose each one serves.

Let the questions guide the system

Ask your team what they regularly need to know. Which reports take too long? Which details are entered more than once? Those questions help reveal what a connected system needs to do. In my nonprofit work, that understanding led me to select a relational database and migrate the organization’s information into one place.

You don’t need to have every answer at the beginning. Start with one process, listen to the people who use it, and document what would make their work easier. A useful system should fit the mission and the team behind it.