7.3 — Optimising Workflows for Efficiency and Effectiveness

CCAO-F Domain 7 · Task 7.3

What You Need to Know

Overhead is anything you type, explain or attach at the start of every similar conversation. Optimising means making your work with Claude cost less time or usage. Measure first.

The Repeated-Overhead Test

Recurring overhead belongs somewhere it only has to exist once:

• Standing context and rules → Project’s instructions
• Recurring reference material → Project knowledge
• Near-identical weekly request → saved form you adapt per use
• Preferences that apply to everything → account-wide personalisation settings

Documented Levers

• Batching — group multiple related tasks in a single message rather than fragmenting them
• File names — well-named files help Claude retrieve the right information (“Worktop price list” beats “pl_v3_final”)
• Match settings to the work — routine reformatting at maximum effort pays for depth it never uses; deep analysis at a low setting underserves the task

The Proportion Rule

Some overhead is not worth removing. A twenty-minute task done once a year does not earn a Project, a saved form or an afternoon of setup. Recognising the optimisation that costs more than it saves is as professional as spotting the one that pays.

Key Concept: Look for the measurement. The keyed answer moves measured, recurring overhead to where it exists once, or declines a setup that costs more than it saves.

Exam Traps

• Sweeping workflow changes proposed off a feeling
• Building a Project or saved form for a task done twice a year
• Raising effort or switching model to speed up a workflow whose overhead is a repeated preamble