- in the [[{4.4} what is the getting things done methodology|gtd method]], a `project` is anything requiring more than one [[{4.4b} next actions in gtd|next action]]. - for example: - return a package → initiate return, print shipping label, seal box, take to post office. - onboard client → send welcome email, customize intake form, send intake form, wait to receive intake form, add to time tracking software, schedule recurring invoice… - like next actions, it can feel tedious to define such granular projects. unlike next actions, you *should* be documenting them all anyway (within reason – use ur brain – you don’t have to put “make a sandwich” on your projects list unless you really need the reminder). - take “replace hallway lightbulb” as an example. it sounds like a simple task that would take two minutes – just get a new bulb and swap it out. - but if it was that simple, you would have done it already :) - in gtd, even basic chores and small admin responsibilities are defined as projects when they require multiple steps. - “replace hallway lightbulb” actually entails checking the bulb type, finding or buying a replacement, taking off the fixture (do you have the right tools?), swapping the bulb, etc. - we consider projects of all scopes because they are all [[{4.4a} open loops in gtd|open loops]] and should be in an external system.