One of the core benefits of Fibery is how flexible and customizable it is. The flipside of that is that things can easily get messy and out of control, which is exactly what happened to us when it comes to the Task database.
The Task as we have customized it in Fibery is by far the most used database. That is because almost everything ties to it: the operational side (worklogs, epics, sprints, runways), system modelling (intents, documents, user interface, etc) and more (feedback highlights, red flags, flow steps, etc)
As such, we ended up with Tasks having relations to ~20 other databases and as a consequences of that, the Task view became a clusterfuck filled with mostly empty lists.
To solve this issue, we made use of the fact that any of the lists we see in Fibery can be customized, including to display elements from more than one database.
And so we made a quick google sheet to decide how to group related entities.
Finally, we put all of that together and we ended up with two lists, “Modelling Entities” and “Related Entities” that group most of the ~20 related databases in just 2 lists. This makes the Task view less noisy and much more easy to navigate, while still keeping the same functionality we had before.
Here is how a Task view looked before:
and this is how it looks now:
and here’s a similar example, with more related entities:
