Projects in Griply

yes. I need project too
goal and task is not fitting the working project format

I don’t think this is a good differentiation between goals and projects:

-Goals are (measurable) outcomes

-Projects represent the "execution" layer.

Why?

Projects are measurable outcomes as well. Also, you can’t really execute a project just like you can’t execute a goal. You can only execute tasks that are part of a project or goal.

My recommendation for differentiating goals and projects:

-Goals should be outcomes that are primarily time-based: For example, you can have 10 year, 5 year, 1 year, quarterly, monthly, and weekly goals.

-Projects should simply be groups of tasks that are trying to achieve one objective.

The problem with nesting projects under time-based goals becomes clear when you consider: What happens when a project must be accomplished by a set of tasks and habits that are part of more than one short or long term goal? Also, what if the project is too big for one goal? Do you divide the project up so it can fit in your goal structure or move it to a longer horizon goal?

What’s the ideal length for a project? There is none. It depends on how long it takes to do the work, but even if the project is really long or an unknown length. It is still helpful to be able to create weekly or monthly goals for segments of the project that you know you can complete in those time frames.

I say all that to say that, I think projects should be added to Griply, but I think they should be more like tags than goals. That way, they can be used to group and track tasks across multiple time-based goals (weekly, monthly, etc.)

I need this, would change a lot of things for me

I’ve struggled to implement Griply, because of the ‘hacky’ way that goals & sub-goals need to double as projects (containers which contain actionable tasks)

Goals are great - but they are not actionable. The problem is that sub-goals technically are milestones and are also not actionable (but in the current hierarchy of functions in Griply - sub-goals have to take the place of projects).

Only the execution layer (tasks & projects) can be actioned by a user - with projects being a container/folder of related actionable todos. The problem with tasks is that 1) they don’t appear on the gantt timeline view (only goals & sub-goals are) & 2) sub-tasks nested inside tasks cannot be scheduled.

With projects, one could schedule start & end dates, see them on the gantt view and then schedule the tasks to gradually complete the components of the project.

E.g goal - implement productive routines this month to improve productivity & organisation at school. but the project container can be:

• project 1 (march 1 - march 14 - 2wks): read atomic habits by james clear

  • task 1: read book and highlight (mar 1-7)

  • task 2: extract highlights and make summary of key concepts (mar 8-14)

  • task 3: implement actionable insights (cue-action-reward) into daily routines e.g lay out running gear at room door (mar8-14)

• project 2: populate daily and weekly routines into Griply planner (mar 15-21)

  • task 1: outline routines and their repeating tasks in markdown/outlining app

  • task 2: add into griply and set up with repeating frequency dates

The goal can act as a marker to work towards, but goals are largely direction markers and relatively static - the flexibility comes at the project layer & how to take action towards achieving the goal (the project for reading could substitute reading a book on habits with ‘watching habits 101 course’ on udemy or ‘watch YouTube top 5 videos on implementing habits’) - the inputs are variable, as long as it moves the user towards their goal.

And without projects, single tasks cannot be grouped to some container - problem with a goal or goal target is that its only for strategic planning (very important to set direction and where one is going), but there needs to be a middle organisational layer to group task under projects first, with the option to align up to goals & life areas as supporting guidance to ensure daily & weekly actions help make progress towards goals and long-term vision.

Analogy is using a map - vision is final destination of the journey (country to travel too), life areas are the cities/states/provincies one wants to visit one-by-one, goals are the points-of-interest and checkpoint sights along the way, to, but projects are the legs of the journey (place 1 to place 2, place 2 to place 3 or day 1’s trip itinerary of places, day 2’s itinerary of places etc). Tasks are the turn-by-turn navigations/street directions from the current location right now.

Essentially, projects are an important planning layer - which goals/sub-goals/life areas and single tasks (or checklist sub-tasks) cannot replicate in terms of its role.

Thanks for reading.

Can’t wait for the Projects feature to be up. Drowning in projects.

I am not clear on whether this is needed. While I come from a task manager background, doing area/project division in some way or fashion, goals and subgoals completely satisfy my planning needs, as I don’t see anything a project will do that a subgoal can’t.

That doesn’t include the suggestion to use tags as project wrappers, but that’s what you could do with tags literally right now already.

This would really help to structure everything inside of griply

Just came by to say I’d really love a Projects delineation, too, and for me, the OP’s definitions make sense . Cleaning up the yard — garden store Friday; mowing and weed-pulling Saturday; mulching and mowing Sunday — doesn’t feel like a “goal” or “subgoal” to me. It’s a collection of tasks that begin to add up to a greater goal of spending this year really rejuvenating the home.

This will be another big step toward feeling even more comfortable working inside Griply.

I have certain projects, like my novel writing ones, that I think would fit a project more, especially since it’s hard to guess the deadline for them, much easier would be to link goals to them and leave those with deadlines as smaller building blocks.