[{"data":1,"prerenderedAt":831},["ShallowReactive",2],{"post:\u002F2025\u002F06\u002F13\u002Finfrastructure-as-a-product-treating-core-systems-with-the-same-rigor-as-software\u002F":3},{"post":4,"newer":694,"older":705,"related":715,"series":738},{"id":5,"title":6,"body":7,"canonical":671,"categories":672,"date":674,"description":675,"extension":676,"featured":677,"hero":678,"image":679,"meta":680,"navigation":681,"path":682,"readingTime":683,"seo":684,"series":685,"seriesOrder":686,"sites":687,"source":671,"stem":689,"tags":690,"updated":691,"url":692,"__hash__":693},"blog\u002Fblog\u002F2025\u002F06\u002F13\u002Finfrastructure-as-a-product-treating-core-systems-with-the-same-rigor-as-software.md","Infrastructure as a Product: Treating core systems with the same rigor as software",{"type":8,"value":9,"toc":652},"minimark",[10,15,24,27,33,36,39,42,46,53,68,75,78,87,90,96,102,108,114,127,130,136,141,144,147,150,153,157,163,170,175,186,189,192,197,204,218,221,226,240,247,251,261,272,275,293,296,300,314,318,324,331,342,346,360,367,371,381,384,398,405,409,423,426,430,433,450,453,457,471,475,481,484,487,504,507,510,513,517,524,531,537,543,549,553,570,574,580,587,591,597,600,603,606,609,612,617,620,626,641,649],[11,12,14],"h2",{"id":13},"infrastructure-is-no-longer-an-afterthought","Infrastructure Is No Longer an Afterthought",[16,17,18,19,23],"p",{},"For the past six weeks, we’ve explored the foundations of modern ITSM, from value streams and guiding principles to service desks and delivery chains. However, we now turn to the unsung hero of digital operations: ",[20,21,22],"strong",{},"infrastructure",".",[16,25,26],{},"Not the server room kind. Not the rack-and-stack legacy. We’re talking about cloud-native, Kubernetes-powered, platform-driven infrastructure that shapes how fast you build, how well you recover, and how efficiently you scale.",[28,29,30],"blockquote",{},[16,31,32],{},"This week, we’re flipping the script. Infrastructure is no longer just “the environment.”",[16,34,35],{},"It’s the platform your teams rely on, the product your engineers consume, and the accelerator that makes or breaks delivery.",[16,37,38],{},"If your infrastructure team still operates like a helpdesk for virtual machines, it’s time to evolve. Because the orgs getting this right aren’t just keeping the lights on… they’re launching, scaling, and learning faster than ever.",[16,40,41],{},"Let’s talk about what it really means to treat Infrastructure as a Product.",[11,43,45],{"id":44},"why-the-old-infrastructure-model-falls-short","Why the Old Infrastructure Model Falls Short",[16,47,48],{},[49,50],"img",{"alt":51,"src":52},"Stylized teal server racks and control panels linked by pipes, representing the traditional infrastructure model","\u002Fuploads\u002F2025\u002F06\u002Fimage-6-1024x576.png",[16,54,55,56,59,60,63,64,67],{},"Infrastructure isn’t broken. However, the way we ",[20,57,58],{},"use",", ",[20,61,62],{},"organize",", and ",[20,65,66],{},"deliver it"," is often.",[16,69,70,71,74],{},"There’s nothing wrong with traditional data centers, blade servers, or private cloud architectures. What matters is ",[20,72,73],{},"how"," they’re managed, and whether they’ve evolved beyond the ticket queues and tribal knowledge that defined infrastructure for decades.",[16,76,77],{},"Let’s be clear: You don’t need to be in a hyperscale cloud to run modern infrastructure. But you do need to evolve past the rack-and-stack mindset that sees infrastructure as a static, background utility.",[28,79,80],{},[16,81,82,83,86],{},"Because in today’s environment, ",[20,84,85],{},"infrastructure is a service","… not a destination.",[16,88,89],{},"Here’s where the legacy model falls short:",[16,91,92,95],{},[20,93,94],{},"1. It’s Ticket-Driven, Not Experience-Driven."," Legacy infrastructure operates like an internal vendor. Developers request resources through a service desk, wait days (or weeks), and get something that may or may not meet their actual need. This slows product delivery and pushes teams to bypass the process just to keep up.",[16,97,98,101],{},[20,99,100],{},"2. It’s Disconnected From Strategy."," Traditional infrastructure teams often get looped in too late. They’re asked to “make it work” after a product is designed, a campaign is launched, or a vendor is selected. By then, it’s too late to design for scale, resilience, or performance. The opportunity to shape outcomes has already passed.",[16,103,104,107],{},[20,105,106],{},"3. It Prioritizes Stability Over Innovation."," Yes, uptime matters. But so does velocity. Too many infrastructure teams still operate under a change-fearing mindset, limiting experimentation, automating nothing, and guarding every change as if it were radioactive. This leads to stagnation, burnout, and finger-pointing.",[16,109,110,113],{},[20,111,112],{},"4. It’s Siloed and Manual."," Even in modern data centers, we see:",[115,116,117,121,124],"ul",{},[118,119,120],"li",{},"No centralized observability",[118,122,123],{},"No service ownership",[118,125,126],{},"No infrastructure-as-code",[16,128,129],{},"Instead, the knowledge lives in someone’s head or in outdated runbooks. Provisioning requires human steps. Recovery takes too long. And every environment behaves differently.",[16,131,132,135],{},[20,133,134],{},"5. It’s Invisible Until It Breaks."," In this model, no one notices the infrastructure until something fails. And that invisibility creates a cycle: underinvestment, lack of recognition, minimal collaboration.",[28,137,138],{},[16,139,140],{},"The irony? When it goes down, the whole business stops.",[16,142,143],{},"The reality is this: You can run bleeding-edge infrastructure in your own colocation facility. And you can run outdated, fragile infrastructure in the cloud.",[16,145,146],{},"It’s not about where the servers live. It’s about how intentional and evolved your approach is.",[16,148,149],{},"The future of infrastructure isn’t cloud vs. on-prem. It’s product vs. process. Strategic vs. reactive.",[16,151,152],{},"And the organizations that treat infrastructure like a modern platform, wherever it runs, are the ones that will lead.",[11,154,156],{"id":155},"the-modern-infrastructure-as-a-product-model","The Modern Infrastructure-as-a-Product Model",[16,158,159],{},[49,160],{"alt":161,"src":162},"Isometric stacks of teal database cylinders on a circuit board beside a rising bar chart, representing infrastructure as a product","\u002Fuploads\u002F2025\u002F06\u002Fimage-9-1024x576.png",[16,164,165,166,169],{},"Infrastructure today isn’t just racked and stacked. It’s ",[20,167,168],{},"shaped, shipped, and supported"," like a product.",[28,171,172],{},[16,173,174],{},"That means moving beyond uptime metrics and into ownership, usability, and value delivery.",[16,176,177,178,181,182,185],{},"Done right, infrastructure becomes the internal engine that powers ",[20,179,180],{},"speed, safety,"," and ",[20,183,184],{},"scale",". It’s not about abandoning traditional environments. It’s about evolving how we use them, whether you’re on bare metal in a private cage or orchestrating containers across multi-cloud regions.",[16,187,188],{},"So what does Infrastructure-as-a-Product actually look like?",[16,190,191],{},"Let’s break it down.",[193,194,196],"h3",{"id":195},"_1-platform-teams-think-like-product-teams","1. Platform Teams Think Like Product Teams",[16,198,199,200,203],{},"Modern infra isn’t just managed. It’s ",[20,201,202],{},"built"," with internal consumers in mind.",[115,205,206,209,212,215],{},[118,207,208],{},"Internal developer platforms offer self-service environments, observability stacks, and data pipelines",[118,210,211],{},"APIs replace tickets",[118,213,214],{},"Developers deploy with autonomy, not dependency",[118,216,217],{},"Roadmaps define capabilities, just like a product release cycle",[16,219,220],{},"Just like a product, these services require owners, documentation, feedback loops, and a focus on usability.",[16,222,223],{},[20,224,225],{},"Transformation Tactics:",[115,227,228,231,234,237],{},[118,229,230],{},"Define a service catalog: what infra services exist, who owns them, and what their SLAs are",[118,232,233],{},"Assign product owners, not just sysadmins, to each major internal offering",[118,235,236],{},"Create a roadmap and publish it to internal teams",[118,238,239],{},"Hold quarterly “platform town halls” to gather feedback and share improvements",[16,241,242,243,246],{},"This mindset shift turns the infra team into a strategic ",[20,244,245],{},"enabler",", not a support bottleneck.",[193,248,250],{"id":249},"_2-kubernetes-and-cloud-native-are-the-norm","2. Kubernetes and Cloud-Native Are the Norm",[16,252,253,254,181,257,260],{},"Infrastructure must now be ",[20,255,256],{},"portable, scalable,",[20,258,259],{},"elastic"," by design.",[115,262,263,266],{},[118,264,265],{},"Kubernetes, containers, and serverless are today’s default, not tomorrow’s trend",[118,267,268,269],{},"But the challenge isn’t just deploying them, it’s ",[20,270,271],{},"operating them",[16,273,274],{},"Ask your team:",[115,276,277,280,283,286],{},[118,278,279],{},"Who owns the pod when it crashes?",[118,281,282],{},"Is observability standardized and enforced?",[118,284,285],{},"Do autoscaling, logging, and alerting function predictably?",[118,287,288,289,292],{},"Are developers aware of the ",[20,290,291],{},"cost"," impact of their architectural decisions?",[16,294,295],{},"This is where ITSM principles matter. Visibility, governance, and accountability help you move fast without chaos.",[16,297,298],{},[20,299,225],{},[115,301,302,305,308,311],{},[118,303,304],{},"Define SLOs for platform resilience and incident response",[118,306,307],{},"Make cost insights accessible at the developer level",[118,309,310],{},"Standardize Helm charts, templates, and deployment patterns",[118,312,313],{},"Align Kubernetes and container governance with change and release policies",[193,315,317],{"id":316},"_3-multi-region-is-no-longer-optional","3. Multi-Region Is No Longer Optional",[16,319,320,321,23],{},"If you’re still building for a single region, you’re creating for ",[20,322,323],{},"yesterday’s load",[16,325,326,327,330],{},"Modern infra needs to be ",[20,328,329],{},"resilient by design",", and that means multi-region or multi-zone deployments.",[115,332,333,336,339],{},[118,334,335],{},"DR isn’t just a runbook. It’s architecture.",[118,337,338],{},"Latency optimization isn’t a nice-to-have. It’s user experience.",[118,340,341],{},"Failover and rerouting aren’t special events. They’re standard paths.",[16,343,344],{},[20,345,225],{},[115,347,348,351,354,357],{},[118,349,350],{},"Design active-active or active-passive architectures early in the build process",[118,352,353],{},"Replicate databases with auto-sync and conflict resolution",[118,355,356],{},"Use global load balancers and DNS to abstract regional complexity",[118,358,359],{},"Extend observability tooling to track performance by region and path",[16,361,362,363,366],{},"And none of it works unless infrastructure is looped into the business from the ",[20,364,365],{},"start",", not when the outage happens.",[193,368,370],{"id":369},"_4-self-service-isnt-just-for-end-users","4. Self-Service Isn’t Just for End Users",[16,372,373,374,181,377,380],{},"Think beyond customer experience; your ",[20,375,376],{},"internal developers, QA teams,",[20,378,379],{},"analysts"," are users too.",[16,382,383],{},"Smart infrastructure teams are reducing toil and enabling autonomy by delivering:",[115,385,386,389,392,395],{},[118,387,388],{},"Portals for spinning up test environments",[118,390,391],{},"CLI tools for log access and job monitoring",[118,393,394],{},"Slack bots that let users trigger common provisioning tasks",[118,396,397],{},"Pre-baked templates for launching secure, observable microservices",[16,399,400,401,404],{},"This is what ",[20,402,403],{},"shift-left"," really looks like.",[16,406,407],{},[20,408,225],{},[115,410,411,414,417,420],{},[118,412,413],{},"Build a basic portal or bot to request environments, logs, or access",[118,415,416],{},"Templatize deployments for dev and test with automation tools",[118,418,419],{},"Implement fine-grained RBAC and logging so teams get what they need safely",[118,421,422],{},"Use feedback loops to refine tools and remove friction",[16,424,425],{},"Internal consumers expect the same clarity and speed they get from external SaaS. If your infra can’t deliver that, it’s time to evolve.",[193,427,429],{"id":428},"_5-infra-strategy-business-strategy","5. Infra Strategy = Business Strategy",[16,431,432],{},"Modern infrastructure teams don’t just maintain systems. They drive:",[115,434,435,438,441,444,447],{},[118,436,437],{},"Speed-to-market through CI\u002FCD, automation, and reliability",[118,439,440],{},"Cost-efficiency via resource optimization and FinOps insight",[118,442,443],{},"Security with embedded guardrails, IAM enforcement, and config drift detection",[118,445,446],{},"User experience with performance, latency, and recovery design",[118,448,449],{},"Team collaboration by integrating with dev, QA, security, and support",[16,451,452],{},"And ITSM ties it all together, offering shared visibility, real governance, and intentional service delivery.",[16,454,455],{},[20,456,225],{},[115,458,459,462,465,468],{},[118,460,461],{},"Include infrastructure in sprint planning and go\u002Fno-go decisions",[118,463,464],{},"Align SLOs and incident response with business goals",[118,466,467],{},"Track infrastructure adoption and service usage like a product team",[118,469,470],{},"Evolve KPIs from uptime and ticket count to enablement and reliability metrics",[11,472,474],{"id":473},"how-to-start-your-infra-as-product-journey","How to Start Your Infra-as-Product Journey",[16,476,477],{},[49,478],{"alt":479,"src":480},"Glowing teal circular interface with circuit-line icons over blurred server racks, representing a self-service infrastructure platform","\u002Fuploads\u002F2025\u002F06\u002Fimage-8-1024x576.png",[16,482,483],{},"You don’t need to reorg everything overnight.",[16,485,486],{},"Start small:",[115,488,489,492,495,498,501],{},[118,490,491],{},"Choose one infrastructure service to treat like a product",[118,493,494],{},"Document it, assign an owner, build feedback loops",[118,496,497],{},"Create a roadmap… even if it’s just two quarters",[118,499,500],{},"Add automation, self-service, or metrics that improve the developer experience",[118,502,503],{},"Tell the story internally: “This is how we’re evolving infrastructure.”",[16,505,506],{},"Then scale that mindset to the rest.",[16,508,509],{},"Because the best infra teams today aren’t hidden behind firewalls and rack doors.",[16,511,512],{},"They’re building platforms. Delivering value. And thinking like product teams.",[11,514,516],{"id":515},"practical-takeaways","Practical Takeaways",[16,518,519,520,523],{},"✅ ",[20,521,522],{},"Define your infrastructure services like products."," Include clear owners, SLAs, lifecycle documentation, and expectations for how internal teams use each one.",[16,525,526,527,530],{},"✅",[20,528,529],{},"Build a basic internal platform."," Start with self-service access to environments, logs, or common tooling. Even a basic script or portal can reduce friction fast.",[16,532,526,533,536],{},[20,534,535],{},"Include infra leaders in the conversation."," They should be in sprint planning, release reviews, and postmortems, not just pulled in after things break.",[16,538,526,539,542],{},[20,540,541],{},"Treat observability and automation as non-negotiable."," If you can’t see it or script it, it’s a liability. Invest in making your systems self-aware and self-managing.",[16,544,526,545,548],{},[20,546,547],{},"Map infrastructure to value streams."," Identify where delays, handoffs, or knowledge gaps happen. If a ticket is the only thing connecting teams, something’s broken.",[11,550,552],{"id":551},"actionable-questions","Actionable Questions",[115,554,555,558,561,564,567],{},[118,556,557],{},"Are our infra teams consulted during roadmap planning, or only during incidents?",[118,559,560],{},"How much of our infrastructure is still provisioned manually?",[118,562,563],{},"Can developers self-serve everyday infrastructure tasks today?",[118,565,566],{},"What’s our plan for multi-region redundancy, cost visibility, and automation?",[118,568,569],{},"Do we track infrastructure usage in the same way a product team tracks feature adoption?",[11,571,573],{"id":572},"coming-up-next-change-enablement-in-a-devops-world","Coming Up Next: Change Enablement in a DevOps World",[16,575,576,577,23],{},"Next week, we’re diving into one of the most debated topics in ITSM: ",[20,578,579],{},"Change Management",[16,581,582,583,586],{},"Forget the 47-step forms and Thursday CAB meetings. You’ll learn how modern orgs are enabling change at DevOps speed, with ",[20,584,585],{},"risk-aware, policy-backed, automation-driven"," models that keep governance tight and delivery flowing.",[11,588,590],{"id":589},"final-thought","Final Thought",[16,592,593],{},[49,594],{"alt":595,"src":596},"Cartoon alien working at a laptop in a server room with circuit lines and dashboards, a light-hearted Final Thought image","\u002Fuploads\u002F2025\u002F06\u002Fimage-7.png",[16,598,599],{},"You wouldn’t build a skyscraper without engineers, architects, and a structural foundation.",[16,601,602],{},"Yet in so many organizations, we expect miracles from infrastructure teams that are under-resourced, underappreciated, and brought in only when things go wrong.",[16,604,605],{},"It’s time to stop treating infrastructure as invisible.",[16,607,608],{},"You can’t build software without it. You can’t run a release without it. You can’t deliver an experience, drive revenue, or recover from failure without infrastructure and operations at the core.",[16,610,611],{},"Modern businesses run on APIs, pipelines, services, and platforms. Every click, every order, and every login flows through the infrastructure. It’s the bloodstream of your entire digital enterprise.",[28,613,614],{},[16,615,616],{},"If you’re still treating your infrastructure team like a helpdesk for VMs, you’re not just behind… you’re actively holding your business back.",[16,618,619],{},"The best orgs know this. They invest. They empower. They bring infrastructure into the strategy room, not just the war room.",[16,621,622,623,23],{},"Because infrastructure is no longer a cost center. It’s a ",[20,624,625],{},"force multiplier",[16,627,628,629,632,633,636,637,640],{},"And when you treat it like a product, ",[20,630,631],{},"built with care",", ",[20,634,635],{},"supported with pride",", and ",[20,638,639],{},"designed for scale",", that’s when your business moves faster, breaks less, and finally starts to unlock the full value of the digital world.",[16,642,643,644,648],{},"Infrastructure isn’t the back of the house. It ",[645,646,647],"em",{},"is"," the house.",[16,650,651],{},"It’s time to start building like we mean it.",{"title":653,"searchDepth":654,"depth":654,"links":655},"",2,[656,657,658,666,667,668,669,670],{"id":13,"depth":654,"text":14},{"id":44,"depth":654,"text":45},{"id":155,"depth":654,"text":156,"children":659},[660,662,663,664,665],{"id":195,"depth":661,"text":196},3,{"id":249,"depth":661,"text":250},{"id":316,"depth":661,"text":317},{"id":369,"depth":661,"text":370},{"id":428,"depth":661,"text":429},{"id":473,"depth":654,"text":474},{"id":515,"depth":654,"text":516},{"id":551,"depth":654,"text":552},{"id":572,"depth":654,"text":573},{"id":589,"depth":654,"text":590},"lasswell",[673],"business","2025-06-13T00:35:22Z","For the past six weeks, we’ve explored the foundations of modern ITSM, from value streams and guiding principles to service desks and delivery chains.","md",false,null,"\u002Fuploads\u002F2025\u002F06\u002FChatGPT-Image-Jun-12-2025-08_32_06-PM.png",{},true,"\u002Fblog\u002F2025\u002F06\u002F13\u002Finfrastructure-as-a-product-treating-core-systems-with-the-same-rigor-as-software",9,{"title":6,"description":675},"itsm-in-practice",7,[671,688],"techcolumnist","blog\u002F2025\u002F06\u002F13\u002Finfrastructure-as-a-product-treating-core-systems-with-the-same-rigor-as-software",[],"2025-06-13T11:44:57Z","\u002F2025\u002F06\u002F13\u002Finfrastructure-as-a-product-treating-core-systems-with-the-same-rigor-as-software\u002F","vFXUPWKTI88e1pvjgydVq9uyUV8bgGpgstLf5D18KQk",{"title":695,"description":696,"date":697,"url":698,"categories":699,"tags":700,"image":701,"readingTime":702,"canonical":671,"sites":703,"series":685,"seriesOrder":704},"Change Enablement in a DevOps World: Replacing fear of change with velocity and trust","We’ve spent the past seven weeks reframing how modern ITSM works, from infrastructure and service desks to principles, value streams, and product thinking.","2025-06-23T23:14:31Z","\u002F2025\u002F06\u002F23\u002Fchange-enablement-in-a-devops-world-replacing-fear-of-change-with-velocity-and-trust\u002F",[673],[],"\u002Fuploads\u002F2025\u002F06\u002FChatGPT-Image-Jun-23-2025-07_04_53-PM.png",10,[671,688],8,{"title":706,"description":707,"date":708,"url":709,"categories":710,"tags":711,"image":712,"readingTime":702,"canonical":671,"sites":713,"series":685,"seriesOrder":714},"Modern Service Desk Operations: From ticket takers to business enablers","The service desk gets a promotion: how modern service desk operations move from ticket takers to business enablers.","2025-06-05T20:11:41Z","\u002F2025\u002F06\u002F05\u002Fmodern-service-desk-operations-from-ticket-takers-to-business-enablers\u002F",[],[],"\u002Fuploads\u002F2025\u002F06\u002FChatGPT-Image-Jun-5-2025-04_01_05-PM.png",[671,688],6,[716,725,734],{"title":717,"description":718,"date":719,"url":720,"categories":721,"tags":722,"image":723,"readingTime":704,"canonical":671,"sites":724,"series":685,"seriesOrder":702},"Service Portfolios & Productization: Defining, marketing, and managing IT services","Ten weeks of rethinking IT not as a cost center, but as a strategic driver.","2025-07-28T23:49:15Z","\u002F2025\u002F07\u002F28\u002Fservice-portfolios-productization-defining-marketing-and-managing-it-services\u002F",[673],[],"\u002Fuploads\u002F2025\u002F07\u002FChatGPT-Image-Jul-28-2025-07_40_34-PM.png",[671,688],{"title":726,"description":727,"date":728,"url":729,"categories":730,"tags":731,"image":732,"readingTime":702,"canonical":671,"sites":733,"series":685,"seriesOrder":683},"Service Knowledge & Configuration: Building a system of record that helps","Building a service knowledge and configuration system of record that actually helps, after eight weeks on the pillars of modern ITSM.","2025-07-02T16:19:15Z","\u002F2025\u002F07\u002F02\u002Fservice-knowledge-configuration-building-a-system-of-record-that-helps\u002F",[673],[],"\u002Fuploads\u002F2025\u002F07\u002FChatGPT-Image-Jul-2-2025-12_18_41-PM.png",[671,688],{"title":695,"description":696,"date":697,"url":698,"categories":735,"tags":736,"image":701,"readingTime":702,"canonical":671,"sites":737,"series":685,"seriesOrder":704},[673],[],[671,688],{"doc":739,"posts":769},{"id":740,"title":741,"body":742,"canonical":671,"cover":678,"date":761,"description":762,"extension":676,"meta":763,"navigation":681,"path":764,"seo":765,"sites":766,"slug":685,"stem":767,"__hash__":768},"series\u002Fseries\u002Fitsm-in-practice.md","ITSM in Practice",{"type":8,"value":743,"toc":759},[744,747,750,753],[16,745,746],{},"For years, ITSM has carried the baggage of thick binders, change advisory boards that meet once a month, and frameworks that feel like they were written for a world of mainframes and ticket queues. But the job hasn't gone away, it's changed shape. Today's IT organizations run in the cloud, ship on sprints, and answer to a business that expects speed without sacrificing reliability.",[16,748,749],{},"This series is my attempt to rebuild ITSM for that world: connective tissue between strategy and delivery, not a stack of approvals standing between them. Over ten parts, we'll work from first principles, the Service Value System, governance that moves with you instead of against you, through to the practical mechanics of service desks, infrastructure as a product, change enablement, configuration management, and how to package what IT delivers as an actual portfolio of services.",[16,751,752],{},"If you've ever felt the tension between \"move fast\" and \"keep the lights on,\" this is for you. Each part builds on the last, but you can also drop in wherever your team is stuck today.",[754,755,756],"takeaway",{},[16,757,758],{},"ITSM is not the approval layer between strategy and delivery. Done well, it is the connective tissue that lets a cloud-native, sprint-driven organization move fast without losing the plot.",{"title":653,"searchDepth":654,"depth":654,"links":760},[],"2025-05-01","A ten-part series on running modern IT service management in a cloud-native, agile, multi-framework world, from governance to service portfolios.",{},"\u002Fseries\u002Fitsm-in-practice",{"title":741,"description":762},[671,688],"series\u002Fitsm-in-practice","9mZGhF0GtiOqnGwdRKG--iMds67WyVuFeBPaDTY8BOE",[770,781,790,799,809,705,819,694,823,827],{"title":771,"description":772,"date":773,"url":774,"categories":775,"tags":776,"image":777,"readingTime":778,"canonical":671,"sites":779,"series":685,"seriesOrder":780},"Why ITSM Still Matters in a Cloud-Native, Agile, Multi-Framework World","Technology is no longer a back-office function; it’s the front door to your customer, your employee experience, and your ability to scale.","2025-05-01T01:43:15Z","\u002F2025\u002F05\u002F01\u002Fwhy-itsm-still-matters-in-a-cloud-native-agile-multi-framework-world\u002F",[673],[],"\u002Fuploads\u002F2025\u002F05\u002FChatGPT-Image-Apr-30-2025-09_33_34-PM.png",12,[671,688],1,{"title":782,"description":783,"date":784,"url":785,"categories":786,"tags":787,"image":788,"readingTime":714,"canonical":671,"sites":789,"series":685,"seriesOrder":654},"The Service Value System: How to connect strategy to execution through value streams","Last week, we discussed why ITSM still matters in a world filled with sprints, pipelines, and cloud-native technology.","2025-05-08T19:29:15Z","\u002F2025\u002F05\u002F08\u002Fthe-service-value-system-how-to-connect-strategy-to-execution-through-value-streams\u002F",[673],[],"\u002Fuploads\u002F2025\u002F05\u002FChatGPT-Image-May-8-2025-02_38_54-PM.png",[671,688],{"title":791,"description":792,"date":793,"url":794,"categories":795,"tags":796,"image":797,"readingTime":683,"canonical":671,"sites":798,"series":685,"seriesOrder":661},"Governance Without Gridlock: Balancing agility and accountability in service delivery","But here’s the rub: even with strategy in place and value streams mapped, progress often grinds to a halt at the first sign of governance.","2025-05-15T18:42:50Z","\u002F2025\u002F05\u002F15\u002Fgovernance-without-gridlock-balancing-agility-and-accountability-in-service-delivery\u002F",[673],[],"\u002Fuploads\u002F2025\u002F05\u002FChatGPT-Image-May-15-2025-02_24_06-PM.png",[671,688],{"title":800,"description":801,"date":802,"url":803,"categories":804,"tags":805,"image":806,"readingTime":704,"canonical":671,"sites":807,"series":685,"seriesOrder":808},"The Service Value Chain: Using Engage, Plan, Build, and Support to run your ops","But let’s be honest, even with clarity of purpose and the best-intentioned guardrails in place, delivery still breaks down when teams aren’t moving in sync.","2025-05-23T13:32:10Z","\u002F2025\u002F05\u002F23\u002Fthe-service-value-chain-using-engage-plan-build-and-support-to-run-your-ops\u002F",[673],[],"\u002Fuploads\u002F2025\u002F05\u002FChatGPT-Image-May-23-2025-09_31_00-AM.png",[671,688],4,{"title":810,"description":811,"date":812,"url":813,"categories":814,"tags":815,"image":816,"readingTime":704,"canonical":671,"sites":817,"series":685,"seriesOrder":818},"Guiding Principles as Decision Filters: Making faster, more intelligent choices across teams","Sometimes you need to make a call right now, with half the information and zero precedent.","2025-05-29T16:16:11Z","\u002F2025\u002F05\u002F29\u002Fguiding-principles-as-decision-filters-making-faster-more-intelligent-choices-across-teams\u002F",[673],[],"\u002Fuploads\u002F2025\u002F05\u002FChatGPT-Image-May-29-2025-11_58_16-AM.png",[671,688],5,{"title":6,"description":675,"date":674,"url":692,"categories":820,"tags":821,"image":679,"readingTime":683,"canonical":671,"sites":822,"series":685,"seriesOrder":686},[673],[],[671,688],{"title":726,"description":727,"date":728,"url":729,"categories":824,"tags":825,"image":732,"readingTime":702,"canonical":671,"sites":826,"series":685,"seriesOrder":683},[673],[],[671,688],{"title":717,"description":718,"date":719,"url":720,"categories":828,"tags":829,"image":723,"readingTime":704,"canonical":671,"sites":830,"series":685,"seriesOrder":702},[673],[],[671,688],1789970931942]