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

Apple's App Tracking Transparency sealing Meta's fate

If you have been following the recent news on Meta (formerly Facebook) you may have read that Meta recently projected their ad revenue will be cut by a staggering $10 billion in 2022 due to Apple’s new App Tracking Transparency feature (also known as ATT). This has resulted in Meta’s stock to plummet by over 20%. Photo by julien Tromeur on Unsplash - modified by Beolle So what is Apple’s ATT and how does it impact ad revenue? Apple has been releasing multiple privacy features for the last few years. This included Apple’s Mail Privacy Protection and Apple’s App Tracking Transparency feature. You can learn more about Apple’s Mail Privacy Protection in our earlier post by clicking here .  Apple’s App Tracking Transparency (ATT) was launched in iOS 14.5 and iPadOS 14.5 where it prompted users to select if they wanted the app to track their activities across other apps on the device. The prompt is displayed when the user opens an app like Facebook or Instagram for the first time o...

SLA-SLO-SLI and DevOps metrics

Companies are in need of the metrics that will allow them to stay in business by making sure they meet the expectations of their customers. The name of the game is higher customer satisfaction by winning their trust and loyalty. To do so, you want to provide good products and services. Therefore you need to find ways to monitor performance, drive continuous improvements and deliver the quality expected by the consumer in this highly competitive market. Photos from AlphaTradeZone via Pexel and Spacejoy via Unsplash SLAs, SLOs and SLIs are a good way to achieve the above. They allow clients and vendors to be on the same page when it comes to expected system performance. If we go one level deeper, vendors/providers work on NFRs (Non-Functional Requirements) when working on their solutions. NFRs define the quality attributes of a system. I bring them up because the relationship between them and the SLAs is that they provide, in a way, foundational aspects for the SLA-SLO-SL...

SRE, DevOps and ITOps

 If you are wondering what the differences between the SRE and DevOps are, as well as how these roles work with ITOps within an organisation then you are not alone; and best of all you are on the right blog post. Often enough business units in a company get confused, assigning the ServiceNow or Jira tickets or any other ticketing system of your preference, to the wrong group, and even having the incorrect expectations when doing resourcing. Let us go through definitions, insights and scenarios that will help you understand the difference. DevOps software development operations - AI Generated When it comes to DevOps and SRE, then you might be wondering which practice came first. While SRE may have originated a bit earlier, internally at Google, DevOps came first publicly as a practice and started to be used by companies. A few years later was when Google decided to open SRE to the world after the publication of the "Site Reliability Engineering" book. Therefore, technically sp...

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