Task statement 4.2 · Workflow integration and solution design

4.2 · Research, Planning and Process Optimization

In Wrenfield Housing, the course example, the operations team has agreed the requirements for handling repair requests (4.1), and now prepares the change with Claude: a look at what other providers do, a plan for a pilot on the Millbrook estate, and a map of where today's requests wait. If Claude works from general knowledge instead of Wrenfield's facts, all three look finished and fit nobody.

Why it's tested

The tempting habit is to ask Claude for the answer in one line, such as "How can we make our repairs process faster?" Claude knows how repairs work in general but nothing about your staff, your times or your budget, so it returns advice that sounds right for any housing provider and fits none in particular. Preparatory work pays off only when Claude has your own facts and limits, and people check what it finds before anyone acts.

KnowledgeClaude as a partner for preparatory work

Preparatory work comes before a change: finding out what others do, planning the change and studying the current process. Claude is a partner in it, not the decision-maker. It is quick at structure: grouping findings, laying out steps, spotting a pattern in a list of times. It cannot know your budget, who is away in March or why a step takes nine days unless you tell it, so it finds gaps only among the facts it has. This rules out acting on Claude's plan or process advice before your sources and staff have checked it. The pattern has four moves, and the last belongs to people:

  1. Give your facts and limits: the goal, figures, dates and what cannot change.
  2. Ask for a structure you can check: options side by side, a plan with owners, or a map with times.
  3. Ask what it misses: gaps, risks, and what may not fit your organisation.
  4. Check with sources and people: open the citations, and ask the staff who do the work.

Interactive · what Claude finds in a process map, and what the check keeps

The seven steps of a damp and mould request at Wrenfield, from the tenant's report at the top to the booked visit at the bottom, each with its typical days, about 41 days in all. Each step leads to the next by an arrow labelled then. On the right, a mark shows what Claude found or what the staff check decided. Waits: steps 2, 3, 6 and 7, dashed and labelled wait. Repeated step: steps 4 and 5 type the same report twice, dashed and labelled repeated. Bottleneck: step 3, only two surveyors for all inspections, dashed and labelled bottleneck. After the staff check: step 2 goes to the pilot, step 5 is escalated to the IT team's developers, and step 6 keeps its rule but runs twice a week, each solid and labelled. DAMP AND MOULD REQUEST · REPORT TO BOOKED VISIT CLAUDE'S MARK OR THE STAFF CHECK 1 · Tenant reports damp call handler logs it DAY 0 THEN 2 · Triage queue waits for the weekly triage 6 DAYS THEN WAIT · 6 DAYSin a queue, nobody working on it PILOT · SORT ON THE FIRST CALLMillbrook, 9 February to 20 March 3 · Officer triages then waits for a surveyor 14 DAYS THEN WAIT · 14 DAYSfor a surveyor's visit BOTTLENECK · LONGEST WAITonly two surveyors for all inspections 4 · Surveyor inspects types a report 2 DAYS THEN REPEATED · FIRST TIMEthe report is typed here 5 · Officer re-keys report into the repairs system 1 DAY THEN REPEATED · SECOND TIMEthe same report, typed again ESCALATED · SYSTEM CHANGEto the IT team's developers 6 · Manager approves jobs over £500, once a week 9 DAYS THEN WAIT · 9 DAYSfor the weekly approval CHECKED · £500 RULE KEPTapprovals now twice a week 7 · Contractor books visit date sent to the tenant 9 DAYS WAIT · 9 DAYSfor the contractor's booking TOTAL: ABOUT 41 DAYS, THE BACKLOG'S MEDIAN WAIT FOR DAMP AND MOULD

Choose what Claude looks for in the map, then what the staff kept.

Waits: in steps 2, 3, 6 and 7 nobody works on the request. They hold 38 of the 41 days.

Repeated step: the surveyor's report from step 4 is typed again in step 5.

Bottleneck: step 3 is the longest wait, because only two surveyors inspect every request.

After the staff check: step 2 goes to the pilot, step 5 goes to IT, and step 6 runs twice a week.

Dashed and labelled: what Claude marked. Solid and labelled: what the staff decided.

KnowledgeThree kinds of preparatory work

1.4 covered the research task type and Research, a mode in the Claude apps that investigates in depth and returns a cited report. The team asked Research how other housing providers triage repair requests, with sources from 2024 on. It found three approaches: sorting requests by urgency on the first call, photos from tenants before an inspection, and a dedicated damp and mould team. A finding is not yet an option, so the next prompt asked Claude to set the three side by side: what each needs, costs and rests on. The last prompt gave Wrenfield's limits (only two surveyors, and no new IT system unless the IT team builds it) and asked which assumptions do not hold. Photos needed an upload route in the repairs system and a dedicated team needed more surveyors, so sorting on the first call went to a pilot.

Planning turns a goal into steps, each with an owner, a date, its dependencies (the steps that must finish first) and its risks. Claude Academy's examples ask Claude for a pilot plan's milestones, success metrics and potential challenges, then for what you are missing. The goal was a six-week pilot on the Millbrook estate, 9 February to 20 March. The team gave Claude the roles, the dates people are away and the other work planned on Millbrook, then asked: "What does this plan miss? List the dependencies and risks we have not named." Claude flagged three gaps. There was no baseline, the current wait measured before the pilot starts. Boiler servicing on the estate from 3 to 14 March would send rebooking calls to the same repairs line. Nobody owned the call handlers' script. Claude saw the boiler clash only because the prompt listed the other work. The team checked each gap, then added a six-week baseline, extra repairs line cover and an owner.

Process optimization means finding where a process loses time or repeats work, then changing it. Claude needs a process map, a list of every step in order with who does it and how long it takes, as Claude Academy's process template asks. A bottleneck is the step where work piles up because it has less capacity than the steps around it. A duplicated step handles the same information twice, and a wait is time when a request sits and nobody works on it. Claude sees only the map, so its suggestions stay hypotheses until the people who do each step confirm them.

Research

Give your limits; ask for options side by side and what does not hold for you.

Then checkThe sources behind each option kept.

Planning

Give roles, dates and other work; ask for owners, dependencies and what the plan misses.

Then checkEach flagged gap, with its owner.

Process optimization

Give every step with its time; ask for waits, duplicated steps and the bottleneck.

Then checkEach suggestion, with the staff who do that step.

SkillWorked example: the process question that got generic advice

The team wanted to know where the 41-day median wait for damp and mould goes. The first prompt asked about a process Claude had never seen:

# before
How can we make our repairs process faster?
→ "Consider an online portal, more staff and a chatbot for reporting."
# after
Below is how a damp and mould request moves today, with typical days.
1 Call handler logs the report (day 0)  2 Triage queue (6)
3 Officer triages, waits for a surveyor (14)  4 Surveyor's report (2)
5 Officer re-keys the report (1)  6 Manager approves over £500 (9)
7 Contractor books the visit (9)
Mark each wait, duplicated step and bottleneck. Suggest changes that
need no new IT system, and say which step each change shortens.
→ "Steps 2, 3, 6 and 7 are waits (38 days). Step 5 repeats step 4.
   Step 3 is the bottleneck: the longest wait, for a surveyor."

The cause was a missing map. With only a goal, Claude could offer only what speeds up repairs in general, and two of its three ideas needed new IT. The new prompt gives the steps, the times and the limit on IT, so each suggestion names a step its staff can check. Sorting requests on the first call became the pilot, and the call handlers needed a written guide to do it (4.3). The repairs manager kept the £500 rule, which finance sets, but now approves twice a week. Ending the re-keying needs a change to the repairs system, so it went to the IT team's developers.

Ask one question: has Claude seen your own facts, and has someone who knows the work checked what it found? Both yes → decide. Either no → add your figures, dates and limits, or take the findings to your sources and staff.
Takeaway
  • Findings become useful once they are options tested against your organisation's size, budget and systems.
  • Every plan step needs an owner, a date and its dependencies; Claude spots missing risks only among facts you listed.
  • A process map with times shows waits, repeated steps and the bottleneck; the staff decide which changes are real.

check yourself

0 / 3 answered

A library services manager asks Claude for an eight-week plan to move a branch's lending to self-service kiosks. Claude returns tidy steps with dates. The kiosks come from an outside supplier, every later step assumes they arrive in week 2, and the plan goes to the director tomorrow.What is the most effective next step before the plan goes to the director?

Select one.

A finance team's supplier invoices take about 15 working days from arrival to approval. The finance manager asks Claude, "How can we speed up invoice approvals?" and gets general advice: buy invoice software, automate approvals and hire a clerk. The team has no budget for new software this year.Which TWO changes would make Claude's next answer most useful to the team?

Select two.

A council's waste team used Research to learn how other cities cut missed bin collections. The report recommends route-planning software, with savings from three large cities, and each claim links a 2025 source. The team has two crews, paper route sheets and no software budget, and the pilot built on the report stalled in its first week.What is the most likely root cause?

Select one.

sources

  1. Claude Help Center, "Use research on Claude": Research investigates a question in depth; turned on from the + button with web search on; paid plans (Pro, Max, Team, Enterprise); searches the web and connected tools such as Google Workspace. Checked 2026-10-15.
  2. Claude Academy, "Claude for nonprofits partnership success guide for admins": use Claude to facilitate planning, with an example prompt asking for a 30-day pilot plan that includes milestones, success metrics and potential challenges. Checked 2026-10-15.
  3. Claude Academy, "Workflow improvement planner": describe the current workflow, its pain points and bottlenecks, inputs and outputs, success and constraints, with specifics such as frequency, volume, who does the work and how long it takes. Checked 2026-10-15.
  4. Claude Academy, "Stress-test your financial plan across scenarios": an "Ask what you're missing" follow-up that has Claude raise points you did not ask about; review the result with a qualified professional before acting. Checked 2026-10-15.
  5. Claude Academy, "Getting better results" (Claude 101): include the context you would naturally have when doing the work; for high-stakes work, verify key facts independently. Checked 2026-10-15.
  6. Wrenfield's research report, the Millbrook pilot plan, the process map and its times are this course's example.