Thanks for the input, noted!

One more item that may help clarity.

Choice vs. Decision

One is an individual selection of options with similar outcomes. The other is milestone that shifts direction.

What do I want for breakfast?

Do we add a feature that will complicate the user experience and shift the product forever?

The key thing in the request is for me to identify a Note that can be located by a filter, can be done by tagging. In paper, I would keep a collection of decisions to trackback progress and key details.

To me, A decision is a note that precedes action(s) with several attributes that are unique from other bullet types. Decisions are important because they trigger action and spawn

Donald Miller has a great formula for big decisions called Missions. I like to think of them as Outcomes for Programs.

'W' will accomplish 'X' by 'Y' because of 'Z'

W = Who

X = Goal

Y = DateTime

Z = Why

I also see big decisions as some sort of vote with special documentation of who agreed as a stakeholder register, disagreed or abstained. I will include the objections made to the decision to manage risk and comeback to evaluate and make better decisions.

So, simply a Decision can be just a Note with a Tag. However adding some of the attributes as fields, enable many features that are not practical in paper.

Having a special icon also beams a personal reward for recognizing you made a decision and triggering a shift in direction.

Allied Shel, would it be enough to have custom bullet types, like Concerned Rebe mentioned (which would just be aliases of a task/note/event), or do you imagine that there's extra functionality specific to decision making?

Frankly, ideally we'd be able to just create custom bullet types. I'm sure we all have our own use cases.