GODS Framework

GODS Framework (Goals, Obstacles, Deliverables, Success)

GODS (Goal–Overview–Definition of Done–Solution) is a comprehensive framework for clear and precise task formulation that connects work with measurable value and ensures completion is observable through verifiable criteria.

The framework provides a structured approach to task definition by requiring four essential components: a measurable Goal tied to business value, an Overview of the current situation with risks and dependencies, a clear Definition of Done with verifiable criteria and artifacts, and at least one Solution option with described risks and assumptions.

What it is

GODS is a framework for formulating tasks through goals, context, verifiable completion criteria, and solution comparison. It helps connect work with value and make completion observable.

Core Principles

• Goal: Must be measurable and tied to value/benefit
• Overview: Describes current situation, root causes, risks with mitigations, and dependencies
• Definition of Done (DoD): Quantitative, verifiable criteria tied to artifacts/locations
• Solution: At least one option with described risks and assumptions

Structure

• Goal: Metric with units, baseline, target value, and deadline; explicit value
• Overview: Context, causes, key risks (probability/impact, mitigation owners), dependencies
• Definition of Done (DoD): List of verifiable criteria, artifacts, and check locations (PR, tests, dashboards, files)
• Solution: ≥1 option with described risks and assumptions

Error Verification Checklist

Critical

• No goal or goal not measurable/without value
• Missing DoD or it's unverifiable (no artifacts/locations)
• No baseline/target value/deadline
• Single prescribed solution without described risks and assumptions
• Automatic failure: slogan/fixed plan ("Do X") without context and DoD

Error

• Overview without causes/risks/dependencies or without mitigations and owners
• Metric without units/data source; metric inconsistency
• DoD describes process instead of result or contains conflicting criteria
• Options not described with risks and assumptions
• Goal not connected to value/strategy

Warning

• Vague formulations ("fast", "quality") without measure
• No risk prioritization; superficial alternatives
• Artifact locations/links not specified; no task owner
• Excessive implementation detail not affecting result

Minor

• Inconsistent terminology or section labeling
• GODS order violated without reason; bureaucratese

Info (Improvements, not mandatory)

• Metrics table; risk registry; options matrix (cost/benefits)
• Tags for grouping; links to data sources/dashboards; review agreements

Example

This example shows how GODS works for software development tasks: implementing dark mode feature with clear business goals, understanding technical constraints, defining measurable success criteria, and evaluating implementation options.

Goal

Increase user engagement by 25%: from current 4.2 to 5.25 minutes average session time by 2025-12-15 23:59 UTC; value — improved user satisfaction and reduced churn.

Overview

Current UI uses only light theme, causing eye strain for users in low-light environments. 35% of users access the app after 8 PM according to analytics. Risks: color contrast issues affecting accessibility (WCAG AA compliance), performance impact from CSS calculations. Mitigations: automated contrast testing (owner — QA Lead M. Johnson), performance monitoring (owner — DevOps T. Chen). Dependencies: design system update completed by 2025-11-20, mobile team availability.

Definition of Done (DoD)

• 4 weeks straight average session time ≥ 5.25 minutes (Google Analytics "User Engagement" dashboard)
• Dark mode toggle available in settings for all users
• WCAG AA contrast compliance (automated test results in CI/CD)
• Lighthouse Accessibility score ≥ 95 on desktop/mobile
• PR with screenshots, automated tests added, and performance benchmarks
• User feedback survey shows ≥ 80% satisfaction with theme switching

Solution

Option 1 (Recommended): CSS custom properties with prefers-color-scheme media query and manual toggle. Effort: 16 hours development + 8 hours testing; risk: low (existing design system); assumptions: browser support ≥ 90%, no major CSS conflicts.

Option 2: Theme provider with React context and styled-components. Effort: 24 hours development + 12 hours testing; risk: medium (additional bundle size ~15KB); assumptions: acceptable performance impact, team familiar with styled-components.

Benefits

GODS provides a single source of truth for requirements, ensures teams think through acceptance criteria in concrete examples, reduces misunderstandings, brings testers in early, and gives developers clear targets to implement.

The framework shifts conversations from abstract statements to concrete examples, forcing clarity and preventing rework. Stakeholders can read a GODS task description and understand what will be delivered without deciphering code or low-level documentation.

1. 1. Enter Your Task

   Paste your task description in the input field. Maximum 1000 characters supported.

2. 2. Select GODS Framework

   Choose GODS from the framework selector to validate against this specific methodology.

3. 3. Get AI Analysis

   Click Analyze to receive instant AI-powered feedback with highlighted issues and improvement suggestions.

4. 4. Apply Fixes

   Review and implement the suggested fixes to transform your task into proper GODS format.

User Story

As a [user], I want [goal] so that [benefit]

BDD/Gherkin

Given/When/Then scenario specifications

OKR

Objectives and Key Results framework

Jobs to be Done

Focus on customer jobs and progress

View All Frameworks