What does it mean to be an implementer?

What does it mean to be a consultant?

Does the difference matter?

The decision of whether, how, and how much to customize seems to come up on most projects. Paul and John weigh the tradeoffs.

And then:

Company culture... What is it really? (hint: not ping pong or foosball)

In lessons learned, Paul gets to the bottom of screen flow non-null variables and John streamlines sales campaign ROI.

In an extension of the previous episode, we expand on how to not be part of the problem:

• To MVP or not to MVP?
• How to escalate with vendors without alienating them
• Prioritize enablement over controls
• Don't over-automate

Lightning round - Artificial Intelligence

Paul and John discuss their 5 steps for preparing for an implementation:

• Assemble your team
• Evaluate your team
• Define expectations
• Select an implementation partner
• Don't be part of the problem

"Relativity applies to physics, not ethics." — Albert Einstein

• We're back! (after a few brief excuses)
• Ethics in consulting - a deep dive

Lightning Round: Know your acronyms

• Scheduled calls vs. Finding your flow state
• Revising History: Reporting snapshots edition
• Replacing the ‘New’ button
• How to get better better
• Lightning Round - Salesforce dates

• Eclipse recap
• Reporting Snapshots
• Automation App
• Waterfall, Agile, or Wagile?
• Lightning Round: Billionaire Club

• Parkour and creaks in the floor
• The not-so-ultimate coffee hack
• UAT - Are we doing it right?
• Kicking customers out of the nest
• Lightning Round: Building character(s)