Placemaker Tools
Crowdsourcing and validating real-world place data—so maps, apps, and measurement stay fresh, accurate, and human-aware.
Overview
Think of it as a Wikipedia for places—an editor and moderation system for real locations: restaurants, stores, venues, and more.
Automation alone cannot keep POI truthy. Placemakers (community contributors) work alongside Foursquare to add, correct, and validate place data—so the dataset reflects what is actually on the ground.
Placemaker Tools = the system Foursquare uses to crowdsource and validate real-world location data at scale.
Why it matters: one accurate dataset feeds maps, apps, measurement, and discovery experiences.
Responsibility
Principal Product DesignerI shaped product UX for contributor-facing flows—pairing with Engineering, Trust & Safety, and data operations so human review at scale stayed usable, fair, and aligned with dataset quality goals.
Problem
The system continuously ingests tens of thousands of suggested edits. Without clear queues, map context, and community checks, noise wins: duplicates, stale hours, and wrong pins erode trust.
Scaling review means more than adding headcount. AI agents and humans need shared surfaces—so triage is fast, decisions are explainable, and contributors still feel ownership.
Human-in-the-loop cycle: every change moves through review, community validation, and publication—then the loop repeats.
Approach
- Review queue first — Surface places that need verification (bad hours, missing fields, conflicting signals) so contributors know where attention matters.
- Map as truth-check — Let people see nearby context when fixing pins, duplicates, or closures—spatial mistakes are easier to catch on a map than in a table.
- Structured add-place — A guided form for new venues keeps categories, address, and hours consistent for downstream consumers.
- Contribution tracking — Show edits and impact so power users stay motivated and accountable.
- Community validation — Approvals, rejections, and voting turn individual judgment into shared consensus.
Key design decisions
Separate verification work from open-ended map browsing
The review queue optimizes for throughput and clarity; the map view optimizes for spatial fixes. Mixing both in one mode created cognitive overload—splitting them kept each task honest.
Schema-driven add-place, not freeform blobs
New locations funnel through structured fields (name, address, hours, categories) so automated checks, deduping, and downstream APIs get predictable shape—reducing “garbage in” at the source.
Transparent contribution history
Contributors see their edits and outcomes—building trust and making moderation auditable when disputes arise.
Peer review as a first-class state
Edits are not final until others weigh in where policy requires it—designing explicit approve / reject / needs info paths kept the social contract visible in the UI.
Outcome
Design direction converged on a single story: scale human judgment without drowning people in noise—with surfaces that internal ops, power contributors, and emerging AI-assisted workflows could share.
Contributor experience
Clear entry points into review, map fixes, and add-place—so motivated users spend time on decisions, not navigation.
Operations & trust
Aligned patterns for queue priority, voting, and audit trails—reducing ad-hoc tooling and ambiguous states between teams.
Impact
Dataset & customers
- Places data stays current for maps, apps, ads, and attribution
- Fewer bad pins and stale attributes propagating to enterprise use cases
- Foundation for recommendations that reflect real-world change
Product & scale
- Human review pipelines that can absorb high edit volume
- Room for AI-assisted triage without bypassing accountability
- Reusable patterns for moderation-heavy contributor products
Contributors
- Power users see impact of their edits and reviews
- Community validation rewards careful work over speed-chasing
- Clear roles between public contributors and internal data teams