Give them only what they need
I have to agree with Dave @ BetaChurch.org regarding . Here is the specific quote:
I have seen many user groups and congregations have the same reaction to a new idea, design or technological solution. The solution providers impliment a system with out testing it with the user group. They launch the design that they are so proud of, with all of the bells and whistles, with all of the fancy widgets, code, and multimedia.
And the congregation receives the solution and they ask, in horror, what is this thing? Can this monstrosity really exist? Please, put it out on the street so that the garbage man can come and take it away.
I think this really expresses the intent of being an Agile Ministry – implement exactly what is needed, not only because you may not know tomorrow’s exact needs, but also because people dislike change. It is easier to introduce slow change and get buy-in at each stage, than to put it all out there.
The other side effect: you can get input before assuming the way someone plans on consuming your ministry or a service of your ministry. Then, adjust as you go rather than forcing people to use what has already been implemented or throwing away a lot of effort. This is the biggest problem with software development (my profession): developers assume they know what the customer wants, and customers assume the developers can read their mind and/or intent.
Deliver early, deliver often, get buy in each step of the way, and don’t assume you know what people want or that people will tolerate the change.
Popularity: 1% []
[...] r church leader, or simply as a volunteer in your church, where do you see difficulties or change that might stop your vision from being realized? How are you leading to the finish line, rather than the [...]