Some projects are naturally easy to rally around.
A new program launch, community event, brand refresh, or major public announcement can generate immediate excitement. People can see the outcome, understand why it matters, and feel energized by the opportunity to contribute.
Other projects are harder to sell.
Updating internal processes, cleaning up data, implementing a new system, documenting procedures, improving reporting, or changing how teams manage their work may be essential to an organization’s success. However, these projects do not always feel exciting, especially when employees are already balancing fundraising campaigns, program delivery, grant deadlines, board meetings, and everyday operational demands.
When a project is not the most visible or enjoyable priority, engagement rarely happens automatically. It has to be intentionally built into the way the project is planned and managed.
Lack of Engagement Does Not Always Mean Resistance
When people miss meetings, delay assignments, or respond slowly to project requests, it can be tempting to assume they do not care.
In many cases, the real issue is capacity.
Nonprofit employees are often responsible for multiple functions. A team member may be supporting a new project while also managing programs, responding to funders, preparing reports, helping with events, and addressing urgent community needs.
The project may be important, but it is competing against work that feels more immediate.
Other team members may not understand how the project connects to their role. Some may agree with the overall goal but feel frustrated by the process. Others may worry that the project will create more work, introduce unfamiliar technology, or change routines that already feel manageable.
Before labeling people as disengaged, project leaders should understand what may be sitting underneath their behavior.
Explain Why the Project Matters Now
Leadership may understand why a project is important, but the rest of the organization may only see another request added to an already-full workload.
People are more likely to participate when they understand:
What problem the project is solving
Why the organization is addressing it now
What happens if nothing changes
How the project will benefit staff, programs, or the community
What success will look like when the work is complete
For example, “We are implementing a new project management platform” may not inspire much enthusiasm.
A more meaningful explanation might be:
We are creating one reliable place to see deadlines, responsibilities, and project decisions so staff members spend less time searching through emails and attending meetings just to understand what is happening.
The second explanation connects the project to an everyday frustration. It makes the benefit personal, practical, and easier to support.
Connect Participation to Each Person’s Role
People are less likely to engage when they are invited into a project without knowing why they are there.
Every project participant should understand:
Why their perspective is needed
What decisions they can influence
What they are responsible for completing
How much time participation is expected to require
When their involvement will begin and end
Avoid bringing people into every meeting simply because they may be affected by the project. Some individuals may need to make decisions. Others may only need to provide input at a specific stage. Some may need regular updates but no active assignments.
Thoughtful engagement respects people’s time.
It also reduces one of the biggest sources of project frustration: attending meetings where a person’s role, authority, and expected contribution are unclear.
Make the Work Easier to Prioritize
During busy periods, vague assignments are easy to postpone.
A request such as “Please review the new process” creates additional questions. What specifically should the person review? How much feedback is needed? Where should comments be submitted? When is the real deadline?
Clear assignments reduce the effort required to begin.
Instead, a project leader might say:
Please review steps three through six of the proposed intake process and add comments about anything that would not work for your team. This should take approximately 20 minutes. Please submit your feedback in the document by Thursday at noon.
This request defines the task, scope, time commitment, location, and deadline.
The easier it is to understand an assignment, the more likely it is to be completed—even during a busy season.
Avoid Treating Every Task as Urgent
When every project request is described as urgent, teams begin to tune out the message.
Project leaders should distinguish among:
Work that must be completed immediately
Work that is important but can be scheduled
Work that requires feedback rather than action
Work that can wait until a less demanding period
This requires coordination with functional leaders.
A project manager may believe a deliverable is urgent, while a department leader knows the same employee is responsible for a grant submission, major event, or board presentation that week. Aligning deadlines with the organization’s broader calendar can prevent unnecessary conflict and frustration.
Effective project management does not simply push people to complete more work. It helps the organization make realistic decisions about what can be completed, by whom, and by when.
Break Large Projects Into Visible Progress
Long internal projects can feel endless, particularly when the final outcome is months away.
Breaking the work into smaller milestones helps people see that their contributions are producing progress.
Instead of communicating only about the final launch, celebrate moments such as:
Completing stakeholder interviews
Approving requirements
Finalizing a new workflow
Cleaning the first group of records
Completing a pilot
Training the first department
Resolving a major project risk
These moments do not require an elaborate celebration. A brief message recognizing the team’s progress and naming specific contributions can help maintain momentum.
People are more likely to stay engaged when they can see that the project is moving forward.
Give People Meaningful Influence
Engagement decreases when employees feel that every decision has already been made.
Inviting people to provide input without explaining how that input will be used can make participation feel performative. Teams may stop offering thoughtful feedback when they believe leadership has already selected the answer.
Project leaders should be clear about what is open for discussion and what is not.
For example:
The organization has decided to move forward with a new intake system. The project team is asking staff to help determine how the workflow should function, what information must be collected, and what training will be needed.
This creates an honest boundary. Staff members may not be deciding whether the system will change, but they have meaningful influence over how the change is implemented.
When people can shape the outcome, they are more likely to take ownership of it.
Make Meetings Worth Attending
Unproductive meetings can quickly turn an already-unpopular project into something employees actively avoid.
Each project meeting should have a clear purpose. Participants should know whether the meeting is intended to:
Make a decision
Solve a problem
Review progress
Gather input
Coordinate upcoming work
Status information that can be shared in writing should not automatically become a meeting.
When a meeting is necessary, send materials in advance, focus the conversation on the decisions or issues that require collaboration, document next steps, and end when the objective has been achieved.
Respecting people’s time is one of the most practical ways to build trust in a project.
Ask What Is Getting in the Way
When participation begins to decline, do not rely only on reminders.
Talk to the people involved.
Ask questions such as:
Is the assignment clear?
Does the deadline conflict with another priority?
Is a decision preventing you from moving forward?
Do you have the information or authority you need?
Is the current process creating unnecessary work?
Would another form of participation be more practical?
The answer may reveal a dependency, workload issue, communication gap, or unresolved concern that the project plan did not account for.
A missed deadline is sometimes a performance issue. However, it can also be a symptom of a project management problem.
Recognize the Difference Between Participation and Adoption
A person can attend every meeting and complete every assignment without truly adopting the project’s outcome.
This is especially common with process and technology projects. Employees may help build a new system but return to their previous habits once the project team steps away.
Engagement should therefore continue beyond launch.
Teams need to understand how the new approach will affect their daily work. They may need training, job aids, manager reinforcement, opportunities to ask questions, and a clear way to report issues.
Successful projects do not end when a tool goes live or a process is approved. They succeed when people consistently use the new approach and the organization begins realizing the intended benefit.
Leadership Behavior Shapes Engagement
Employees notice what leaders consistently reinforce.
If executives describe a project as important but repeatedly cancel decisions, miss meetings, or allow competing priorities to override the work, employees will adjust their effort accordingly.
Leaders can reinforce engagement by:
Making timely decisions
Resolving conflicts between priorities
Protecting appropriate staff capacity
Communicating consistent expectations
Recognizing contributions
Using the new processes themselves
Holding teams accountable without ignoring workload realities
Visible leadership support signals that the project is not temporary background work. It is an organizational commitment.
Not Every Project Needs to Be Fun
Important work does not always need to be exciting.
Teams do not have to feel passionate about data cleanup, policy documentation, system configuration, or reporting improvements. They do, however, need to understand why the work matters, what is expected of them, and how the organization will support them in completing it.
Engagement grows when projects are well structured, participation is purposeful, assignments are realistic, and leaders respect the demands already placed on their teams.
At Okavane, we help nonprofit organizations plan and lead complex initiatives while keeping people, capacity, and organizational realities at the center of the work. We create the structure needed to clarify responsibilities, coordinate competing priorities, maintain momentum, and help teams adopt changes that last.
When an important project is struggling to compete for attention, the solution is not always another reminder or meeting. Sometimes the organization needs a clearer plan, stronger coordination, and dedicated project leadership.
If your nonprofit has an important initiative that keeps losing momentum, Okavane can help turn it into coordinated, achievable action. Feel free to contact us for a chat about your project.