Most SAP AMS pain starts before any work begins — at intake. Vague requests turn into scope creep, rework, and unsafe changes.
Attribution
Creator: Dzmitryi Kharlanau (SAP Lead).
Canonical: https://dkharlanau.github.io/datasets/ams/ams-036.json
JSON (copy / reuse)
{
"id": "ams-036",
"title": "Change Intake & Agreement: Stop Negotiating Chaos",
"hook": "Most SAP AMS pain starts before any work begins — at intake. Vague requests turn into scope creep, rework, and unsafe changes.",
"idea": "Modern AMS treats intake as a contract. Not legal — operational. Clear intent, impact, scope, and verification are agreed before effort is spent.",
"sap_intake_failures": {
"what_goes_wrong": [
"‘Small change’ with hidden cross-country impact",
"Business intent lost in technical wording",
"No agreement on what ‘done’ means",
"Testing assumed instead of defined"
]
},
"intake_contract": {
"mandatory_fields": [
"Business intent (what decision or flow improves)",
"Impacted flows (OTC/P2P/RTR/MDM/etc.)",
"Objects involved (BP, material, pricing, jobs, interfaces)",
"Countries/company codes affected",
"Risk appetite (can we rollback?)",
"Verification criteria (how we prove success)"
],
"nice_to_have": [
"Deadline driver (why this date matters)",
"Known constraints or freezes",
"Fallback or workaround if delayed"
]
},
"agreement_rules": [
"No agreement → no estimate.",
"No verification criteria → no deployment.",
"If scope changes, the agreement is re-opened.",
"Urgency does not replace clarity."
],
"change_acceptance_matrix": {
"accept": [
"Clear intent and impact",
"Known blast radius",
"Testable outcome"
],
"challenge": [
"Cosmetic change during risk window",
"High coordination for low impact",
"Logic that increases SAP lock-in"
],
"reject_or_defer": [
"Undefined success",
"No owner on business side",
"Conflicts with stability objectives"
]
},
"coordination_and_signoff": {
"who_signs": [
"Flow Owner (business impact)",
"Change Owner (delivery and safety)",
"Security/SoD (if access or roles change)"
],
"what_signoff_means": [
"Risk understood",
"Scope frozen",
"Verification agreed"
]
},
"automation": {
"copilot_moves": [
"Detect missing or vague intake fields.",
"Suggest impacted flows and objects from text.",
"Generate a draft verification checklist.",
"Flag requests that historically caused regressions."
],
"outputs": [
"Intake completeness score",
"Risk and blast-radius summary",
"Ready-for-estimate packet"
]
},
"why_this_saves_time_and_money": [
"Less rework and renegotiation mid-flight.",
"Fewer unsafe changes rushed into production.",
"Clear accountability when priorities clash."
],
"anti_patterns_to_kill": [
"Estimating on half-information",
"‘We’ll define testing later’",
"Silent scope expansion"
],
"metrics_that_show_intake_quality": [
"Changes re-scoped after start (%)",
"Change-induced incidents tied to poor intake",
"Average time from intake to ready-for-work",
"Requests rejected or deferred due to low value"
],
"design_question": [
"Would we still agree to this change if we had to explain its risk in one paragraph?"
],
"meta": {
"schema": "dkharlanau.dataset.byte",
"schema_version": "1.1",
"dataset": "ams",
"source_project": "cv-ai",
"source_path": "ams/ams-036.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-036.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": "Most SAP AMS pain starts before any work begins — at intake. Vague requests turn into scope creep, rework, and unsafe changes."
}
}