I seen this mistake made by many people, including myself.
Work BUG: Mindlessly working without an end goal PER work day/session. I seen people just work..work..and work.. but can’t seem to get it “done.”
If you have experience the following, you’re suffering from this work bug.
- It’s time to call it a day, but you feel like you have not accomplished much even though you did “work.”
- You’re consistently waiting on something, and none of your task are “complete.”
- You don’t have much to show in terms of work, but thank goodness your status updates are verbal.
- You spend too much time on one detail that doesn’t add value to the end product. But you have no clue because all you do is work on a particular task without looking at the overall arching task.
BUG Fix: There are projects that we cannot complete in a day. But we can complete a task from start to end. Write down what you want to get done in a given day with a rough estimation of how much time it would take in hour/minute(s). Work from that list. It’s simple, but not easy. By putting it down on paper, the task will be less taunting and you’ll have a bird’s eye view of your day. Your plan will change as the day progress. That is OKAY.
Expected outcome: You will feel a sense of accomplishment at the end of the day when you can check off items from your task list. You’ll benefit from thinking and acting out what used to be a week, month, or year long process in ONE day because you’re completing something from start to end.
TIP: Your task must include a clear description of completion. Think agile. Is this task viable product (MVP)?
If you’re writing a book, a good task could be write an outline with a short description of the each chapter (this allows you to explore what you already know, often times we know more than we think we do). The next session could be do broad research with a description of how it would fit into your outline. And each following session task is write a chapter (with research, grammar check, etc.)
If you’re designing a wireframe, a good task could be to understand the requirement and create an outline, based on the requirements. And each task after that involves creating one particular page with look and feel, potential real data, and use flow.
I challenge you to try this.