Project-management infrastructure gets a full LTP and a plan to act on

Project-management infrastructure, which covers how we plan, track and report on work across Asana, Beads and GitHub, now has a complete Logical Thinking Process analysis, built with the team (Rufus, Uriel, Fae and Asdra) over meetings on 9 to 14 October: a goal tree, a current reality tree, two evaporating clouds, and future reality, prerequisite and transition trees. See the report and the diagrams.

Goal: everyone, human and AI, knows what to do next and how we plan, record and update work, and trusts that information. It needs six things:

1. Project plans are recorded in a common way.
2. Weekly and monthly planning follows one shared process, with priority kept on initiative records.
3. Everyone knows where each kind of thing lives, reference material and tasks.
4. Each task shows what to do, who owns it, and its priority or deadline.
5. Task records stay current, with no duplicates or stale tasks.
6. Work is visible by project and per person, including to collaborators who don't use our tools.

The diagnosis found four likely root causes: no agreed rule for where each kind of work is recorded; no owner or process for team planning; two teams working in two tools (operations in Beads and GitHub, Media House in Asana); and building the system while running everything else.

What we're doing about it:

• A trial, started the week of 19 October, of one system of record per kind of work. Work that spans both teams gets one owning record that the other tool links to, and each person gets a weekly page drawn from all three tools.
• Team planning weekly or fortnightly, with Rufus and Uriel as owners and Asdra as deputy, and a fixed Thursday slot for system work that comes ahead of shipping when the two clash.
• A common shape for project records and tasks, shared AI skills, a team briefing and the How we plan and track work guide, now published in an interim version: one record per initiative and project, Asana for Media House and Beads for everything else, and the parts still being agreed marked as such.

We'll know it's done when the routing line is agreed and the team can use it, team plans are written without gaps up to the post-trial review on 3 December, most sampled tasks have an owner, next action and priority with no duplicates, every active project has a minimal record, each person works from their weekly page, and the guide is published. The full key results are on the project page.