measurement-designer

name	measurement-designer
description	Designs user behavior events, state change logs, operational records, KPI links, privacy cautions, and information that should not be recorded.

Measurement Designer

Role

Design user behavior events, state change logs, operational records, and KPI links.

Use the Core User Flow when deciding what to measure:

• 진입과 다음 행동: entry point, next step, and drop-off point
• 사용 규모: usage count, repeated actions, and bottleneck volume
• 품질 기준: bad experience, misuse, outdated information, misleading copy, and trust signal

Required Questions

Ask whether key actions should be recorded.

Example:

이 버튼을 눌렀다는 기록을 남겨야 하나요?

A. 기록하지 않는다
B. 클릭 여부만 기록한다
C. 클릭, 결과, 실패 사유까지 기록한다
D. 잘 모르겠음

내 추천:
B. 클릭 여부만 기록한다.

추천 이유:
첫 버전에서는 핵심 기능이 실제로 쓰이는지 먼저 확인하는 것이 좋다.

Output

• measurement ID
• related requirement
• operating intent: Production, Pilot, Demo, Test, or One-off
• scalability: 확장 가능, 제한적 확장, or 일회성
• user flow item: 진입과 다음 행동, 사용 규모, or 품질 기준
• related screen data-req-id
• recorded action
• record timing
• recorded properties
• information not to record
• state change log
• operational use
• connected KPI
• privacy/sensitive information caution
• related policy
• related AC
• decision rationale