We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://imageslr.com/2022/efficiency-gtd.html
〇、前言
The text was updated successfully, but these errors were encountered:
最近在研究GTD和PARA的结合,虽然一个是任务管理,一个是信息组织方式,但是两者的切入点都是以可操作的内容为基础,实行“块”的转移。感觉大有可为。
关于博主清单系统的分类那里,个人感觉不用分的太细,GTD的精髓就是轻便简单,分类不同、区别再大的事情最后都会变成一个能不能落实完,执行如何去排序(假如无法做完)。那些复杂具体的分类可以变成PARA中的领域去重点维护。而滴答清单中就简单的变成workspace和life这两块内容即可。我所使用的app不支持指定清单的事项汇总,所以我还会建立一个父级清单来囊括这些执行·项目·等待的事情(如果按照GTD来划分的话),然后再设一个Inbox,一个可能清单,还有一个辅助清单(存放定期回顾之类的事情,辅助GTD流程的完成)
而关于GTD和PARA的结合,我目前还在摸索和学习中。我期望能够把自己的信息管理成系统地嵌入到生活中,实现“无压”的状态。哈哈
Sorry, something went wrong.
关于博主清单系统的分类那里,个人感觉不用分的太细,GTD的精髓就是轻便简单
这一点很赞同。我使用的也一直是 4 个大清单(工作、个人、某天、重复)。某些时候,如果一个项目下的子任务较多时,我才会把它拆分成为一个单独的清单,这样便于查看和修改。但是当这个项目完成后,我一定会把清单删除(归档),避免清单系统越来越细。
No branches or pull requests
https://imageslr.com/2022/efficiency-gtd.html
〇、前言
The text was updated successfully, but these errors were encountered: