#64 DBDS Database Design - Insufficient distinction between level descriptions: change request accepted
The wording in Database Design skill-level descriptions is too similar for levels 3, 4 and 5. It is difficult when assessing against this skill, or when considering the skill for a role-profile, to gauge what level is relevant.
In broad terms, it appears that there too many levels described for Database Design (DBDS). The wording is practically identical for Level 3 and Level 4. For Level 5 much of the wording is similar, with additional clauses that don't appear to reflect great autonomy, influence, etc., but suggest specific types of database. The Level 6 description doesn't really correspond with Level 6 per se and is better aligned to Level 5.
The result of this is that when an individual, with DB experience, is assessing themselves against this skill, it is almost impossible to choose which level is the best fit. Simiilarly, when compiling a role profile that includes DBDS, the skill-level wording does not help a manager or consultant to select one level as being more relevant than another.
I request that the skill descriptions are revised to have levels, 2, 3, 4 and 5, with clear distinction between the levels.
Attached to Database design
What we decided
Accepted. Note that by removing level 6 and clarifying differences between levels this is likely to impact skills assessment processes.
What we changed
Level 2, 3, 4 and 5 skill descriptions are revised to have, with clear distinction between the levels. Level 6 deleted.