This vision board visualizes the multiple personas/identities/roles you have on the blue sky.
For each persona you are able to set goals.
As a foundations, the earth beneath our feet, we have our strenghts, values and weaknesses.
We also use this space to define activities which we allow ourself when in need of some slacking.
These slacking activities should idealy be short and finite.
Goals should be positive. When we say 'I cannot eat suger' (negative),
we still identify ourself with someone who eats sugar.
If you say
'I am an athlete, therefore I do not eat sugar' (positive),
it's easier to abstain from sugar.
Something can start as a difficult goal and develop into a
just like your first piano class was hard.
Before creating this vision board,
we advice some basic understanding of
Sapolsky's research on dopamine,
Nietzsche, The Gay Science, §290,
Human, All Too Human
Habits and routines
The goals we have should be worked on by activities we incorporate in our routines.
Working on them is most easy when it becomes a habit
(which is a
cue + routine + reward).
When we want stronger abs (reward), we can create a habit of sitting on a fitness ball.
The science on willpower
learns us that it takes more willpower
to go to the gym than actually doing the excersizes there.
Having this knowledge, we set a low-bar on our activities when forming a new habit.
When you aim for doing pushups or reading in the morning,
it is good to allow for just one pushup/sentence (low-bar),
which creates the pattern of getting into the position/grabbing a book.
For this reason it is good to have a resting day (just like major religions have),
getting you familiar with picking up the routine when you have skipped a day.
In the data, we define activities, which we give a priority (MoSCoW)
and specify if it
This section should be
PLEASE WAIT, PAGE IS LOADING . . .
(this export will contain the list of activities part of the routine)
Time allocation in calendar per goal
Time management matrix
provides us with an easy way of visualizing our personal backlog.
urges us to distinct the items into what we
want, should or need to do.
It is not part of the print layout since it should be revised daily.
For work/study/projects one should have a different system,
such as a Product Backlog used in Scrum or Kanban.
For coding projects one could have the backlog items
(as markdown files/open issues)
inside the Git project, containing developer notes
and use a link to it on the Project Planning board.
This allows you to keep everything of the project;
requested features, documentation, diagrams etc.
inside the Git project, except for the (centralized) planning.
Everything seen above is rendered based on the data stored in
this YAML file.
You can use this file as an example to create your own.
To render your data, simply paste it into the textarea below.
For more advanced users, we recommend using git for version control,
which enables you to load your YAML from an URL