Tech Workplace Dictionary

Specific observable conditions that a change must satisfy to be accepted.

A specific follow-up task assigned to an owner with an expected outcome.

The documented inputs outputs behaviors and guarantees consumers can rely on from an API.

The scope of systems users or functionality that could be affected by a failure or change.

An issue that prevents meaningful progress on a task or outcome.

Work performed within or around an existing system and its constraints.

Active support or commitment from people needed to make a decision succeed.

A sequence of processes that moves transforms and validates data from sources to destinations.

Something a task system or team relies on to complete its work.

A shared collection of design principles components patterns and standards for building consistent experiences.

A manager responsible for the health effectiveness and delivery environment of an engineering team.

The gradual addition of features that makes a product more complex than its purpose requires.

The recommended supported way to complete a common engineering task.

A project built without significant constraints from an existing implementation.

An unplanned event that degrades or interrupts a service or business operation.

A professional role focused on direct craft or domain contribution rather than people management.

A quantitative measure used to monitor behavior performance or progress.

An architecture that divides a system into independently deployable services around capabilities.

A durable advantage that makes a business difficult for competitors to copy or displace.

An application whose major capabilities are deployed as one integrated unit.

A recurring private meeting between two people often a manager and direct report.

A decision that is difficult expensive or impossible to reverse.

A well-supported technical path that makes preferred practices easier to adopt.

A reusable strategy and set of actions for handling a broader situation.

The relative importance and order assigned to work when resources are limited.

A preliminary model used to explore or test how a product or interaction might work.

A proposal to merge a set of code changes into another branch.

A required set of checks or criteria that must pass before work advances to the next stage.

A previously working behavior that breaks after a change.

A documented procedure for diagnosing or handling a recurring operational situation.

Uncontrolled expansion of work after a project begins without corresponding tradeoffs.

A classification of how much impact an incident or defect has.

A component whose failure can stop an entire critical system or workflow.

A meeting between an employee and a manager above their direct manager.

A person or group affected by a decision or able to influence its outcome.

A structured description of assets attackers trust boundaries threats and mitigations for a system.

Manual repetitive operational work that scales with service growth and creates little lasting value.

Evidence that a product or business is gaining meaningful adoption demand or momentum.

A decision that can be reversed at acceptable cost after learning from the outcome.

A short description of desired value from the perspective of a user or stakeholder.

A weakness that can be exploited to compromise confidentiality integrity or availability.

A simplified representation of a screen's structure content and interaction without final visual detail.

The amount and mix of work assigned to a person team or system.