Differences

This shows you the differences between two versions of the page.

--- emerson:stone-soup:digital-infra-overhaul [2025/04/01 16:11] – created (correct content this time) naptastic
+++ emerson:stone-soup:digital-infra-overhaul [2025/04/29 15:05] (current) – naptastic
@@ Line 1: / Line 1: @@
 ====Digital Infrastructure Overhaul====
     * Involving the current stakeholders sounds hard but it's completely doable.
       * Need a list of who owns what
       * **ASYNC** Brainstorming session on how to provide all the church's digital needs
-    * We Probably Need Jira (sorry)
+    * We need a task management system; Hilary suggests Asana
-    * Wiki needs to have everything in it. We need to "write the book" on this church.
-      * Maps
-      * Directory
-      * Org chart - needs to have links to personal directory
-        * Executive / C-positions
-        * List of committees, members, and responsibilities
-      * Calendar
-      * Playbooks (specifically, the instruction manual for Westwood Hall needs... yeah)
-      * Archives and links
-      * History
-        * There's a book of old member sermons in the Ready Room that ought to be digitized
     * Aim for Discord until we find something better. **It's going to take a long time for communications to converge and I'm sorry.** I'm doing my best. Some people are going to be stuck on Zoom, Signal, and Facebook until we have something that actually ticks all the boxes.
     * User accounts
@@ Line 21: / Line 10: @@
     * I have another computer for the work room
     * Network upgrades
+====Worship Workflow App====
+Ed's template-based system is genius. The weak points are the result of how it's implemented. To fix the pain points and get the flexibility and usability we need, it really needs to be an app.
+This is something I have to manage myself. I have zero faith that another project manager could get it done without hiring an entire team and **we don't need that**. The way to get the app developed and delivered successfully is to get the smallest team possible of the right people. We don't have those people yet, and the theorycrafting piece explaining how this is all going to work (and how we're going to avoid all the traps that app development usually falls into) isn't written yet. I'll have it before we need it.
+====The Book On The Church====
+===Org Chart===
+  * needs to have links to personal directory
+     * Executive / C-positions
+     * List of committees, members, and responsibilities
+     * connections with other orgs, churches, etc., as part of our organizational chart. Liaisons and their relationships need to be listed.
+(Change language of "committee", "team", "ministry", and perhaps a few other terms. There are times and reasons for each word. We need to change a few around in order to get the results we want. More later.)
+  * Maps
+  * Directory
+  * Calendar
+  * Playbooks (specifically, the instruction manual for Westwood Hall needs... yeah)
+    * The checklists from which we operate need to come from a single place. The workflow for "being in charge of a service" needs to start with making a copy of the appropriate checklist.
+  * Archives and links
+    * There's a book of old member sermons in the Ready Room that ought to be digitized
+  * History
+    * Somebody wrote a history that's complete up to ??? years ago. It should be digitized, and I should read it.