Organization Unit
An Organization Unit is a node in the company hierarchy — company, division, department, team, or squad — used to own OKRs and filter execution.
Overview
Axiean models structure as a nested tree of units (not a flat department list). Units can nest to policy-defined depth. Objectives assign to units; cascading policies control how goals link across branches.
Why it matters
Without a real hierarchy, filters, ownership, and cascade become ad-hoc labels that drift from how the company works.
Examples
Company → Product → Platform squad, each with its own Objectives and optional parent links.
Best practices
- Mirror real reporting lines, not every project name.
- Start with root + a few departments; add teams when ownership needs it.
Common mistakes
Filters and cascade become noise.
Nest units; keep depth readable.
Entity relationships
This entity is a node in the Axiean OKR knowledge network. Edges below power navigation for people, search engines, and AI systems.
Parent of
Related to
Owns
How Axiean implements Org Unit
Build and edit the unit tree on Organization, open Structure from Settings, and assign Objectives to units. Depth and cross-unit alignment are controlled by strategic policies.
Frequently asked questions
Is an org unit the same as a department?
A department is one common unit type. Org units also cover company, division, team, and squad in one hierarchy.