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

Steer for a talent transformation strategy (and avoiding AI fatigue)

 There was a debate on whether to feature the term “AI” in the title of this article. Honestly, a key motivation for pursuing the research that led to this post was sparked by the widespread excitement about AI appearing constantly in our LinkedIn feed, to the point of feeling the fatigue, and even a bit disappointed in the algorithm of this, and the others, social media and content curated apps.  We soon discovered that there is an entire concept called "AI fatigue", not exactly how we were feeling it, but more about the mixed emotions people in the workforce have regarding the use of AI tools. Photo by Mart Production via Pexels (background updated with AI and Adobe  tech) From micro blog posts to video podcasts, lately, most of the tech content we encounter revolves around AI. They often sound or read very similar, usually mentioning the same few top providers. The articles (and social posts... at least the popular ones with paid-campaigns behind it) tend to focus less...

Building MCP with TypeScript

MCP servers are popular these days. We’ve been researching and exploring a few code repos, some where missing modularity, others just not having pieces that we were looking for… therefore we decided to build our own, simple and foundational that could be a starting point for those trying to solve for the similar things we were… and we decided to share it with the community, via our public github. MCP host, server,data sources     Before we start.  Using Typescript and NodeJS was one of our requirements. This proved somewhat challenging because I don't code as frequently these days due to my leadership responsibilities, and I typically prefer working with C# or Python. Colleagues in my tech community have been working with their teams on some of their MCPs going the Python route. Therefore, I said, “I guess we are trying the other route” 😊. One of our reasons to go with TypeScript was due to the need of the integration with APIs, and based on the research, it seems t...

Digital Sovereignty in a Polarised World - Data, Cloud Power, and the Search for Trusted Alternatives

 Relationships have deteriorated, with trust diminished to an extent that may preclude restoration. The world, once structured to favour certain regions, has undergone significant shifts; for numerous countries, such advantages never existed. In this polarised reality, stakeholders are re-evaluating alliances, as former partners now often embody the role of "frenemy," thereby threatening freedom. This phenomenon is longstanding, rooted in historical power dynamics. When politics and influence supersede principles of fairness, respect, and integrity, ethical boundaries become blurred. Previously, issues that did not directly affect you would get overlooked out of principle, but current risks necessitate action to safeguard sovereignty. Information has consistently served as a key strategic asset, a trend only intensified by technological advancements that have elevated data as the principal factor. In other words, technology has amplified that, and data is the name of the game...

Assembling MLOps practice - part 2

 Part I of this series, published in May, discussed the definition of MLOps and outlined the requirements for implementing this practice within an organisation. It also addressed some of the roles necessary within the team to support MLOps. Lego Alike data assembly - Generated with Gemini   This time, we move forward by exploring part of the technical stack that could be an option for implementing MLOps.  Before proceeding, below is a CTA to the first part of the article for reference. Assembling an MLOps Practice - Part 1 ML components are key parts of the ecosystem, supporting the solutions provided to clients. As a result, DevOps and MLOps have become part of the "secret sauce" for success... Take me there Components of your MLOps stack. The MLOps stack optimises the machine learning life-cycle by fostering collaboration across teams, delivering continuous integration and depl...

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