The adoption problem
You have done the research. You have evaluated the platforms. You have chosen board management software that will save your organisation hours of administrative time, strengthen compliance, and make governance genuinely better. There is just one problem: half your board does not want to use it.
This is the adoption problem, and it kills more board software implementations than bad technology ever does. A platform that directors refuse to use is worse than no platform at all -- you end up maintaining two systems, the new software and the old email-and-paper process, doubling the administrative burden instead of reducing it.
The good news is that board member resistance is predictable, understandable, and manageable. Directors resist new technology not because they are difficult people, but because they are busy people with established habits and legitimate concerns. Understanding those concerns and addressing them directly is the key to successful adoption.
Understanding why directors resist
Before you can overcome resistance, you need to understand it. Board members resist new technology for several distinct reasons, and each requires a different response.
Comfort with existing processes
Most directors have served on boards for years or decades. They know how the current process works. Email may be inefficient, but it is familiar. Paper board packs may be wasteful, but they are tangible. Asking directors to change established habits feels like an unnecessary disruption to people who already have full schedules.
Technology anxiety
Not every director is comfortable with technology. Some directors -- particularly those from older generations or non-technical backgrounds -- worry that they will struggle with new software, look incompetent in front of their peers, or spend hours learning a system that changes nothing about the substance of their role.
Scepticism about value
Directors who have seen technology projects fail -- in their own organisations or on other boards -- are understandably sceptical. They have heard promises about efficiency and transformation before, and they have watched those promises evaporate when the software turned out to be difficult to use or poorly suited to the task.
Time concerns
Board members are volunteers in many nonprofit contexts, or at minimum, they are contributing their time alongside demanding professional roles. Any perceived increase in the time required to participate -- even temporarily, during a learning curve -- is a legitimate concern.
Privacy and security concerns
Some directors worry about the security of digital platforms. If their board materials are sensitive -- and they usually are -- the idea of moving them to the cloud can feel risky, even when the reality is that a proper board portal is far more secure than email.
The pre-launch strategy
Getting buy-in starts well before you introduce the new platform. The groundwork you lay in the weeks before launch determines whether adoption succeeds or stalls.
Involve directors in the decision
The single most effective strategy for getting buy-in is to involve directors in the selection process. When directors participate in choosing the software, they have ownership over the decision and a personal stake in its success.
You do not need every director on the evaluation committee. Two or three directors -- ideally including one who is less technologically confident -- is enough. Their involvement in reviewing options, attending demos, and providing feedback transforms them from reluctant users into advocates.
Identify your champions
Every board has at least one or two directors who are enthusiastic about technology and improvement. Identify these champions early and enlist their support. They will be your allies during the rollout, encouraging peers, answering questions, and modelling the behaviour you want to see.
Build the business case
Directors are decision-makers. They respond to evidence, not enthusiasm. Build a clear business case that quantifies the benefits of board software in terms that resonate with your board's priorities.
Focus on three arguments:
-
Time savings. Quantify the hours saved per meeting cycle. Directors value their own time and will appreciate anything that makes governance more efficient. See our detailed guide on calculating ROI on board management software for a framework.
-
Risk reduction. Explain the security limitations of your current process and how board software addresses them. Directors understand fiduciary responsibility and will take security arguments seriously.
-
Governance quality. Show how better tools lead to better-prepared meetings, more reliable follow-up, and stronger compliance. Directors who care about governance -- and most do -- will see the value.
Address concerns proactively
Do not wait for directors to raise objections. Anticipate them and address them in your initial communication.
- "Will this take more of my time?" Acknowledge the short learning curve but emphasise that the ongoing time savings are significant. Most directors become comfortable within one or two meetings.
- "Is my data secure?" Explain the security features of the platform: encryption, access controls, two-factor authentication. Point out that the current process (emailing unencrypted PDFs) is far less secure.
- "I am not good with technology." Emphasise that modern board software is designed for non-technical users. Offer one-on-one support for anyone who wants it.
The rollout plan
A successful rollout is structured, supportive, and gradual. Avoid the temptation to switch everything over in one big bang.
Phase 1: Pilot with a committee
If your organisation has committees, pilot the software with one committee before rolling out to the full board. This gives you a smaller group to support, an opportunity to identify and fix any issues, and a group of experienced users who can mentor others when the full board comes on board.
Phase 2: Introduce at a board meeting
Introduce the software at a board meeting with a brief, live demonstration. Keep it short -- ten minutes maximum. Show the three or four things directors will do most often: accessing a board pack, reading an agenda, viewing actions assigned to them, and voting on a resolution.
Do not try to show every feature. Directors need to see that the basics are simple, not that the platform is comprehensive. Comprehensiveness can be intimidating; simplicity is reassuring.
Phase 3: First real meeting
Use the software for the next board meeting. The administrator should prepare the agenda and board pack in the platform and distribute it to directors through the normal notification system. But also send a brief email explaining where to find the materials and offering help.
During this meeting, have the agenda displayed on screen from the platform. Record minutes and actions in the platform in real time. This normalises the software as part of how the board operates.
Phase 4: Full adoption
After one or two meetings, make the platform the sole channel for board materials. Stop sending board packs via email. When directors know that the platform is the only place to access their materials, adoption becomes a practical necessity rather than an optional preference.
Phase 5: Expand functionality
Once the board is comfortable with the basics -- accessing board packs, reviewing agendas, checking actions -- introduce additional features gradually. Voting and resolutions, compliance tracking, and the document repository can be introduced over subsequent meetings.
Training that actually works
Training is critical, but the type of training matters. Directors are not employees attending a mandatory workshop. They are busy people who need to learn quickly and with minimal friction.
Keep it short
Directors do not need comprehensive training on every feature. They need to know how to do three things: access their board pack, view their actions, and vote on resolutions. Everything else can be introduced gradually.
A ten-minute overview at a board meeting, supplemented by a one-page quick-start guide, is more effective than a two-hour training session.
Offer one-on-one support
For directors who are less confident with technology, offer a one-on-one session. This removes the embarrassment of asking basic questions in front of peers and allows you to tailor the introduction to their specific device and comfort level. Fifteen minutes over a phone call or video chat is usually enough.
Use their preferred device
When training directors, use the device they will actually use. If a director reads board packs on an iPad, show them the iPad experience. If they use a laptop, demonstrate on a laptop. The experience should feel familiar from the first interaction.
Provide a quick-start guide
Create a simple, one-page guide with screenshots showing the three or four most common tasks. Include login instructions, how to access the board pack, how to view actions, and how to vote. Make it printable for directors who prefer a physical reference.
Record a short video
A two-minute video walkthrough of the basics gives directors something to refer back to at their own pace. Keep it simple, use a conversational tone, and focus on the tasks directors do most often.
Handling resistance during rollout
Despite your best efforts, some directors will resist. Here is how to handle the most common forms of resistance.
The "I prefer paper" director
Some directors genuinely prefer reading on paper. This is not a trivial preference -- research shows that some people comprehend and retain information better when reading on paper.
Response: Acknowledge the preference without conceding the process. The platform can still be the single source of truth. If a director wants to print their board pack from the platform, that is their choice. What matters is that the materials are distributed through the platform, not via email, so that you maintain security, access controls, and audit trails.
The "I do not have time to learn" director
This director is not opposed to the technology -- they are overwhelmed by their existing commitments.
Response: Offer a brief, personalised introduction at a time that suits them. Emphasise that the learning curve is measured in minutes, not hours. Most directors are comfortable after a single meeting cycle.
The "This is a solution looking for a problem" director
This director does not see the need for change. The current process seems to work.
Response: Use specific examples from your organisation's recent governance experience. Was a board pack ever distributed late? Did an action fall through the cracks? Was there confusion about a resolution? These are concrete problems that the software solves. You can also point to the security gaps in current processes or the hidden costs of manual governance.
The "I have seen this fail before" director
This director has been burned by technology projects in the past.
Response: Acknowledge their experience and explain what is different this time. Modern board software is designed for non-technical users, implementation is straightforward, and the learning curve is minimal. Offer the pilot approach as a low-risk way to test the waters.
The persistent holdout
Occasionally, a director simply refuses to use the new platform. This creates a problem because maintaining two systems is unsustainable.
Response: This is ultimately a governance issue, not a technology issue. The chair should have a private conversation with the holdout, framing the platform as a board decision that all directors are expected to support. If the holdout is the chair, you have a different challenge -- one that requires patience and persistent, gentle persuasion.
Measuring adoption success
How do you know whether your rollout is succeeding? Track these metrics:
Board pack access rates
Most board portals show who has accessed the board pack and when. Aim for 100% of directors accessing the pack before the meeting within two or three meeting cycles.
Login frequency
Track how often directors log in to the platform. Regular logins indicate that directors are using the platform between meetings, not just accessing it once per cycle.
Feature usage
Monitor which features are being used. If directors are accessing board packs but not checking their actions or voting on resolutions, there is an opportunity for further training and encouragement.
Support requests
Track the volume and nature of support requests. A declining trend indicates that directors are becoming more comfortable. Persistent requests about the same issue indicate a usability problem that needs addressing.
Director feedback
Ask directors directly. A brief survey after the first two or three meetings can surface issues that metrics do not capture. Keep the survey short -- three to five questions maximum.
Long-term adoption strategies
Getting directors to use the software once is the first challenge. Keeping them engaged over the long term is the second.
Make the platform indispensable
The most powerful adoption strategy is to make the platform the only way to access board materials. When directors know that the board pack, the agenda, the minutes, and their action items are only available through the portal, using it becomes automatic.
Celebrate improvements
Share the benefits as they materialise. When board pack preparation time drops from six hours to two, mention it at a board meeting. When action completion rates improve, highlight the trend. Directors who see tangible results are more likely to remain engaged.
Keep the platform current
Nothing kills adoption faster than stale content. Ensure that the platform is always up to date: materials are uploaded promptly, actions are current, and compliance records are maintained. A platform that is clearly maintained signals that it is important.
Listen to feedback
Directors will have suggestions and complaints. Take both seriously. If a director finds a particular feature confusing, work with the vendor to improve it or adjust your training. Feeling heard reduces resistance and builds trust.
Choosing software that helps with adoption
Some board portals are easier to adopt than others. When evaluating software, consider the adoption challenge explicitly:
- Simplicity over complexity. Choose a platform that feels simple to use, even if it has powerful features under the surface. Complexity intimidates directors.
- Mobile experience. Directors who can access the platform on their tablet or phone are more likely to use it regularly.
- Vendor support. Look for vendors that provide onboarding support, training materials, and responsive help during the rollout period.
- Gradual feature introduction. Platforms that let you enable features progressively, rather than overwhelming users with everything at once, support a smoother adoption curve.
NFPHub is designed with adoption in mind: a clean, intuitive interface that non-technical directors can navigate from their first login, with progressive feature depth for administrators who need it. Try it free and see for yourself.
The payoff
Getting board member buy-in is the hardest part of implementing board management software. But it is also the most rewarding. When your board is fully engaged with the platform, you unlock the real benefits: shorter meetings, better preparation, stronger accountability, and governance that actually works.
The effort you invest in adoption pays dividends for years. Every meeting runs more smoothly. Every action is tracked. Every compliance deadline is met. And every director, including the ones who initially resisted, wonders how they ever managed without it.