---
id: "concept-step-change-ai"
type: "concept"
source_timestamps: ["00:03:55", "00:04:30"]
tags: ["ai-trends", "hardware-scaling", "model-capabilities"]
related: ["concept-claude-mythos", "entity-product-nvidia-gb300"]
definition: "The distinction between minor, iterative model updates (5-15% better) and massive, paradigm-shifting leaps in capability driven by new hardware generations."
sources: ["s44-claude-mythos"]
sourceVaultSlug: "s44-claude-mythos"
originDay: 44
---
# Step Change vs. Incremental Improvement

## Definition

The distinction between **incremental improvements** (5–15% better on a benchmark, frequent) and **step changes** (paradigm-shifting capability jumps, rare, hardware-driven).

## Incremental improvement

- Frequent
- Driven by fine-tuning, architecture tweaks, point releases
- Performance gains in the 5–15% range
- Existing workflows remain valid

## Step change

- Rare
- Typically driven by **new generations of compute hardware** — in this source, [[entity-product-nvidia-gb300|Nvidia GB300]]
- Unlocks entirely new categories of autonomous behavior, not just better versions of old behavior
- Forces re-evaluation of architectures and workflows

## Why this matters

Recognizing a step change in real time is a strategic skill. If you misclassify a step change as incremental:
- You keep your procedural prompts (see [[concept-bitter-lesson-llms]])
- You keep your hardcoded RAG (see [[concept-model-driven-retrieval]])
- You keep your human handoffs (see [[claim-human-handoffs-bottleneck]])
- You leave 10x improvements on the table

## The source's claim

The alleged emergence of [[concept-claude-mythos|Claude Mythos]] on GB300 hardware constitutes a step change. Per Nvidia GTC 2025 references, GB300 delivers ~4–8x H100-equivalent flops, supporting the *hardware* premise even where the *model* premise is unverified.

## The strategic response

The entire [[framework-mythos-readiness|Mythos Readiness Transformation]] is the response framework for a step change.