Mk 033

---
name: mk-033
description: "Separating events from personality descriptions. Use when the task requires abstract labels rewritten as verifiable events. Apply this method to the specified inputs and verify the deliverable"
---

# MK-033 | Separating events from personality descriptions

For a regular chat, upload `packs/mk-033.md`. It includes the shared rules, this method, and required references

## Purpose

This skill delivers: **Abstract labels rewritten as verifiable events**

Task stages are analytical categories, not a claim that every customer follows the same path

## Required inputs

Provide: The product or service, customers' own words, existing pages, and actions the company can support

## Method

1. An event description must state something observable that happens, not a personality label such as "values quality" or "likes looking good"
2. If a description cannot answer "What happened?", return to the event level and rewrite it
3. Do not substitute Persona traits for evidence of a need trigger

## Calculations and interpretation

Search phrases and paths are planning hypotheses; check them against real search terms and evidence of how pages support the need

## Required output fields

| Order | Field | How to complete |
|---:|---|---|
| 1 | Trigger event | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 2 | The customer's current problem | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 3 | Available answer | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 4 | Supporting page/creative | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 5 | Gap | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 6 | Reasonable next step | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 7 | Basis | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |

## Verification cases

**MK-033-C05 | An ad promotes a service that the page does not explain**

Expected: Record a verifiable promise gap; do not immediately conclude it caused all abandonment

**MK-033-C06 | No verbatim customer statements are available**

Expected: Produce only a need map awaiting validation, not a claimed finding from actual research

## Method sources

Source file: Google Ads 第一堂｜看懂需求，才知道廣告怎麼接

Location: Trigger event

Source basis: extracted from course materials

Source URL: https://docs.google.com/presentation/d/15ZOg0pX_xikpdA3FwGEoCSVgWortvCnxSe4hz4ugizg/edit

English translation of source excerpt:

> Identify need-trigger events