-
LEARNING MANAGEMENT tracks what skills/knowledge I am learning, and helps me make sure I don't get bogged down with taking on too many new concepts at once.
- LEARNING AREAS are parents of/containers for KNOWLEDGE NODES
- Each KNOWLEDGE NODE reflects a specific area of learning, which take around 3-4.5hrs to complete
- The methodology for Learning Management is based on a great keynote that for the life of me I can't find again. I think it was given by a person named Carol, and they highlighted the importance of moving things from "Don't know" to "Mastery" very quickly. The more that accumulates in our "kind've know" columns, the more cluttered and confusing things get. That's definitely something I've been experiencing!
-
PROJECT MANAGEMENT tracks what projects I am working on, and the tasks needed to execute those projects.
- PROJECTS are parents of/containers for TASKS.
-
Relations: LEARNING MANAGEMENT and PROJECT MANAGEMENT are related to each other, so that I can see what project I should work on if I want to develop a given skill. Similarly, their children (KNOWLEDGE NODES and TASKS) are related.
- I'm not sure if this is going to work well in practice, but it makes sense at a theoretical level.
-
All tasks under the "Anuva" umbrella are stored elsewhere as this is client work.