- In short
- Consolidating steps means combining workflow steps that can logically run together into a single prompt or Skill call rather than leaving them as separate manual steps. Promoting patterns means capturing a repeated personal workaround in shared configuration, a Project or Skill, so it becomes a team-wide efficiency that benefits every future run. Consolidation and promotion are the two moves that account for most of the gain in a workflow optimization.
The two moves that produce most of the gain
Spotting friction and placing fixes are preparation; the actual optimization comes from two moves that do most of the work. The first is consolidation: combining steps that can run together instead of leaving them as separate manual prompts. The second is promotion: capturing a repeated pattern in shared configuration so it benefits everyone, not just the person who found it. The Claude Certified Associate - Foundations (CCAO-F) exam treats these as an apply-level skill, because knowing about them is not enough; you have to recognise, in a concrete workflow, which steps to consolidate and which patterns to promote.
Together, consolidation and promotion account for the bulk of what a workflow optimization delivers. Consolidation removes internal friction, the manual handoffs between steps. Promotion multiplies a gain across people and cycles. A workflow that has been consolidated and promoted is both leaner to run and consistent across everyone who runs it, which is the compounding benefit optimization is after.
- Consolidation and promotion
- The two core optimization moves. Consolidation combines workflow steps that can logically run together into a single prompt or Skill call rather than separate manual steps. Promotion captures a repeated personal workaround in shared configuration, a Project or Skill, so it becomes a team-wide efficiency benefiting every future run.
Consolidation: combining steps that belong together
Many workflows are run as a chain of separate prompts out of habit rather than necessity: draft in one prompt, reformat in the next, summarise in a third, each with a manual handoff between them. When the steps can logically run together, splitting them just adds overhead, the friction of shepherding output from one step to the next by hand. Consolidation combines them into a single prompt or Skill call, so the sequence runs as one operation.
The judgement is which steps genuinely can run together. Steps that are independent of each other, or that only exist as separate prompts because that is how they were first written, are consolidation candidates. The exception, worth flagging because the next skill covers the risk, is a step deliberately kept separate for a reason, such as an intentional human review point. But absent such a reason, more prompts than the task needs is friction, and folding them into one is a direct gain. This is why a procedure captured as a Skill, per the rule-reference-procedure placement test, can also be a consolidation: the Skill runs the whole sequence in one call.
Promotion: from personal workaround to team-wide gain
Promotion is the move that scales an improvement beyond the person who discovered it. A workaround you have refined by hand, a particular prompt structure, a saved piece of context, a sequence you always run, is a personal efficiency until it is captured in shared configuration. Once promoted into a Project or Skill, it becomes available to everyone who runs the task, and the gain multiplies across the whole team and every future cycle.
The content type decides the promotion target, exactly as in promoting a working fix into a standing instruction or Skill: context that is pasted every time goes to the knowledge base or a standing instruction, and a procedure run every time goes to a Skill. The essential recognition is that leaving a good improvement as a personal habit wastes most of its value. The habit helps one person; the promoted pattern helps everyone, forever, which is the whole reason promotion is one of the two high-leverage moves.
What the CCAO-F exam trips candidates on
The first trap is leaving a discovered consolidation as a personal habit instead of promoting it into shared Project configuration. Someone works out a slicker way to run the workflow and keeps it to themselves, and the team keeps running the old, friction-heavy version. The credited move is to promote the improvement so everyone benefits; a private optimization captures only a fraction of the available gain.
The second trap is splitting a task into more separate prompts than necessary when the steps could safely run together. Over-splitting adds handoff friction with no benefit, treating steps as sequential when they are actually consolidatable. The exam rewards recognising when steps can run together and folding them into a single prompt or Skill call. Both traps are failures of leverage: one leaves promotion on the table, the other leaves consolidation on the table, and the two moves are precisely where the gain lives.
Worked example
An analyst has personally streamlined the team's weekly digest. She used to run four separate prompts, extract highlights, categorise them, format a table, and write a summary, but has found the first three can be done in one prompt. She keeps this as her own routine. Two teammates still run all four steps and get inconsistent results. What should she do?
Two of the high-leverage moves are available here, and she has done neither fully.
First, consolidation. She has already discovered that extract, categorise, and format can run together in a single prompt rather than as three separate ones with manual handoffs between them. That is a real consolidation, folding three steps into one, and it removes the friction of shepherding output between them. The judgement that these three can logically run together is sound; the summary might stay separate if she wants to review the categorised table before it is written, but the first three are genuine consolidation candidates and she has correctly combined them.
Second, and this is the gap, promotion. She is keeping the consolidated approach as her personal routine, so her two teammates still run the old four-step version and get inconsistent results. That leaves most of the value on the table: her improvement helps one person while the team keeps absorbing the old friction and the variance. The fix is to promote the consolidated sequence into a shared Skill in the Project, so all three analysts run the same streamlined procedure. Promotion turns her private optimization into a team-wide efficiency and, as a bonus, resolves the variance, since everyone now runs the identical setup. Consolidation made her own run leaner; promotion is what makes the whole team benefit.
Common misreadings to avoid
Misconception
A better way of running the workflow that I have worked out is fine to keep as my own routine.
What's actually true
Misconception
Breaking a task into more separate prompts is generally safer and clearer.
What's actually true
How this shows up on the exam
Domain 7 questions here describe a workflow with combinable steps or a private improvement and ask for the best optimization. The credited answers consolidate steps that can run together and promote patterns into shared configuration. Distractors either leave a good improvement as a personal habit or split a task into more prompts than it needs.
This knowledge point builds on the rule-reference-procedure placement test, which decides where a promoted pattern lands, and draws on promoting a working fix into a standing instruction or Skill from the feedback task statement. It sets up validating an optimization before full reliance, because a consolidated, promoted change should be proven before the old approach is retired. Consolidate and promote, and a workflow gets leaner and more consistent for everyone at once.
An analyst discovers a faster way to run a shared reporting workflow by combining three steps into one prompt, but keeps it as her personal routine while teammates run the slower version. What is the best next move?
People also ask
How do I consolidate steps in an AI workflow?
What does it mean to promote a pattern?
When should steps run together instead of separately?
Watch and learn
Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.
No videos curated for this concept yet
We are still curating the best official and community videos for this topic.
Official prep for this domain
Anthropic's own free prep module for this part of the syllabus, on the official prep course. Free with an Anthropic Academy sign-in.
References & primary sources
Master this concept with Archie
Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.