1.  Cayuga-Syracuse Presbytery: Evaluation Results Rev. Dr. David Cleaver-Bartholomew May 16, 2015

2. Transition Pains  Before: highly structured, centralized, top down  After: minimal structure, decentralized, bottom up  Pendulum swing from one end of spectrum to the other with no transition period  Move back to the middle, recovering what was good about the prior structure while incorporating what is good about the current structure; in other words, a hybrid structure.  Fortunately, original understanding was for a transitional structure and a prototype; not definitive, not an archetype,

3. Technical Recommendations  Reevaluate and clarify Steve’s position  Communicator vs. webmaster  Administrative support  Supervisor, PPR group, payroll, reimbursements, other issues  His status within the Presbytery – can he follow his interests?  Website – more user friendly, constantly update, expand use  Communication is crucial

4. Technical Recommendations  Develop Manual on Administrative Operations  Need more detailed job descriptions for working groups  Need to develop policies and procedures for L.T. and W.G.s  Redesign the nominating, electing, and serving process  Current process (May: nominate, Oct.: elect, May: install)  Extends time commitment, unrealistic  Seek people with gifts required for positions open  Reexamine size of L.T. and W.G.s

5. Larger Issues  Gatherings of the Presbytery  Develop vision and goals  Deal with history  Leadership Team  Church Growth and Evangelism  Wisdom/Prudence of current Presbytery

6. Gatherings of the Presbytery  People are more disconnected than before  Want to be connected: “We are a connectional church”  Gathering for:  Worship – connect to the source of life, the vine  Program – equipping the saints and churches for ministry  Community – building relationships, connecting with one another  Awareness – opportunities to serve and connect, other groups  Agenda discipline – honor people’s time commitment  Not business – have separate business meetings, if practicable

7. Develop Vision and Goals  Mission Statement – necessary but not sufficient  Vision Statement  Interprets mission, unites, gives direction  SMART Goals  Specific  Measurable  Achievable  Realistic/Relevant  Time-limited

8. Deal with history  Preface and Bylaws: “This new creation depends on …”  Past continues to impinge upon the present  High level of distrust and dysfunction  Inhibits Presbytery developing and living out its mission  Address this issue; ignoring it will not lead to it going away  Presbytery as an expression of the Body of Christ  Healthy congregations, conflict mediation/resolution, stuck  Outside help: Ken Halstead, Peter Steinke, Marie Fortune, Lombard Mennonite Peace Center

9. Leadership Team  High degree of appreciation  Governing board only (no Executive Presbyter)  Important role of Leadership Team as the Governing Board  Leadership vs. management/administration  Relationship between L. T. and Working Groups  Relationship between L. T. and local church  More and better communication  Board development (study, retreat, outside assistance)

10. Church Growth and Evangelism  Mission: Equipping our churches to fulfill the Great Commission  Membership declining, no working group, no resources on website, no programs  Address the inconsistency  PCUSA resources; e.g., Presby. Mission Agency, Evangelism and Church Growth Ministries, Office of Church Growth  Programs and speakers (e.g., Diana Butler Bass)

11. Wisdom/Prudence  Numerous comments regarding maintaining the current Presbytery; e.g., dissolve, share, ecumenical partners  Is going it alone, given the Presbytery’s current size, resources, and trends the wisest/most prudent course?  Fiduciary duty to explore options, including ecumenical partners, for accomplishing the Presbytery’s mission so that when the next evaluation and decision making time comes the necessary information will be available with which to make a decision  Task force with no predetermined outcome working in the background