Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Items

...

Meeting Participants and cadence

...

Values and Culture

...

Examples Of Complexity

301

The number of active flows

20

The number of flows on the contact object

36

The number of validation rules on the Opportunity Object

232

The number of Permission Sets

349

Number of Issues in the Backlog

2

Number of API’s from SITS

Sharing Rules for EE

Profiles and Roles

Overarching Principles

  • Stabilise: The platform to reduce technical debt

  • Simplify and Standardise: The Processes and Technology

  • Scale: Build capability to enable growth and value

Principles of Design Simplicity

  • Adopt over Adapt - Structure business processes around “out of the box” functionality (bend the process to the system not the other way around)

  • Clicks over Code - Exhaust declarative configuration options before attempting programmatic customisation

  • Reuse and Simplify - Think of the system as a whole and understand where repeated functionality can be avoided

  • Optimise data - Establish the right database structure and relationships using standard objects before custom

  • Integrate efficiently - Transform and orchestrate in the integration layer

  • Code well - Design with efficiency, minimisation and reuse in mind; robustly test and deploy. Ensure good practices such as abstraction and avoidance of tight-coupling components.

  • Don’t over-engineer -Don’t ask the platform to perform beyond its capabilities by building complex processes using tools and features not designed for it.

    Overarching Principles

  • Stabilise: The platform to reduce technical debt

  • Simplify and Standardise: The Processes and Technology

  • Scale: Build capability to enable growth and value

Items

  • Meeting Participants and cadence

  • Values and Culture

Examples

  • Example of a record with the same phone number in seven different fields

...