GXD Guardian.

Make the next decision
with the whole context in view.

GOVERNANCE & CENTRE OF EXCELLENCE

GOVERNANCE & CENTRE OF EXCELLENCE

A proposed change needs more than a technically valid answer. GXD Guardian brings platform knowledge, your standards and previous decisions into the review of changes to your Salesforce estate.

Librarian is its knowledge and context core.

SEE HOW CHANGE IS REVIEWED

SEE HOW CHANGE IS REVIEWED

ARRANGE A CONVERSATION

ARRANGE A CONVERSATION

GXD GUARDIANGOVERN · CONTROL · ASSURELIBRARIANKNOWLEDGE · CONTEXTINTELLIGENCEPOLICIESACCESSDATARISKCOMPLIANCEMONITORINGETHICSIMPROVEMENTGXD GUARDIANGOVERN · CONTROL · ASSURELIBRARIANKNOWLEDGE · CONTEXT · INTELLIGENCEPOLICIESACCESSDATARISKCOMPLIANCEMONITORINGETHICSIMPROVEMENT
GXD GUARDIANLIBRARIANKNOWLEDGE · CONTEXTINTELLIGENCE
POLICIES
ACCESS
DATA
RISK
COMPLIANCE
MONITORING
ETHICS
IMPROVEMENT

Capabilities and delivery arrangements are agreed for each engagement.

01 / LIBRARIAN

01 / LIBRARIAN

Understand what is possible.
Remember what was decided.

Understand what is possible.
Remember what was decided.

Understand what is possible.
Remember what was decided.

Salesforce guidance explains the platform. Your organisation’s records explain the choices, responsibilities and constraints around its use. Librarian brings those sources together while preserving their origin and making missing information visible.

PLATFORM KNOWLEDGE

PLATFORM KNOWLEDGE

Salesforce capabilities, documentation and release information provide the platform context.

Salesforce capabilities, documentation and release information provide the platform context.

Authoritative documentation.
Relevant release information.
Platform constraints.
Supported capabilities and design guidance.

Authoritative documentation.
Relevant release information.
Platform constraints.
Supported capabilities and design guidance.

Where freshness matters, identify the source and its relevant version or date.

Where freshness matters, identify the source and its relevant version or date.

ORGANISATIONAL CONTEXT

ORGANISATIONAL CONTEXT

Your standards and earlier decisions show how the platform guidance applies to your organisation.

Architecture principles.
System and data ownership.
Approved patterns.
Requirements and design decisions.
Exceptions.
Delivery and validation records.

Architecture principles.
System and data ownership.
Approved patterns.
Requirements and design decisions.
Exceptions.
Delivery and validation records.

Official Salesforce guidance explains the platform. Approved client material establishes the client’s decisions and standards. Neither silently replaces the other.

Official Salesforce guidance explains the platform. Approved client material establishes the client’s decisions and standards. Neither silently replaces the other.

The answer needs a source. The recommendation needs context. Missing information must remain visible.

The answer needs a source. The recommendation needs context. Missing information must remain visible.

02 / WHAT GXD GUARDIAN BRINGS INTO REVIEW

02 / WHAT GXD GUARDIAN BRINGS INTO REVIEW

Consider the change
and what surrounds it.

Consider the change
and what surrounds it.

Consider the change
and what surrounds it.

GXD Guardian supports governance of your Salesforce estate. Review considers the proposed change alongside architecture, dependencies, risks and existing decisions.

ARCHITECTURE AND STANDARDS

ARCHITECTURE AND STANDARDS

Assess proposed designs against agreed principles, established patterns and the decisions already made.

Assess proposed designs against agreed principles, established patterns and the decisions already made.

Does an approved pattern already exist?
Does the proposal duplicate a capability?
Is the system of record clear?

Does an approved pattern already exist?
Does the proposal duplicate a capability?
Is the system of record clear?

CHANGE AND DEPENDENCIES

CHANGE AND DEPENDENCIES

Identify the questions a change raises across processes, systems and reporting.

Identify the questions a change raises across processes, systems and reporting.

Which known dependencies are affected?
Is a local change compatible with the shared model?
What needs revalidation?

Which known dependencies are affected?
Is a local change compatible with the shared model?
What needs revalidation?

RISK AND EXCEPTIONS

RISK AND EXCEPTIONS

Keep findings, unresolved questions and approved exceptions attached to the change.

Keep findings, unresolved questions and approved exceptions attached to the change.

Which client controls apply?
What information is missing?
Who owns the decision and any follow-up?

Which client controls apply?
What information is missing?
Who owns the decision and any follow-up?

DECISIONS AND TECHNICAL DEBT

DECISIONS AND TECHNICAL DEBT

Retain the rationale behind decisions so later work does not start from scratch.

Retain the rationale behind decisions so later work does not start from scratch.

Why was this approach chosen?
Was an exception accepted temporarily?
What needs to be revisited?

Why was this approach chosen?
Was an exception accepted temporarily?
What needs to be revisited?

Review depends on the knowledge supplied. Missing estate context and unconfirmed dependencies remain open questions.

Review depends on the knowledge supplied. Missing estate context and unconfirmed dependencies remain open questions.

03 / FOLLOW ONE CHANGE THROUGH REVIEW

03 / FOLLOW ONE CHANGE THROUGH REVIEW

A useful review makes
the next decision clearer.

A useful review makes
the next decision clearer.

A useful review makes
the next decision clearer.

WORKED EXAMPLE

An illustration of a governance review, not a live client assessment.

“Can one region add a new stage to the admissions process?”

“Can one region add a new stage to the admissions process?”

“Can one region add a new stage to the admissions process?”

REQUEST → CONTEXT → REVIEW → DECISION

REQUEST → CONTEXT → REVIEW → DECISION

A / REQUEST

A / REQUEST

Fictional proposed change

Fictional proposed change

PROPOSED CHANGE

PROPOSED CHANGE

Add a regional admissions stage.

Add a regional admissions stage.

REASON

REASON

The regional team needs to distinguish enquiries awaiting additional information.

The regional team needs to distinguish enquiries awaiting additional information.

DECISION REQUESTED

DECISION REQUESTED

Whether a local stage can be added without changing the shared reporting model.

Whether a local stage can be added without changing the shared reporting model.

B / CONTEXT

B / CONTEXT

Supplied and missing inputs

Supplied and missing inputs

SUPPLIED EXAMPLE STANDARD

SUPPLIED EXAMPLE STANDARD

“Regional stages must map to an approved global reporting stage.”

“Regional stages must map to an approved global reporting stage.”

MISSING INFORMATION

MISSING INFORMATION

Whether connected systems or automations depend on the existing stages.

Whether connected systems or automations depend on the existing stages.

C / REVIEW

C / REVIEW

Questions before a decision

Questions before a decision

REVIEW QUESTIONS

REVIEW QUESTIONS

Which global reporting stage would the new regional stage map to?
Which known automations or integrations use the stage value?
Who owns the regional variation?
What acceptance checks would be required?

Which global reporting stage would the new regional stage map to?
Which known automations or integrations use the stage value?
Who owns the regional variation?
What acceptance checks would be required?

FINDING

FINDING

The proposal cannot be assessed fully until the reporting mapping and affected dependencies are confirmed.

The proposal cannot be assessed fully until the reporting mapping and affected dependencies are confirmed.

D / DECISION

D / DECISION

No approval recorded

No approval recorded

EXAMPLE STATUS

EXAMPLE STATUS

NEEDS INFORMATION

NEEDS INFORMATION

REQUIRED NEXT ACTION

REQUIRED NEXT ACTION

Confirm the global mapping and relevant dependencies, then return the proposal for review.

Confirm the global mapping and relevant dependencies, then return the proposal for review.

DECISION RECORD · ILLUSTRATIVE

DECISION RECORD · ILLUSTRATIVE

Request

Request

Add a regional admissions stage.

Add a regional admissions stage.

Sources considered

Sources considered

Supplied example regional-to-global reporting standard. Dependency information not supplied.

Supplied example regional-to-global reporting standard. Dependency information not supplied.

Findings

Findings

Reporting mapping and affected dependencies require confirmation.

Reporting mapping and affected dependencies require confirmation.

Open questions

Open questions

Global mapping, relevant dependencies, variation ownership and acceptance checks.

Global mapping, relevant dependencies, variation ownership and acceptance checks.

Decision owner

Decision owner

Unassigned.

Unassigned.

Decision and rationale

Decision and rationale

Needs information. No approval recorded; the available context is insufficient for a complete assessment.

Needs information. No approval recorded; the available context is insufficient for a complete assessment.

Follow-up

Follow-up

Confirm the mapping and dependencies, then return for review. Owner and date not supplied.

Confirm the mapping and dependencies, then return for review. Owner and date not supplied.

04 / GOVERNANCE AFTER THE DECISION

04 / GOVERNANCE AFTER THE DECISION

Keep the reasoning
available for the next change.

Keep the reasoning
available for the next change.

Keep the reasoning
available for the next change.

A decision is more useful when its evidence, rationale and responsibilities stay attached. GXD Guardian distinguishes approved decisions, exceptions and open questions so subsequent work can start from the recorded position.

INTENDED RECORD STRUCTURE

INTENDED RECORD STRUCTURE

RECORDED DECISION

RECORDED DECISION

What was decided, why and which evidence informed it.

What was decided, why and which evidence informed it.

APPROVED EXCEPTION

APPROVED EXCEPTION

What differs from the standard, who authorised it and any review condition.

What differs from the standard, who authorised it and any review condition.

OPEN QUESTION

OPEN QUESTION

What is still unknown, who needs to resolve it and what it prevents.

What is still unknown, who needs to resolve it and what it prevents.

The next review should be able to find the decision, not reconstruct it.

The next review should be able to find the decision, not reconstruct it.

05 / THE RELATIONSHIP WITH GXD PROGRESS

05 / THE RELATIONSHIP WITH GXD PROGRESS

DELIVERY KNOWLEDGE.
ONGOING CONTEXT.

DELIVERY KNOWLEDGE.
ONGOING CONTEXT.

DELIVERY KNOWLEDGE.
ONGOING CONTEXT.

GXD Progress creates requirements, designs and validation records through delivery. Those records become part of the context available to Librarian and GXD Guardian.

INTENDED RELATIONSHIP

INTENDED RELATIONSHIP

GXD Progress.

Delivery artefacts

Delivery artefacts

→

→

→

GXD Guardian.

Review and governance

Review and governance

LIBRARIAN

LIBRARIAN

Knowledge and context

Knowledge and context

We start with the systems you have and the information available about them. Delivery records, existing documentation and approved standards all contribute to that context.

EXPLORE GXD PROGRESS

↗

EXPLORE GXD PROGRESS

↗

GXD Assess can establish an evidence-backed view of Salesforce risks, gaps and priorities to inform ongoing governance. You do not need a GXD Assess engagement to use GXD Guardian.

EXPLORE GXD ASSESS

↗

Need continuing Salesforce guidance? GXD Advance supports businesses; GXD Impact is shaped around a charity’s mission, budget and capacity. Implementation requires a separate agreement on outcomes, work and price.

GXD ADVANCE

↗

GXD IMPACT

↗

06 / LET’S TALK

06 / LET’S TALK

Where is missing context making decisions harder?

Where is missing context making decisions harder?

Where is missing context making decisions harder?

ARRANGE A CONVERSATION

ARRANGE A CONVERSATION

CLARITY. OWNERSHIP. ACCOUNTABILITY.