Forty-seven people found a reason to join the same AI conversation.

About twenty attendees were expected for Howard Pearlmutter's custom AI-for-product-development seminar at Telos Alliance. Forty-seven came.

The audience crossed software and hardware development, product and project leadership, executives, and skeptics. For an organization building combined hardware and software products for broadcast infrastructure, the subject had several kinds of relevance.

Howard prepared with the CTO, VP of Engineering, and division leadership. The learning connected foundational understanding and mental models with practical opportunities in AI-assisted development.

The engagement also included prototypes and demonstrations spanning native integration, enterprise middleware, high-performance computing, media, graphics, and simulation.

That gave the encounter a useful shared foundation. Different roles could examine the capability in relation to real technical work.

John Schur recognized requirements discovery, thought partnership, attention to skeptical concerns, practical risk treatment, and implementation. He wrote: “I felt that Telos received multiple times the value of our investment.”

For a gathering designer, the combination is instructive. The subject was shaped around the organization. Several roles had a reason to attend. Skeptical expertise was part of the discussion. Practical artifacts helped connect the explanation with what people could inspect.

Your own occasion may need a different balance of presentation, conversation, and shared work. The purpose could be learning, comparison, exploration, or a practical decision about what happens next.

Explore private rooms, variclusive encounters, shared artifacts, and participation.

Start with what the people involved need to understand together. Give their different reasons to care a coherent place in the encounter.