{"id":1249,"date":"2026-11-10T19:30:00","date_gmt":"2026-11-10T19:30:00","guid":{"rendered":"https:\/\/cotocus.org\/blog\/?p=1249"},"modified":"2026-11-10T19:30:00","modified_gmt":"2026-11-10T19:30:00","slug":"eight-questions-must-vs-nice","status":"publish","type":"post","link":"https:\/\/cotocus.org\/blog\/eight-questions-must-vs-nice\/","title":{"rendered":"Eight Questions That Separate a Must-Have From a Nice-to-Have"},"content":{"rendered":"<p>A few years ago I watched an operations lead named Carla spend forty minutes in a meeting deciding between two monitoring options, only to realise afterwards that both met every condition her team really cared about. The forty minutes had gone into arguing about extras. That day she wrote a card of questions to ask whenever a choice felt stuck, and she has used it ever since. Here are eight of them, shared as a list you can copy for your own must-have versus nice-to-have decisions.<\/p>\n<h2>1. What happens if this is missing on day one?<\/h2>\n<p>Start with the bluntest question. If the honest answer is &#8220;we could not do our job&#8221; or &#8220;we would break a rule&#8221;, you have a must-have. If the answer is &#8220;it would be a bit annoying&#8221;, you have a nice-to-have. Carla says this question alone sorts about half of any list, and the rest need the next seven.<\/p>\n<h2>2. Can I point to evidence?<\/h2>\n<p>A real need leaves footprints: an incident review, a customer complaint, a clause in a contract. A wish tends to arrive with adjectives instead, such as &#8220;modern&#8221;, &#8220;slick&#8221; or &#8220;future-proof&#8221;. When the evidence is thin, move the item to the tie-breaker column and see whether anyone produces proof later. If they do, it can come back up.<\/p>\n<h2>3. Who is harmed if we leave it out?<\/h2>\n<p>Name a person or a group. &#8220;On-call engineers get woken for no reason&#8221; is specific. &#8220;The organisation&#8221; is not. Items that cannot name anyone who is harmed are rarely hard requirements, though they might still be valuable extras.<\/p>\n<h2>4. Is there another way to meet the same need?<\/h2>\n<p>Often the must-have is the outcome, not the feature. A team may need to know within minutes when a service degrades; it does not necessarily need a particular tool to do it. Phrase requirements as outcomes and you widen your options at no cost. Readers planning operations tooling might compare notes with <a href=\"https:\/\/cotocus.org\/blog\/aiops-roadmap-a-practical-guide-for-devops-sre-and-operations-teams\/\">a practical roadmap aimed at DevOps, SRE and operations teams<\/a>, which treats capabilities as stages instead of products.<\/p>\n<h2>5. Could we add it later without pain?<\/h2>\n<p>Reversibility is a quiet sorting tool. A feature that is easy to bolt on after launch is a natural tie-breaker. A decision that is hard to reverse, such as how data is organised or where it lives, deserves more attention early, and sometimes belongs on the hard list for that reason alone. Ask: if we skip this now, what does it cost to come back?<\/p>\n<h2>6. What does it displace?<\/h2>\n<p>Nothing is free. Every addition pushes something else down the queue or increases the bill. Carla draws a line under the most expensive three items and asks the group whether each is worth the delay it creates. Surprisingly often, a lively wish loses to a dull necessity once the trade is visible.<\/p>\n<h2>7. Would we still want it if it were not trendy?<\/h2>\n<p>Fashion distorts priorities. A capability can dominate conversations simply because everyone is talking about it. Strip away the buzz and ask whether you would want it based on your own situation. A balanced overview, such as <a href=\"https:\/\/cotocus.org\/blog\/complete-guide-to-aiops-for-it-operations-teams\/\">an end-to-end introduction to AIOps for IT operations groups<\/a>, is a good place to separate genuine fit from hype, as long as you read it with your own hard list beside you.<\/p>\n<h2>8. Does everyone agree on the words?<\/h2>\n<p>The last question is about language. If one person says &#8220;must&#8221; and means &#8220;I badly want&#8221;, and another says &#8220;must&#8221; and means &#8220;we cannot launch without&#8221;, your list is built on sand. Write the definition at the top of the page and read it aloud. Two minutes spent on shared words saves hours later.<\/p>\n<h2>Bonus: a card for decisions that are not about work<\/h2>\n<p>Carla now uses the same card at home. When her uncle needed to arrange care abroad, she suggested he begin with the practical must-haves: dates that suited the family, support in a language he was comfortable with, and a companion for the trip. He read about the process on <a href=\"https:\/\/bestcardiachospitals.com\/\">BestCardiacHospitals, an educational website for international patients<\/a>, which lays out steps from sharing needs through comparing options, and which tells readers on its own pages that its aim is to teach, that it gives no medical direction and that it cannot help in an urgent situation. Everything clinical went to his own doctors; the card handled only the practical parts. It was a small example of the list doing what it is meant to do.<\/p>\n<h2>The questions applied to a real list<\/h2>\n<p>Last spring Carla&#8217;s team had six candidates for an on-call improvement project: a smarter paging schedule, a new status page, a chat integration, a runbook clean-up, a second alerting vendor and a trial of a trendy correlation feature. Question one removed the chat integration and the vendor at once, since the team could page people perfectly well without them. Question two, evidence, kept the paging schedule, because three incident reviews had mentioned tired responders, and kept the runbook clean-up, which nine engineers had complained about. Question five put the status page in the tie-breaker column, since it could be added any week. Question seven made the correlation trial wait for a quiet quarter.<\/p>\n<p>The whole conversation took twenty-five minutes, and two people who lost their favourites said it was the first time they felt the reasoning was fair.<\/p>\n<h2>How Carla runs the card in a meeting<\/h2>\n<p>She does not read all eight questions aloud. She begins with the first and moves down only when an item is still unresolved. Most items settle by question three. The tough ones, perhaps one or two per meeting, reach question six, where the displacement discussion usually ends the debate. She then records the decision, the question that settled it and a review date, in two lines.<\/p>\n<p>The record matters more than it seems. A month later, when someone asks why a favourite feature did not make the cut, the answer is on the page: it failed question two, and here is the date it will be reviewed. The conversation stays friendly because the reasoning is visible and impersonal.<\/p>\n<h2>Three habits that make the list stick<\/h2>\n<ul>\n<li><strong>Keep the hard list under ten items.<\/strong> Past that, ask the first question again for each entry.<\/li>\n<li><strong>Review at every milestone.<\/strong> Let the evidence move items up or down, and note why.<\/li>\n<li><strong>Celebrate a good &#8220;no&#8221;.<\/strong> A deferred wish with a clear reason is a sign the process works, not a failure of ambition.<\/li>\n<\/ul>\n<h2>What the card cannot do<\/h2>\n<p>It will not tell you what your hard requirements should be; that comes from your obligations, your users and your past mistakes. It will not replace expert advice in areas where you lack the knowledge, whether technical, legal or medical. And it will not stop a determined colleague from lobbying. What it does is lower the volume. When the questions are on the table, arguments become about facts and trade-offs rather than about who feels most strongly.<\/p>\n<p>Try it on your next stuck decision. Write the eight questions on a card, work through the items that are still unresolved, and watch how quickly the pile sorts itself. Carla keeps hers in her notebook, a little creased now, and says it has paid for itself many times over in meetings that ended early.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Eight practical questions, collected on one operations lead&#8217;s notebook card, that sort any stuck decision into true must-haves and ranked tie-breakers.<\/p>\n","protected":false},"author":4,"featured_media":1250,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[129],"tags":[],"class_list":["post-1249","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/comments?post=1249"}],"version-history":[{"count":1,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1249\/revisions"}],"predecessor-version":[{"id":1322,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1249\/revisions\/1322"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media\/1250"}],"wp:attachment":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media?parent=1249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/categories?post=1249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/tags?post=1249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}