Effective leaders recognize that not all challenges are alike, and not all challenges require the same kind of leadership. Some problems can be solved by applying existing knowledge and expertise. Others require people to rethink assumptions, change behaviors, and learn new ways of working. Still others demand flexibility, experimentation, and the ability to respond quickly as circumstances evolve. Technical, adaptive, and agile leadership represent three complementary approaches to navigating these different challenges.

Technical leadership is most effective when a problem is relatively clear, the desired outcome is known, and the expertise or resources needed to address it are available.

Key characteristics 

• Relies on expertise, established practices, and proven solutions.
• Emphasizes efficiency, consistency, reliability, and execution.
• Defines clear goals, responsibilities, timelines, and expectations.
• Measures success through tangible outcomes and completed tasks.

Examples in a church or nonprofit setting

• A church's heating system fails. Leaders hire a qualified contractor to diagnose and repair the equipment.
• A congregation needs a new database. Leaders research software, select a platform, train staff, and implement it.
• A nonprofit needs to comply with updated financial reporting requirements. Leaders consult experts and revise procedures.

The leader's primary question: What do we already know that can help us solve this problem?

Potential limitation: Technical leadership becomes insufficient when leaders try to solve deeply rooted cultural or behavioral challenges simply by introducing new policies, programs, or procedures.

Core focus: Mobilizing people to confront difficult realities, challenge assumptions, learn together, and change their thinking and behavior.

Adaptive leadership, associated with Ronald Heifetz and Marty Linsky, is essential when existing solutions are inadequate and progress requires people to change—not simply their processes, but their priorities, relationships, habits, or expectations.

Key characteristics

• Recognizes that complex challenges rarely have simple solutions.
• Encourages reflection, curiosity, experimentation, and shared learning.
• Helps people navigate uncertainty, resistance, conflict, and loss.
• Distributes responsibility for change rather than expecting leaders to provide all the answers.
• Addresses underlying beliefs, values, loyalties, and organizational culture.

Examples in a church or nonprofit setting

• Worship attendance has declined for years. Rather than simply changing worship times or advertising more, leaders help the congregation explore how people's relationships with faith communities have changed and what new forms of ministry might be needed.
• A church struggles to engage younger generations. Leaders invite younger adults into meaningful conversations and decision-making, reconsider inherited traditions, and experiment with new ways of forming relationships.
• A nonprofit has become overly dependent on its founder. Leaders help staff and board members redefine authority, distribute ownership, and develop a healthier leadership culture.

The leader's primary question: What do we need to learn, rethink, or change to move forward?

Potential limitation: Adaptive leadership can create anxiety and resistance because people may need to relinquish familiar practices, privileges, expectations, or identities. It requires patience, courage, and sustained engagement.

Core focus: Leading with flexibility, responsiveness, and continuous improvement in rapidly changing or unpredictable environments.

Agile leadership emphasizes shorter planning cycles, decentralized decision-making, experimentation, feedback, and the ability to adjust direction without losing sight of the organization's mission.

Key characteristics

• Responds quickly to emerging needs, opportunities, and challenges.
• Uses small experiments and pilot projects rather than relying exclusively on long-term plans.
• Encourages collaboration, shared ownership, and empowered teams.
• Values feedback, learning, iteration, and continuous improvement.
• Maintains a clear sense of purpose while remaining flexible about methods.

Examples in a church or nonprofit setting

• A church wants to reach young families. Instead of launching a large new ministry immediately, leaders pilot three family-oriented gatherings, gather feedback, and refine the approach.
• A nonprofit experiences a sudden increase in demand for services. Leaders reorganize teams, adjust priorities, and test new service-delivery methods.
• A congregation wants to improve its hospitality. Leaders experiment with new guest follow-up practices over 30 days, evaluate results, and expand what works.

The leader's primary question: What can we try now, what can we learn, and how should we adjust?

Potential limitation: Without a clear vision and shared priorities, agile leadership can deteriorate into constant activity, frequent changes in direction, and initiative fatigue.

Consider a congregation experiencing declining worship attendance and decreasing engagement among younger adults.

• Technical response: Improve existing systems - Analyze attendance patterns, update the website, improve communications, provide better signage, and adjust worship schedules based on attendance data. The desired outcome is to remove identifiable obstacles to participation.
• Adaptive response: Rethink how ministry happens - Engage members and neighbors in conversations about belonging, faith, changing generational expectations, and the congregation's purpose. Explore what traditions may need to evolve and how leadership might be shared differently. The desired outcome is to develop new mindsets, relationships, and ministry practices.
• Agile response: Pilot new possibilities - Launch a 60-day experiment involving monthly community meals, a parent connection group, or neighborhood gatherings. Collect feedback, assess participation, and refine the most promising ideas. The desired outcome is to discover what works through practical experimentation.

The strongest approach integrates all three: technical leadership improves the systems, adaptive leadership addresses the deeper changes required, and agile leadership enables the congregation to test and refine new approaches.

These are complementary leadership capabilities, not competing leadership styles or necessarily sequential stages. Effective leaders develop the capacity to move among these approaches based on the nature of the challenge.

A technical solution might be essential to make an adaptive change possible. An adaptive conversation might reveal the need for a new agile experiment. An agile pilot might uncover a technical issue that can be addressed using existing expertise. The key is diagnosing the challenge before deciding how to lead.

1 | Do we already know how to solve this problem? If so, a technical approach may be sufficient.

2 | Does meaningful progress require people to change their assumptions, priorities, relationships, or behaviors? If so, adaptive leadership is needed.

3 | Are circumstances changing so quickly that we need to test ideas and adjust along the way? If so, agile leadership will be valuable.

4 | Who needs to participate in developing the solution? Technical challenges may require specialized experts, while adaptive challenges require the people affected to participate in the work.

5 | What would meaningful progress look like in the next 30–90 days? This question helps translate insight into action, especially through agile experimentation.

For pastors, nonprofit executives, and other organizational leaders, these approaches suggest three important leadership commitments:

• Be competent enough to address technical challenges. Build systems, clarify expectations, leverage expertise, and follow through on commitments.
• Be courageous enough to address adaptive challenges. Name difficult realities, invite diverse perspectives, tolerate discomfort, and help people embrace necessary changes.
• Be flexible enough to lead with agility. Encourage innovation, empower others, experiment with new approaches, and adapt based on what you learn.

These commitments also require leaders to be grounded, self-aware, and less reactive. When leaders are anxious, they may rush toward technical fixes, avoid difficult adaptive conversations, or make impulsive changes in the name of agility.

One of the most important skills leaders can develop is the ability to distinguish between a problem that needs fixing, a challenge that requires transformation, and an opportunity that calls for experimentation.

• Technical leaders ask, "How do we fix it?"
• Adaptive leaders ask, "How must we change?"
• Agile leaders ask, "What can we try and learn?"

Leaders who can ask all three questions are better equipped to navigate uncertainty, cultivate healthy organizations, and help people move toward a preferred future. The goal isn't to become a technical, adaptive, or agile leader. It's to become a leader who knows when and how to use all three.