sebastian-software/skills.sebastian-software.com/effective-product

Effective Product

Choose the route for the research or product decision. Read only the relevant references; an existing brief can supply the context for a focused question.

Distinguish observations, participant accounts, commitments, and assumptions. Never invent research, demand, metrics, customer language, or willingness to pay. Prefer observed behavior and meaningful commitment to hypothetical intent. Use exact denominators and preserve evidence limits.

Recommend a direction with its tradeoffs and the uncertainty that could change it. When evidence is missing, offer a labeled hypothesis or a way to obtain it. Keep scope, evidence gathering, and next steps proportionate to the decision; not every request needs an evidence register or a research program.

Route by Intent

Routing Boundaries

• effective-marketing: segment/category positioning, messaging, approved

claims and pricing communication, launches, sales, channels, and conversion experiments. Research fieldwork and product/pricing decisions stay here.

• effective-web: browser specifications, implementation and verification,

reference capture, originality reviews, and web privacy/consent/disclosures.

• effective-engineering: system architecture, data models, language-level

implementation, and focused non-frontend test design.

• effective-delivery: repository lifecycle work, technical documentation,

engineering ownership, and team coordination.

• effective-writing: editorial prose, locale typography, and team messages.

Do not substitute simulated participants for research or use deception and coercion as retention mechanics. Specialist statistical, legal, regulated research, tax, and industry decisions require appropriate expertise.