Emerging media requirements became something people could inspect.

At Telos Alliance, Howard Pearlmutter's work combined a custom AI-for-product-development seminar with practical prototypes and demonstrations.

The organization develops combined hardware and software products for broadcast infrastructure and operations. The work naturally crossed several kinds of expertise.

About twenty attendees were expected for the seminar; forty-seven came, including software and hardware developers, product and project leaders, executives, and skeptics.

Howard had prepared with leadership, including the CTO, VP of Engineering, and division leadership. The conversation connected foundational understanding with possibilities for practical AI-assisted development.

The prototypes gave that conversation another form.

Dynamic Media Facility and Media eXchange Layer work joined enterprise software, high-performance computing, media, graphics, and simulation. It made emerging requirements inspectable at several levels of detail.

Implementation and demonstrations included Apple Silicon CPU/GPU execution, MPSGraph, Java native integration, Netty, Vert.x, Quarkus, and Jakarta EE CDI.

These details matter because the representation was grounded in practical engineering. A model or demonstration can support shared understanding when it remains connected to the mechanisms underneath it.

John Schur recognized requirements discovery, thought partnership, attention to skeptical concerns, practical risk treatment, and technical delivery. He wrote:

“I felt that Telos received multiple times the value of our investment.”

He also described Howard's AI-assisted engineering as visible in low-level implementation, multiple languages, native/platform integration, scalable middleware, and domain-specific media workflows.

For another organization, the relevance may lie in the combination. A technical subject can benefit from a clearer narrative, but it may also need a working model, prototype, or interactive representation. Different participants need different ways to inspect what the work means.

That is why cross-media thinking reaches beyond promotional assets. A live session, practical demonstration, diagram, detailed explanation, and software artifact can each help carry a different part of the understanding.

Their relationship should be deliberate.

Explore media prototyping, team sessions, and technical storytelling. For the longer foundations, read NASA's human question and the factory-design system.

Begin with what people need to inspect together. Choose the form that makes the relationship tangible enough to question and useful enough to carry forward.