The name vanilla9 sounds harmless at first. Almost like ice cream.
But it’s actually a pretty clear statement about how the system is supposed to work.
Vanilla
“Vanilla” stands for simplicity.
Not boring, but accessible, clear, and uncomplicated.
Getting started shouldn’t feel like attending a training seminar for enterprise software from hell. It should feel more like: “Oh right, I just thought of something. Let me quickly write that down.”
That’s it.
That’s a deliberate design principle. Because most people don’t need yet another system they have to study before it can help them. They need something they can use immediately.
Fast.
Simple.
No 80 mandatory fields.
No administrative drama.
No sudden feeling that you’ve accidentally become the project manager of your own to-do app.
vanilla9 should therefore feel as effortless as writing on a sheet of paper — just with a lot more brainpower behind it.
The 9 Parameters
Those 9 parameters are exactly that brain behind the scenes.
They give the system enough structure to turn a quick note into an actual task you can work with. Because writing down a to-do is nice… but if it just sits in a list like a lonely sock behind the washing machine, it’s not doing much for anyone.
The 9 parameters help vanilla9 understand tasks, categorize them, and manage them in a a useful way.
Not complicated.
Not academic.
Just practical.
Here are the 9 core parameters of the vanilla9 To-Do system:
Importance
How relevant is this task really?
As in: does this genuinely need to be done, or does it just feel important right now?
Urgency
How quickly does this task need attention?
Today?
This week?
Sometime before the sun implodes?
Difficulty
How demanding or complex is the task?
Two clicks… or a boss fight with your inner demons?
Duration
Roughly how long will it take?
A quick “while I’m at it”, or half a day with coffee support?
Priority Status
Does the task have a special priority level?
For example: normal, high, critical, or blocker.
Status
Where does the task currently stand?
Open, in progress, paused, done or the classic
“yes… technically this still exists.”
Deadline
When does it actually need to be finished?
Not “would be nice”, but genuinely relevant.
Motivation
How willing are you right now to tackle this thing?
Because yes, that’s a real factor.
Humans are not toasters.
Location
Where can or must this task be done?
At home, at the office, on the go, at the supermarket, on the laptop, on the phone — because that often determines whether something is realistically doable right now.
Why This Matters
This combination is what makes the vanilla9 philosophy powerful.
A task isn’t just written down, it’s understood in the context of real life.
So instead of just: “This needs to be done.”
The system can also think in terms of:
How important is it?
How urgent?
How difficult?
Is it even doable right now?
And does it fit the reality of this person’s current situation?
A Small Example
Take the task:
“Buy flowers.”
Sounds trivial.
But it’s actually a great example of why structure helps.
Using the 9 parameters, it might look like this:
– Importance: medium to high
– Urgency: high
– Difficulty: easy
– Duration: short
– Priority status: normal
– Status: open
– Deadline: tonight
– Motivation: hopefully high
– Location: out and about / flower shop / supermarket
Suddenly this isn’t just a loose note anymore – it’s a task that can actually be evaluated.
The system can understand what makes sense to do when, and what shouldn’t only become obvious once you’re already standing at the door without flowers and your relationship has entered an unexpected beta-testing phase.
The Core Idea
That’s what vanilla9 is all about:
As simple as possible for the user.
As intelligent as necessary in the system.
Or even more directly: vanilla9 should feel like a small piece of paper. But work like an assistant who actually takes their job seriously.