Johannes Immanuel Schneider

Inclusion · Faith · Society

Select language / Languages

Practical guide for church leaders

You want a more inclusive community and see tasks everywhere? A clear timeframe can help you move from wish to action. Not everything will be finished in 90 days. But you can begin reliable changes and learn how to continue working on them.

This guide provides a work plan. Adapt the scope and pace to your capabilities. The involvement of people who experience barriers is essential from the outset.

Agree on responsibilities before starting

Within the management team, appoint a coordinator and at least one other person who will support the decision. Clarify which decisions the team can make independently and which expenditures require approval.

Formulate a clear and understandable goal: "People should be able to find our visitor information and use the next event more independently." Such a goal is easier to work towards than the desire to become more inclusive in general.

Days 1 to 20: Listen and explore a possible path forward

Invite feedback voluntarily. Offer both oral and written communication channels. Ask about specific situations, not a complete biography.

Parallelly examine the path of participation from the first indication to the departure. Where is information lacking? Which obstacles are known with certainty? Distinguish between observations and assumptions. Document personal information only to the extent necessary and with a clear and transparent approach.

Days 21 to 35: Choose two priorities

Rank the identified barriers according to how strongly they hinder participation and what you can realistically change. Choose one short-term task and one that requires more preparation.

For example: Revise visitor information and check for suitable technical support. Discuss the selection with the people involved. Explain which issues can be addressed first and how you will follow up on them.

Days 36 to 65: Implementation with clear responsibilities

For each task, you need a responsible person, a deadline, and a verifiable result. "Someone will take care of the website" remains vague. "The verified access credentials will be published by the deadline" is more specific.

Meet briefly and regularly to coordinate. If an obstacle cannot be resolved independently, seek appropriate expert advice. Avoid making hasty promises about structural or technical solutions that have not yet been tested.

Days 66 to 80: Check actual usage

Test the revised services with volunteers. Can anyone find the information they're looking for? Is registration possible? Does the agreed-upon on-site support work?

A single test doesn't prove complete accessibility. It gives you specific indications. Also ask about difficulties you hadn't considered. Plan time for improvements.

Days 81 to 90: Joint evaluation and further planning

Document what has changed and what remains open. Clearly explain to the community what they can use in the future. Honestly define existing limitations.

Agree on the next review period and a realistic budget. Examine whether people with disabilities can continue to participate in decision-making or whether they have only been asked about their experiences so far. Participation should extend beyond the project launch.

A template for your team meeting

For each task, note down five pieces of information: the specific barrier, the desired change, the responsible person, the deadline, and the form of feedback. Also note who will be reviewing the impact with you.

Start with a task you can realistically manage. A reliably completed step builds trust. In this way, a 90-day plan can become a habit that permanently transforms your community.

Continue working together

Team development and bridge building

Go to the knowledge library with further practical guides