Glossary

Glossary

The words Amphora Ops uses, in plain language.

Amphora OpsAmphora Ops
Our system for the organisation's work: positions and holders, processes, projects, milestones, tasks and decisions, with the facts filled in from what really happens.
Cardcard
One item on the Flow board: a piece of a release with its tasks, its stage, its owner and where to act.
Casecase
One run of a process, for example one task going from need to live.
Decisiondecision
A question put to a named person, with options and a recommendation. It stays open until that person answers.
Focus projectfocus project
The project the organisation puts first. The Board shows it first, then the others by priority.
Holderposition holder
Who fills a position: a person, an AI bot, a service or an outside party. One position can have several holders, and one holder can fill several positions.
Milestonemilestone
A part of a project with a done-check, planned dates and, once done, its actual date.
Not measurednot measured
Shown where Amphora Ops has no real event at one end of a time. It never shows 0 or a guess in its place.
Positionposition
A post in an organisational unit, with its duties and roles. A position with no holder is a vacancy.
Projectproject
A piece of work with a goal, an owner, a priority and milestones.
Stagestage
One step of the main process, from need (S0) to live (S11). A card or case is in the stage its work has reached.
Stalledstalled
A project with activity before, but none in the last 7 days.
Tasktask (row)
One unit of work, also called a row. It has a key, an owner, a state and, when a person owns it, the link to where they act.
Unitorganisational unit
A part of the organisation. Units form a tree, and every position belongs to one unit.
Where to actaction URL
The link to the page where the owner of a task or decision does the work: a signing page, a document or an Amphora Ops view. When a person's task has none, Amphora Ops shows that it is missing.