Smart Event Studio

This is the #1 question teams should ask before they buy licenses for their team.

Not "what could this theoretically do." Not "what are other organizations doing with it." What problem, in your organization, with your team, your workflows, your constraints — does this tool exist to solve?

I saw such a cool example of that this week using AI.

Someone at Salesforce posted about how they have significantly changed how they manage their code by using AI. They detailed out how they had built a variety of different agents with specific tasks, including agents who were explicitly trained on their exact coding processes and QAed everything along the way.

I couldn't help but think that it was such a great example of technology operations in motion. My systems brain also sent a virtual kudos to the team that architected all of that out.

AI, in particular, has so many applications that it's really easy to just buy licenses and say, "here, go use this."

But, that is where good intentions go to die.

A registration platform has a defined set of features. It does what it does. AI doesn't work that way. The same tool that helped me debug a technical problem this morning helped someone else plan a dinner party.

Before you adopt another tool, ask yourself:

What problem is this solving?
Who owns it?
What does good output actually look like here?
How will we know if it's working?

Those aren't just AI questions. They're operational readiness questions. They belong in the Technology Operations conversation — the same one you'd have before deploying any system that touches your event workflow.

If this sounds familiar, know that this is a very solvable problem. I have been doing this work recently with clients and a Workflow Re-Architecture Session is designed for exactly this.

‍