I’m Called a Business Architect. But Sales, Finance, Operations, and HR Don’t Use My Work.
- Sunil Dutt Jha
- May 2
- 5 min read
The Title Suggests Business Adoption
I’m called a Business Architect.
That should mean the business uses my work.
Sales should use it. Finance should use it. Operations should use it. HR should use it. Customer Experience should use it. Product should use it. Legal should use it. Procurement should use it. Risk should use it. Support should use it.
If my work truly defines how the business operates, then departments should depend on it when they make decisions.
But in many organizations, they do not.
They attend the workshops. They review the diagrams. They approve the slides. Then they go back to their own processes, spreadsheets, meetings, systems, and local interpretations.
The Business Architecture exists. But the business does not use it. That is the distortion.
The Adoption Gap
The problem is not that the diagrams are poor. The problem is that they are not used as the operating definition of the business.
Sales still manages commitments through pipeline meetings and CRM fields. Finance still manages cost and margin through its own controls.
Operations still handles execution through local procedures.
HR still plans capability through workforce reports. Customer Experience still manages promises through service policies and escalation logic. Support still handles complaints through its own case rules.
Want to read more?
Subscribe to architecturerating.com to keep reading this exclusive post.
