Man, I am so misunderstood... I just think it's funny that EVERY Stake/ward/branch has to define this process, then when a change in admin staff happens, another process is defined, and another and another, every ward, every stake......davesudweeks wrote:100% agree. I do quality and process improvement for a living. If you don't plan the process, a process plans you. Too often we forget the links and potential failures that can occur, especially when there are multiple data hand-offs where a simple miss breaks the chain. Simplification of the steps will always yield fewer errors. With all the handoff's that used to be required to get MP ordinations properly recorded, it's a testamant to all involved that we do as well as we do.lajackson wrote:I am glad they are defining an actual process.JohnShaw wrote:I think its funny you were looking for an actual process....
I have always found it intriguing that stakes that think through and establish an actual process usually get their Melchizedek Priesthood ordinances recorded on the membership records, and rarely have to scramble to update records later when temple ordinances and missions come along.
I advocate implementing the workflow system built into the leader tools so this can happen exactly the same way in every stake. I am not advocating a random nothingness hoping that nobody creates a process.... In my mind this is needless wasted time and effort by already REALLY busy people, that could be helped by a centralized tool...