{"id":79265,"date":"2025-08-19T17:08:45","date_gmt":"2025-08-19T10:08:45","guid":{"rendered":"https:\/\/www.wowrack.com\/?p=79265"},"modified":"2025-08-19T17:08:45","modified_gmt":"2025-08-19T10:08:45","slug":"your-90-day-plan-to-smarter-cloud-use","status":"publish","type":"post","link":"https:\/\/www.wowrack.com\/en-id\/blog\/cloud-2\/your-90-day-plan-to-smarter-cloud-use\/","title":{"rendered":"Your 90-Day Plan to Smarter Cloud Use"},"content":{"rendered":"

A lot of teams say they want to \u201cmake the cloud more efficient.\u201d Fewer actually get it done. The problem? Cloud optimization can feel like a moving target. There\u2019s too much data, too many priorities, and no clear deadline.<\/span>\u00a0<\/span><\/p>\n

That\u2019s why a 90-day sprint works so well. It\u2019s short enough to keep everyone focused, but long enough to deliver real, measurable changes. In just three months, you can go from unclear goals to actual improvements, without dragging the process out.<\/span>\u00a0<\/span><\/p>\n

Phase 1: Audit (Days 1\u201330)<\/span><\/span><\/span><\/h2>\n

Goal:<\/span><\/b> Understand where you are right now.<\/span>\u00a0<\/span><\/p>\n

You can\u2019t improve what you don\u2019t measure, but you also don\u2019t need to track every single number. Focus on metrics that tie your spending to real value, like cost per workload or idle resource percentage. Then pull the data from your cloud provider\u2019s reports and cross-check it with your own usage so you know exactly where your money\u2019s going.<\/span>\u00a0<\/span><\/p>\n

Steps to take:<\/span><\/b>\u00a0<\/span><\/p>\n

    \n
  1. Pick 4\u20135 core metrics to track for the sprint.<\/span>\u00a0<\/span><\/li>\n
  2. Gather cost and usage reports from your cloud console.<\/span>\u00a0<\/span><\/li>\n
  3. Tag or group resources by owner, project, or environment.<\/span>\u00a0<\/span><\/li>\n
  4. Flag unusual patterns, like sudden weekend spikes or resources running outside normal hours.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

    Example:<\/span><\/b>
    \nOne DevOps team found out 15% of their budget was going to dev environments just sitting there all weekend. They set them to shut down outside work hours and instantly saved millions of rupiahs, without messing with production.<\/span>\u00a0<\/span><\/p>\n

    Who to involve:<\/span><\/b>\u00a0<\/span><\/p>\n