FREE

Course certificates are free until March 31, 2027.

PT714E Leading Through Change and Conflict

Lecture 1-2: Two Kinds of Problem: Fixing and Learning

Contents 31
PT714E Leading Through Change and Conflict
Chapter 0 · Introduction: Change Is a Road People Walk Together
  1. Introduction: Change Is a Road People Walk Together
Chapter 1 · Week 1: What Must Change, What Must Stay
  1. Lecture 1-1: The Faith and Its Clothing
  2. Lecture 1-2: Two Kinds of Problem: Fixing and Learning
  3. Lecture 1-3: Three Stories of Change in the Bible
  4. Lecture 1-4: Questions to Ask Before You Propose a Change
  5. Lecture 1-5: Practice Lab: What We Keep, What We Might Change
Chapter 2 · Week 2: People in the Face of Change
  1. Lecture 2-1: What Change Takes Away
  2. Lecture 2-2: Listening to a Congregation's Story
  3. Lecture 2-3: Generations, Languages and Cultures
  4. Lecture 2-4: Who Is Not in the Room
  5. Lecture 2-5: Practice Lab, A Change Seen from One Seat
Chapter 3 · Week 3: Walking the Change
  1. Lecture 3-1: Who Decides? Polities and Their Roads
  2. Lecture 3-2: Small Steps and Reversible Changes
  3. Lecture 3-3: Speaking About Change
  4. Lecture 3-4: Buildings, Money and Endings
  5. Lecture 3-5: Practice Lab: A One-Page Proposal
Chapter 4 · Week 4: Reading a Conflict
  1. Lecture 4-1: Conflict Is Not a Failure
  2. Lecture 4-2: Layers: Facts, Methods, Values, Relationships, Power
  3. Lecture 4-3: How Conflict Grows
  4. Lecture 4-4: Conflict or Harm?
  5. Lecture 4-5: Practice Lab: Drawing a Conflict Map
Chapter 5 · Week 5: In the Middle of It
  1. Lecture 5-1: Where a Leader Stands
  2. Lecture 5-2: Running the Meeting
  3. Lecture 5-3: Calling in Help
  4. Lecture 5-4: Where Mediation Must Not Go
  5. Lecture 5-5: Practice Lab: What I Will Say First
Chapter 6 · Week 6: After the Conflict
  1. Lecture 6-1: Forgiveness, Reconciliation and Trust
  2. Lecture 6-2: When People Leave and When a Church Divides
  3. Lecture 6-3: Rebuilding Trust and Telling the Story Again
  4. Lecture 6-4: The Wounded Leader
  5. Lecture 6-5: Practice Lab: Review and a Policy for Our Community

Jump to the key points ↓

22 min

When a church has a problem, the first instinct is to fix it. Someone is asked to find a solution. A committee is formed. A budget line is drawn. Often this works. A leaking roof is mended; a broken boiler is replaced. The problem was the kind that has an answer, and somebody who knew the answer did the work.

But some problems do not respond to this. The roof is mended, the new programme is bought, the right person is hired, and a year later the same trouble is still there. The congregation is still getting smaller, or still divided, or still tired. The fix did not fail because it was badly done. It failed because the problem was a different kind.

This lecture draws one distinction and asks you to carry it through the whole course. Some problems are solved by someone who knows how. Others are solved only when the people who have the problem learn something and change. Leaders who confuse the two cause a great deal of trouble. They also cause themselves a great deal of exhaustion.

The distinction is the work of two teachers of leadership, Ronald Heifetz and Marty Linsky, who named them technical and adaptive problems. Their books are written for leaders in government, business and organisations of every kind, not for churches. This lecture explains the idea in plain words and uses its own examples, and it does not claim that they would agree with everything said here.

What these 22 minutes give you

  • Explain the difference between a technical problem and an adaptive problem.
  • Sort a given problem by asking three questions about it.
  • Say why treating an adaptive problem as a technical one usually fails, and what it costs the people involved.
  • Describe a leader's task in an adaptive problem as helping people face it at a pace they can bear.
  • Explain why most real problems in a congregation are a mixture of both kinds.

Then I said to them, “You see the evil case that we are in, how Jerusalem lies waste, and its gates are burned with fire. Come, let us build up the wall of Jerusalem, that we won’t be disgraced.” I told them of the hand of my God which was good on me, as also of the king’s words that he had spoken to me. They said, “Let’s rise up and build.” So they strengthened their hands for the good work." — Nehemiah 2:17-18

World English Bible

I have yet many things to tell you, but you can’t bear them now." — John 16:12

WEB

Nehemiah names a problem and invites the people into the work of solving it. Jesus, speaking to his disciples, says that there is more to tell them and that they are not yet able to bear it. Between them the two verses make the two halves of the lecture: a problem has to be named, and it has to be named at a pace people can carry.

1. A technical problem has an answer that someone already has

A technical problem is one for which the knowledge to solve it already exists. An expert, a manual or an earlier experience of someone else contains the way through. The people with the problem do not have to change their minds or their ways. They have to find the right person, give the right instruction and wait for the result.

Here is an example (an invented example). A congregation has outgrown its car park. On a Sunday, cars are left along the narrow road, and the neighbours have begun to complain. This is a technical problem. A surveyor can measure the site. A neighbour may offer a field. The council, the diocese or the board can be asked what is allowed. Someone can mark out spaces more efficiently. Not everything is easy, and some of it costs money. But the way forward is known. The right expert and a decision will settle it.

Technical problems are not small problems, and they are not unimportant. A building that is unsafe must be made safe. A church treasurer who needs a better system of accounts needs someone who knows accounting. When a problem is technical, the humble and sensible thing to do is to call in someone who knows.

2. An adaptive problem is solved only when people change

An adaptive problem is one for which no one holds the answer in advance. Whatever the solution is, it will require the people who have the problem to change something: their habits, their expectations, their loyalties, or the way they see themselves. No one can do the work for them. An expert can help, but cannot take the place of the people.

Here is the second example (an invented example). The same congregation has no families with young children. The members are grateful for their friends and are warm to visitors, and there is real concern about the future. This is an adaptive problem.

Think about what would be needed. A congregation might have to accept that the service will sound and feel different from what it has loved. It might have to accept that children will be noisy during prayer. It might have to share rooms and money and a seat in leadership with people who have different tastes, and it might have to risk the loss of some who will not stay. It might also have to look honestly at why young families have not come, which may be a question the congregation does not want to hear answered.

None of that can be bought. If the congregation hires a children's worker and puts a leaflet through doors, and nothing else changes, the family who comes on one Sunday will find a welcome and a service that does not make room for them. They will not return. The congregation will then say, "We tried," and be sincere, and be hurt.

The difficulty here is not carelessness. It is that the real problem was not "no children's worker." It was that a community had to learn what it was prepared to put down in order to receive people it had not yet met. That is a question about what the community treasures. It is the central question of this course.

3. The common error

The usual mistake is to treat an adaptive problem as if it were technical. It is understandable. A technical solution is quick, visible and comfortable. It lets everyone feel that something has been done without anyone having to change. A committee can be formed, a report written, a person hired, and the real question left unasked.

There are reasons for this, and none of them is wicked. The people who ask for a quick answer are often anxious, and a quick answer calms anxiety. A leader may be anxious too, and the leader's own sense of being useful depends on providing an answer. A congregation that has no one to give it an answer can feel as if it has no leader at all. And people who are asked to change are asked to put down something they treasure. It is natural to prefer a solution in which that is not required.

But the cost is real. The fix does not work, and people lose faith in the leaders who offered it. The real problem remains, and grows. And some, who have quietly known all along what the real question was, conclude that nobody is willing to say it aloud.

There is a mirror-image mistake. A leader can treat a technical problem as though it were adaptive, a long meeting about a matter that a competent person could settle in an afternoon. This wastes goodwill and tires people. Part of a leader's wisdom is to say, "This one just needs doing."

4. Three questions for sorting

You do not have to reach certainty. Three questions will usually show where a problem lies.

First: does someone already know the answer? If a qualified person can say, "Here is what to do," the problem is probably technical. If the best expert you can find says, "That depends on what your community is willing to do," it is probably adaptive.

Second: when the solution is installed, will anyone have to behave differently? If the answer is no, because a roof, a system or a contract does the work, the problem is technical. If the answer is yes, because people must give up a habit, share a space, accept a leader or change a custom, it is adaptive.

Third: who has to change? In a technical problem, mainly the person doing the fixing. In an adaptive problem, the people who have the problem, and that includes the leader.

You will often find that a problem has both kinds inside it. A building project has technical parts (plans, permits, contractors) and adaptive parts (what the building will say about who the church is for, and who will lose a room they loved). A good habit is to split the problem and ask of each piece, "Which is this?"

5. The leader's work in an adaptive problem

If an adaptive problem cannot be solved by the leader, what does the leader do?

The answer given by Heifetz and Linsky, put in plain words, is something like this: the leader helps the people face the problem, keeps the question in front of them, and manages the pace so that the work is hard enough to be real and not so hard that people break or flee. The leader does not carry the problem for them. A leader who does so removes the very learning the problem was meant to produce.

That means four plain tasks.

Name the real problem. Say what the problem is, in a way people can recognise. Nehemiah did this. In the passage quoted above he told the people what they could all see: “You see the evil case that we are in, how Jerusalem lies waste, and its gates are burned with fire” (Nehemiah 2:17). He did not offer a plan until the problem was shared. The people answered, “Let’s rise up and build.” Their agreement did not mean there would be no further trouble, as the story shows, but the problem had become theirs and not only his.

Hold the question open. When the answer is not yet known, resist the urge to supply a false one. A leader in this position may need to say, "I do not yet know. Let us find out together." That sentence costs something, because it admits that the leader's role is not to know everything. It is also the honest thing to say.

Set the pace. Jesus said to his disciples, “I have yet many things to tell you, but you can’t bear them now” (John 16:12). It would be wrong to use this verse as a rule for how fast any change must go. But it shows that even the Lord of the church did not say everything at once, and did not treat the limit of his hearers as a fault in them. A leader reads how much the people can take. Too much, too quickly, and they stop listening or leave the room. Too little, and the problem will wait for the next generation.

Give the work back. When someone brings the leader a problem that belongs to the community, the leader's help is to give it back with a question: "What do you think we should do?" This is not a refusal to care. It is a refusal to take away someone's part in the learning.

6. The balcony

Heifetz and Linsky use a picture of a dance floor and a balcony. On the dance floor you are part of the action. You cannot see the whole pattern. From the balcony you can see where people are moving and where they are stuck. A leader needs to be able to step back from the argument, even for a moment, and ask, "What is really going on here?" The practical form of this is to ask the three sorting questions in a quiet hour before the meeting and not for the first time during it.

7. What this lecture does not say

It does not say that every problem is spiritual and therefore slow. It does not say that experts are unimportant. It does not say that people who resist a change are only afraid. Some resist because they see a real danger that the leader has missed.

It also does not say that an adaptive problem has no technical help. An outsider with training can sometimes help a community to see itself, and later lectures will say when to ask for that. But no outsider can do the learning for the people who have to change.

It also does not teach how to move a congregation through stages of a change plan. That is taught in other courses of this school, and Leadership (PT702E) and Christian Leadership (PT705E). This course asks something earlier: before you plan a change, what kind of problem do you have?

8. Back to the central claim

Now the central claim of the course can be said more sharply. Change asks people to put down something they treasure. In a technical problem, nothing a person treasures is asked of him, so a technical fix goes quietly. In an adaptive problem, something is. That is why such a problem is hard, and why a leader who understands it does not hurry to a solution. The first work is to find out what is being asked of whom.

The next lecture turns to Scripture to see how three communities in the Bible faced a change, and what we may learn from them and what we may not.


Diagram 1. Technical and adaptive, side by side

Two Kinds of Problem Fixing a technical problem and learning through an adaptive one Question Technical problem Adaptive problem Who has the answer? An expert or a known method already has it. Nobody yet. The answer has to be found by the people involved. What solves it? A decision, a purchase, a repair, a new rule. A change in habits, expectations, loyalties or ways of seeing. Who must change? Mostly the person who does the fixing. The people who live with the problem, including the leader. What is the right pace? As fast as the work allows. The pace people can bear. Too fast and they push back or go quiet. A technical problem Too small a car park. Measure, ask the neighbours, mark the spaces. Experts can help. (an invented example) An adaptive problem A congregation with no young families. No purchase solves it. People must learn what they will put down. (an invented example) The usual error: treating an adaptive problem as if it were technical.

Diagram 2. Sorting three situations (invented examples)

Situation Technical, adaptive or both? What gives it away
The roof of the hall leaks Technical An expert knows how to mend it. Nobody must change.
Two language groups hold separate services and rarely meet Adaptive No purchase will join them. People must learn to share a table.
The congregation must replace a heating system and shares the cost among members Both The system is technical. How the cost is shared tests people's trust.

In short

  • A technical problem has an answer that someone already holds. An adaptive problem is solved only when the people who have it learn and change.
  • Three sorting questions: does someone already know the answer, will anyone have to behave differently, and who has to change?
  • The usual error is to treat an adaptive problem as technical. It feels like progress, but the real question is left unasked.
  • A leader names the real problem, holds the question open, sets a pace people can bear, and gives the work back.
  • Nehemiah named the problem before he offered a plan. Jesus did not say everything at once.
  • Most real problems contain both kinds. Split them and ask of each part which it is.
Front Back
Technical problem The answer already exists in the hands of an expert. Nobody has to change.
Adaptive problem Solved only when the people with the problem learn and change.
The usual error Treating an adaptive problem as a technical one.
The leader's task Name it, hold it open, set the pace, give the work back.

One sentence to remember If a problem is solved only when people change, no expert can solve it for them, and a leader's first work is to help them face it.

This week's action Take one problem your community has met before and split it into its technical part and its adaptive part, then write one sentence on who would have to change.

Review every summary in this course →

Check yourself

Not "did you read it" but "can you explain it". Ticks are kept on this device only.

Reflection and discussion

  • Think of a problem your community has faced for a long time. Which kind is it? What makes you say so?
  • Why is a technical fix attractive to an anxious leader? What does it let the leader avoid?
  • In Nehemiah 2:17-18, what did Nehemiah do before he proposed a plan? What was the effect on the people?
  • What would it mean for a leader to "give the work back" to a committee that wants the leader to decide?
  • Can you think of a time when a problem was treated as adaptive when it was only technical? What did it cost?
  • John 16:12 shows the Lord setting a pace. What might the "many things" be in your community that people cannot yet bear?

Sign in to write and keep your answers

What next

The lecture ends here. What follows was written by its readers.