somethingmeeting

Somethingmeeting is a term used in some business and software development contexts to describe a loosely defined meeting whose purpose is to surface unresolved topics, blockers, or nascent ideas that lack a fixed scope. The concept emphasizes discovery and quick alignment over formal decision-making, often serving as a conversational kickoff for items that will later be clarified through backlogs or further analysis.

Etymology and usage context

The word is not tied to a specific methodology but reflects a pragmatic approach: the content of the meeting is intentionally not fully specified in advance. It is commonly employed in startups, product teams, and agile environments where requirements evolve rapidly and teams want to avoid over-structured gatherings that can stall momentum.

Typical format and objectives

Somethingmeetings are usually short, with durations in the 15 to 30 minute range. They may begin with a quick status check and then proceed to volunteers proposing topics or blockers. A facilitator or note-taker records issues and assigns follow-up actions, often funneling items into a backlog, a product roadmap, or a risk register rather than into immediate decisions. The goal is to quickly surface what needs clarification, who should own it, and what the next concrete step is.

Benefits and criticisms

Proponents argue that somethingmeetings reduce planning overhead, accelerate issue discovery, and keep teams flexible. Critics contend that the lack of a defined agenda can lead to drift, unclear ownership, and insufficient accountability. When used, they are typically complemented by more structured meetings for prioritization and decision-making.

See also

Meeting, stand-up meeting, backlog refinement, discovery session.