From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id CE3kKg+DZ2chDAEA62LTzQ:P1 (envelope-from ) for ; Sun, 22 Dec 2024 03:10:07 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id CE3kKg+DZ2chDAEA62LTzQ (envelope-from ) for ; Sun, 22 Dec 2024 04:10:07 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; none Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 8322596107 for ; Sun, 22 Dec 2024 04:10:07 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tPCLf-0007Cl-H9; Sat, 21 Dec 2024 22:09:43 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tPCLd-0007CR-Ox for emacs-orgmode@gnu.org; Sat, 21 Dec 2024 22:09:41 -0500 Received: from mail-lf1-x12e.google.com ([2a00:1450:4864:20::12e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tPCLc-00016y-3k for emacs-orgmode@gnu.org; Sat, 21 Dec 2024 22:09:41 -0500 Received: by mail-lf1-x12e.google.com with SMTP id 2adb3069b0e04-53df80eeeedso3174970e87.2 for ; Sat, 21 Dec 2024 19:09:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734836978; x=1735441778; darn=gnu.org; h=content-transfer-encoding:to:subject:message-id:date:mime-version :references:in-reply-to:from:from:to:cc:subject:date:message-id :reply-to; bh=vMNDPkYJ/aKR7yZ1WXg31q4iCSQjLtHKg/FJoaaek/U=; b=gfjDg+ww0KKr/+3Mzqs5ezG7syqvyIRHWWUIV2vF4X7+XtCPVJuyoC40ZhveBvWeaa H72SYeXqpDSqx7fB8fzxbP7k2tfzKJYJGJfex4H20l+4+qLsEYbtdWn8GXRfkMpeF6qg FgwK4IYUppslRd6sJx9yynIdEuEttdEpMmvULbiNKp5Ity5RssLqK94c7XeuMJgKu1D4 tHNENBZ0b6QL281Na92a0zrkdz/Pww86Jen87tjkTNkvtRQzh+RjMtrkOsXf3beOLhzK XksFU9GNrejjK78jQWrI/dWxFxZzeDoiYW1YYArNbPp2tx1rDF00nW3fErcZ8Jl7yIkS jB9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734836978; x=1735441778; h=content-transfer-encoding:to:subject:message-id:date:mime-version :references:in-reply-to:from:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=vMNDPkYJ/aKR7yZ1WXg31q4iCSQjLtHKg/FJoaaek/U=; b=NkxHx15XdYecH4V7i/8zHC//VRa+qh3cGYfmzEK13L/x17oMSXsoDmbIJz9P5A8Lq+ 3xl+YEbDpyk2wrlro3S3RFM+QePz2pRp1p9WeK8RLlmGGZN+NkvAT7+9Y1pmubtfsPAl xuci9QpLGC2jRv8x/y7Jf9uL0jwnEoXlDMczEx8kSm6I4iAZjFXpjLEBOaZ7bmiF2CqW jzmdirU6LVx6gD01A5TmGnuzJHtfV2iTIqBVPwhoplLYz7AF0wEo0NYFMW28GybizLdr B/+e1lZ25QtawtxQRsGkCTjSo2z6OEhYCl2o/cdJGaTO5/Ug+wr2S9I1GhUsFMYgpdkK mu1Q== X-Forwarded-Encrypted: i=1; AJvYcCW8fX/vFJ+NPgoC+mIWta7HHnGZnNoXNM3qFfcYYTN3rjqgAGXelAaUToBH5J+wKruYxaNLuE5G11Bil72X@gnu.org X-Gm-Message-State: AOJu0YwCLozf0uJRJ4ao9BujOq/dNEmH3KI9WNQMi7mVynBFB8C/su3w x2WFtztzmPppVaGfEZiVDCe5Nef/N4uH+eYrNsX+0ygYvsQHM7ECi8tq6sqYhC6gHLM+DevI4d9 eqjigIrA5EU3Z3FqJLn4Y/d/3hDI= X-Gm-Gg: ASbGnctbpVAGNwH77EufWN0sTgYLuwYmue/RqUMZc2EF34oIPa3o4550MbyAQr5q9VU Ei2m2L2wNsswY/CdrQo++vvt4vwQDsPw1q+EDLg== X-Google-Smtp-Source: AGHT+IFAVzzChGboci1v8v5FwAHroCJEJtJrc48TRBHvIn+LtUHXokPUso+CCn7wiosQPzHZS+EJ3SahETXGfgZUtFA= X-Received: by 2002:ac2:4c46:0:b0:540:2022:e3c7 with SMTP id 2adb3069b0e04-54229581ed5mr2100823e87.40.1734836977332; Sat, 21 Dec 2024 19:09:37 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Sat, 21 Dec 2024 19:09:37 -0800 From: Kristoffer Balintona In-Reply-To: References: MIME-Version: 1.0 Date: Sat, 21 Dec 2024 19:09:36 -0800 Message-ID: Subject: Re: Workflow for planning and scheduling tasks with org mode To: Ashish Panigrahi , emacs-orgmode@gnu.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::12e; envelope-from=krisbalintona@gmail.com; helo=mail-lf1-x12e.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -4.00 X-Spam-Score: -4.00 X-Migadu-Queue-Id: 8322596107 X-Migadu-Scanner: mx10.migadu.com X-TUID: s8L8SfRTSvo4 On Sat, Dec 21 2024, Ashish Panigrahi wrote: > Hi, > > I am fairly new to org and was wondering what are the common workflows th= at people follow for planning and scheduling with org-mode. > > Currently I have one file called agenda.org to which I write a top level = header for the week that I'm planning tasks for, followed by the tasks with= the TODO keyword in front of the tasks. Still trying to figure out org-age= nda as it often seems to fail me (or perhaps I've not understood the exact = working behind it) but I often find myself pressing "C-x [" to bring agenda= .org to the front of the agenda list, after which I can see my org agenda. You can find a lot of other workflows for org-agenda throughout online forums and blog posts. I'll briefly outline the general shape my "workflow" has currently. For me, I'm a proponent of having flexibility in a task management system. That is, I cannot have the system become dysfunctional after e.g. a day or week of falling behind. In the past, with org-agenda and other task management apps, I had too rule-based of an approach so if I didn't do a task the exact day I scheduled it for, then it'd pile up on the next day, and then that day I wouldn't be able to do both the backlog of items and the items I scheduled for that day... and so on. Nowadays I have this: I have one org-agenda view for tasks that have a deadline or scheduled date for today[1] and that are have the todo keywords I've designated for "tasks I will do"[2]; then I have another view for tasks with the "inbox" tag that are "assigned for review." By "assigned for review" I mean tasks that, using the org-review[3], have a NEXT_REVIEW property date that is today or in the past. This second agenda view allows me to create tasks that aren't fixed to a certain date (because if I do that for all tasks, the tasks for any given day will be a mix of "have to do" and "can do later") nor a bunch of tasks without a date (which results in too many tasks visible at once, making it hard to prioritize). With these two views, I can always do the following. (1) When I want to be productive, I open the first view to see the tasks I have to get done today (because I scheduled them today or their deadline is today) and the tasks which I've determined should be out of the "inbox," and are therefore tasks I should consider either resuming or starting. (2) At the start of the day or when I feel it appropriate, I can see the tasks which are in my inbox. Those tasks are ones my past self decided my current or future self should judge: do I do it now (remove inbox tag and schedule it for today), do it sometime soon (just remove inbox tag), or defer the decision to my future self (call org-review-insert-next-review then select a date so I can see this task again on that date), or don't do it at all (set the todo state to CANCELED). The reason this workflow has stuck for me is because if I am unproductive for a day or two, I don't have a backlog of items: my first agenda view has only a few scheduled items from previous days and my "do this stuff soon" tasks are the same. When I go to review my inbox (second agenda view), I can defer items further if necessary. I can also move items into the inbox for review on a certain date (using org-review-insert-next-review) if there's too much on my plate. And through all this, in my first agenda view, I clearly see which items are urgent/important to be clearly visible (using deadlines and priorities) There are of course more details specific to my workflow, like using org-super-agenda to create the views, my tagging conventions, relying on filtering the org-agenda, not scheduling too many items, and so on--but that's the gist of it. Footnotes: [1] Or, with delay cookies, certain items in the future. [2] For me, this is just TODO and NEXT. [3] https://github.com/brabalan/org-review --=20 Best, Kristoffer