I’d like to see if someone else could benefit from this evolution.
We are a Startup following the classic OKR approach for every “department” (Marketing, Sales, Development, Strategy, …)
Key Result has a set of
Tasks that have common fields (e.g.
Status, etc… ) plus some departmental specific ones (e.g.
Account Reference, …).
This leads to have a comprehensive table
Tasks holding all the fields with different views to show/hide the most relevant for the context.
It would be extremely useful to define a single table entity
Task with the common set of fields and “extended” tables (e.g.
Development Tasks, etc) that only define the differences needed to be tracked.
Something like: New Table [Extend from …]:
This would allow to have a common aggregation for metrics/statistics on reference tables - in the scenario example,
Key Result would still have a set of “generic”
At the same time, every departmental evolution/addition would not affect the “base” table.
This would permit also to keep some basic features on common low-level tables.
Curious to know Community & Codans opionions!