The core idea in Nektion is that you can adjust the tool to the way you are working:
1) set-up a model that corresponds to the terminology you use and how you group things together, and
2) create views based on the model that support the way you manage work, make decisions, and follow-up things (see Picture 1).
In other words, rather than figuring out if a predefined set of features in a tool fits your use cases, you can set-up Nektion just right for your needs.
The two most important concepts in Nektion are contexts and views. Contexts are used to logically group the “pieces” of your work model such as product, team, sprint, feature, and user story. The views then use your contexts to display items in a structure that supports managing work and collaboration.
One of the big benefits of Nektion is that once you define your contexts and views, you can create items in views and drag-and-drop them within and even between views. This enables you to create really efficient workflows. For instance, you could have a list view where you prioritize tasks by putting the most important ones at the top, and then you can open a board view where you allocate the tasks to your team members by drag-and-dropping them from the list view.