Monday morning. Back at work. The problem statement from Saturday is sitting in my Notes app between a grocery list and Zoe’s SAT tutor schedule. “Your enterprise accounts are at risk and your dashboard doesn’t show it yet.” Fourteen words. I’ve been looking at them on and off all weekend the way you look at a parking spot you’re not sure is legal.
Today I watched it happen.
Quarterly business review for one of our top ten accounts. Twelve people on the Zoom. My manager leading. Slides about usage metrics, adoption rates, NPS trends. Everything green. The customer success team had that particular energy people get when they’re delivering good news they haven’t examined too carefully.
I noticed three things nobody mentioned.
The VP of Operations, who had been our primary champion for two years, was on the call but hadn’t spoken. Not once. Not even a “great, thanks.” She was there, camera on, muted for forty-two minutes straight. That’s not engagement. That’s attendance.
Second, the renewal is in eleven months. But the new procurement policy they mentioned in passing, the one about consolidating vendor agreements under a single enterprise license, means the decision timeline isn’t eleven months. It’s probably six. Nobody flagged it.
Third, there was a person on the call I didn’t recognize. New title. VP of Enterprise Systems. That title didn’t exist three months ago. When a company creates a new role that sits between you and your champion, that’s not a reorganization. That’s a signal.
I wrote all three observations in a notebook. Not the shared meeting notes. My notebook. The one I keep in my desk drawer that nobody has ever asked about.
And then I realized what I’d done. I’d just written case study number four.
Not on purpose. I was sitting in a meeting doing the thing I’ve done for twenty-four years, the thing I’ve been trying to name for three weeks, and I documented it in real time without meaning to. The VP who went quiet. The timeline that’s shorter than everyone thinks. The new decision-maker nobody’s mapped.
Same pattern. Fourth time.
The meeting ended. My manager said “great account, team” and moved to the next agenda item. Nobody asked about the VP’s silence. Nobody asked about the new role. Nobody mentioned that eleven months might actually be five.
I could have said something. I’ve said something hundreds of times before. That’s literally my job. And I did, eventually. I sent a Slack message after the meeting. “Quick note, might want to check in on the VP separately. She seemed disengaged today. Also, the new Enterprise Systems role might change our renewal path.”
Thumbs up emoji. That was the response.
I stared at that thumbs up for longer than I should have. It’s a perfectly normal response to a Slack message from a colleague. But I thought about what I would charge for that same observation as a consultant. What that two-sentence analysis would be worth if I were outside this company looking in, if it came with a letterhead and an invoice instead of a Slack message and an emoji.
I’m not bitter about it. That’s not what this is. Or maybe it is, a little. I’m still sorting that out.
What I know is this. The problem statement works. “Your enterprise accounts are at risk and your dashboard doesn’t show it yet.” That account is at risk. That dashboard doesn’t show it. I saw it in forty-two minutes of someone not talking.
And I’m giving it away. Every day, I walk into meetings and notice what nobody else notices and flag it in a message that gets a thumbs up, and then I go to the next meeting and do it again. This is the product. I’m performing a free demo of the service I’m trying to build, forty hours a week, for a “meets expectations” and a bonus I hit about two-thirds of the time.
I caught myself thinking “this is insane” and then pulled back. It’s not insane. It’s just employment. This is what a job is. You trade your skills for a salary and the company owns the output. That’s the deal I agreed to. The deal hasn’t changed. I have.
The fourth case study is in my notebook. I can’t use it, not specifically. But I know it’s there. Same pattern. Same proof. The difference is that this time I watched myself do it while knowing what I was watching.
I drove home with the problem statement still in my Notes app. Still fourteen words. Still between the grocery list and the SAT tutor.
I thought about saying them out loud, just to hear how they sounded in my own voice. I didn’t. Maybe because saying something out loud in your car, alone, on a Monday, means you believe it.
And I’m not there yet. Close, though. I think.