Glossary

Key terms used across the EM-OS manual, grouped by topic. See the linked pages for full details.

Team & Organization Management

Team Topologies: A framework that defines team roles as one of four types: Stream-aligned, Enabling, Platform, or Complicated Subsystem. → Team & Organization Management
Interaction Modes: How teams collaborate — Collaboration, X-as-a-Service, or Facilitating. → Team & Organization Management
RBAC (Role-Based Access Control): Least-privilege access control via three roles — Org Admin, Lead, and Member. → Administration
Skill Matrix: A grid visualizing skill sets such as languages, frameworks, and tools. → Team & Organization Management
Team Condition: Team-wide sentiment trend and engagement, derived from 1on1 data and survey responses. → Team & Organization Management

OKR (Objective and Key Results): A goal-management method linking Objectives and Key Results across organization, team, and personal tiers. → OKR
Dynamic KR: A Key Result type that syncs automatically from data already in EM-OS [PRO Plan Only]. → OKR
Confidence Score: A 0.0-1.0 measure of how confident someone feels about hitting a goal, separate from numeric progress. Updating it during a 1on1 auto-logs the change to shared notes. → OKR
Progress Roll-up: The mechanism by which Key Result progress updates recursively propagate to parent Objectives. → OKR

ADR (Architecture Decision Record): A record of technology and architecture decisions, tracked through Proposed → Accepted → Superseded/Deprecated. → Technical Management
Four Keys: The four DORA metrics — Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service. → Technical Management
SLI / SLO / Error Budget: SLI is the measured metric, SLO is its target value, and Error Budget is the margin against that target. → Technical Management
Post-mortem: The fact-finding and prevention-planning process after an incident or SLO breach, built on Root Cause Analysis (RCA) and a Blameless culture. → Technical Management
Technical Roadmap: A mid-to-long-term plan connecting strategic themes to execution phases and concrete assets (projects, debt, ADRs). → Technical Management

Growth Loop: A model of the circular structure driving product growth, mapped as nodes and edges from acquisition through retention and monetization. → Product Management
Loop Speed: The time it takes for one full rotation of a Growth Loop, used alongside conversion rates in growth analysis. → Product Management
Delivery Analysis (Value Funnel): A funnel view of value flow from idea to delivery. → Product Management
Estimated Points: A numeric measure of a backlog item's complexity or size, used for velocity measurement. → Product Management
Throughput / Cycle Time / Backlog Health: Core Product Stats metrics — completed items per period, average time from start to completion, and the size of the ready backlog. → Product Management

Skill Ladder: Skill requirements defined across three categories (Technology, Delivery, Leadership) and grades from L1 (Junior) to L3 (Senior). → Personal & Growth
Sentiment Analysis: AI-driven analysis of positive/negative trends in 1on1 session content. → Personal & Growth
Bug Hunter: A gamification feature that turns bug reports into contribution scores and badges. → Personal & Growth
Work Log: A daily record of activities and per-project time allocation, which feeds Man-hour Analysis. → Personal & Growth

Audit Logs: Records of "who did what and when" across authentication, organization, management, and data operations. → Administration
Standard / PRO Plan: Subscription tiers — features like Dynamic KR and organization-wide Objectives are PRO-only. → Administration
Man-hour Analysis (Aggregation): Analysis of working hours and cost across the organization, teams, or projects. → Administration