---
name: management-communicate-iterate-delegate
description: "Help your team finish the right work without late surprises."
category: Strategy & Measurement
stage: —
definitive_article: /9-triangles-framework-scalable-home-service-businesses/
status: complete
---

# Management (Communicate, Iterate, Delegate)

Help your team finish the right work without late surprises. This guide sets clear owners, early checks and useful next steps. Start with one assigned task and what a good result looks like.

**The path:** Clear assignment → Early check → Small correction → Verified handoff

**Start when:** Work is being delegated or an existing assignment needs a reliable feedback loop.

## Inputs

- The task’s goal, source recipe, pass criteria and current work.
- A real owner, agreed due date, review channel and person authorized to judge the result.
- Previous feedback and the scope each person or AI worker can actually carry.

## Steps

1. Communicate the result, inputs, allowed actions, deadline and check method. Ask the receiving owner to confirm the assignment or name the missing input; do not infer acceptance from a sent message.
2. Agree a useful status cadence for this task: result shipped, blocker and next step. A missed report is unknown state to resolve, not proof that no work occurred.
3. Review a small representative draft early, around the source’s 10% teaching point when useful. Use the real deliverable and checklist to test direction before expensive work.
4. Give specific corrections tied to evidence. Separate a one-off execution error from a defect in the recipe; save the changed draft and confirm the correction actually addressed the issue.
5. Delegate a bounded next scope based on demonstrated results. Access, sending, publishing and spending authority remain explicit; a model name or a good draft does not establish them.
6. When feedback repeats, inspect its cause and propose a maintained-guide improvement. Record the actual accepted change and check its effect in a later run rather than treating an edit as proof of improvement.
7. Close only when the saved result meets the checks and reaches the next owner. Track real rework and turnaround against comparable prior tasks without claiming that more delegation always means better results.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the result against its agreed requirements; see the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] The assignment has an accepted owner, scope, deadline and pass criteria.
- [ ] Early review and corrections have actual saved evidence.
- [ ] Handoff and any responsibility change are confirmed; unresolved work stays visible.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional manager assigns a service-page draft with a real source and a Friday due date. The early outline targets the wrong town, so the manager corrects it before writing. The revised draft passes its content check but still awaits publishing access. The tracker shows a checked draft, not a live page.

## Handoff and Content Factory context

[Build task competence](https://local-service-spotlight.github.io/task-library/?task=learn-do-teach-apprentice-model#task-learn-do-teach-apprentice-model) handles training needs; [Improve the repeatable process](https://local-service-spotlight.github.io/task-library/?task=systematization-content-checklists-software#task-systematization-content-checklists-software) handles a proven recipe defect.

This work supports the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/) across its relevant stages. It uses the actual inputs and next owner above; a strategy or measurement guide does not manufacture transcripts, clips or other unrelated stage outputs.

## Start with an agent

Give the AI worker this recipe, the real Inputs, the desired result and the actions already authorized. Ask for the saved output, source evidence, passed and failed checks, and the next owner. A skill is a set of instructions. Loading it does not prove access, install a scheduled job or complete the work. Use the [current installation guide](https://localservicespotlight.com/install/) only if reusable setup is needed; a ZIP contains instructions and is not an access grant.

Use the actual supported app and verified source access. A model name is not a promise of browser control, memory or unattended work. For recurring work, inspect the real job’s trigger, owner, timezone and observed firing; this recipe creates no schedule. Before any media playback, mute the player and set volume to zero. A silent review does not prove sound was heard.

## Record the real execution

Open the run record when work begins. Keep one execution ID, the exact starting recipe revision, input sources and actual state. Write a [meta article, the record of one real execution](https://blitzmetrics.com/meta-article-prompt/) with results, checks, failures and next owner. Link it to this task in the [Task Library](https://local-service-spotlight.github.io/task-library/). Writing is required; public release follows existing authority.

Reuse the same execution ID for internal reviews, meta writing, revisions and retries. A blocked run stays open with its dependency and owner, without an invented finish time. Keep historical public examples as dated evidence; article counts alone are not verified execution frequency. Use supported findings to propose and verify a recipe improvement.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- [Maintained source guide](https://blitzmetrics.com/9-triangles-framework-scalable-home-service-businesses/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=management-communicate-iterate-delegate#task-management-communicate-iterate-delegate)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records work together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `complete`. It is preserved, not promoted by this rewrite. That label alone does not verify document readiness, account access, an actual execution or a client outcome.

A relevant real execution, source evidence, independent reviewer and accepted handoff remain to be recorded. The fictional example teaches the method and does not fill a real-run evidence gap. The opening and full method need a named semantic reviewer; the task-specific path is source guidance, with visible desktop/mobile presentation still to check.