August 27, 2011<\/p>\n
There\u2019s nothing worse than an overloaded task list. It makes it unusable. The MYN system offers a lot of solutions to that. But one main reason people are putting too many tasks there is because they’re putting systematic<\/em> tasks in their list. What do I mean by that? If you have an invoice processing job and you process 50 invoices a day, do not put all 50 invoices in your task list. Use a separate list of invoices and then put one entry in in your task list that says Complete Invoices.<\/p>\n Same if you are say a sales person who is making cold calls. If you are required to make 10 calls today, don’t list each one individually on the Critical Now list; instead make one entry and keep the 10 items in a separate list.<\/p>\n The point is that the purpose of your MYN task list is to give you a way to organize loose and scattered to-dos, allowing you to make sense of a chaotic work life. It allows you to clearly identify the urgency of those scattered items. The MYN list does not take the place of other tools you may use for systematic work processing. Any repetitive tasks which are part of a well-defined process you do routinely\u2014keep those separate, in their own lists or systems.<\/p>\n Michael<\/p>\n","protected":false},"excerpt":{"rendered":" August 27, 2011 There\u2019s nothing worse than an overloaded task list. It makes it unusable. The MYN system offers a lot of solutions to that. But one main reason people are putting too many tasks there is because they’re putting … Continue reading