Types, fields, views and hierarchy
Teamhood is built from four ideas: types, fields, views and hierarchy.
Types — what an item is
Section titled “Types — what an item is”Every item has a type. A new organization starts with four.
| Type | What it is for |
|---|---|
| Project | A body of work with a start and a finish |
| Task | A unit of work, and the default child of everything |
| Issue | A problem to resolve, shaped like a Task, in its own colour |
| Risk | Something that may go wrong in a project, kept beside the project’s work |
A type decides four things: the colour an item shows and the fields it carries. It also decides what may live inside it and what happens when you open it.
A Project opens to show its children. A Task, an Issue or a Risk opens its own detail panel. Ctrl+click opens the other one instead.
You can add your own types in Settings.
Fields — what an item knows
Section titled “Fields — what an item knows”Fields hold the values on an item, such as Status, Start, Finish, Assignees, Estimate (h), Budget, Tags and Tracked Time (h). Each field is scoped to the types it applies to.
On an item, the fields sit in groups. Every item has Planning and Details. A Project adds RACI, and a Risk adds Risk assessment.
- Status drives the board columns. A status the type does not allow is refused. A Risk has two statuses of its own, Monitoring and Occurred.
- Start and Finish drive Gantt bars and Schedule bars.
- Estimate (h) and Assignees are what the schedule views read to show who is booked. Assignees takes teams as well as people.
- Health on a Project is On track, At risk or Off track.
- Accountable, Responsible, Consulted and Informed form the RACI group on a Project. Accountable is one person. The other three take people and teams.
- Probability, Impact, Risk score and Response form the Risk assessment group on a Risk. Risk score is Probability times Impact, calculated by Teamhood.
Views — how you look at items
Section titled “Views — how you look at items”A view is a saved way of looking at your items, never a separate copy of them. Change an item in one view and every other view already agrees.
See Create your first view for adding your own view.
Hierarchy — how items nest
Section titled “Hierarchy — how items nest”Any item can live inside another item.
- Progress rolls up. Complete every child and the parent completes itself.
- Context rolls down. The Project field on a task, an issue or a risk resolves the nearest project above it. Picking a different project in that cell moves the item.
- Deleting rolls down too. Deleting an item deletes everything inside it.