---
id: "question-scaling-taste"
type: "open-question"
source_timestamps: ["00:13:31", "00:15:50"]
tags: ["design", "future-of-work"]
related: ["concept-quality-without-a-name", "concept-incompressible-experience"]
sources: ["s25-builders-identity-shift"]
sourceVaultSlug: "s25-builders-identity-shift"
originDay: 25
---
# How to Scale 'Taste' in AI Workflows?

## The Open Question
While 'civil engineering' (explicit coding and structuring) can be easily delegated to AI agents, instilling a product with [[concept-quality-without-a-name]] (human taste, intuition, and coherence) remains a manual, human-driven process.

**As AI dramatically increases the volume and velocity of output, how can organizations scale this subjective human judgment without it becoming the ultimate bottleneck?**

## Why It's Hard
The difficulty is rooted in [[concept-incompressible-experience]]: taste is forged through time and friction, and cannot be speedrun. Yet AI velocity demands that some judgment apparatus keep pace with output volume.

## Possible Resolution Paths (Per Source)
- Developing new frameworks for **embedding human intuition and aesthetic judgment** into agentic workflows
- Advanced **evaluation models trained on specific human preferences**
- Redefining the human role purely as an **'editor of taste'** — letting agents generate volume while humans curate against an internalized standard

## Why It's Important
If this is unsolved, then [[concept-quality-without-a-name]] becomes the new bottleneck (replacing prompt engineering as the bottleneck per [[claim-bottleneck-shift]]). The framework [[framework-2026-builder-practices]] explicitly elevates this as Practice #5 precisely because it remains an open problem rather than a solved discipline.


## Related across days
- [[concept-quality-without-a-name]]
- [[concept-incompressible-experience]]
- [[concept-vertical-taste]]
- [[claim-opus-visual-superiority]]