About ZenPoll
Who we are, what we publish, and why scheduling advice on this site is worth trusting.
Who we are
ZenPoll is a small, independent team that builds scheduling software for a living. We started ZenPoll because we were tired of watching group coordination turn into hour-by-hour "calendar Tetris" — the emails, the spreadsheets, the Doodle chains, the polite silences after someone asks for "the 14th, but actually not after 3pm."
We are not a marketing department writing about a product we have never used. We are the people who design, build, and operate the tool you see on this site, day in and day out. We have run day-level coordination with dozens of groups — team retrospectives, offsites, family gatherings, and community meetups — and the guides in our library are built on that first-hand experience, not on recycled listicles.
Who ZenPoll is for
ZenPoll is for anyone who needs to find a date a group can agree on: teams planning sprint reviews, organizers of events and gatherings, board members coordinating committee meetings, and remote or hybrid teams spread across timezones. It is specifically not for granular hourly booking, calendar-sync automation, or appointment scheduling — we keep the scope deliberately narrow because day-level coordination is where most scheduling friction lives.
Our editorial approach
The guides on this site follow a consistent editorial process. Each article starts from a real coordination problem we have encountered, is written with concrete, worked examples, and is reviewed against current scheduling and remote-work research before it is published. Every guide states who it is for, what problem it solves, and how to apply it.
We fact-check claims about scheduling behaviour, response rates, and remote-work patterns against reputable sources, and we test the practical advice against our own usage of the tool. Where research is inconclusive, we say so rather than presenting opinions as facts. We do not publish sponsored articles, accept payment for coverage, or disguise advertising as editorial content.
How we write
Every article begins with a problem statement rather than a keyword. We ask: what is someone actually struggling with when they search for this topic? From there we outline the scenarios people run into in real life — a team that cannot agree on a retrospective date, a family trying to book a shared weekend, a distributed group spread across four timezones — and write the advice around those situations. We then read the draft aloud as if explaining it to a colleague, cut anything that adds length without adding insight, and only publish when the article passes our internal review checklist.
We update articles when the evidence changes or when readers write in with corrections. Every article carries both a publish date and a last-updated date, and we note substantive revisions so returning readers can tell what changed.
Our research sources
Where we cite research, we draw on published studies and surveys about meeting load, context switching, decision fatigue, and distributed work. We are careful to distinguish between established findings (for example, that frequent interruptions slow focused work) and emerging or contested claims (for example, exact productivity gains from any single scheduling technique). We link to sources where practical so you can read the underlying material and judge it for yourself.
What we believe
Our philosophy is simple: scheduling should be calm. We believe the right first question is "which day works for everyone?" — not "which 45-minute window aligns across four timezones?" By agreeing on a day first, groups dramatically reduce the cognitive load of coordination. This principle drives both the product and everything we publish.
How we stay accountable
We hold ourselves to the same standards we ask of our guides. We are transparent about what we do and do not know, we correct mistakes publicly, and we welcome challenge. If you believe an article is wrong, biased, or missing an important perspective, tell us. We would rather fix an error than defend it.
We also track the practical outcomes of the advice we publish. When a strategy we recommended helps a reader — or falls short — we use that feedback to refine the relevant guide. The tools and workflows we describe are things we actually use, which means our recommendations change as our own practices improve.
Because we operate the product ourselves, our editorial work and our engineering work share the same feedback loop. Every support message, correction, and poll-usage pattern teaches us where scheduling advice breaks down in the real world, and that experience feeds directly back into the guides. It is a cycle that keeps our content honest and grounded.
Transparency & updates
This page was last updated on August 7, 2026. We review and update our guides when scheduling practices change or when readers point out errors. Every guide shows its publish and last-updated dates. If you spot something incorrect, outdated, or unclear in any article, please tell us via the contact page — we take corrections seriously and publish them.
The product relationship
Some guides compare ZenPoll with other scheduling tools. When we do, we aim to be fair and specific: we name real alternatives, summarise what each does well, and recommend a poll tool only when the evidence supports it. We disclose that ZenPoll is the product we build, so you can weigh our recommendations accordingly.