When working with your items in KaiNexus, you will often discover that the level of effort on certain Projects or Improvements would be best executed by breaking them down into smaller units of work.
For simple bottom-up Improvement, you may be working on an Improvement that requires you to delegate Tasks to individuals and the Tasks would be tied to the completion of that Improvement. For top-down project management, you may have a long-term/ongoing multi-tiered project structure that you wish to visualize in a hierarchical manner. For strategy deployment, you may want to have all of your project and improvement work roll up to a top-level strategic pillar. Whatever your use case, all of this mapping in KaiNexus is determined by nesting items, which is done using an item’s Parent field.
Let’s take a deeper dive into the functionality and possibilities of this Parent field: