The Interface Is Shrinking — And That Changes ERP Strategy
For two decades, ERP strategy revolved around the interface. We optimized navigation trees, refined role centers, adjusted page layouts, and built extensions to reduce clicks. Entire implementation methodologies were designed around how users moved through screens.
That approach made sense when clicking was the primary mode of interaction.
It makes less sense when asking becomes the primary mode.
As Copilot capabilities expand within Business Central, Customer Engagement, and the broader Power Platform, users are no longer required to navigate through layered menus to retrieve information or initiate action. They can request summaries, surface records, draft communications, and generate analysis directly through a conversational layer.
When the front door changes, the architecture behind it must evolve as well.
At a Glance
- Navigation is becoming less central to ERP interaction.
- Copilot is emerging as a primary entry point into workflows.
- Page layout is losing strategic dominance.
- Data structure and modeling are gaining influence.
- Partners who continue optimizing clicks instead of structure risk misalignment.
The Pattern I’m Seeing
Users who are comfortable with Copilot increasingly bypass traditional navigation paths. Instead of clicking through multiple pages to locate information, they ask for it. Instead of manually filtering records, they request summaries. Instead of memorizing where data resides, they rely on conversational retrieval. The adoption is slow, but it’s going this way, for sure.
The interface still exists, but it is no longer always the starting point. Crazy, I know.
For years, consultants and developers focused on minimizing clicks, rearranging fields, and refining page experiences. That work delivered measurable efficiency gains in a click-driven world. In an ask-driven world, the hierarchy of value changes.
The system’s ability to interpret structure becomes more important than its ability to present layout.
Navigation Matters Less, Structure Matters More
When interaction happens through conversation, traditional menu hierarchies lose influence. Role centers and curated page flows still have value, but they are no longer the sole gateway to productivity.
If a user can say, “Show me open invoices for this vendor,” the efficiency of the navigation tree becomes secondary. What determines the quality of the response is how clearly and consistently the underlying data is structured.
We have spent years optimizing the visible layer while tolerating inconsistency in the structural layer. In a conversational environment, that imbalance becomes more apparent. If categorization is inconsistent, retrieval becomes inconsistent. If naming conventions drift, interpretation drifts with them.
As the interface becomes thinner, the data model becomes more influential.
Page Design Is Losing Strategic Weight
This is not an argument against thoughtful user experience. Clear layouts and intuitive design will always matter.
However, the strategic weight of page design is shifting.
Historically, page layout determined discoverability. Conversational access reduces dependency on placement. Users no longer need to know exactly where a field sits on a page. They need that field to exist, be structured correctly, and be populated consistently.
Rearranging fields to reduce clicks may produce incremental improvement. Standardizing structure and enforcing meaningful data entry produces compounded improvement.
One optimizes movement. The other optimizes interpretation.
Data Modeling Is Becoming the New UX
In an AI-augmented ERP environment, data modeling increasingly defines user experience.
Entity relationships, category structures, status definitions, and field governance now directly influence how Copilot interprets and responds. The clarity of those relationships matters more than the elegance of page layout.
User experience is no longer limited to what users see. It includes how the system reasons about what it sees.
Partners and architects who understand this shift will prioritize structure as aggressively as they once prioritized visual refinement.
Clean Wrap-Up
The interface is not disappearing, but it is becoming less dominant.
As conversational interaction becomes more embedded in daily workflows, the visible layer of ERP loses some of its strategic weight while the structural layer gains it. Navigation still matters, but interpretation matters more. Page layout still contributes to usability, but data modeling increasingly shapes intelligence.
For years, ERP strategy focused on optimizing how users moved through the system. The next phase requires equal attention to how the system understands the business it represents. The front door is changing. Strategy should change with it.
