Announcing ClarityLift to your team without wrecking trust.

Currently: #engineering, #product, #sales-floor, #customer-success. [Edit this to match your actual list.]

If we add or remove a channel, I will update this FAQ and post the change in general. You can always ask me directly.

It processes messages from the channels above for signals, then discards them. No message text is stored in their database. The tool looks for patterns across teams of 10+ people, never at individual messages attached to individual people.

No. The tool does not have access to direct messages. This is enforced at the Slack / Teams integration layer — the permissions it requested at install do not include DM access.

No. There is no output in the tool that shows individual messages attributed to individual people. The schema does not have that information. I wouldn't be able to answer “what did [employee] say about [topic]” even if I wanted to.

No, for two reasons. First, contractually: the acceptable use policy I signed prohibits using ClarityLift outputs for hiring, firing, performance review, or compensation decisions. Second, architecturally: the outputs are team-level, so there is no individual data to bring into a review in the first place.

That concern is real and I want to engage it directly. The architectural limits (no individual data, 10-person minimum, no DMs) survive any change in leadership — they are structural, not policy. The AUP that prohibits individual-decision use is contractual and would have to be explicitly violated.

If you see us drifting from these commitments, hold me accountable to this announcement.

Yes. Tell me, and I'll disable it. It stops flowing signals within 30 seconds.

Yes. The public architecture page is at claritylift.ai/privacy-architecture. Section 4 lists exactly what the product cannot do. Section 2 walks through the ingest pipeline. It is not marketing material — it is the technical spine of how the tool is built.

Fair. Let me give you the specific answer instead of the reassuring one.

Surveillance implies watching individuals. The architecture of this tool makes watching individuals impossible — not because we turned off a feature, but because the data to watch individuals is not collected. The minimum group size is 10. The schema has no user id on any output row. If I wanted to know what a specific person on your team has been saying, I could not ask the tool. The tool cannot answer that question.

That is the specific claim. Section 4 of the architecture page lists every thing the tool cannot do, with the reason for each.

Honestly: no. I made this decision as a leadership call, and I am telling you about it now. I want to be up front about that because the alternative — telling you we had a whole consultation process — would not be true.

What I am committing to is the opposite side of that. From this point forward, everything about this tool is transparent. You see the channel list. You see the architecture document. You can ask me to remove a channel and I will. If we expand scope — which today means picking a new channel — I will announce it the same way I am announcing this.

The architectural rules are not rules I can turn off. No DMs is baked into the Slack / Teams integration — changing it would require a full re-auth with new scopes, which would be employee-visible. The 10-person minimum is in the database schema. The lack of individual attribution is in the schema. A new leadership team inheriting this system would inherit those limits too.

The contractual rules — the AUP that prohibits individual-decision use — a new leadership team could theoretically violate. But that violation would be a specific, public breach of a specific, public document. It would be exactly the kind of thing a whistleblower or plaintiff's attorney can point at.

None of that is zero risk. But the risk surface is much smaller than deploying something without these limits.

Nothing your manager couldn't catch if they had 40 hours a day to read every channel carefully and remember what they said three months ago. The value is not that it sees something humans cannot — it is that it reads consistently and surfaces patterns across time and across teams that humans miss because humans are busy.

Also: if your manager is doing the reading, the reading is filtered through one person's biases and one person's relationships. The tool is not unbiased, but its biases are different from a human's biases, which is sometimes useful.

Yes. My plan is to share the major signals at our monthly operating review, aggregated and without anything that would identify specific people. If the tool surfaces something that needs a response, my job is to start the conversation with the relevant team, which means you will hear about it.

What I will not share: raw dashboard screenshots or specific channel signals in a large public setting. The signals the tool produces are aggregate but they are still team-specific, and I'd rather discuss them with the team they refer to first.

Post in general. Two to three sentences. “First week of ClarityLift is running. We enabled [list]. So far the major signal has been [one specific thing, aggregate]. I'll share a fuller view at 30 days.”

The point is not the content of the update. The point is that you are communicating on the schedule you committed to. Silence after a big announcement reads as retreat.

Schedule 15 minutes at a team meeting. Walk through:

• What signals have shown up (aggregate, no individual data).
• What you've changed based on them (if anything).
• What you'd change about the setup in hindsight — channel choices, threshold tuning, etc.
• Whether you are keeping it for another 30 days, pausing it, or turning it off. Make a decision out loud.

If the answer is “we found it useful, keeping it,” that is fine. If the answer is “the signals were noisy and not adding much, turning it off,” that is also fine — and communicating that decision openly builds more trust than quietly leaving it on.

DM three or four people at different levels and ask them directly: “Is ClarityLift landing the way I described it? Anything that feels off?” Do not make this public. This is where real feedback comes — the things nobody wants to raise in a group setting.

If the feedback is that it is landing fine, great. If the feedback is that something feels different from the commitment, take the feedback seriously and either fix the issue or turn the tool off.

Five minutes at an all-hands. Short. “Three months in, here's what we learned, here's what changed, here's what didn't.” Close with: “If any of you has concerns about this I haven't heard, my DM is always open.”