Experiential learning is the process of learning through experience, and is more narrowly defined as "learning through reflection on doing".

Anxtgo implements the experiential learning cycle by Kolb, which loops over the following stages:

1. Concrete Experience

2. Reflective Observation

3. Abstract Conceptualization

4. Active Experimentation

Since acting and experiencing fully take place in real life, these two steps are not integrated by Anxtgo directly, rather reflecting and abstracting are the core part of Anxtgo, due to the fact that these stages are processed by our brains mainly. Here, Anxtgo comes into play and wraps the whole cycle into a digital experience to help us go through it with ease and getting the most out of it.

Learning is the process whereby knowledge is created through the transformation of experience.

While the learning cycle can be kicked off at any stage, it’s probably the most efficient to start on experiencing.

If there is something positive or negative in a given experience, we faced it and therefore see the point directly. At this point, we are no longer talking about some theoretical thing anymore, it’s something we are experiencing and reflecting on for real.

Once we abstracted what we want to learn from the situation, it’s a lot easier for us to remember our abstraction next time we enter a similar situation, because we linked that knowledge to an experience in our life. That’s a natural human-like way to save information in our brains. Because of that, it’s a also lot easier for us to build up persistent knowledge and actively bring our abstractions into real actions in our lifes.

• Write reflections and abstractions in one single flow designed for effective experiential learning. Or write down your reflection and come back later to abstract on the reflection. Make use of every experience, never miss something to learn from.

• Filter your personal list of reflections to quickly see what reflections you already have turned into abstractions and which you still have to get your head around.

• Connect new reflections to existing abstractions to build up your own network of knowledge and get a detailed history view, of when you made which reflections, that led or tries to implement your abstractions.

• Mark your reflections as implementations of your abstraction to generate a rating for each of your abstractions. This helps you see whether you are taking an abstraction into real life with success. Also you are able to sort all of your abstractions based on your scoring, to see what you should focus on and what you are doing great already.

• Define differnet consequences like for example "time" and keep track of them on an reflection basis.

• Get a statistical overview of all your entries to see the bigger picture of your experiences:

  • Amount of already abstracted reflections (reflections linked to an abstraction)

  • Amount of not yet abstracted reflections (reflections with no linked abstraction)

  • Amount of reflections that implement their abstraction (successful)

  • Amount of reflections that do not implement their abstraction (unsuccessful)

  • Amount of not yet rated reflections (reflections where implements or not implements abstraction is not set)