Introduction to nCino Flashcards
Many companies are moving away from on-premises software and to the cloud! This allows them to “x” with speed, lower “x” and limit ongoing “x”.
Many companies are moving away from on-premises software and to the cloud! This allows them to “scale” with speed, lower “initial implementation costs” and limit ongoing “maintenance expenses”.
Why do nCino love partnering with Salesforce?
- “x” certified security
- Proven “x”
- Proven real-time “x”
- Real-time “x”
- Real-time “x”
- Real-time “x”
- 3 “x” and “x”
Why do nCino love partnering with Salesforce?
- “ISO 27001” certified security
- Proven “reliability”
- Proven real-time “scalability”
- Real-time “transparent system status”
- Real-time “upgrades”
- Real-time “sandbox environments”
- 3 “global data centres” and “disaster recovery”
Why nCino?
- Increased “x”
- Decreased “x”
- Decreased “x” and “x”
- Reduction in “x”
- 100% “x”
- A complete “x”
Why nCino?
- Increased “loan volume”
- Decreased “regulatory compliance costs”
- Decreased “loan cycle times” and “operating costs”
- Reduction in “policy exceptions”
- 100% “paperless environment”
- A complete “digital banking experience”
Challenges: Executive Sponsorship & Decision Makers
- Strong “x” with the appropriate “x” and “x” is critical.
- Lack of empowered “x” at the “x” level is a common challenge.
- Must have a definitive and empowered “x” to make timely decisions in daily sessions.
Challenges: Executive Sponsorship & Decision Makers
- Strong “executive sponsorship” with the appropriate “messaging” and “participation” is critical.
- Lack of empowered “decision makers” at the “project” level is a common challenge.
- Must have a definitive and empowered “product owner” to make timely decisions in daily sessions.
Challenges: Release Management
- Possibly the most disruptive aspect to any project is chasing the “x”.
- nCino has “x” major releases per year while Salesforce has “x” - plan for them.
- Define an “x” and document/maintain the “x”.
Challenges: Release Management
- Possibly the most disruptive aspect to any project is chasing the “new functionality/feature(s)”.
- nCino has “two” major releases per year while Salesforce has “three” - plan for them.
- Define an “MVP” and document/maintain the “scope”.
Challenges: Data and Integrations
- “x” is a common challenge - bad data into nCino leads to bad data out.
- Define the number and type of “x” required - use “x”.
- Majority of “x” are custom built - these are typically the long pole in the tent.
Challenges: Data and Integrations
- “Core data accuracy” is a common challenge - bad data into nCino leads to bad data out.
- Define the number and type of “integrations” required - use “productised integrations”.
- Majority of “integrations” are custom built - these are typically the long pole in the tent.
Challenges: Change Management
- Change is hard - ensure proper “x” is in place to drive “x”.
- Transform old “x” and associated “x” - be more efficient than your current “x”
- “x”, “x” etc - critical roles in a transformative program.
Challenges: Change Management
- Change is hard - ensure proper “change management” is in place to drive “adoption”.
- Transform old “processes” and associated “policies” - be more efficient than your current “process”.
- “Executive Sponsors”, “Change Champions” etc - critical roles in a transformative program.
Challenges: BAU Support
- FI should define who will own “x” once nCino is live.
- It is necessary to enable “x” and”x” prior to go-live.
- Encourage each project team to embed BAU resources in “x” to ensure proper ramp up.
Challenges: BAU Support
- FI should define who will own “BAU support” once nCino is live.
- It is necessary to enable “system admins” and “technology support engineers” prior to go-live.
- Encourage each project team to embed BAU resources in “activitIes” to ensure proper ramp up.
If there are existing or multiple Salesforce instances…
- “x”: Do you include an upgrade in the program?
- “x”: Who will access what?
- “x”: What needs to be replaced or rebuilt?
- “x”: Who owns the data? Who owns BAU?
- “x”: Do you have the right type and right number?
- “x”: Who owns this process ands do you have the right tools?
If there are existing or multiple Salesforce instances…
- “Classic versus Lightning”: Do you include an upgrade in the program?
- “nCino users v non-users”: Who will access what?
- “Existing Integrations”: What needs to be replaced or rebuilt?
- “Data”: Who owns the data? Who owns BAU?
- “Sandboxes”: Do you have the right type and right number?
- “Migrations”: Who owns this process ands do you have the right tools?
Configuration Challenge: Complex Data Model
- 100+ “x”
- 5m+ “x”
- Resulting in heavy “x” and “x” complexities.
Configuration Challenge: Complex Data Model
- 100+ “objects”
- 5m+ “lines of source code”
- Resulting in heavy “record-based configuration” and “migration” complexities.
Configuration Challenge: Teams face configuration considerations
- Multiple configuration options on the “x” platform
- Many “x” feature-specific optional configuration components
- Resulting in possible “x” of the solution
Configuration Challenge: Teams face configuration considerations
- Multiple configuration options on the “SFDC” platform
- Many “nCino” feature-specific optional configuration components
- Resulting in possible “over-configuring” of the solution
Configuration Challenge: Custom Written Code
- Difficult to “x” custom written code into the “x”
- Resulting in the inability to “x”
Configuration Challenge: Custom Written Code
- Difficult to “absorb” custom written code into the “solution”
- Resulting in the inability to “absorb nCino releases”
Considerations for Customizing
nCino advocates “x” as the implementation approach. If this approach won’t meet the customers need, then guide them to carefully consider any customizations. These are the questions to consider before deciding the implementation approach:
- Is the requirement on the nCino or Salesforce “x”?
- Can the augmentation be adjusted to support a “x” solution?
- Can the custom solution be “x” once it’s released?
Considerations for Customizing
nCino advocates “Gold Standards” as the implementation approach. If this approach won’t meet the customers need, then guide them to carefully consider any customizations. These are the questions to consider before deciding the implementation approach:
- Is the requirement on the nCino or Salesforce “roadmap”?
- Can the augmentation be adjusted to support a “configurable” solution?
- Can the custom solution be “supported” once it’s released?
Guiding Principles of Augmentation
- Minimise “x” by following nCino gold standards.
- Consider using a “x”.
- Define “x” and style guide.
- Use a “x” to handle business logic.
- Keep within the”x” (no queries or DML in loops).
- Install a “x”.
Guiding Principles of Augmentation
- Minimise “customisations” by following nCino gold standards.
- Consider using a “documentation repository”.
- Define “naming conventions” and style guide.
- Use a “trigger framework” to handle business logic.
- Keep within the “governor limits” (no queries or DML in loops).
- Install a “code review process”.
nCino Releases: Sandbox Release
Contents:
- “x” iteration of nCino product release
- Includes new “x”, “x”, “x” not fully GA
Audience:
- Intended for users/banks interested in “x” and “x”.
- Should only be applied to lower level “x” environments.
Frequency:
- “x”
nCino Releases: Sandbox Release
Contents:
- “In-progress/non-finalised” iteration of nCino product release
- Includes new “features”, “enhancements”, “defect resolutions” not fully GA
Audience:
- Intended for users/banks interested in “upcoming features” and “enhancements”.
- Should only be applied to lower level “dev sandbox” environments.
Frequency:
- “Twice a year - Spring and Fall”
