AMS as a Product: Roadmap, Value Promises, and ‘Stop Doing’ Lists

{
  "id": "ams-034",
  "title": "AMS as a Product: Roadmap, Value Promises, and ‘Stop Doing’ Lists",
  "hook": "If SAP AMS is treated as a service desk, it stays expensive forever. If it’s treated as a product, it becomes predictable, improvable, and cheaper over time.",
  "idea": "A modern AMS roadmap is not a list of tickets. It’s a product plan: reliability targets, elimination of demand drivers, automation expansion, and deliberate deprecation of low-value work.",
  "product_definition": {
    "product": "Reliable SAP business operations + controlled change delivery + continuous cost reduction",
    "customers": [
      "Business process owners",
      "Key users and super users",
      "Internal IT and security",
      "Vendors and integration partners"
    ],
    "value_promises": [
      "Critical flows stay stable (SLOs)",
      "Changes are safe and predictable",
      "Recurring pain is eliminated, not normalized",
      "Cost-to-serve trends down"
    ]
  },
  "roadmap_streams": {
    "reliability_stream": [
      "SLO catalog per flow",
      "Observability and runbook coverage",
      "Error budget policy and freeze rules"
    ],
    "prevention_stream": [
      "Top demand driver elimination plan",
      "RCA quality uplift",
      "Master data and integration stabilization"
    ],
    "automation_stream": [
      "Standard change catalog expansion",
      "Self-service and templates",
      "Agentic triage and diagnosis support"
    ],
    "architecture_stream": [
      "Move volatile logic off-core",
      "Strengthen interface contracts",
      "Reduce Z-code blast radius and ownership gaps"
    ]
  },
  "prioritization_rules": [
    "If it protects a critical flow, it outranks convenience work.",
    "If it reduces repeats, it outranks new features with unclear ROI.",
    "If it increases lock-in or blast radius, it needs stronger justification.",
    "If we can’t verify success, it’s not a roadmap item."
  ],
  "deprecation_and_stop_doing": {
    "why_it_matters": "Cost reduction requires removing commitments, not just adding improvements.",
    "stop_doing_candidates": [
      "Manual repetitive role changes without standardization",
      "One-off custom reports with no reuse",
      "Cosmetic changes during stability risk windows",
      "Unsupported side-channel requests outside intake templates",
      "Fixes that repeatedly regress without addressing root cause"
    ],
    "deprecation_protocol": [
      "Declare what stops and why",
      "Offer replacement (self-service, KB, edge solution)",
      "Set a cutoff date",
      "Monitor backlash and real impact"
    ]
  },
  "governance": {
    "monthly_product_review": [
      "SLO compliance and stability trends",
      "Top 10 demand drivers movement",
      "Automation ROI realized",
      "Roadmap trade-offs and ‘stop doing’ decisions"
    ],
    "quarterly_reset": [
      "Rebuild roadmap from demand + business priorities",
      "Retire stale commitments",
      "Rebalance Run/Change/Improve/Reserve"
    ]
  },
  "automation": {
    "copilot_moves": [
      "Generate roadmap candidates from demand driver and cost-to-serve data.",
      "Suggest ‘stop doing’ items based on low ROI and high coordination cost.",
      "Track roadmap value realized vs promised."
    ],
    "outputs": [
      "Roadmap options with trade-offs",
      "Deprecation candidate list",
      "Value realization report"
    ]
  },
  "why_this_is_modern": [
    "AMS becomes intentional instead of reactive.",
    "Improvement is continuous and measurable.",
    "Dependence on individuals and SAP-only mechanisms decreases."
  ],
  "anti_patterns_to_kill": [
    "Roadmap = random backlog",
    "Always saying yes",
    "Never deprecating anything"
  ],
  "metrics_that_prove_product_maturity": [
    "Cost-to-serve trend down",
    "Repeat incidents trend down",
    "Percent of work on top demand drivers",
    "Delivery predictability (commit vs deliver)",
    "Automation coverage growth"
  ],
  "design_question": [
    "What are we willing to stop doing to make SAP operations cheaper and calmer?"
  ],
  "meta": {
    "schema": "dkharlanau.dataset.byte",
    "schema_version": "1.1",
    "dataset": "ams",
    "source_project": "cv-ai",
    "source_path": "ams/ams-034.json",
    "generated_at_utc": "2026-02-03T14:33:32+00:00",
    "creator": {
      "name": "Dzmitryi Kharlanau",
      "role": "SAP Lead",
      "website": "https://dkharlanau.github.io",
      "linkedin": "https://www.linkedin.com/in/dkharlanau"
    },
    "attribution": {
      "attribution_required": true,
      "preferred_citation": "Dzmitryi Kharlanau (SAP Lead). Dataset bytes: https://dkharlanau.github.io"
    },
    "license": {
      "name": "",
      "spdx": "",
      "url": ""
    },
    "links": {
      "website": "https://dkharlanau.github.io",
      "linkedin": "https://www.linkedin.com/in/dkharlanau"
    },
    "contact": {
      "preferred": "linkedin",
      "linkedin": "https://www.linkedin.com/in/dkharlanau"
    },
    "canonical_url": "https://dkharlanau.github.io/datasets/ams/ams-034.json",
    "created_at_utc": "2026-02-03T14:33:32+00:00",
    "updated_at_utc": "2026-02-03T15:29:02+00:00",
    "provenance": {
      "source_type": "chat_export_extraction",
      "note": "Extracted and curated by Dzmitryi Kharlanau; enriched for attribution and crawler indexing."
    },
    "entity_type": "ams_byte",
    "entity_subtype": "",
    "summary": "If SAP AMS is treated as a service desk, it stays expensive forever. If it’s treated as a product, it becomes predictable, improvable, and cheaper over time."
  }
}