Conversational Operations: When the Work Updates the System
A conversation during my travels brought a different way of working into focus.
This week, I sat beside a fellow traveler who generously shared how they run their business and incorporate AI.
A successful leader at a Fortune 500 company, they still valued their formal CRM and were using AI selectively. Their argument was straightforward: when people consistently log information, they understand their business. Even if that takes two to four hours a week.
I respect the discipline behind that view. Our conversation brought me back to a question I have been working through for months:
What if keeping the business informed became a natural consequence of doing the work?
At AISymmetric, we have built an early version of an approach we are calling Conversational Operations.
Teams work with AI through conversation inside a shared workspace organized around customers and work, with relevant documents and defined business rules. As they do the work, the system maintains the records and updates the views people need.
Business records become a result of doing the work.
Imagine a seller saying, “The customer is considering a $50,000 project for January. Draft the scope, capture the open questions, and prepare the next steps.”
Within defined permissions, that interaction could prepare the materials for review, update the opportunity, and refresh the team’s dashboard. The seller moves the work forward. Leadership sees the opportunity, its assumptions, and what still needs to happen.
The workspace still needs ownership, reliable records, approval rules, and a history of changes. Those rules can evolve with the business. Conversation becomes the primary way to operate, and dashboards become views of the work happening underneath.
A few months ago, we explored an earlier iteration through Sparks, a customer pricing unit we were developing that may still have a future. That work helped shape this broader approach.
Around the same time, I tried explaining the concept to a customer’s CFO. I failed to make it clear.
They cared deeply about sales activity tracking. I was describing a different way to work, but I had not adequately explained how accountability would carry forward.
Having previously led a sales organization approaching $2 billion, I understand the need for visibility. I also believe activity tracking can become corporate overhead when maintaining the record starts competing with moving the business forward.
A busy activity log can create confidence without showing whether a customer is any closer to a decision.
We still need clear expectations, coaching, and the willingness to address persistent underperformance. Removing administrative friction should help people perform and make it easier to see where support or change is needed.
I believe Conversational Operations points toward a more agile business, with people spending more time advancing the work and less time maintaining its administrative trail.
We are early. The model will evolve. But the direction is one I am willing to build toward.
To my fellow traveler: thank you for the thoughtful conversation. I wish you and your team every success.