Skip to content
Beta

Briefings and Workshops

Create a shared understanding of requirements, responsibilities, and the commercial relationship before the engagement begins.

In 1 trail

Briefings and Workshops are focused exchanges between the customer and STACKIT before the contractual relationship begins. They are appropriate when self-registration alone does not provide enough clarity for the planned use of the platform, the migration scope, or the required commercial and operational setup.

The sessions create a common understanding of the customer’s objectives and requirements, as well as the services, responsibilities, and engagement model that STACKIT can provide. Their goal is a contract relationship that is clear, practical, and suitable for both parties.

Use briefings and workshops when the planned engagement requires coordination beyond a standard self-service setup, for example because it involves a larger migration, specific compliance needs, several customer organizations, or individual commercial and operational requirements.

The format can include a short briefing, a series of working sessions, or a joint workshop. The scope and participants should match the complexity and decision needs of the engagement.

The sessions establish a shared, documented basis for the following topics:

  • Business objectives and scope: Intended platform use, migration goals, priorities, expected scale, and relevant workloads.
  • Organizations and responsibilities: Customer contacts, decision-makers, technical teams, procurement, and the respective responsibilities of the customer and STACKIT.
  • Account and project structure: Required organizations, projects, access roles, ownership model, and the setup needed for the intended use.
  • Security, compliance, and data protection: Regulatory requirements, data classification, data residency, security expectations, and evidence needed for internal approval.
  • Commercial model and contracting: Required contract scope, pricing and billing expectations, commitments, procurement process, and any necessary contractual clarifications.
  • Operations and support: Service expectations, support model, escalation paths, operational responsibilities, and relevant availability requirements.
  • Delivery planning: Preconditions, dependencies, timeline, decision points, and the next steps toward onboarding, design, and migration.

Include the people who can clarify the relevant business, technical, legal, and operational questions. Depending on the engagement, this may include customer sponsors, procurement, legal, security and compliance representatives, technical owners, and the corresponding STACKIT contacts.

Prepare the sessions with an initial description of the intended use, known requirements, expected scale, and open questions. This allows the discussion to focus on decisions and unresolved assumptions instead of basic fact finding.

At the end of the module, both parties should have:

  • a shared understanding of the intended platform use and engagement scope;
  • a documented view of requirements, assumptions, dependencies, and open items;
  • agreement on the required account, security, support, and commercial setup;
  • clear responsibilities and decision owners for the next steps; and
  • a mutually understood path toward contracting and subsequent onboarding.

Briefings and Workshops do not replace technical discovery, a Deepdive Workshop, or detailed solution design. They ensure that the commercial, organizational, and operational foundation is aligned so that those activities can proceed with clear expectations and an appropriate contractual basis.