concept-testing
Test product and messaging concepts with target users to learn appeal, clarity, and preference before heavy build investment. Use when evaluating early ideas, value propositions, or design directions with structured feedback.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- concept-testing
- description
- Test product and messaging concepts with target users to learn appeal, clarity, and preference before heavy build investment. Use when evaluating early ideas, value propositions, or design directions with structured feedback.
03 SKILL.md 正文
Concept Testing
Overview
Concept testing evaluates ideas while they are still cheap to change. It measures understanding, desirability, and relative preference — not final usability of a finished product.
When to Use
- Early product or feature concepts
- Value proposition and messaging tests
- Comparing alternative directions
- Go/no-go inputs before roadmap commitment
Core Practices
- Present concepts consistently (fidelity matched to the question)
- Test comprehension before preference
- Ask about job relevance and differentiation from alternatives
- Use both qualitative probes and structured ratings when useful
- Avoid over-indexing on polite enthusiasm
- Compare concepts against each other and against status quo
Principles
- Stated intent ≠ future behavior — treat as directional
- Higher fidelity is not always better for early concepts
- Audience quality matters more than sample size theater
- Kill weak concepts quickly; don’t “average” them into mediocrity
Verification
- [ ] Concepts were understood as intended
- [ ] Evaluation criteria match the decision needed
- [ ] Results distinguish winners from polite nods
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.