Choosing the Right Approach for the Competition

Opening Scene

A genuinely experienced coach doesn’t decide between adjusting an archer’s sights and retraining their stance on a whim. They weigh the target’s stability, the cost and time available, how varied competition conditions actually are, and how deep the needed correction genuinely goes — and only then decide. Choosing between prompting and fine-tuning deserves this exact same deliberate weighing of concrete factors, not a coin flip or a default habit.

In Plain English

A practical decision framework for choosing between prompting and fine-tuning weighs several concrete factors together: whether prompting has been genuinely exhausted first (Article 4), whether the problem shows real signals of having outgrown prompting (Article 5), the task’s expected call volume and resulting cost tradeoff (Article 10), how much the task or its data is expected to drift over time (Article 11), and how varied or stable the task requirements genuinely are (Article 13). No single factor decides the question alone — the framework is the combination.

The Old Way

Before this kind of multi-factor framework was applied deliberately, the choice between prompting and fine-tuning was often made on a single, incomplete signal:

Teams sometimes chose based on a single factor alone — cost, familiarity, or which approach happened to be trendier at the time — rather than weighing the fuller set of relevant considerations together.
There wasn’t yet a well-established, shared framework for making this decision consistently across different projects and teams within the same organization.
The decision was sometimes made once, upfront, and never revisited even as a project’s volume, stability, or requirements genuinely changed over time.

A genuine multi-factor framework, revisited as circumstances change, reflects the accumulated lessons from every individual factor this series has covered.

What’s Changing (and Why AI Is the Reason)

Organizations increasingly apply a consistent, multi-factor decision framework across projects, rather than leaving the prompting-versus-fine-tuning choice to individual habit or preference.
This framework treats “both together,” covered in Article 14, as a legitimate outcome alongside choosing either approach exclusively.
The framework is increasingly revisited periodically, not decided once and forgotten, since volume, drift, and requirement stability can all genuinely shift over a project’s lifetime.

The Metaphor, Fully Extended

The Archer	Decision Framework Concept
Weighing target stability, cost, time, and needed correction depth together	Weighing exhausted prompting, drift risk, volume cost, and task stability together
A coach’s deliberate judgment, not a coin flip	A team’s deliberate, multi-factor decision, not a default habit
Revisiting the decision as competition conditions change	Revisiting the decision as volume, drift, and requirements genuinely change
Sometimes choosing both a trained stance and adjustable sights together	Sometimes choosing fine-tuning and prompting together, covered in Article 14

For Beginners: What to Actually Do

Practice walking through this framework’s factors explicitly for a real or hypothetical project, rather than jumping straight to a preferred approach.
Learn to weigh factors together rather than letting any single one — like cost alone — decide the question in isolation.
Get comfortable revisiting a past prompting-versus-fine-tuning decision periodically, checking whether the same factors still point the same way.

For Practitioners and Leaders: The Deeper Layer

Formalize a shared, multi-factor decision framework across your organization’s projects, rather than leaving the choice to individual habit.
Build a periodic review cadence for revisiting past decisions, since volume, drift, and requirement stability can genuinely shift over time.
Treat “both together,” covered in Article 14, as a legitimate, often optimal outcome the framework should surface, not an edge case.

Quick Recap

A practical decision framework weighs exhausted prompting effort, outgrowth signals, cost at volume, drift risk, and task stability together.
No single factor should decide the question alone — the framework’s value is in the combination.
Organizations increasingly formalize this as a consistent, shared framework across projects.
The decision should be revisited periodically, since the relevant factors can genuinely change over a project’s lifetime.

Where This Fits in the Series

Article 18 pulled every factor into one practical framework. Article 19 looks at the broader economics of this decision at an organizational level, beyond any single project.