marketing-behavior-design-frameworks

Select and apply evidence-aware marketing, customer-needs, positioning, motivation, persuasion, behavioural-economics, copywriting, content, storytelling, UX, website, and app-design frameworks. Use w

SKILL.md

GitHub

Marketing, Behavior, and Design Frameworks

Use frameworks to improve diagnosis and decisions, not to decorate an answer with acronyms. Select the smallest combination that addresses the task and state what each selected framework contributes.

Framework contract

  1. Define the desired audience outcome and the artifact being created or reviewed.
  2. Separate observed evidence, user-supplied assumptions, and unanswered research questions.
  3. Choose frameworks by function:
    • diagnose: understand the market, audience, need, behaviour, or usability problem;
    • decide: choose positioning, priorities, intervention, architecture, or content role;
    • compose: structure copy, content, narrative, or an interface;
    • evaluate: review the result against evidence, usability, accessibility, and ethical constraints.
  4. Distinguish an empirical theory, professional method, and practitioner heuristic. Never present a mnemonic as a scientific law.
  5. Translate every framework finding into a concrete decision, requirement, experiment, or content element.
  6. Validate important assumptions with research, usability testing, analytics, or controlled experiments appropriate to the task.

Do not force a fixed number of frameworks. One suitable model is better than several overlapping ones.

Use these default classes unless a source warrants a narrower description:

  • empirical theory/model: Self-Determination Theory, Expectancy Theory, COM-B, Fogg B=MAP, Elaboration Likelihood Model, Theory of Planned Behavior, Prospect Theory, and named cognitive or behavioural effects;
  • professional method: 4Ps/7Ps, STP, JTBD practice, Value Proposition Canvas, journey mapping, Double Diamond, Nielsen heuristic evaluation, and WCAG review;
  • practitioner heuristic: AIDA, PAS, BAB, 4Us, Message House, Golden Circle, brand archetypes, StoryBrand, Hero-Hub-Help, and most hook formulas.

Routing

For subscriptions, pricing, financial or health decisions, children, sensitive data, safety, high-pressure conversion, or vulnerable audiences, always load both the decision/persuasion and evidence/ethics references. Treat legal or professional review as a separate requirement when applicable.

Load only the references needed for the current task.

Useful framework stacks

Task Diagnostic Decision Composition Evaluation
Landing page JTBD or VoC positioning; add STP only if the audience is unresolved Message House or one copy structure the smallest applicable usability, accessibility, and ethics checks
Blog or guide Search/user intent + audience job Topic cluster + editorial mission SCQA, inverted pyramid, or claim-evidence-reasoning Accuracy, information scent, cognitive load
Social campaign Audience need state Content pillars + Hero-Hub-Help + PESO Hook-Value-CTA or narrative structure Platform fit, proof, accessibility, repetition
Email sequence Journey stage + COM-B lifecycle role and desired behaviour AIDA, PAS, BAB, or message hierarchy consent, deliverability, claim, friction, and CTA review
Website or app Journey map + task analysis Double Diamond, JTBD, or service blueprint user flows + progressive disclosure + design system Nielsen heuristics, accessibility, usability testing
Positioning VoC or JTBD plus competitive research STP, then POP/POD; add a perceptual map only with perception data positioning statement; add a benefit ladder only for feature-led claims differentiation, proof, comprehension testing

These are starting combinations, not mandatory recipes.

Required handoff

For framework-driven work, include:

  • selected framework names and why they fit;
  • evidence and assumptions used;
  • the decisions or artifact elements produced;
  • risks, limitations, and unresolved questions;
  • an appropriate validation method.

Do not expose this internal selection process inside reader-facing copy unless the user asks for the rationale.

Creator

Created for and maintained by Brownsmith Dynamics as part of the Apnatva skill collection.