Cut my Life into Pieces

You may recognize the title as the first line of incredibly poetic compositions in the 2000s (an excellent music period) specifically “Last Resort” by the philosopher group Papa Roach.

A few years ago, I began to notice connections between different aspects, a pattern I began to notice in a number of different frameworks and methods I was working with and observed in my work. In various workplace situations, I began to look back at my experiences across various tasks and roles. I could identify patterns that I’ve done. It also applies to many things in my personal life. The main one is the idea of breaking things into smaller fragments. This method can be seen in a variety of scenarios and is the same idea every time. It makes things simpler to

I was while on a train in wet Gothenburg morning when I was pondering the huge project we were working on and the best way to take on the task. I was thinking, as I have numerous occasions before me “How should I divide the project into smaller fragments? …?” Then I was as if I was in film, watching the matrix unfold in the blink of an eye linking the dots in an elusive system of life. It’s the same idea I’ve experienced many times previously and what I discovered was linking various frameworks and methods with using the exact same concept. It’s called the fragmentation principleand is connected to Bounded Ratio theoriesas human decision-making. That is, we are only intelligent and productive within the confines of time and cognitive capacity of our minds. Simple and straightforward There are limitations in the amount of information we can manage at the simultaneously and our decision-making process is affected by this limitation. The principle of fragmentation is to break things into smaller pieces, so that we’re within our cognitional limitations and become more effective decision-makers. You’ve probably encountered this, without pondering its significance in the words

  • Division and Conquer
  • Baby Steps
  • What is the best way to eat an elephant? A bite at a time

I found this fascinating and decided to give my thoughts on this.

My career began software development as a project management specialist and solution architect for various software projects. The principle of fragmentation is extremely simple. I would suggest that the foundation of managing projects in general is the complete principle. Split a project into smaller, more manageable chunks and design them according to budget, time, and the scope. It was incredibly basic to me . I suspect it’s because I’m hard-coded by the principle of fragmentation since my very first day of. I am able to recall vividly how I used to organizing my assignments using hierarchical bullets or even dividing my space into separate areas for toys. When I was introduced to Excel I set out to build databases for all of the VHS tapes to make it better could manage and search the entire collection of films we owned. Therefore, it was natural for me to use project management and to structure the various aspects of a software-based project.

This led me to develop into Business Consulting and working tight with my customers, and placing myself in their organization’s process and shoes to understand the potential for improvement. In this case, we frequently used techniques such as impact mapping to better understand the goal-oriented approach to change in the business. Similar to in the OkR framework is to identify the goal for an initiative, and then break it into smaller impacts or actions that could be measured or translated to a major outcome that can be will eventually lead to the desired goal. Another approach that is frequently used include that of the Framework for SMART to establish specific goals that can be measured and time-bound. The idea behind it was to pinpoint the high goal and break it into smaller actions or tasks that could be the basis of the organization, typically with the help of a software program to make these magic efforts more efficient at the end.

In this time, I began to develop a greater curiosity about software solutions as well as product management. This led me to study programming. There were some illustrations of the principle of fragmentation in the object-oriented program. It is the process of breaking down code and functions into independent methods or classes that can be reused in an more efficient manner. Also, it came into contact with Atomic Design Frameworkwhere you break down and separate designs into parts that can be reused and simpler to manage due to their smaller components. Instead of having to rename a button five times, you create all buttons using the same component, resulting in better management of the time. The components are utilized for compounding to create larger components.

Compounding is an excellent term in relation to the fragmentation principle. They is often utilized in personal growth. A lot of self-help books focus on the idea that “baby steps” leads to the development of certain aspects in your life. I was exhausted mentally due to excessive work at one point , and I did some soul searching and travel. I read these books and techniques and found them to aid me. Particularly the concept of Stoicismwhere you pinpoint the area of your life that you are in control of but not. Cut the world view into smaller pieces and concentrate on what is essential to you and which you are in control of, then take care not to worry about the rest. The effects of compounding can be observed in the study and the techniques that are used to develop habit in the effort to alter the way you conduct yourself. Atomic Habits is an ebook which has had a significant influence on me through instructing me to avoid setting ambitious goals that are based on superficial plans to change everything in a single moment. Instead, goals for personal development are achieved by many tiny contributions that eventually lead to something larger. I recently developed a brand new model for personal development built on this concept as well as the OKR framework that is fascinating to experiment with, but it’s a different scenario.

After a lot of soul searching, I finally found a balance in my career and life that led me to the field of product management, where most of these experiences are recapped. As a leader of a product, you must establish the vision of your product and then break it down into a plan of action which can be used to make the development of an overall roadmap. This is the same for roadmap initiatives, which can be broken into four risk zones

  • Risk of value – whether buyers will buy it, or users decide to make use of it
  • Risks to business Risks for business whether this method is applicable to the different aspects of our company
  • Risk of Usability – whether or not customers will buy it or whether users choose to utilize it
  • Risk of feasibility Risk of feasibility the ability of our engineers to create what we require with the resources, experience, and technologies we have

We can also use methods like design thinking which helps us reduce a larger project into a smaller, more specific problem we wish to concentrate on in order to ensure that we are effectively solving real problems that have a positive outcome for our customers as well as customers.

Personally, I am a fan of this story mappin Gmethod of managing an unfinished task and the tasks that must be accomplished by the team responsible for product development. It is, to me the most effective way to show alignment of expectations and create value-creating features. The idea of breaking bigger actions into smaller tasks that the system or user performs to tell a story and then break it down the implications for us with regards to the solutions we need to consider. Story telling is a wonderful method to create a shared understanding among stakeholder as well as users and team members. Combining storytelling methods along with the fragmentation principle is very effective. The interesting thing is that you could reduce things to levels that appear to be insane and cumbersome, but it’s often the most effective method to achieve excellent results. While in an idea or refining sessions with my engineers, my main concern is “can we break it up to smaller steps” to allow us to move ahead. The entire concept of agile development is built on smaller steps that can be taken to mitigate leaps of faith risk in software development.

Provide the team with the most effective tools to analyze the issue and ability to break things down can help them work faster , and they will also experience that dopamine rush of seeing the progress. This is the basic principle of productivity strategies that have been in the spotlight for quite a while. They are often referred to as “micro tasks” which use the principle of fragmentation to break down larger tasks into smaller tasks that which you can tackle in a short timeframe to ensure you remain focus and move towards the correct direction. This is what I would like my engineers and stakeholders to aim to achieve, the feeling of working together and continually generating value. Famous quote by Mark Twain says it all

“The way to get ahead is starting. The key to getting started is breaking down your complicated massive tasks into smaller manageable tasksand then starting from the beginning .”

Leave a Comment

Your email address will not be published. Required fields are marked *