Skip to main content

Productivity framework for 2024

[PLACEHOLDER]

Recently I was at a Christmas party and I found myself giving advice to a friend on being more productive. I shared the approaches that I take which helped me become more productive at work and in my personal life. The conversation with my friend inspired me to share my approaches in this blog

Photo by Moose Photos from Pexels

 

My productivity framework has five key pillars and to remember them I use the mnemonic, POFOR = Plan your tasks, Organize yourself, Focus on your tasks, Optimize yourself with habits and Reflect to ensure you are being productive on the right tasks.

Plan

Planning is very crucial as it sets the tone for the rest of the pillars. I always found I was more productive when I planned my tasks compared to when I didn’t, and hence planning has become my rule of thumb. I recommend taking 30 minutes at the end of each day to plan your next day. This means prioritizing your tasks and blocking your calendar accordingly. By not doing so, you are at risk of others booking your time on your behalf, turning your calendar into "meetings' nightmare". This can negatively impact your productivity, force you to work off hours and disrupt your work for the following days. In the worst-case scenario, it can trigger a domino effect that can cause burnout. 

Pexels-eugene-shelestov-paper-burning-says-time

My productivity framework has...

...five key approaches and to remember it I use the mnemonic, POFOR = Plan your tasks, Organize yourself, Focus on your tasks, Optimize yourself with habits and Reflect... - Herak

- Photo by Eugene Shelestov

Organize

Another pillar of being productive is organizing your work, resources, and artifacts. I recommend using Brian Forte’s PARA framework to organize your digital work. PARA stands for Projects, Areas, Resources, Archive. The key approach here is to have the projects you are actively working-on under the Projects folder. Once a Project is completed you move it to Archive. You keep your recurring tasks, like status updates, presentation decks, under Areas. You store your reference documents under Resources. 

Focus

Focus is key to ensure you remain productive during the execution of your planned tasks. I apply three key strategies to stay focused:

  • I avoid external distractions. I keep my phone away or upside down when I am doing deep work. I stopped my notifications from Teams, Slack, Outlook and blocked 30 minutes' time slots during the day to check my messages.
  • I time box my tasks. I personally use the Pomodoro technique. However a general time boxing of your preferred period works as well. The key is to break down tasks into smaller tasks and work on them during the timebox.
  • I resist intrinsic distraction: We are constantly being trained by social media to seek instant gratification. How many times have you found yourself reaching for your phone unconsciously when working on tough tasks?
    • My approach is to be aware of when this happens and apply a 10 minutes rule. I try to resist the temptation for 8-10 minutes', and often I find the need for that distraction fades away, letting me focus on my work.

Optimize

Every framework has optimization as part of its building blocks, therefore, in mine I focus on incremental improvements.

One thing that helped me with my productivity was to resist perfectionism on all tasks, thus giving all task the same "weight" which is not practical. Instead I adopted LNO framework, by Shreyas Doshi.

This framework has allowed me to prioritize my tasks by their potential impact and exercise perfectionism on the highly impactful tasks also referred as Leveraged tasks. Here's a breakdown of LNO framework. 

  • L stands for Leverage. These are tasks that can lead to double digits' gains (~10X). As Shreyas' says, these are the ones that you "Do a great job, let your perfectionist shine."
  • N stands for Neutral. These are tasks where the effort to gains ratio is approx. 1X. Effort = Reward.
  • O stands for Overhead. These are tasks that have less than 1X gain/return. Effort > Reward.

Reflect

Let’s assume your goal is to write and publish a book, of which you have drafted the idea three (3) months back. You managed to establish a cadence for this work, and have scheduled session in your calendar, leading you to a publication milestone in 5 months’ time. However you also have been focusing at learning how to code. You have set both with the same level of priority, and you have started to deviate your efforts towards coding, instead of writing your book. In this hypothetical scenario,  this will not help you reach your main goal of writing your book and hence when you reflect back you will realize that your "productivity" went to a completely different goal. The worst case scenario would be that we don’t fully accomplish any of the two, falling into a counter-productive situation.

Trending posts

AGILE For DIGITAL AGENCIES

Introduction Some Digital agencies have a project process where waterfalls still plays a big part of it, and as far as I can tell, the tech team is usually the one suffering as they are at the last part of the chain left with limited budget and time for execution. I do believe that adopting an Agile approach could make a Digital Agency better and faster. In this article I’m presenting you just another point of view of why it make sense looking at Agile Methodology.  Why Agile for a Digital Agency? The Agile movement started in the software development industry, but it has being proven to be useful in others as well. It becomes handy for the type of business that has changing priorities, changing requirements and flexible deliverables. In the Digital Agency of today you need a different mindset. Creative will always play a huge role (“the bread and butter”). But the “big guys” need to understand that without technology there is no Digital Agency. Technical resources are

Key takeaways from landmark EU AI Act

 Recently, the European Parliament voted and passed the landmark EU AI Act. It's the first of its kind and sets a benchmark for future AI regulations worldwide . The EU AI Act lays the foundation for AI governance, and it's pertinent for organizations delving into AI systems to comply with the legislation, build robust and secure AI systems, and avoid non-compliance fines.  Photo by Karolina Grabowska via Pexels My three key takeaways from the legislation are as follows: The Act introduces the definition of an AI system: "An AI system is a machine-based system designed to operate with varying levels of autonomy and that may exhibit adaptiveness after deployment and that, for explicit or implicit objectives, infers, from the input it receives, how to generate outputs such as predictions, content, recommendations, or decisions that can influence physical or virtual environments" The Act introduces the classification of AI systems based on risk to society. The Act outlin

AI with great power comes responsibility

Generative AI continues to be front and centre of all topics. Companies continue to make an effort for making sense of the technology, investing in their teams, as well as vendors/providers in order to “crack” those use cases that will give them the advantage in this competitive market, and while we are still in this phase of the “AI revolution” where things are still getting sorted.   Photo by Google DeepMind on Unsplash I bet that Uncle Ben’s advise could go beyond Peter Parker, as many of us can make use of that wisdom due to the many things that are currently happening. AI would not be the exception when using this iconic phrase from one of the best comics out there. Uncle Ben and Peter Parker - Spiderman A short list of products out there in the space of generated AI: Text to image Dall.E-2 Fotor Midjourney NightCafe Adobe Firefly

Research around JIRA vs TFS

By: Carlos G.    An opportunity came from a colleague to discuss the case of company “X” for improving the ALM by introducing tools to this company. The challenge was to decide between Microsoft and Attlasian . He came to me because I’m a Microsoft kind of guy and he wanted the opinion from my perspective, not as a consultant, but as a friend of what he was trying to accomplish. He said that even though I was inclined to a technology I was able to explore other things and be “fair”. I agreed to be a part of his research because of 3 things: because of my curiosity I'm always willing to learn new techy stuff. Sometimes is good to be the dumbest one of the group. You learn so much! This was a story that I could blog about. (Of course no names are used in this post). My first impression was thinking “cool”; let’s compare Visual Studio TFS vs JIRA. Immediately I got a comment back with: “ Sure but JIRA by itself is more like an issue tracker in simple terms ”. That sa

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed