No "Hello", No "Quick Call", and No Meetings Without an Agenda

Tone and Framing of the Original Post

  • Many agree with the core ideas (no “hello” alone, context for pings, no agendaless meetings) but find the article’s tone smug, condescending, or “parent to child,” which they think undermines the message.
  • Several say they’d never send the article to colleagues because it would make them look hostile, even if they share the preferences.

No‑Hello and Asynchronous Chat Etiquette

  • Strong support for “greet + context in one message” so recipients can prioritize asynchronously and avoid anxiety or unnecessary back‑and‑forth.
  • Others argue a bare “hi” doesn’t have to create anxiety if you simply ignore it until convenient.
  • Some note cultural habits where greeting first and waiting is mandatory, making change hard; others see “hello only” as a junior/IM-social norm that needs coaching.

“Quick Calls” vs Written / Async Communication

  • Many dislike “quick call?” with no context: calls often expand, derail flow, and leave no searchable trace; they can also hide repeated support work and office politics.
  • Advocates of calls say short, ad‑hoc conversations:
    • Resolve fuzzy issues faster than “text tennis.”
    • Help detect XY problems via screenshare.
    • Enable serendipitous brainstorming and relationship-building.
  • A common compromise: start with a contextual chat message, escalate to a short call if needed, and reserve frequent calls for those who prefer them while enforcing boundaries against abuse.

Meetings, Agendas, and Documentation

  • Broad agreement: meeting invites should include agenda, goal, and expected outcomes; otherwise decline or ask for clarification.
  • Post‑meeting minutes and explicit responsibilities (e.g., RACI) are praised to avoid re‑meeting and missing stakeholders.
  • Some warn that rigid “agenda or nothing” rules can hinder urgent incident response or informal syncs.

Remote Work, Socialization, and “Watercooler” Debates

  • Some view the workplace as a social hub and fear that strict “no quick calls / no hello” norms erode cohesion and creativity.
  • Others call “watercooler innovation” largely a myth or overused RTO talking point, arguing async channels and occasional social calls can substitute.
  • Attempts at scheduled “social Zooms” often feel forced and dominated by a few voices; in‑person ad‑hoc chats or shared breaks are seen as more natural by some.

Productivity, Flow, and Team vs Individual Optimization

  • Many emphasize the high cost of interruptions and reference maker vs manager schedules; they support focus blocks, status indicators, and declining low‑quality requests.
  • Counterpoint: over‑optimizing for individual flow can reduce team effectiveness; mild social friction and accessibility are part of being a good coworker, and careers benefit from being approachable.

Culture, Power, and Enforcement

  • Commenters note power dynamics: managers can successfully push “no agenda, no meeting,” while juniors risk backlash.
  • Some managers explicitly instruct reports to decline agendaless meetings and log meeting time as “real work” (e.g., tickets) to surface its cost.
  • Several argue norms should be set at the organizational level with polite guidance, not enforced via passive‑aggressive links or rigid personal “rules.”