Moving the work to the person who wants the meeting
One link ends the thread where two people compare calendars.
- The surface
- Setting availability once, sharing an event link, and what the invitee sees when they open it.
- What the user wants
- I want to stop trading three emails about which Tuesday works.
Availability defined once
The host sets working hours, meeting durations, buffers between meetings and a minimum notice period, and these persist across every future booking.
Set a policy, not an answer
Scheduling by email means re-deciding the same constraints every time, and people apply them inconsistently when tired. Encoding them once means the rules hold even on the days the host would have caved. Buffers and minimum notice in particular are boundaries the host would rarely defend in a live conversation.
Event types
Different meeting kinds get separate links with their own duration, questions and availability windows, such as a short intro call and a longer working session.
One object per intent
A single generic link forces the host to negotiate length and purpose afterwards, which is the negotiation the product exists to remove. Separate links let the choice of link carry the context. The host is effectively pre-writing their answers to the questions they always get.
The invitee view
The invitee sees a month grid with available days, times rendered in their own detected timezone, and no account requirement.
Reduce the choice to what is actually possible
Asking someone what time suits them is an open question with a bad answer rate, because they have to guess your constraints. Showing only valid slots turns composition into selection. Local timezone rendering removes the single most common scheduling error without asking anyone to do arithmetic.
Confirmation and calendar write
Booking writes the event to both calendars, sends confirmations, and attaches a conferencing link where one is configured.
Finish the job, not the transaction
A booking that leaves either party to create the calendar entry has only moved the work. Writing to both calendars and attaching the video link means the interaction is genuinely over. The job was a meeting that happens, not a meeting that is agreed.
Reschedule and cancel links
Both confirmation messages carry reschedule and cancel links, and using them updates both calendars without a new conversation.
Design the exit as carefully as the entry
Most scheduling pain happens after the booking, when something moves. A self-serve reschedule keeps the change out of email and out of the host's day. It also makes cancellation socially cheaper, which is better than a no-show.
The negotiation, before and after
What not to copy
- The link transfers effort rather than deleting it. Sending your calendar to a customer, a candidate or anyone senior can read as a status move, and the product cannot detect the cases where it will cost you the meeting.
- Exposing availability exposes information. A public link tells anyone how busy you are, and for some roles that is competitive intelligence.
- Rules compete once a host runs several event types across shared hours. Debugging why a slot did not appear means reasoning about overlapping availability, buffers and calendar conflicts with very little explanation from the interface.
- Group scheduling remains the hard case. The product is excellent for one host and one invitee and gets progressively less convincing as the number of people with constraints grows.
The takeaway
Replace an open question with a short list of valid options and most of the negotiation disappears.
Finished the teardown? Bank it and the day counts toward your run.
Where the principles come from
- The Paradox of Choice, Barry Schwartz
- Nudge (choice architecture and defaults), Richard Thaler and Cass Sunstein
- Competing Against Luck (jobs to be done), Clayton Christensen
Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.
