jdcr256 wrote:I don't understand the "it doesn't work the way I want, so prove to me you are working on something valuable" position.
I did not mean to indicate that it was not working the way I want, I thought I plainly laid out my argument that it doesn't seem to follow the direction the brethren are driving in the local units, Bishops, Ward council, etc... Here's the quote "I don't think the priorities are aligned with the greater message behind the push" If one stops to consider the argument, and look at the 5 quarters worth of improvement in this specific tool, I believe the request to publish or share in some way a roadmap is a valid request (which btw was also not part of a response, though it is a good and valid request as well). If it is just plain much harder than we previously indicated, that's fine. If there is a requirement for CDOL to release new code, and for MLS to get to version x.x.x (which won't be until Nov 2011) before we can devote any more time to it, these are simple things for us to grasp, let us in on the plan.
Additionally, I do realize the broad assumptions I'm making, however, it is assumed that I don't understand the complexity behind the solutions, and I respectfully disagree. This board reaches a broad mix of experts in many fields, mine happens to be in infrastructure management and hosting services for data centers all over the globe, the complexity is not lost on some of us. Again, I would only comment that this can all easily be solved with information.
We have clients all over the world... we spend countless hours invested in roadmap discussions with our clients, it helps us improve our services, it helps them prepare for upcoming service enhancements and availability... I realize there are some counter-arguments here... it's not like church members can pick a different church's service offerings (wow would't that be an interesting thought), but that is a different part of the problem for another time.
I'll give you an example. We work with 2 different FM groups in our stake, we've gone through a lot of pain implementing a system recently for submitting work orders, etc... Many volunteer hours were spent on this, training, etc, if we had any idea that the FIR system was being built, and if we had a list of requirements that were being assembled, we may have made the decision to hold off the development of our system to wait for what the church is delivering or we could've easily modified ours so that when the new solution is rolled out, our system would transfer easily to the official one. Maybe what we came up with will transfer easily anyway, but with a little knowledge members of the church can be more strategic in what we do. We can be your partners in this, I would think that the church would want it that way.
I've said it in other posts, I don't think you'll find a greater advocate for all the church development efforts over the last 6-7 years, I've watched our online presence make rapid improvements, and been a strong advocate in our stake and other stakes for adopting the technologies to drive the use of these tools down to the least of these, please know I personally appreciate all your efforts.
“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”
― Thomas Paine, Common Sense