A sensible default is a widely applicable practice for a specific task that should be followed unless overridden by context. In software development, examples include using version control and separating UI logic from domain logic. This concept differs from "best practice" by acknowledging that defaults can and should be changed based on circumstances. The term was popularized at Thoughtworks by Evan Bottcher, who sought a phrase conveying a known-good starting point. Sensible defaults represent the expected approach in the absence of hard constraints, requiring justification if altered. Thoughtworks has documented its sensible defaults, expecting teams to know and apply them. These defaults were chosen due to their proven effectiveness across various situations. However, teams must understand their limitations and adapt them when necessary, aligning with agile principles of continuous reflection and adjustment. The company regularly reassesses these defaults, a process central to the Thoughtworks Technology Radar. The origin of the term may also be linked to Steve Bennett's writing around the same time.