Legacy route · personal lab

Problem-led practice playbooks.

This URL is kept stable because older pages and external links use it. The content is now a set of personal analysis exercises and reusable playbooks. It is not a commercial consulting catalogue.

Use public or synthetic data. Do not add client information.

Practice paths

Start with the problem.

Each route gives a structure for evidence, ownership, decisions, controls, and verification.

  1. 01

    AMS repeat work

    Find why the same support work returns.

    Use a repeat-pattern register, evidence boundary, owner map, and prevention backlog.

    Open playbook
  2. 02

    Data foundation

    Trace one critical master-data object.

    Follow creation, approval, replication, control, and business use.

    Open playbook
  3. 03

    Logistics & planning

    Make the exception decision visible.

    Connect signal, evidence, owner, approval, action, and feedback.

    Open playbook
  4. 04

    Integration

    Find the failed hand-off before changing tools.

    Separate business ownership from protocol and middleware choices.

    Open playbook
  5. 05

    AI agents

    Test one narrow task with clear authority.

    Keep production actions, approvals, and irreversible changes under deterministic and human control.

    Open playbook
  6. 06

    Architecture

    Compose a target architecture from explicit context.

    Inspect constraints, unknowns, rule traces, and delivery hand-offs.

    Open exercise

Lab boundary

Experiment without pretending it is production.

These pages are for learning, analysis, prototypes, and public technical discussion. They do not replace landscape-specific architecture, security, legal, or operational approval.

Business questions

Frequently asked questions before starting

Use these questions to choose the right problem boundary before discussing a project, platform, or delivery model.

When is a SAP transformation friction audit the right starting point?

It is the right starting point when change is happening but value is lost across process, data, integration, handover, and support boundaries. The goal is to find the friction before scaling more delivery work.

How do you protect clean-core S/4HANA during new delivery work?

Separate deterministic ERP logic that must stay close to transactional truth from automation, APIs, events, analytics, and edge services that should remain portable. The boundary is a business and lifecycle decision, not a slogan.

What is the fastest way to prove value before a larger SAP transformation programme?

Start with one audit slice, one repeat incident pattern, one handover gap, or one manual workflow where time, cost, or business risk is already visible. A narrow problem creates a measurable first decision.