Digital Transformation Is an Operations Issue

If your nonprofit is choosing a database, project platform, or AI-supported workflow, start with the process the technology needs to support.

What should happen, who owns it, and which decisions need human authorization?

A platform may help route work, apply configured rules, or make information visible. But someone still needs to decide which rules and responsibilities are appropriate.

Map one workflow

Choose a process the new tool is supposed to improve. Walk through a recent example with staff who perform and receive the work.

Record:

• The starting request and completed outcome.
• Required information.
• Owners and decision-makers.
• Approvals and exceptions.
• Current tools and records.
• Waiting points and repeated entry.

If you need a starting method, use the workflow bottleneck review.

Turn the map into requirements

Replace broad expectations such as “improve collaboration” with observable needs.

For a hypothetical referral workflow, requirements might include:

• Assign each referral to a named owner.
• Show whether required information is missing.
• Distinguish pending review from accepted referral.
• Limit access according to approved responsibilities.
• Preserve a usable record of the next action.

Confirm privacy, security, accessibility, contractual, and other applicable requirements with the responsible specialists. A workflow walkthrough does not replace those reviews.

Test a scenario, not just a demonstration

Ask staff to complete an ordinary case and an exception using fictional or appropriately approved information.

Can they identify the next step? Does the receiving person have what they need? Is it clear who may authorize an exception?

A polished demonstration is different from evidence that your team can use the configuration.

If staff return to email or a separate spreadsheet, ask why. The cause may be the workflow, configuration, access, usability, training, or another constraint.

Plan for use after launch

Name the process owner, the person responsible for configuration changes, and the source of current guidance.

Provide supported practice and a way to report problems. Set an early review to decide what needs adjustment.

You do not need a perfect workflow before adopting technology. You need enough agreement to know what the tool should support and whether it is helping.

---

P.S. Curious about the financial cost of how work gets done? I put together an operations and funds check. Take the Operations & Funds Check