{"id":1294,"date":"2016-06-19T17:07:00","date_gmt":"2016-06-19T16:07:00","guid":{"rendered":"http:\/\/silta.es\/juantatay\/2016\/06\/19\/the-assumption-is-the-mother-of-all-mistakes\/"},"modified":"2016-06-19T17:07:00","modified_gmt":"2016-06-19T16:07:00","slug":"the-assumption-is-the-mother-of-all-mistakes","status":"publish","type":"post","link":"https:\/\/silta.es\/juantatay\/the-assumption-is-the-mother-of-all-mistakes\/","title":{"rendered":"The assumption is the mother of all mistakes"},"content":{"rendered":"

 How To Write Project Task Descriptions<\/a><\/p>\n

\u2026We are all familiar with this scenario: We start our workday as we open our team\u2019s task list and our eyes pop in front of something reading \u201cUpgrade website\u201d, \u201cX integration\u201d, \u201cWrite an article\u201d.<\/p>\n

Now, let\u2019s see what\u2019s behind this mess<\/b>, and if there is a way to handle it. We find:
\u2022 Vague Task Descriptions<\/b>
Example: \u201cAnchor links on blog\u201d
\u201cInsert anchor links to subtitles in the X blog article\u201d
\u2022  Oversimplifying Complex Tasks<\/b>
Example: \u201cWrite blog content\u201d
\u201cBlog request: Write an article about how to write better task descriptions.\u201d (With subtasks)?<\/p>\n

How to Write Better Task Descriptions<\/b>
\u2022 First, define the purpose by asking \u201cWhy<\/b>?\u201d You need to know where you\u2019re going before plotting the course.
\u2022 Next, start with the end in mind<\/b>. To figure out how to do something, visualize the end result.
Then, you can start articulating tasks.<\/p>\n

Each task needs<\/b>:<\/p>\n