Nathanael Yellis

It was a big launch meeting: here’s the new CRM! My pitch was polished; the screenshots and demos were airtight. We gathered in the conference room, but then the whole thing landed with a thud.

When I’d finished the first part of the presentation and was about to switch into the demo, the first question was, “do we have to use this?” Followed up with a senior partner musing, “yeah, why do we even need a CRM?”

We hadn't even launched, and the CRM implementation was about to fail.

On LinkedIn this week I saw a post from LL Bean. And as an exiled Mainer, I had to click the link. Its headline was arresting: “Social distancing does not mean staying inside.” One wouldn’t think this needed to be said. On the other hand, endlessly online celebrities having been telling us to stay inside at home. But, keeping a safe distance from others and aiming not to spread the virus doesn’t require endless Netflix on the couch. We can be safe and be outside. Perhaps, it’s even safer to be outside.

When starting a consulting call these days, the first thing everyone discusses is how COVID-19 and its self-quarantine impacts our lives. But, aside from now working from home, the COVID-19 quarantine doesn’t disrupt my life all that much.

Why? I live a calm lifestyle, constructed from simple, repeating patterns. With work and home, parenting and hobbies, my life alternates work and rest. It’s a life to be lived consistently for decades. The kind from which you don’t need a vacation. It’s a calm life: valuing simplicity over complexity, time over speed, limits over stimuli.

Image: Phil Roeder

Jonah Goldberg has a great podcast. It’s a great reflection of the traditionally conservative but Trump-skeptical. He’s a center-right pundit who’s maintained some sense of true north and a modicum of straight talk amidst the recent turbulence. That’s rare. Now he’s launching, along with two partners, a media company called The Dispatch.

A friend wrote:

I’m neck-deep in planning for a migration to Salesforce, which has exposed some fascinating differences in philosophy. Salesforce is, in principle, infinitely customizable, which leads to this dispute: leaving intact the system’s core data structure (based on B2B), or gutting Salesforce’s data structure to power the simplicity of future usage.

How should you approach structuring a new Salesforce instance? If, for example, your company doesn’t think in terms of leads, opportunities, and accounts, would you use those as the default objects or would you use something custom? On the one hand, a custom CRM architecture feels both simpler and better, but on the other hand you’d end up losing a fair amount of any CRM’s interoperability, extensability, and, likely, outside expertise.

From the beginning, I’ve been impressed with Michael Marinaccio’s work. The latest chapter in his writing promises to be the best yet. People Over Product puts technology in its proper context.

Acton taught me how to be an entrepreneur: in the classroom I learned to make the critical decisions required to lead my own company.