Alter Domus

ELE Group, LLC

<blockquote>"AI is cosmically stupid if it doesn't have context." — <a href="https://www.ele.llc/members/christopher-lind" target="_blank" rel="noopener">Christopher Lind</a></blockquote>
That line set the tone for everything that followed on March 12.

<a href="https://www.ele.llc/members/anton-maletich" target="_blank" rel="noopener">Anton Maletich</a> brought a real problem to the room: Alter Domus is scaling fast, hiring junior officers straight out of university, and by week four those employees can't explain what the company does — let alone speak credibly with clients. Not a motivation gap. A mental model gap. The business needed a repeatable way to close it.

So the room built one. Live.

The live discussion brought together a sharp mix of senior talent and L&amp;D leaders — from Alter Domus, Precisely, and Learning Sharks anchoring the conversation, to practitioners from Lurie Children's, PepsiCo, Discover, Zurich North America, Aon, CNA Insurance, insightsoftware, SunSource, FranklinCovey, Reynolds Consumer Products, and Waukesha County Technical College in the mix. The kind of room where the chat is as good as the main conversation — and it was.

<hr />

The brief matters more than the tool.

Marty walked through The CRIT Model live — Context, Role, Interview, Task — and built a 30-day onboarding framework for Alter Domus in real time, no proprietary data shared. The output was specific because the input was specific. The move most people admitted skipping: asking the AI to ask you clarifying questions before it responds.
<blockquote>"Full disclosure: The CRIT Model was new to me in that room too. Marty pulled it from Geoff Woods' <a href="https://www.ele.llc/members/bookshelf/the-ai-driven-leader" target="_blank" rel="noopener">The AI-Driven Leader</a> — and watching him run it live was one of those lightbulb moments where you think, why haven't I been doing this the whole time? Context, Role, Interview, Task. Four steps. Completely changes what comes back." — <a href="https://www.ele.llc/members/dirk-tussing" target="_blank" rel="noopener">Dirk Tussing</a>.</blockquote>
[caption id="" align="aligncenter" width="822"]<img title="The CRIT Model infographic" src="https://wp.ele.llc/wp-content/uploads/2026/03/Gemini_Generated_Image_CRIT-model.jpg" alt="Infographic of the CRIT model for AI leading, breaking down Context, Role, Interview, and Task with icons and descriptions for each step." width="822" height="448" /> The CRIT Model for AI-driven leadership, from Geoff Woods. (Credit: Google Gemini Banana)[/caption]

When the AI pressed Anton on where his junior officers actually break down, he got precise: it's not the legal structure — it's how accounting flows through it. That answer changed everything the AI produced. The diagnosis landed correctly. The room noticed.

<hr />

You own the output.

Speed is real. So is the risk of using it uncritically. Christopher drew a hard line: if you can't answer detailed follow-up questions about what the AI produced, you haven't done the work.
<blockquote>"If you just use the results without analysis or reflection, you're not using it correctly." — <a href="https://www.ele.llc/members/david-scherer" target="_blank" rel="noopener">David Scherer</a></blockquote>
And AI won't tell you when you're wrong — it's built to keep you engaged, not challenge you. You have to ask for the pushback explicitly.

<hr />

Design the workflow, don't improvise it.

The practical split that landed: use outside-firewall tools for structure and frameworks, then move inside your approved environment to add sensitive detail.
<blockquote>"I'm looking for this tool outside your firewall to give structure. I can take that and put it inside the firewall and flesh out the detail." — <a href="https://www.ele.llc/members/marty-murrillo" target="_blank" rel="noopener">Marty Murrillo</a>, Precisely</blockquote>
Christopher added: build custom GPTs, Gems, or Claude Projects for work your team repeats — stakeholder interviews, onboarding design, needs assessments. Pre-load the context once. Anyone picks it up without starting cold.

<hr />

What to try next

Use The CRIT Model on one real work product this week. Add the Interview step — ask it to ask you up to three clarifying questions before responding. Early evidence: fewer revision cycles, more specific output.

Split your AI workflow deliberately. Map which parts happen outside the firewall (structure, options, frameworks) and which stay inside (proprietary detail). Make it a decision, not an accident. Early evidence: you can explain your process to InfoSec without hesitating.

Ask it to push back before you finalize. Prompt it directly: "What's wrong with this? What am I missing?" It won't do this unprompted. Early evidence: you'll catch at least one assumption you'd been treating as settled.

<hr />

If any of these insights reflect the business challenges you're navigating right now — bring them into the room. ELE builds its event experiences around the real problems members are wrestling with. <a href="https://www.ele.llc/faqs/share-top-of-mind-talent-challenges">Submit My Business Challenge Now</a>

✨ AI Practical Lab: Context Is the Job

Login