Great Products Start with Better Questions
Artificial Intelligence has become one of the most defining conversation in enterprise software. Every technology conference, product announcement, and investor presentation seems to promise an AI-powered future, and organizations across nearly every industry are exploring how these capabilities can reshape the way they operate. While the possibilities are remarkable, many organizations are approaching innovation from the wrong direction. Too often, the conversation begins with the technology itself rather than the business problem customers are trying to solve.
Technology alone is rarely a durable differentiator on its own. Throughout my career, I have found that the organizations creating the greatest long-term value are those that remain relentlessly focused on customer outcomes. They do not pursue innovation simply because new technology exists. They pursue innovation because they understand the challenges their customers face every day and recognize opportunities to help them achieve better results.
This perspective has been particularly important in the heavy building materials industry, where our customers manage operationally complex and time sensitive. Ready mix concrete, asphalt, aggregate, and cement producers are responsible for coordinating production, quality, logistics, fleet operations, inventory, customer service, and financial management, often across multiple sites operating simultaneously. Every decision has downstream consequences, and every delay has the potential impact on profitability, customer satisfaction, and project schedules.
For many years, these operators relied on a collection of disconnected systems that evolved independently over time. Production data lived in one application while dispatch information existed somewhere else. Financial systems, quality management, inventory, and customer communications often required employees to manually bridge information between separate platforms. The challenge was never simply about having “better” software. It was about enabling businesses to operate as a connected enterprise rather than a collection of independent functions.
As we began modernizing our product strategy at Command Alkon, it became clear that solving this challenge required more than new technology. It required fundamentally changing how we thought about innovation itself.
Moving Beyond Features to Customer Outcomes
Several years ago, we challenged ourselves to rethink a question that product organizations often take for granted: How do we decide what to build next?
Many software companies rely on a familiar combination of customer requests, competitive analysis, analyst reports, market trends, and internal product ideas. Those inputs are valuable, but they can also create a cycle of incremental improvement requirements. Teams become exceptionally good at delivering requested features without asking whether those new features solve the underlying business problem.
We wanted to move beyond that mindset.
That led us to adopt the Jobs to Be Done framework as the foundation of our product development operating model. Rather than treating customer conversations as collections of feature requests, we began treating them as opportunities to understand the outcomes customers were ultimately trying to achieve. Every roadmap discussion, every product discovery exercise, and every strategic investment began with a different question: What job is the customer looking to accomplish?
At first glance, the distinction may seem subtle, but it fundamentally changes how product organizations think.
Consider a dispatcher who asks for enhancements to scheduling functionality. It is easy to interpret that request as a need for additional screens, new filters, or more configurable workflows. These requests do not reveal the full underlying problem. More often, the dispatcher is trying to maximize fleet utilization while ensuring every customer receives material on time despite changing traffic conditions, production delays, weather disruptions, and fluctuating order priorities. The feature request is simply the dispatcher’s best attempt at expressing the challenge they face every day.
The same principle applies throughout materials business processes. A plant manager requesting new production reporting is not asking for another dashboard because dashboards are inherently valuable. They are trying to identify production bottlenecks, reduce material waste, maintain consistent quality, and make faster operational decisions. Likewise, a finance leader requesting additional billing visibility is ultimately trying to accelerate cash flow, reduce disputes, and improve confidence in the financial health of the business.
When product teams begin by understanding those desired outcomes instead of the requested functionality, they often discover solutions that are significantly more valuable than the customer originally imagined. Sometimes the answer is a new feature. More often it is a workflow improvement, a simplified user experience, an automated recommendation, or a completely different approach to solving the problem.
Over time, Jobs to Be Done evolved beyond a product framework and became a shared language across our organization. Product managers used it to prioritize investments based on customer outcomes rather than feature counts. UX designers focused on simplifying real-world workflows instead of individual application screens. Engineers gained a deeper understanding of the operational context behind every requirement, allowing them to make better implementation decisions throughout development. Product marketing shifted from describing functionality to communicating measurable business value, while customer success teams reinforced those same outcomes throughout implementation and adoption.
What began as a product methodology ultimately became an organizational mindset, aligning every discipline around a common definition of customer value.
Building AI Around Customer Outcomes
That mindset also transformed how we approached artificial intelligence.
As AI capabilities accelerated across the technology industry, many organizations understandably began asking where AI could fit into their products. We deliberately chose to ask a different question: Where can artificial intelligence help our customers accomplish their most important jobs more effectively?
That distinction fundamentally shaped our strategy.
Rather than treating AI as another feature to add to the roadmap, we viewed it as a capability that could help customers make better decisions, automate repetitive work, surface operational insights, and reduce unnecessary complexity. AI became valuable not because it was new, but because it could help customers accomplish outcomes they already cared about more efficiently.
This philosophy also reinforced the importance of platform architecture. Artificial intelligence cannot compensate for fragmented data, disconnected workflows, or inconsistent business processes. Before intelligent recommendations or conversational experiences could deliver meaningful value, we first needed to establish the platform foundations that make enterprise AI reliable. That meant standardizing data, creating common operational definitions, connecting workflows, centralizing master data, and building cloud-native infrastructure capable of supporting intelligence at scale.
Only when those foundations exist can AI consistently provide recommendations that customers trust and act upon.
Creating an Organization That Can Innovate Continuously
While technology often receives the greatest attention, sustainable innovation is ultimately an organizational capability rather than a technical one.
One of the most rewarding aspects of product leadership has been building teams and operating models that enable innovation to happen consistently rather than occasionally. Great products rarely emerge from isolated moments of inspiration. They are typically the result of disciplined discovery, thoughtful collaboration, continuous customer engagement, and a culture that encourages learning across every stage of the product lifecycle.
At Command Alkon, that philosophy extends well beyond product management. Continuous discovery is reinforced through customer advisory boards, product update forums, Net Promoter feedback, health checks, sprint reviews, open office hours, and early adopter programs that keep our teams connected to evolving customer needs long after development begins.
Equally important is creating an environment where product managers, UX designers, engineers, product marketers, and customer success professionals all share responsibility for customer outcomes. When each discipline understands not only what is being built, but why it matters, collaboration becomes stronger and better ideas emerge naturally.
Innovation becomes far more sustainable when every team member understands the customer’s job as clearly as the customer does.
Looking Beyond the Next Technology Trend
Artificial intelligence will undoubtedly continue reshaping enterprise software over the coming decade, just as cloud computing transformed the previous one. New technologies will continue to emerge, customer expectations will continue to evolve, and product organizations will face increasing pressure to innovate more quickly than ever before.
Despite those changes, I believe the principles of successful innovation will remain remarkably consistent.
Organizations that begin with customer outcomes rather than feature requests, invest in resilient platform foundations, create repeatable product operating models, and cultivate cultures of continuous learning will be better positioned to create lasting value than those simply pursuing the latest technology trends.
Technology will always evolve. The job our customers are trying to accomplish is what gives that technology purpose.
Innovation, at its core, has never been about building more software. It has always been about helping people solve meaningful problems, make better decisions, and achieve outcomes that strengthen their businesses. When product organizations remain grounded in that philosophy, every new technology, including artificial intelligence, becomes another opportunity to deliver value rather than simply another feature to release.