Category: Technology Success Partner

  • The Nonprofit Digital Transformation Discovery Toolkit

    Most digital transformation projects fail in the same place: a team picks a shiny new system, signs the contract, and only then discovers the three workarounds, two shadow spreadsheets, and one mandatory state portal the new system has to live alongside. The fix is not a better vendor demo. It is better discovery.

    Before we recommend a single new platform, we map two things: what tools an organization actually uses, and how the work actually flows between them. Those two pictures almost always reveal that the real problem is not “we need a new system,” but “the same information is entered four times, by three people, in two departments, and nobody can see the whole thing.”

    Here are the two tools we use to build those pictures. They are deliberately simple, they work on any stack, and you can run them yourself. Take them and use them, whether or not you ever work with us.

    Prefer to work in a spreadsheet? Download the full toolkit as an Excel workbook – both the systems inventory survey and the day-in-the-life worksheet, ready to fill in.

    Tool 1: The Systems & Tools Inventory Survey

    A five-minute survey that every staff member fills out, so you can see every tool in use across the organization, including the ones that never appear on an org chart.

    The goal is the honest picture: the official systems, yes, but also the personal Canva account, the spreadsheet that quietly runs payroll reconciliation, the free app someone downloaded to get their job done. Those “shadow” tools are not a sign of bad staff. They are a map of exactly where your official systems fall short.

    A few principles that make it work:

    • Keep it short and make it optional. The only questions that truly matter are which team someone is on and the full list of tools they use. Everything else is bonus. People bail on long surveys.
    • Let it be anonymous. You get far more honest answers about personal logins and workarounds when nobody’s name is attached.
    • Ask where files live and how people communicate. This is where you find the fifteen shared drives nobody can navigate and the client coordination happening over personal text messages.

    The questions we use:

    1. Which team or service line do you work in?
    2. What is your role?
    3. List every software, app, or website you use to do your job, one per line, the big ones and the small ones.
    4. Which of those did you set up or choose yourself, rather than something the organization gave you?
    5. Do you keep information in Excel, paper, or a notebook because a system cannot do what you need? What, and why?
    6. Do you use any personal accounts or tools you pay for yourself for work tasks?
    7. Where do you save your files and documents?
    8. When you need to coordinate with teammates about a shared client or task, how do you usually do it?
    9. What is the most repetitive or time-consuming manual task in your week?
    10. If one thing in your workday “just worked” automatically, what would you pick?

    Run it as a Microsoft Form or a Google Form, leave it open for about a week, then tally the tools by frequency. The result is a word-cloud of what your organization really runs on. Anything named by only one or two people is a single-owner risk worth a closer look.

    Tool 2: The Day-in-the-Life Workflow Worksheet

    The survey tells you what tools exist. This worksheet shows you how the work flows, and it is where the expensive problems hide.

    Pick one real, representative workflow and trace it end to end: every step, every system, every handoff, and every place a human re-types information that already exists somewhere else. Do not describe how it is supposed to work. Describe how it really happens, sticky notes and side-emails included.

    Good candidates to start with:

    • A new client or participant intake into a program.
    • Logging a client note or filing an incident report, and where it has to end up.
    • A major gift, from the ask through to it being recorded and acknowledged.
    • Month-end close, where finance and your system of record have to reconcile.
    • Onboarding a new employee, from HR through to system access and training.

    For each step, capture: what happens, which system or tool is used, who does it, whether it is automated or manual, who it gets handed to next, where the friction is, and how long it takes. Then, once you have walked the whole thing, answer the questions that matter most:

    • Where is the same information entered more than once? This is your duplicate-data list.
    • Where does work stall waiting on another person or department? These are your handoff bottlenecks.
    • Which steps touch a system you are required to use (a state portal, a funder’s system, banking)? These are fixed points any new architecture must respect.
    • Where does information leave a real system and live in email, a spreadsheet, or paper?
    • If this workflow were seamless, what would it look like?

    One worksheet per workflow, thirty to forty-five minutes each. Three or four of these across your busiest departments will teach you more about what to fix than any vendor RFP.

    How to use them together

    Run the survey across everyone first, then use the results to choose which workflows to walk. The departments with the most shadow tools and the most “we do this in Excel” answers are exactly where the day-in-the-life sessions pay off.

    What you end up with is a defensible foundation: a real inventory of your systems, a clear-eyed map of how work moves, and a prioritized list of the duplicate work and broken handoffs costing your team time every week. That is the difference between buying a system and solving a problem. It is also the cheapest insurance you can buy before a multi-year, multi-system transformation, the documentation that keeps whoever modernizes your core systems from discovering a surprise six months in.

    Want help running this?

    We do this work with nonprofits and mission-driven organizations: mapping the current state, finding the quick wins, and building a roadmap that respects the systems you are required to keep. You can download the toolkit workbook to get started, and if you would like a hand running the discovery, or a second set of eyes on what the results are telling you, get in touch. The toolkit is yours either way.