The research standard behind every number on this site.
“Checked, not asserted” is a claim you can verify the discipline behind, not just take our word for.
Official Sources Only
Every domain — all eleven — is researched the same way, against SAP’s own official documentation: sap.com product and feature pages, the SAP Learning platform, the SAP Help Portal, and SAP Signavio’s own product pages. Not third-party blogs, not forum posts. An earlier pass of this work leaned on those; this round replaced it entirely with primary sources.
Disclosed, Not Hidden, Limitations
Two access constraints are stated plainly rather than glossed over. Some SAP Help Portal pages block automated fetches, so a handful of citations are confirmed via their own search result rather than a full page read — flagged inline where it applies. And SAP’s retired Best Practices Explorer, along with the full Signavio Process Navigator catalog behind a login, were never accessible at all — so they’re simply not used as sources, despite being directly relevant.
A Further Cross-Check, Not Just One Pass
The capability list was checked a second time against SAP’s own Fiori Apps Library — a public, no-login catalog of SAP’s actually-named, ID’d apps. The transactional capabilities came back strongly confirmed, each backed by a real, named app. Two categories genuinely have no standalone app of their own — not a research gap, but a structural fact: validation and duplicate-management checks live inside the creation apps rather than as separate apps, and platform-level capabilities like integration or workflow automation are architectural categories no single app represents.
Built to Fail If the Rule Is Broken
The cross-domain consistency this site claims — the same capability always getting the same verdict, the same accountable-role rule applied without exception — isn’t just asserted in prose. It’s checked programmatically against the full underlying dataset every time the model is built, and the build fails if either check is ever violated.
Why This Page Exists
Most of what a consultancy publishes about its own method can’t be checked. This can. If you want to see exactly which SAP documentation a specific number is built on, ask — the sourcing is kept, not thrown away once the summary is written.
Related: SEE IT · STEER IT · Business Case · How a Capability Gets Scored · Inside the Method · Home
