Dreamforce is next week. I have been building out my calendar for it. Meetings with admins, a few systems owners, some partners, a couple of sessions I want to sit in on. Everyone going has a version of this list. I looked at mine and noticed something. I am going to ask every one of these people the same thing, and I do not know what they are going to say.
That is not usually how I show up to a conference. I show up to explain. It is what I do for a living, to investors and to customers. I have a point of view and I bring it. This time the thing I am bringing is a question I can’t answer myself.
Here it is.
Take your last bad week. The one where cases jumped, or a Flow that had run fine for two years stopped doing what it did, or an integration started dropping records and nobody could say which side was at fault. That week ended. The cases closed. The incident closed. Someone patched the change or rolled it back. Every one of those things has a date on it. You could pull them up right now.
What I don’t know is the other date. The day someone in your building could say why, and back it up.
I don’t know how many teams have that date at all.
I have a guess. I have been in enough of these conversations to have one. My guess is “the same day” is rare, “later” is what most people say, and “we’re not sure” is the real answer more often than anyone admits in a meeting.
But a guess is a guess. I have been wrong about how orgs work before, usually because I was looking at it from the outside. One honest answer from someone who lived the week is worth more than my guess. I would rather find out on the floor that I had it wrong.
So I am not going to Moscone to prove anything. I am going to count.
In sessions I will be listening for the point where someone describes the fix and skips the reason. That skip is the part I am interested in.
In hallways I will ask the question and then stop talking. The first answer is usually the polished one. The second is the real one.
If someone says “the same day,” I want to know how they did it. If someone says “we’re not sure,” I am not going to treat it like a confession. It is the normal state of a well-run org. Explaining was never something anyone had to report on. Everything the org was asked to track, it tracked. This was not on the list.
A pitch ends when the session ends. Not knowing something lasts the whole week. I think that is a better reason to be there.
If you own the systems at a Salesforce shop and you have an honest answer, I want it. Especially if it breaks my guess.
Teams who can name the day it closed and can’t name the day it was explained are exactly who we’re thinking about.
If that’s your team, and you’d rather not wait for the conference, we run a complimentary Investigation Cost Audit. Forty-five minutes. A structured look across five dimensions of what happens between a case landing and someone saying what caused it. You leave with a scorecard. Numbers on what last quarter asked of your team: in time, in recurrence, and in the reasons that arrived after the case closed.