Demo sessions stay in this browser session only. Sign in to store permanently.
No filter active — role “All” and open domain/stack.
The Governance Hub is not just a link list. Flows shows the decision cycle from setup to recurring work. Then the advisor clarifies the situation; guides, workshop, and tools deliver the artifacts.
Decision Ladder: flow orientation → branch decision → tools/playbooks → evidence. Entry is the Flows tab; the advisor deepens the situation.
Collect Infos 8 names the eight canvas steps. Evidence Loop: decision → control → evidence. Platform Starting Point and Source Load First are one-liners from the existing series — the 8 Pillars stay the practical scaffold.
Each tool works standalone, but contributes a block to the same governance report. KPI Intake creates KPI cards, Source Scope the load scope, Mart Design table decisions, Starting-Point Decision the platform start, Data Quality rules/gates, Decision Brief the approval.
A guided entry point for data governance decisions: start with the flow (setup through operate), then advisor, guides, tools, suppliers, and playbooks.
It shows the governance lifecycle with branch decisions and deep links into existing playbooks, tools, and the calendar — without a workflow engine.
No. Recommendations work without sign-in. Permanent save needs an account; demo sessions stay in the browser.
Open the KPI entry or Workshop, capture stakeholders and KPI cards, then source scope and mart design.
No. The site provides curated guides and templates, not a substitute for legal or contract review.
Governance Help Hub
By Thomas Lindackers: start with the governance flow (setup through operate), then the right question, playbooks, tools, vendor resources, supplier library, and compliance. Example path without login: demo workspace and sample report.
Pick a flow via tabs. On the operating flow, also filter by phase (All / Setup / Pilot / Operate / Improve).
From the first decision mechanism through pilot to recurring work — with branch choices and links into playbooks, tools, and calendar.
This hub orchestrates setup → pilot → operate → improve. Clarify which decision is pending first — not which tool.
Roles may combine; decision rights must not blur. Size steers bundling, not the core logic.
Run three real cases through the flow. Do not rebuild an enterprise org chart — prove decision capacity.
Who may decide what? Which pillars are missing? Intake and matrix before the pilot.
Clarify platform starting point and governance boundaries before the pilot starts.
One well-run flow teaches more than five half-finished services. Pick the slice with visible business value and enough readiness.
Pick supplier, clarify core entities and skip tables, check PII/DSDR — then return to the master flow.
Evidence Owner decision separately from Custodian implementation — then return to the master flow.
Close the evidence loop. Decision brief and workspace report make the pilot approval-ready.
Forums follow decision volume. Anchor reviews, recertification, and ownership rounds in the calendar.
In operate mode, access, incidents, feedback, retirement, definition change, and new sources recur. Open the segment; each loop returns to intake, Owner decision, and plan update.
Run recurring access and recertification cases through the access flow.
Incident intake, severity, and improve — then back to intake, Owner decision, and plan update.
Onboard further sources with the same scope and gate pattern.
Capture the misread, Owner decides, fix or GDR — then return.
Retire asset and consumers with A, date, and stop line — then return.
Bind the change as a GDR — then back to intake and plan.
Every operate loop ends visibly: update intake, record the Owner decision, update the plan. Then back to cadence.
Which patterns repeat? Bundle exception age, escalations, radar topics, and review notes into an improve backlog — do not only close tickets.
Recurring cases belong in policy, gate, or product backlog. One-off residual risks stay documented exceptions with expiry.
Set owner, evidence, and next review date. Then return to operate — or restart the full cycle when setup must be revisited.
Übernimm bei Bedarf eine gespeicherte Presales-Discovery. Prüfe den ausgewählten Stand und bestätige die Übernahme; deine Advisor-Antworten werden durch die Auswahl allein nicht verändert.
Meine Nutzerrolle passt die Empfehlungen an. Ziel und Ausgangslage bleiben meine Auswahl.
Discovery entry points into hubs and tools.
Intake → authority matrix → gap register → charter → pilot — a repeatable delivery path for new programs.
Move from business question and stakeholders to KPI card, grain, owner, and first mart candidates.
Pick a supplier, understand core entities, review PII/DSDR, and mark skip tables before loading.
Treat Fabric, Databricks, Snowflake, dbt, BI, and catalog tools as one governance stack.
Handle personal data, free text, copies, masking, and evidence as an early project path.
Report inventory → KPI definition → grain/owner → mart → formula tool → evidence.
Eight steps from stakeholders to decision brief — with Markdown export for workshops.
Which question do you answer where — and which artifact comes next?
Decision question
Decision question
Decision question
Decision question
Decision question
The supplier library is not a favorites list. Pick the source type first, then the concrete system, and derive scope, PII, skip, and KPI usefulness.
Typical components per stack and three start tools — not a vendor directory.
Classic analytics stack: Snowflake, Fivetran, dbt, Atlan. BI: Tableau or Power BI (pick one).
Typical tools: snowflake, fivetran, dbt, tableau, powerbi, atlan
Start with these 3 tools
Azure-based: Fabric as analytics platform, Purview for governance, Power BI, Copilot, and planning/whiteboard tools.
Typical tools: azure, fabric, pureview, powerbi, microsoft-copilot, microsoft-whiteboard, microsoft-planner
Start with these 3 tools
Lakehouse with Databricks, dbt, Atlan and lineage. BI: Power BI or Tableau (pick one).
Typical tools: databricks, dbt, atlan, openlineage, marquez, powerbi, tableau
Start with these 3 tools
Google Cloud + BigQuery and dbt. BI: Metabase, Superset or Lightdash (pick one).
Typical tools: gcp, bigquery, dbt, metabase, superset, lightdash
Start with these 3 tools
Self-hosted / OSS with dbt. Catalog: DataHub or OpenMetadata; BI: Metabase, Superset or Lightdash (pick one each). Lineage: OpenLineage and Marquez are complementary.
Typical tools: dbt, metabase, superset, lightdash, datahub, openmetadata, openlineage, marquez
Start with these 3 tools
EU/DE hosting and on-prem-capable products for GDPR and public-sector contexts. Hosting: Hetzner or OVH; catalog: DataHub or OpenMetadata; BI: Metabase or Superset (pick one each).
Typical tools: hetzner, ovhcloud, sap, qlik, dbt, metabase, superset, datahub, openmetadata, talend, argonos
Start with these 3 tools
Select SAP components by inventory, goal and entitlement. BDC is the suite; accept native access, master data and external handoffs separately.
Typical tools: sap-s4hana, sap-bdc, sap-datasphere, sap-bw, sap-bw4hana, sap-analytics-cloud, sap-mdg
Start with these 3 tools
Delivery and enablement with GitHub. Coding agent: Cursor, Copilot, Codex, Claude or ChatGPT (pick one). Board: Miro or Planner (pick one); Microsoft Copilot optional alongside.
Typical tools: cursor, github-copilot, codex, claude, chatgpt, github, miro, microsoft-planner, microsoft-copilot
Start with these 3 tools
On-prem/hybrid lakehouse with CDP: NiFi or Kafka (pick one), Hive, Spark, Ranger and Atlas, Airflow.
Typical tools: cloudera-cdp, apache-nifi, apache-kafka, apache-hive, apache-spark, apache-ranger, apache-atlas, apache-airflow
Start with these 3 tools
Decision/intelligence with Argonos as platform core — governance via pillars, access, residency and evidence, not sovereignty claims alone.
Typical tools: argonos
Start with these 3 tools
Stakeholders, KPI cards, grain, and source — then mart design.
Related tools
Which entities to load, what to skip, where PII sits — then source scope and readiness.
Related tools
Eight workshop steps to the decision brief — notes stay local without login; after login you can save a session. Export as Markdown/JSON/CSV.
Diese Dokumentation ergänzt deinen Arbeitsfall. Für Empfehlungen im Advisor ist keine Texteingabe erforderlich.
Diese Angabe dokumentiert euren Review. Der Hub prüft die Belege nicht selbst und erteilt keine automatische Freigabe.
Output: RACI and interview list
Output: Prioritized question list
Output: kpi-cards.csv
Output: source-scope.csv
Output: PII/DSDR review sheet
Output: dq-backlog.csv
Output: mart-design-brief.md
Output: decision-brief.md
Notes belong to the shared case record. They are saved locally and included when explicitly saving the session to your account. Markdown/JSON here; CSV in the tools.
