What Happened When I Stepped Down From the Tableau Visionary Program

On stepping down, on Salesforce, and on what the word "DataFam" actually means.

In October 2025, I publicly stepped down from my Tableau Visionary, Ambassador, and User Group Leader roles. Three years inside the program, ended in a single LinkedIn post.

I am writing about it now, seven months later, because what happened in the days and weeks after I posted, and what has happened since, has clarified something I think anyone who works inside the Tableau community should hear plainly.

This is not a complaint about any type of snubbing. It is also not a takedown of any individual. The community managers, the product teams, the engineers I have worked with over the years are mostly still in the same jobs and most of them are people I respect.

This is about a word. The word is "DataFam." It is the term Tableau uses to describe the analyst, builder, and consultant community that has grown up around the product over the years. It appears on tee shirts. It appears in keynote remarks. It appears in the Slack channels and the user group invitations and the program literature. Last week, at the TC26 opening keynote in San Diego, the three main presenters used it at least thirteen times across 68 minutes of stage time. It was the rhetorical center of the entire production.

What I want to write about is what that word means in practice when a member of that community tries to engage the company on something hard.

Why I Stepped Down

In early October 2025, the New York Times reported that Salesforce had pitched the Trump administration on a contract to help ICE recruit ten thousand new agents. The pitch proposed Salesforce AI software to "implement an aggressive, high-yield marketing strategy" for ICE recruitment. In the same window, Marc Benioff publicly called for President Trump to send the National Guard into San Francisco. He later walked the comments back after employee and community pushback, but the position had been stated, and reporters had documented who was on the other end of his text messages while he was forming it.

I sat with the reporting for a day. There were people I respected on the inside. There were product teams I had worked with whose work I admired. There were friends and former colleagues whose livelihoods were tied to the platform. But the underlying facts of what Salesforce was doing, and the public posture of its CEO, were not compatible with how I want to spend the recognition that the Tableau community had given me. The community had built me up. It was not the company that had built me up. The titles tied my name to the company.

On October 17, 2025, I posted publicly that I was stepping down. The post said, in part:

"I want to share however, that these actions in no way reflect my personal values. Throughout my career I have built a trustworthy name for myself and my work, partly through allowing the community to walk along with me through my journey and love of learning Tableau. Eventually I was fortunate enough to hold the role of Tableau Visionary and Ambassador, recognized by members of the community. I will be forever grateful for the members of the community that made this happen and allowed me to have opportunities I never thought possible. While my expertise on the software remains and I understand the very real need for clients and companies who have invested in the licensing to continue their use of this product, I no longer wish to hold these titles alongside my name. At Cogs & Roses, we strive to foster a culture of respect, inclusion, and human decency."

It was not a quiet exit. It named the company. It named the reason. And it ran during Dreamforce week, when Salesforce executives were in the news cycle and Tableau leadership was paying attention to what the data community was saying.

What I Heard Back

In the Tableau Slack channel, a member of the community team posted a single message asking me to confirm I was leaving the program.

That was it.

No phone call. No email. No outreach from the team that had recognized me three years earlier. No question about why a long-tenured Visionary, Ambassador, and User Group Leader was walking out the door publicly during the company's biggest week. No acknowledgment that the underlying issue I had raised was something Salesforce was hearing from many people inside and outside the company. The company had two options. One was to engage. The other was to process me as an exit ticket. They chose option two.

I am told by people with personal connections to Marc Benioff that he was directly forwarded what I had written, and that other community members were independently raising the same concerns to him through their own channels. I have no way to verify what he saw or what was relayed. What I can verify is what came back to me, which is nothing. No response. No acknowledgment. No engagement at any level.

What Came Next

In February 2026, at the internal Salesforce Company Kickoff event in Las Vegas, Benioff asked the international employees in the audience to stand to be recognized for traveling to attend, and then joked that ICE agents were in the building monitoring them. The room booed. Over 1,400 Salesforce employees signed an open letter demanding the company end its business with ICE. The internal recording was reportedly edited to remove the comments before it was distributed.

On February 11, the day the comments became public, I posted again. I noted that my words from the first resignation had been passed directly to Benioff, that the response from Salesforce leadership had been silence, and that I would not be at TC or any Salesforce-affiliated event for the foreseeable future. The line from that post that has stayed with me is the simplest one: "Marc made his position clear. Human treatment isn't a priority to Salesforce leadership. Profit is."

In that same post, I made an observation that I want to surface here too, because it is the cleanest way to see what is going on. A few years back, when Salesforce introduced an AI mascot named "Astro" at Tableau Conference, the community reaction was loud and immediate. There were posts. There were petitions. There were memes. The introduction of a corporate mascot into a community-led conference was treated as an identity-level concern worth public organizing.

In October 2025, when news broke that Salesforce was pitching ICE on a contract to recruit ten thousand agents, the community response was, to put it generously, muted. Some individuals stepped up. A few of us posted. There was no equivalent firestorm. The community that had organized passionately against a marketing mascot was largely silent on a federal recruitment pipeline.

I am not writing this to shame anyone. People have jobs. People have employers who run on Salesforce. People have visa situations and mortgage payments and reasons to be careful about where they put their name in public. I understand all of that, and I sat with it myself before posting. The point is not the silence. The point is that the silence was structurally encouraged by a company that uses community language for marketing and offers no infrastructure for the community to actually express disagreement when it matters.

What "DataFam" Actually Means

Last week, at the TC26 opening keynote, the word "DataFam" was used at least thirteen times across 68 minutes by all three of the main presenters. The CPO opened with it. The new GM, built his introduction around it. The CMO invoked it directly to anchor the new "DataFam AI and analytics showcase." It is the marketing center of the entire production.

I want to be specific about what is happening when that word is used.

It is being used as a brand asset. It functions, on the keynote stage, the same way a logo functions. It has emotional resonance because it is anchored in real relationships people have built with each other over years, but the company invoking it is not a participant in those relationships. It is a beneficiary of them. The relationships were built by individuals who taught each other Tableau, supported each other through career changes, met at conferences and stayed in touch for a decade. The company has been adjacent to that work, and at times has supported it, but the word "DataFam" describes something the community made, not something the company made.

What the company has built is a partner program with tiered titles, a Slack workspace, an annual conference, and a marketing department that knows the word performs well on stage. Those are not nothing. They are also not community. They are the infrastructure for a marketing relationship.

The test of the difference is what happens when a member of that community tries to engage the company on something the company would prefer not to discuss. In a real community, that engagement gets a response. The response might be disagreement. The response might be a hard conversation. The response might be a clarification of where the company stands and an honest statement of why. What it would not be, in a community, is silence followed by access deactivation.

A company that uses community language while treating community members as exit tickets is not in community. It is performing one. The performance is well-rehearsed and the stage lighting is excellent. But the gap between what is said about the DataFam and what is done by the company that says it is not subtle, and it is not closing.

What I Would Have Wanted to Hear

I have thought about this a lot. I do not think I needed an apology, and I did not need anyone to talk me out of stepping down. I had my reasons and the reasons have not weakened.

What I would have wanted was a single sentence acknowledging that a long-tenured community member was walking out the door publicly, and that the company had heard the reason. Not even an engagement on the substance. Just an acknowledgment that I had been seen, by name, by the people who had given me the recognition I was now returning.

I did not get that. The Slack message was a process step. It was the kind of message you get when you cancel a streaming subscription. It was not a message from anyone who had ever been part of a community I was part of.

I think that is the moment that has stayed with me the most. Not the silence from the executive level, which is its own thing, but the procedural quality of the only response that came back. There was a moment to be human in. The company chose to be operational instead.

Why I Am Writing This Now

TC26 happened last week. I watched parts of the keynote on the live stream. I read coverage of the announcements. I have written separately about the technical reality of what was actually announced, and that is its own piece of work.

The reason I am writing this piece, separately, is that the keynote made something visible that has been visible to me for seven months but might not have been visible to people who do not work as closely with the company. The marketing has not changed. The word is still being used, on the biggest stage the company has, by the most senior leaders in the building. The community has not received any acknowledgment of the political and ethical issues that prompted at least some of us to step away.

It is worth being precise about what the company has and has not said in public. On the National Guard comments, Benioff did apologize on X, but the apology was carefully scoped to "the concern it has caused" rather than to the underlying position itself. On the ICE contract pitch, Salesforce issued a defensive statement noting that the company had also worked with the Biden and Obama administrations and that Microsoft, IBM, and Palantir hold ICE contracts as well. That is normalization, not engagement. On the Vegas comments, where Benioff joked to international employees that ICE agents were in the building monitoring them, there has been no public apology or statement from him or the company. As of April 2026, San Francisco Today was reporting that employees were still demanding public condemnation that had not arrived. On the open letter from more than fourteen hundred employees, CNBC reported that Salesforce declined to comment, and no subsequent public engagement with the letter's substance has surfaced.

The pattern is more telling than blanket silence would be. The company is willing to issue carefully worded statements when the topic is reputational damage to itself. It does not issue statements when the topic is the substance of what employees and community members are raising. That is a deliberate posture, and it is the posture that should inform how anyone reads the word "DataFam" the next time it appears in a keynote.

The keynote used the word "DataFam" thirteen times. The company has not used it once in any meaningful direction in seven months.

If you are part of the community Tableau calls the DataFam, and you have felt something off about the marketing language for a while, this is the gap. The word is doing rhetorical work for a company that does not have, and has not built, the infrastructure to be in community with the people the word is supposed to describe. That does not make the relationships among community members less real. The friendships are real. The mentorships are real. The careers built on top of the product are real. None of that came from the company.

What did come from the company is a name for it. The name is being used in the marketing because it works. It is not being used as the basis for a relationship, because there is not one.

To Be Clear

I have tried to write this without anger. I do not think anger is the right register, and I do not think it is honest to the situation. I am not angry. I am clear.

Tableau changed how I work. The product is real and the people I met through it are real and I would not undo any of it. What has happened in the last two years to the company that owns the product is a separate question, and the answer to that question is now visible in the choices being made about what to market, what to ignore, and what to invoke without earning.

If you are a community member trying to figure out where you stand, you do not have to make the same choice I made. You have your own situation and your own reasons. What I would offer is this. Pay attention to the gap between the language the company uses about the community and the actions the company takes when community members try to engage on something the company would prefer not to engage on. The gap is the answer.

The DataFam is real. The relationships are real. The company that markets the word is not in those relationships. It is selling them back to you.