Reduce barrier to entry: Disconnect matrices from elements
As part of user engagement sessions in December 2018, the topic of "reducing the barrier to entry" were removed.
One of the stories raised on the back of this was
As a MooD BA user, I do not want to have to think about which element a matrix belongs to when creating, so that my congnitive load in using the product is reduced.
Matrices are the only library item to need "ownership" by an element, and this inconsistency does not make sense to users.
-
As added information:
I actually prefer the way Matrices work to the way Queries work, mostly because I am able to build hierarchies around matrices but not around queries. This leads to very flat structures for queries where it is hard to find the right thing because there's so much in each category (or so many categories).
I support this in theory, but only if I can retain the ability to make a hierarchy with more than one level of depth. I would rather retain things "as they are" than lose the ability to make a break down hierarchy which comes from the current (kind of funky) design.
Please sign in to leave a comment.
Comments
1 comment