Use case
Status meetings exist because the status is not visible.
A weekly hour spent collecting numbers that could have been on a page is an expensive way to read them, and it means the news is always at least a week old.
What it costs
Finding out late.
- Slippage surfaces at the review. The milestone moved a fortnight ago; the first time anybody outside the team heard was at the meeting called to discuss something else.
- The budget lives in a spreadsheet. Maintained by hand, by one person, and reconciled against reality occasionally.
- Nobody agrees what phase it is in. Planning for one person is execution for another, so estimates are compared against different things.
- Decisions lose their reasoning. The route was changed in March. Why it was changed is in somebody’s notes, which means it will be argued again.
- The board does not tell you the story. Deck is honest about cards and says nothing about whether the project is in trouble.
What changes
The project reports itself.
A project team is a Nextcloud Team with a project structure on top of it. The board stays in Deck, the documents stay in Files, and the thing that was missing, a readable statement of where the project stands, sits on the team page.
- Four phases across the top of the page, so everybody is describing the same stage with the same word.
- The Project Compass, which says what the next thing to do is when a project is new or has drifted.
- Milestones tied to Deck cards, so a milestone moves when the work moves rather than when somebody updates a slide.
- Budget and time per workstream, recorded where the work happens rather than in a separate spreadsheet.
- A health panel that shows whether the project is within bounds now, not at the next review.
- Decisions in context, attached to the project that made them, with the reason recorded.
What it is worth
At each level.
For the organisation
Oversight without a meeting.
Project health, milestones and spend are readable across projects at any time, so a review is a conversation about what to do rather than a session collecting numbers.
For the team
One vocabulary.
Everybody means the same thing by planning, execution and closing, and the milestone reflects the card rather than the summary of the card.
For the person
Work arrives in context.
A task on this project shows up in My Work with the project it belongs to, and acting on it updates the Deck card it came from.
Being clear about it
What this is not.
- It does not replace Deck. The cards stay in Deck. TeamHub reads across the boards and writes changes back to them.
- It is not a resource planner. There is no capacity model, no critical path and no dependency solver. If your projects need those, TeamHub is the wrong tool and the OpenProject integration may be the right shape instead.
- Advanced Projects needs a licence. The phases, the Compass, milestones, budget, time and the health panel are gated modules. A team home, messages, decisions and the Deck integration are not.
Make the status visible.
Tell us how your projects are tracked today and what usually surfaces late. That is normally the thing the health panel is for.