Inside a Xcelus Decision Brief™ · Watch the full session
Ready for Monday
It’s Sunday night. The work laptop is at the office, the customer meeting is at nine, and the approved AI assistant is right there in the browser — signed in under a personal account. Same name, same logo.
One of five people in the room chose to pause.
[ 7:41 ] · No sign-up required
About this session: An illustrative discussion. The team, the dialogue, and the vote are a fictional composite — the decisions and operational findings represent the types of issues a Decision Brief is designed to uncover. It is one way this discussion went, not a script to follow.
What to watch for
The scenario is about an AI account. The session is about something else, and it shows up in what the manager does — and doesn’t do.
Nobody explains anything before the vote. One participant starts to give the answer during the opening discussion, and the manager parks her — warmly, and without saying why. Once the answer is spoken aloud, the vote stops measuring anything.
The manager never teaches the policy. When the answer does arrive, it comes from two people in the room. The manager’s entire contribution is four questions.
The wrong answers get asked first. If you ask the people who were right to explain themselves first, the room converges, and nobody admits what they actually thought.
The silence after “A, B, or C?” It runs three or four seconds. It feels much longer to the person running the meeting, and filling it is the most common facilitation mistake there is.
The committed vote
Five people, four things noticed, and still a three-way split
1 vote
2 votes
2 votes
What this reveals
Before voting, the room had already named the home computer, the sensitive customer material, and the personal account. They saw everything relevant — and three of five still chose to proceed. The gap was not attention. It was not knowing what “approved” attaches to.
What the session discovered
They knew which tools were approved. Not one of them could verify which account they were in.
Late in the session, the manager asks a practical question: if you were working from home tonight, how would you check? The answers are honest, and they are all the same answer.
“I’d look at the profile icon, I guess.”
“If the browser remembered my personal login, I’d probably miss it.”
“I don’t know our rule on personal devices at all.”
That is the finding, and it is not a training problem. Two things the organization never made checkable: where to verify the approved account, and what the rule is for personal devices. Both have owners and a date by the end of the session.
If you’re about to run one of these
Managers who watch this before their first session run a better session. Four things carry most of the weight:
Don’t teach before the vote. Once you’ve explained it, you can no longer find out what your team thought.
If someone gives the answer early, park it. “Hold that — I want to come back to it.” No explanation needed.
Ask the wrong answers what they were relying on. Ask them before you ask anyone who was right.
Name the gap as the organization’s, not the person’s — then put an owner and a date on it.
You are not expected to be the expert on the topic. In this session the manager isn’t — two people in the room supply the answer, and the manager asks four questions. That is the job.
Two more sessions, two different discoveries
Each session in this series found something different. That is the point of running them more than once.
Responsible AI — the careful-seeming workaround
The wrong answer that drew the most votes was an act of care: sanitize the transcript first.
Conflicts of interest — a misunderstanding about the process
Nobody was avoiding the rule. They held different theories of what it protected against.
Run this one with your own team.
A pilot runs three Decision Brief topics with 10–20 of your managers, and we assemble your first Insights roll-up with you.
Illustrative session. The team, dialogue, and vote are a fictional composite; the decisions and operational findings represent the types of issues a Decision Brief is designed to uncover. No real company, person, tool, or vendor is depicted. Approved-use requirements differ by organization — follow your own policy. Xcelus Decision Brief™ is a trademark of Xcelus LLC. This page is for buyer education and is not legal advice.
Developed by Xcelus under the direction of Todd R. Corbett, MBA, Founder.
© 2005–2026 Xcelus LLC. All rights reserved.
© 2005–2026 Xcelus LLC. All rights reserved. This content is for training and discussion only and is not legal advice; consult qualified counsel about your organization’s specific obligations.