SIAM principles and the service integration mindset
Domain 2 tests whether you can apply SIAM's principles to a scenario and recognise the behaviours the service integration mindset demands - not merely recite slogans.
The principles as applied rules
The BoK's principles cluster around a small number of testable ideas:
- End-to-end service focus: optimise the service the business consumes, not one provider's metrics.
- Integration of people, process, technology and information: the SIAM layer joins these; it does not duplicate delivery.
- Collaboration and trust, with verification: providers share performance data, risks and problems early.
- Transparency: one version of the performance truth, visible to all parties.
- Clear accountability and governance: collaboration is not consensus; decision rights and escalation are defined.
- Culture and behaviour: contracts and processes enable SIAM, behaviour delivers it.
- Continual improvement and standardisation: consistent, automated interfaces wherever practical.
The integration mindset
It is a shift from adversarial, contract-first behaviour to shared goals and shared consequences. In practice it appears as joint change calendars, blameless post-incident reviews, shared risk registers, common terminology and a single service catalogue. Providers remain commercially separate - the mindset changes the interface, not the contract.
Worked example
Two providers schedule conflicting changes on the same Saturday. Provider A's SLA rewards speed; provider B's penalises downtime. Applying transparency and joint planning, the integrator runs one change calendar with a shared risk assessment, sequences both changes inside a maintenance window the business approved, and records the dependency in the integrated CMDB. Reasoning: without shared visibility each provider optimises locally and the business absorbs the collision. The principle drives a design change, not the other way round.
Traps that cost marks
- Listing principles as slogans without linking them to a design or behaviour decision.
- Assuming collaboration removes accountability - the integrator still decides and escalates.
- Assuming a blame-free culture means tolerating poor performance; consequences still apply.
- Assuming SIAM always means an external integrator or a complete cultural reset from zero.
- Treating transparency as reporting to the customer only, rather than provider-to-provider as well.