---
name: maa-cycle-metrics-analysis-action
description: "Turn reports into a clear next step for your team."
category: Strategy & Measurement
stage: —
definitive_article: /9-triangles-framework-scalable-home-service-businesses/
status: complete
---

# MAA cycle (Metrics, Analysis, Action)

Turn reports into a clear next step for your team. This guide links each key number to what it means and what to do next. Start with the goal, this week’s facts and the last plan.

**The path:** Metrics → Analysis → Action → Check the next result

**Start when:** A business review needs to connect sourced results to concrete next actions.

## Inputs

- [Goals, Content, Targeting: the result, proof and people for this work](https://blitzmetrics.com/gct-business-strategy/) and the agreed metrics, period, targets and definitions.
- [Collect verified weekly measurements](https://local-service-spotlight.github.io/task-library/?task=collect-verified-weekly-measurements#task-collect-verified-weekly-measurements) outputs and the prior report with action evidence.
- The current business context, action owners and authorized scope.

## Steps

1. Read the prior actions first. Mark each proposed, approved, executed, blocked or verified from its evidence. An unchanged outcome after an unexecuted action is not a failed test.
2. Collect the agreed metrics with the same definitions and comparable windows. Lead with the result the business needs, such as qualified leads, then include the balancing numbers and source limits.
3. Analyze material changes against target and history. State what is observed, the best supported explanation and what remains uncertain. A plausible reason is a hypothesis until evidence distinguishes it from alternatives.
4. Turn each important finding into a concrete next action or a defined evidence check. Name the owner, deadline, expected signal and acceptance condition. Do not invent extra actions merely to fill a report.
5. Keep actual actions separate from proposals. Execute or send only under current authority, retaining readback or delivery evidence. A report does not itself change an account or brief.
6. Save one coherent report using [Metrics, Analysis, Action: what happened, why and what to do](https://blitzmetrics.com/maa/). The next agreed cycle starts with this action list and checks what happened; retain changed targets or definitions instead of comparing unlike numbers.
7. Capture a reusable lesson and propose a recipe improvement when evidence supports it. Internal checks and edits stay under the same execution identity.

## 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 metrics are sourced and comparable; missing data is explicit.
- [ ] Analysis explains evidence and labels unknown causes.
- [ ] Important findings lead to named, bounded actions whose state can be checked next cycle.

## Example(s)

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

A fictional shop records 20 qualified leads after 16 last week. It also has six missed calls. The report suggests that phone coverage may limit bookings, but does not claim a cause from totals alone. The action owner checks the call log and tests the agreed coverage change; next week’s report checks its result.

## Handoff and Content Factory context

[Write the agreed weekly report](https://local-service-spotlight.github.io/task-library/?task=submit-weekly-maa-report-every-friday#task-submit-weekly-maa-report-every-friday) packages the client-facing cycle; [Diagnose weak results](https://local-service-spotlight.github.io/task-library/?task=analyze-why-underperformers-fail#task-analyze-why-underperformers-fail) or the specific action task receives the evidence needing work.

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:** 4/5 `●●●●○` — frequency 4, revenue 4, gating 2 (runs every factory cycle or weekly; creates the asset ads amplify)
- **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=maa-cycle-metrics-analysis-action#task-maa-cycle-metrics-analysis-action)
- [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.