{"id":1288,"date":"2026-11-14T04:30:00","date_gmt":"2026-11-14T04:30:00","guid":{"rendered":"https:\/\/cotocus.org\/blog\/?p=1288"},"modified":"2026-11-14T09:30:00","modified_gmt":"2026-11-14T09:30:00","slug":"wip-limits-trend-ops","status":"publish","type":"post","link":"https:\/\/cotocus.org\/blog\/wip-limits-trend-ops\/","title":{"rendered":"The Quiet Rise of Work in Progress Limits in IT Operations"},"content":{"rendered":"<p>Something interesting is happening in operations and delivery teams. After years of talk about doing more, faster, with more tools, a quieter idea keeps showing up in retrospectives and planning rooms: do less at once. Capping work in progress has moved from a niche practice borrowed from lean manufacturing to something many ordinary IT teams talk about over coffee. What follows is an easygoing tour of the idea&#8217;s origins, its current shape and its likely next steps. No hype, and no made-up numbers, just what practitioners tend to describe.<\/p>\n<h2>Where the idea came from<\/h2>\n<p>The roots are in factory floors. Production engineers noticed long ago that piling up half-built goods between stations slowed everything down, so they limited how many items could wait at each stage. When software teams adopted visual boards in the 2000s, the limit travelled with them, and a column on a board became the new station on the line. It is a well-documented piece of history, and the core logic has not changed: a smaller pile moves faster than a larger one.<\/p>\n<h2>Why it is getting attention now<\/h2>\n<p>Several pressures push teams toward limits at the same time. Work arrives through more channels than before: chat, tickets, email, alerts and code reviews. Tooling has multiplied, and every new tool adds another place where an open item can hide. Teams are also asked to handle operations, security and delivery together, which means more kinds of work competing for the same attention. When everything can be started easily, the scarce skill becomes finishing.<\/p>\n<p>Another factor is plain fatigue. People feel the mental drag of unfinished work, and a rule that lowers the pile is a relief. Many teams describe adopting a limit not out of theory but because a retrospective revealed that everyone felt behind while being constantly busy.<\/p>\n<h2>What the practice looks like in today&#8217;s teams<\/h2>\n<p>The common pattern is modest. A shared board has columns for waiting, active, review and done. Active and review carry a number. Individuals often add a personal ceiling of one or two items. An expedite lane handles real emergencies. Weekly reviews look at how long items stay open, not only at how many were completed. It is not a grand framework; it is a set of small rules that people can follow without training.<\/p>\n<p>Operations teams in particular are pairing the limit with their incident work. When alerts fire, the instinct is to open yet another thread. A cap pushes teams to resolve and close before reaching for the next, and it fits neatly with the approach in this <a href=\"https:\/\/cotocus.org\/blog\/mastering-incident-management-with-aiops-for-faster-resolution\/\">look at handling incidents more quickly with automation-assisted tooling<\/a>, where closing the loop matters as much as detecting the problem.<\/p>\n<h2>Trends worth watching<\/h2>\n<ul>\n<li><strong>Limits on review queues.<\/strong> Teams are discovering that the pile often sits waiting for review, so they cap that column as well.<\/li>\n<li><strong>Personal limits alongside team limits.<\/strong> The two work together; the team ceiling prevents overload and the personal ceiling protects focus.<\/li>\n<li><strong>Visible age of items.<\/strong> Rather than counting alone, teams now mark how many days each card has been open.<\/li>\n<li><strong>Smaller slices of work.<\/strong> Tight limits favour tasks that can finish in a day or two, which changes how people write tickets.<\/li>\n<li><strong>Roadmaps that respect capacity.<\/strong> Planning documents increasingly show what is active now, what is next and what is later, instead of everything at once.<\/li>\n<\/ul>\n<h2>The roadmap connection<\/h2>\n<p>Longer-term plans are still essential, and they pair well with a limit. A roadmap tells you the order; a ceiling tells you how many steps to take at the same time. Teams working toward more automated operations often draw up a staged plan, such as the one laid out in this <a href=\"https:\/\/cotocus.org\/blog\/aiops-roadmap-a-practical-guide-for-devops-sre-and-operations-teams\/\">practical route to smarter operations for engineering and reliability staff<\/a>. Following it works best when each stage is completed before the next one opens.<\/p>\n<h2>A wider cultural current<\/h2>\n<p>The preference for fewer open loops is not confined to engineering. Look at how people use the web in general and you see the same tension between curiosity and completion. A wellness-themed site such as <a href=\"https:\/\/www.askdoctorlive.com\/\">AskDoctorLive<\/a>, with discussion threads, articles and hospital and doctor listings under one roof, is a small example of how a single destination can offer many places to go at once, and visitors have to decide for themselves how much to open. Teams make the same choice every day on their boards, which may be why the idea feels familiar even to people outside IT.<\/p>\n<h2>What the sceptics say<\/h2>\n<p>Not everyone is convinced. Critics point out that limits can be applied mechanically, that they can mask deeper problems with planning, and that some creative or exploratory work does not fit a tidy column. These are fair points. A limit is a tool for revealing where work gets stuck, not a cure. Teams that benefit tend to treat it as an experiment: set a number, watch the flow for a month, and keep or change it based on what they see.<\/p>\n<h2>Where it might go from here<\/h2>\n<p>Expect more attention on how long work waits rather than how busy people are. Expect boards that show age and blockers as plainly as counts. Expect planning conversations that begin by asking what can be finished this fortnight before asking what could be started. None of that requires new software; it requires a willingness to count honestly and to say &#8220;not yet&#8221; to the next exciting thing.<\/p>\n<h2>A friendly suggestion<\/h2>\n<p>If you are curious but cautious, try the smallest possible version. Pick one team, one board and one number, and run it for four weeks. Write down how long a typical item took before the trial and how long it takes after. If the answer is better, you have your own evidence. If it is not, you have learned something about your team&#8217;s flow either way. The trend is encouraging, but your own board is the only place where it will prove itself.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A relaxed look at why operations and delivery teams are capping open work, how the practice looks today and what to watch next.<\/p>\n","protected":false},"author":4,"featured_media":1289,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[129],"tags":[],"class_list":["post-1288","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\/1288","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=1288"}],"version-history":[{"count":1,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1288\/revisions"}],"predecessor-version":[{"id":1415,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1288\/revisions\/1415"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media\/1289"}],"wp:attachment":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media?parent=1288"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/categories?post=1288"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/tags?post=1288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}