Tech Workplace Dictionary

The expectation that a person or team explains and answers for an agreed outcome.

A shared understanding of goals facts decisions roles and next actions.

The ability of a newer system version to keep working with older clients data or behavior.

A change that requires existing consumers to modify how they use a system or interface.

The degree to which responsibilities within a component belong together.

The degree to which one component depends on knowledge or behavior of another.

A system whose components coordinate across multiple networked computers.

An architecture where components publish and react to events about state changes.

A consistency model where replicas may temporarily differ but converge when updates stop.

A system's ability to continue operating when some components fail.

A system's ability to preserve its most important functions when part of it is impaired.

The property that repeating the same operation has no additional unintended effect.

A framework for understanding the progress people seek when they choose a product or solution.

The principle of granting only the access needed for a task and no more.

The ability to understand a system's internal state from the signals it produces.

Responsibility for driving an outcome including decisions follow-through and communication.

The ability of a system to perform correctly and consistently over time.

A system's ability to handle increasing load without disproportionate cost or redesign.

The future cost created when a team chooses a faster or simpler technical solution today.

A testing model favoring many fast focused tests and fewer broad end-to-end tests.

The revenue and direct costs associated with one unit such as a customer order or subscription.

A security approach that continuously verifies access instead of trusting requests based only on network location.