Workflow design and role playbooks

Exam domain 4: Workflow Integration and Solution Design (16%)

The biggest gains come from redesigning a process around Claude, not from faster one-off prompts. This domain tests using Claude to analyze requirements, research and plan, support solution design, integrate into existing workflows, and explain its value and limits to stakeholders.

Augment or redesign?

Claude drafts the weekly status report; the PM edits and sends it Re‐

• design
• The process changes because
• Claude exists

Status updates flow into a Project; Claude produces the report, a risk log and stakeholder versions; the PM reviews exceptions only

Start by augmenting. Redesign once the outputs are reliable and the review points are clear.

A six-step method for integrating Claude into a workflow

Figure 5. Six steps for bringing Claude into a workflow

Map the current process. List steps, owners, inputs, outputs and time per step. Claude can help: describe the process and ask it to draw a step list and flag bottlenecks. Find good candidates. Look for steps that are repetitive, text-heavy, rules-based or researchheavy, with outputs a human can check quickly. Rule out poor fits. Avoid steps needing guaranteed accuracy without review, final legal or HR judgment, or data your policy forbids sharing.

Design the new flow. Decide the feature (Project, Research, connector, Skill), the model tier, and where human review sits.

Pilot and measure. Run on real work for two to four weeks. Track time saved, error rate and rework.

Standardize and hand over. Document the Project setup, prompts and review steps so others can run it. Assign an owner.

Using Claude across the solution lifecycle

Requirements. Paste stakeholder notes; ask Claude to extract requirements, spot conflicts and list open questions.

Research and planning. Use Research mode for market or policy background, then ask for a plan with milestones, risks and dependencies.

Design and iteration. Ask for options with trade-offs, prototype a template or small tool in an Artifact, and refine with feedback.

Process optimization. Describe a process; ask where time and errors pile up and how to fix them.

Map the current process

steps, owners, inputs, time

• Find good candidates
• repetitive, text-heavy,
• checkable

• Rule out poor fits
• no unreviewed accuracy,
• final HR or legal calls

• Design the new flow
• feature, model, where
• review sits

• Pilot and measure
• 2 to 4 weeks: time saved,
• errors, rework

• Standardize and hand
• over
• document it and assign an
• owner

Explaining Claude to stakeholders

Be concrete and balanced. Give the value ("cuts first-draft time for proposals from 3 hours to 45 minutes in our pilot"). Give the limits ("it can state wrong facts confidently, so pricing and legal terms are always checked"). Give the controls ("no customer personal data is uploaded; a manager approves every external send"). Overpromising is a common wrong answer on the exam.

Know when to escalate

CCAO-F expects you to recognize work beyond a business user's remit. Escalate to IT, developers or architects when a solution needs API integration, automated agents acting without review, custom connectors, processing at very large scale, or access to sensitive systems.

Role playbooks

Operations

Task Approach

Write or update an SOP Project with existing SOPs as examples; Claude drafts from a recorded walkthrough or notes; process owner reviews

Analyze an operations

dataset

Upload CSV; Claude uses code execution to compute and chart; recheck key figures Vendor comparison Upload proposals; ask for a comparison table against your criteria, with quotes supporting each score

Meeting to action items Paste transcript; ask for decisions, owners and due dates in a table

Marketing and communications

• Task Approach
• On-brand content at
• scale

Project with brand guide, audience personas and best past examples; or a brand Skill Campaign research Research mode for competitor and market scans; verify statistics before use Repurpose content One webinar transcript to a blog, five social posts and an email, each tuned to its channel Message testing Ask Claude to critique copy as specific personas would; it supplements, not replaces, real customer testing

Project management

Task Approach

Project plan Decompose scope into phases, tasks, risks and dependencies; review against team capacity Status reporting Connector to tracker or notes; Claude drafts exec and team versions Risk register Ask for risks by category with likelihood, impact and mitigation; the team validates Knowledge work, education and consulting

• Task Approach
• Literature or policy re‐
• view

Research mode plus uploaded sources; ask for citations and check them Client deliverable Project per client with background, standards and templates; partner review before sending Training materials Claude drafts lesson outlines, quizzes and examples; a subject-matter expert checks accuracy

Scoring candidate tasks

When you map a process, score each step to decide where Claude helps most. Give each criterion 1 (low) to 3 (high).

Criterion High score means

Volume The step happens often

Text or data heavy The work is mostly reading, writing, summarizing or analyzing Easy to check A person can verify the output quickly

Low risk Errors are minor and reversible

Clear rules Good output can be described with examples or criteria Steps scoring 12 or more out of 15 are strong candidates. Steps with a low "Low risk" score need heavier review or should stay manual.

Measuring value honestly

Stakeholders will ask whether Claude is worth it. Measure before and after a pilot:

Measure How to capture it

Time per task Time a sample of tasks before and after, including review time Quality Rework rate, error rate found in review, or reviewer ratings Throughput Tasks completed per week

Satisfaction Short survey of staff and, where relevant, customers Risk events Errors that reached a customer or breached policy

Report total time, not just drafting time. A draft produced in two minutes that takes 40 minutes to fix is not a saving.

Worked examples

Worked example 6.1: Redesigning employee onboarding

Current process. HR emails a new hire a 30-page handbook, managers answer the same questions repeatedly, and IT setup requests are sent by email. Map and score.

• Step Volume Text heavy Easy to check Low risk Clear rules Total
• Answer common policy questions 3 3 3 2 3 14
• Create a personalized first-week plan 2 3 3 3 2 13
• Draft the welcome email 2 3 3 3 3 14
• Decide salary band 1 1 2 1 1 6
• Submit IT access request 2 1 3 2 3 11

Redesign. An "Onboarding Assistant" Project holds the handbook, benefits summary and FAQ, with instructions to answer only from those sources and to route anything personal to HR. Managers use a Project template to generate first-week plans. Salary decisions stay entirely with HR. IT access stays in the IT ticketing system; integrating it with Claude would be a technical project to escalate.

Pilot result after one month (illustrative). Manager time on onboarding questions down by about half; two answers found inaccurate in review, both traced to an outdated benefits file, which was replaced.

Worked example 6.2: Requirements analysis from messy notes

Situation. A project manager has notes from six stakeholder interviews about a new expense system.

Prompt.

From the attached interview notes, produce: (1) a list of requirements, each tagged Must, Should or Could based on how stakeholders described it; (2) any requirements that conflict, with who raised each side; (3) open questions to resolve. Quote the note that supports each requirement.

Result. 23 requirements, three conflicts (for example, Finance wants approval for all claims over $50, while Sales wants auto-approval under $200), and eight open questions. The PM verifies the quotes and takes the conflicts to the steering group.

Worked example 6.3: Explaining a pilot to leadership

A one-paragraph stakeholder update that balances value, limits and controls:

Over a four-week pilot, the proposals team used Claude to draft first versions of RFP responses. Average drafting time fell from about 6 hours to about 2.5 hours per response, including review. Review caught three factual errors about product capabilities, so every technical claim is now checked against the product facts sheet before submission. No client confidential information beyond the RFP itself was entered. We recommend extending the pilot to the second proposals team, keeping the same review step.

Worked example 6.4: Knowing the limit

Situation. A marketing coordinator wants Claude to post to social media automatically every morning based on a content calendar.

Analysis. Drafting the posts in a Project is well within CCAO-F scope. Automatically publishing to external channels without review requires integrations and governance decisions. The right step is to draft in Claude, review, and schedule in the existing social tool, and to raise any automation idea with the technical team and marketing leadership.

Role playbooks in depth

Operations: monthly operations report. Connect the shared metrics folder, keep the report template in a Project, and ask Claude to compare this month with last month, flag variances over 10%, and draft commentary. The operations lead verifies the variances and adds context only they know.

Marketing: content repurposing pipeline. One webinar transcript feeds a Project whose instructions define each channel's format: a 900-word blog post, a LinkedIn post under 200 words, three short social posts and a newsletter paragraph. A human editor checks claims and approves each piece.

Project management: risk review. Upload the project plan and status reports. Ask Claude to identify schedule risks, dependencies at risk, and items with no owner. Use the output to run the risk meeting, not to replace it.

Education: course design. Provide learning outcomes and learner profile. Ask for a module outline, activities, an assessment rubric and a quiz. A subject-matter expert checks every factual statement and the rubric's fairness. Communications: crisis holding statement. Claude can draft a holding statement quickly from verified facts. Legal and leadership must approve before release, and Claude must not speculate beyond confirmed facts.

Consulting: interview synthesis. Upload anonymized interview notes. Ask for themes, supporting quotes and contradicting evidence for each theme. The consultant validates each theme against the notes before it reaches the client.

Scenario walkthroughs

Scenario A. A department head wants to "use AI everywhere" and asks you where to start. Analysis. Map the department's main processes, score steps for fit, and pilot the two or three highest-scoring steps with clear measures. Avoid starting with high-risk steps. Scenario B. A pilot cut drafting time but increased customer complaints about errors. Analysis. Review was too light for a customer-facing step. Strengthen review, ground outputs in approved sources, and re-measure before expanding.

Scenario C. A colleague claims Claude "knows our processes" because it gave a convincing description of their purchasing workflow. Analysis. Claude produced a plausible generic workflow. It knows your processes only if you give it your documentation.

Scenario D. A team wants Claude to make final pass/fail decisions on supplier applications. Analysis. Claude can summarize applications and check them against criteria, but final decisions with commercial and legal consequences need human judgment and accountability. Scenario E. An executive asks for a one-line answer: "Will Claude save us money?" Analysis. Answer with evidence and conditions: the measured time saved in a pilot, the review cost, and the risks managed, and propose how to scale and measure.

Key points

Map the process first; pick steps that are repetitive and easy to check.

Augment before redesigning. Put human review at the points that carry risk.

Explain value, limits and controls together. Never overpromise.

Escalate API, agent and large-scale integrations to technical teams.

Common traps

Automating end to end before mapping the process or piloting.

Judging success on drafting speed alone and ignoring review time.

Overpromising to stakeholders, or building integrations that should go to IT.

Check yourself

Name the five criteria for scoring a candidate task.

What is the difference between augmenting and redesigning a workflow?

Why must review time be included when measuring time saved?

Give two examples of work a CCAO-F holder should escalate to technical teams. What three things should a stakeholder update about Claude include?

Answers. (1) Volume, text or data heavy, easy to check, low risk, clear rules. (2) Augmenting speeds up a step in the current process; redesigning changes the process because

Claude exists. (3) Because fast drafts that need heavy fixing may save nothing. (4) Any two of: API integrations, automated publishing or actions without review, custom connectors, large-scale automation. (5) Value with evidence, limits, and controls.

Exercise

Map one process you run weekly. Mark which steps Claude could augment, which it could redesign, and where review must sit. Estimate time saved.