--- title: The Meeting That Should Have Taken Six Minutes Took Six... description: Enterprise teams waste enormous time by applying the same decision-making process to every choice, regardless of its actual weight. A simple two-axis framework... canonical: https://daily.dev/posts/the-meeting-that-should-have-taken-six-minutes-took-six-weeks-vja268o0p twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The Meeting That Should Have Taken Six Minutes Took Six Weeks | daily.dev og:description: Enterprise teams waste enormous time by applying the same decision-making process to every choice, regardless of its actual weight. A simple two-axis framework... og:url: https://daily.dev/posts/the-meeting-that-should-have-taken-six-minutes-took-six-weeks-vja268o0p og:image: https://api.daily.dev/og/posts/VJa268O0p.png og:image:alt: The Meeting That Should Have Taken Six Minutes Took Six Weeks og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The Meeting That Should Have Taken Six Minutes Took Six Weeks **[Medium](https://daily.dev/sources/medium_js)** · 7 min read · 2 upvotes · 0 comments ## Summary Enterprise teams waste enormous time by applying the same decision-making process to every choice, regardless of its actual weight. A simple two-axis framework — reversibility vs. blast radius — sorts decisions into four quadrants: Delegate (reversible, low blast radius), Commit (irreversible, low blast radius), Deliberate (reversible, high blast radius), and Slow Down (irreversible, high blast radius). Each quadrant prescribes a different process, owner structure, and meeting size. The core insight is that most organizational dysfunction isn't a discipline problem but a classification problem — teams never sort decisions before debating them, so every choice defaults to the most expensive process available. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I decide how much process a business decision actually needs? Classify the decision along two axes: reversibility (can it be undone cheaply?) and blast radius (who or what is affected if it's wrong?). This produces four quadrants: Delegate (reversible, low blast radius) needs no meeting; Commit (irreversible, low blast radius) needs one owner deciding quickly; Deliberate (reversible, high blast radius) needs discussion with an exit ramp; Slow down (irreversible, high blast radius) needs exec sponsorship and real deliberation. _daily.dev surfaces frameworks like this for engineers pushing back on over-processed team decisions._ ### Why do teams spend so long debating decisions that don't matter much? Most organizations never build a way to sort decisions by weight before debating them, so every choice defaults to the same slow, consensus-heavy process regardless of stakes. This produces four failure patterns: consensus-seeking without a designated owner, framing trade-offs as false binaries instead of dials, requesting data that wouldn't change the outcome or arrive in time, and treating reversible and irreversible decisions identically. _engineers frustrated by slow team decisions can find similar management frameworks on daily.dev._ --- Tags: [#leadership](https://daily.dev/tags/leadership), [#company-culture](https://daily.dev/tags/company-culture) [View this post on daily.dev](https://daily.dev/posts/the-meeting-that-should-have-taken-six-minutes-took-six-weeks-vja268o0p) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The Meeting That Should Have Taken Six Minutes Took Six Weeks","url":"https://daily.dev/posts/the-meeting-that-should-have-taken-six-minutes-took-six-weeks-vja268o0p","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-meeting-that-should-have-taken-six-minutes-took-six-weeks-vja268o0p"},"datePublished":"2026-07-21T19:30:12.445Z","dateModified":"2026-09-13T20:29:41.936Z","description":"Enterprise teams waste enormous time by applying the same decision-making process to every choice, regardless of its actual weight. A simple two-axis framework...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e29eeee8a4ba0c23e24551d70fee7e13?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e29eeee8a4ba0c23e24551d70fee7e13?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-meeting-that-should-have-taken-six-minutes-took-six-weeks-vja268o0p","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"leadership,company-culture","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"The Meeting That Should Have Taken Six Minutes Took Six Weeks"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-meeting-that-should-have-taken-six-minutes-took-six-weeks-vja268o0p#faq","mainEntity":[{"@type":"Question","name":"How do I decide how much process a business decision actually needs?","acceptedAnswer":{"@type":"Answer","text":"Classify the decision along two axes: reversibility (can it be undone cheaply?) and blast radius (who or what is affected if it's wrong?). This produces four quadrants: Delegate (reversible, low blast radius) needs no meeting; Commit (irreversible, low blast radius) needs one owner deciding quickly; Deliberate (reversible, high blast radius) needs discussion with an exit ramp; Slow down (irreversible, high blast radius) needs exec sponsorship and real deliberation. daily.dev surfaces frameworks like this for engineers pushing back on over-processed team decisions."}},{"@type":"Question","name":"Why do teams spend so long debating decisions that don't matter much?","acceptedAnswer":{"@type":"Answer","text":"Most organizations never build a way to sort decisions by weight before debating them, so every choice defaults to the same slow, consensus-heavy process regardless of stakes. This produces four failure patterns: consensus-seeking without a designated owner, framing trade-offs as false binaries instead of dials, requesting data that wouldn't change the outcome or arrive in time, and treating reversible and irreversible decisions identically. engineers frustrated by slow team decisions can find similar management frameworks on daily.dev."}}]} ```