TxM 021 Section 2.4 What is an engineered taxonomy? Created by James on 6/26/2013 7:28:34 PM
We have defined taxonomies and now we have defined strategic taxonomies, so what is an engineered taxonomy?
Well, what is engineering?
I set out in 1989 to "bring the disciplines of engineering to the IT industry" and that remains my essential goal.
I have consistently explained this goal as "when you go to an engineer to design a bridge you get the bridge you asked for and IT STANDS UP".
I have amplified this over time with the realization that:
Engineers do NOT design bridges to stand up
è They design bridges NOT to fall down
So, an engineered taxonomy is a taxonomy designed NOT TO FAIL!
I have done a huge amount of work around this goal and, in the process, come to understand that strategic engineered precision taxonomies (SEPT) are an essential and integral part of ERP, datawarehouse (DW) and business intelligence (BI) configuration and operation.
In fact, I have come to conclude that if you do not have SEPT in your implementation you will NOT achieve the potential of your investment.
It is that simple!
So then, WHAT is an engineered taxonomy?
1. Rigorous
By rigorous I mean "no short cuts" – analyse every table and maintenance screen of every module of every system that makes up the entire information environment and be thorough and dogmatically scrupulous about analysing every single information item and then coding it.
2. Systematic
Start at the beginning and proceed till you get to the end, you may need to iterate two or three times to build the complete picture. Structured system walkthrough's are the order of the day.
Make sure you visit every component.
Build every taxonomy systematically, hierarchically, in a structured way – hierarchy is by its nature systematic.
Do not use personnel or consultants who do not have a proven track record of working systematically.
3. Detailed
Engineers design bridges down to "the last nut and bolt", engineered taxonomies are the same.
There must be a logical code bin for every piece of information at the most detailed level. Throwing large numbers of diverse transactions into one information bin is absolutely out.
The metaphor of screws in a hardware store à arrange all information in precise, small bins
NOT large buckets
Which is the norm in nearly all ERP implementations I have ever seen!
4. Comprehensive
Cater for ALL reasonably foreseeable eventualities.
How do you do that? you may ask.
Well, start by using ALL the existing data as a "brainstorm list"—make sure that everything that has ever been encountered before is accommodated in your new taxonomies.
NOTE – I did NOT say copy those lists, I said use them as a source of ideas.
Copying old lists is the single biggest reason so many new ERP implementations are a mess and combining lists from several other implementations is a guaranteed way to fail.
Then get ALL the different knowledge and experience sets that represent the information space in a room in a workshop or series of workshops and challenge them to think about EVERYTHING that might possibly occur in that particular information set.
Then add structure to that list, NOT necessarily with all the parties present, typically a skilled facilitator will work alone or with one senior business representative to build comprehensive hierarchies that cater for all the information gathered during the brainstorm session.
Committees and teams are NOT good at building hierarchies, do not even attempt it!
Once you have a solid hierarchy test it with a few of the people who were in the brainstorm session and once you have refined the hierarchy in response to their input take the hierarchy to the whole team for review.
5. Precise
I have already touched on precision and it is discussed in more detail in a following section.
Precision is central to what is being described here.
We live in a precise world.
Our houses are built precisely, our cars are manufactured precisely, wherever we go we find precision, except in the information lists that drive our ERP's, data warehouses and business intelligence environments!
Those software systems are PRECISION MACHINES and precision machines only produce valuable outputs when they are used precisely and fed precise inputs.
It is a massive delusion of the business information space that systems fed with sloppy, illogical and badly structured data can produce precision decision support and business operation outcomes.
It is an even bigger delusion that personnel who have not be trained in depth in precision and discipline can produce precise configurations.
If you want a high value outcome then it is in your best interests to utilize the most disciplined staff who understand precision as an integral part of their training and day to day practice.
6. Multi-disciplinary
Engineers work in multi-disciplinary teams.
It is vital when developing engineered taxonomies to mobilize multi-disciplinary teams.
It is no good expecting just Finance or just Operations or just Human Resources or just … to produce a comprehensive engineered taxonomy, all the disciplines in the business who have knowledge and experience that has a bearing on the taxonomy MUST be engaged with during the development of the taxonomy.
AND leadership of this process, or at least custody of the leadership of this process must rest with an executive reporting directly to the CEO and the CEO MUST recognize that he or she is the custodian of the integrated view of the business.
Facilitating and consulting with all disciplines takes time, costs money and requires skilled high level facilitation from a facilitator who understands the multi-facetted nature of business and is able to engage effectively and intelligently with ALL role players and ALL stake-holders.
Complex engineered systems are designed and built by teams managed by mature, highly experienced, highly skilled engineers who know when to call in other specialists.
Engineered taxonomies should be designed and built the same way.
7. Sustainable
Engineered taxonomies are sustainable.
They are sustainable because every effort has been made to anticipate ALL future growth and information need scenarios.
They are sustainable because high level executive strategic input has engaged with the taxonomy to ensure that it fully takes account of all foreseeable growth.
They are sustainable because hierarchies and code schemes are spaced out and gap coded to accommodate reasonable growth.
They are sustainable because they are designed from the "ground up" to be sustainable.
8. Reliable and dependable
Engineered taxonomies are reliable and dependable because all the preceding HUMAN ACTIONS result in reliable and dependable outcomes.
An engineered "anything" is the result of meticulously directed, highly trained human creative talent mobilized in systematic disciplined thinking and doing that produces things that are reliable and dependable BECAUSE they were designed by professionals to BE reliable and dependable.
The design, configuration, deployment and operation of any major computerized system, be it an ERP, a data warehouse or a business intelligence solution is FUNDAMENTALLY an engineering endeavour and should be managed accordingly.
Strategic Engineered Precision Taxonomies are a fundamental component of an engineered computerized information system that is designed NOT to FAIL.
[MAKERATING]
The comment feature is locked by administrator.
Return