Found & Trusted
Development
Writing
Book a call
Knowledge Base
/
topic: observable-proxies-for-judgment
Topic:
observable-proxies-for-judgment
16 entries tagged
observable-proxies-for-judgment
.
Rules (4)
rule
R7 — When the owner can read a number off a screen, have them do so
rule
R6 — In easy-looking markets, override owner optimism with observed counts
rule
R3 — Where comparison is unavoidable, use a concrete NAMED competitor target
rule
R1 — Convert every judgment into an observation or counting task
Reference entries (12)
reference
Research brief: SMB widget capture layer — what owners can vs cannot self-report (June 2026)
reference
CANNOT — "How do you compare to your competitors?" (abstract → max overplacement)
reference
CANNOT — "How strong is your SEO?" (no instrument; owner has no access to the metric)
reference
CAN — "Search your main service + city. How many businesses appear above you?" (live counting task)
reference
CAN — "Do you have a Google Business Profile? Is it claimed?" (binary state)
reference
CAN — "When was the site last updated?" (recent behavioral event)
reference
CAN — "How old is your website?" (concrete date-based fact)
reference
CAN — "When was your most recent review?" (recent, distinctive, checkable)
reference
CAN — "How many Google/Yelp reviews do you have?" (counting from own profile)
reference
CAN — "Do you currently run paid ads?" (behavioral, binary, current)
reference
BARS (Smith & Kendall 1963) — anchoring scale points to concrete observable behaviors
reference
The concrete-target moderation — the design lever against overplacement
