How To Build A Hot Enterprise Taxonomy
posted by Anna Mar, October 01, 2011Can you make a enterprise taxonomy sound exciting? How about selling a taxonomy to your organization?
At first, working with taxonomies seems as exciting as watching paint dry. But the fact is that a good taxonomy is valuable and easy to sell. Enterprise taxonomies fit your strategies, capabilities and models into neat little boxes. In other words, they have the power to impose order on complex enterprises.
Enterprise Taxonomies
Enterprise taxonomies are vocabularies used to describe an organization. Any patterns that can be found in your business, operations or technology can potentially be described as taxonomies. Common examples include:- business capabilities
- organizational roles
- product catalogues
- customer types
- order types
- operational capabilities
- technology platforms
Taxonomies are typically hierarchical — meaning they are defined at (progressively more detailed) levels.
The Value of Enterprise Taxonomies
Whether information is textual, visual or verbal — there is always room for subjective interpretation. Taxonomies structure information as building blocks that leave little to the imagination. In other words, they ensure that information is interpreted consistently.There are several valuable uses for taxonomies:
- to drive reporting and metrics
- to clarify communication and documentation
- to improve business processes
How to sell a Enterprise Taxonomy
Taxonomies impose order — they can easily be perceived as dictatorial and rigid.The key to selling a taxonomy to your organization is collaboration. Stakeholders who feel consulted are less likely to resist adoption. Ideally, all stakeholders feel that the taxonomy is their idea.
|
CxO level executives are demanding metrics for EA — can you deliver? |
|
Learn about common root causes of security risks. |
|
This is the way to prove to your stakeholders that your recommendations are not just whims. |
|
Learn about the 10 most important patterns for SOA success. |
Recently on Simplicable
| 9 Reasons You Need a Current State Architectural Blueprintposted by Anna MarA current state enterprise architecture blueprint represents your organization's high level architecture. It's probably the most important documentation that any IT organization can create and maintain. |
| 10 Big Data Definitions: Take Your Pickposted by John SpaceyAs with any emerging field, the definition of big data is always in flex. |
| 9 ITIL Implementation Challengesposted by Anna MarITIL implementation is no cakewalk. ITIL impacts your entire organization — your business, your IT department and your inflight projects. |
| The 9 Principles Of Soa Designposted by Anna MarService-oriented Architecture (SOA) is as simple as can be — it can all be boiled down to these 9 principles. |
