How to buy a house?

Principle:

Buying house is like any other purchase. But do we plan when buy chocolates from a retail outlet? 99% would say no. When we go to buy clothes do we plan? 60% would say no. When we go to buy a car do we plan? Most of us would say yes. When we go to buy a house do we plan? 99.99% would say yes. The point I am trying to make is when amount of money involved in a purchase is more risk is also more as lot is on stake. Hence one needs to be double sure that you make the right purchase. If you go wrong most of us won’t be having an option to make a second purchase.

Process:

How Does IBM Cognos Planning Work? Overview

Principle:
System Diagram is the key to visualize each fundamental unit in a system and understand the significance of each unit. System diagram plays a critical role in:

1. Impact Analysis of a change to unit in a system
2. Root Cause Analysis
3. Achieve clear view and understanding of a system to take decisions and solve problems

Process:

CEP Assembly Overview

How To Manage Multiple Action Items At Work?

Action Items

Fundamental Steps

Principle:

Our mind can handle only one thing at a time. Even most advance microprocessors handle one task at a time. Hence our brain should also handle only one problem at a time. Multiple algorithms are available to manage multiple problems / tasks. FIRST COME FIRST SERVE algorithm is applicable in this case but ability to prioritize needs to be available. Hence, 2 rules will work; primary will be FIRST COME FIRST SERVE. Secondary each task in queue will be assigned a priority. The one with higher priority will be handled first then the low priority ones. There will be only 2 priorities to avoid complexity – HIGH & LOW. Priority will be determined based on level of impact. Level of impact will be determined by asking a question: IS THE PROBLEM CAUSING A STOP WORK? If yes then priority is high else priority is low.
Our brain or even microprocessors can execute fundamental steps only. Knowing only problem or action item is not sufficient. Hence, process execution time and errors can be reduced if work is planned till the fundamental steps level before commencing the execution. Having fundamental steps ready to use will save a lot of time thinking after each step about the next one to be executed. It will also ensure no critical step is missed out and will play a critical role in time slicing too i.e. working of multiple action items / problem at the same time.

Process:

How To Do Revolutionary Work At Office?

Principle:

Key to efficient work management with ease and revolutionary outcome is:

• Visualize = Visualization helps in understanding.
• Articulate = Know clearly to the level of finest detail i.e. to the level of fundamental units
• Why = Knowing reason makes you realize the importance of it
• Process & Micro Process = Process helps in keeping one prepared with the steps that need to be followed to achieve what is desired. These steps being tested ensures desired results. Documented process ensures no critical step is missed and is followed in required sequence. Process after each successful implementation gets tested for reliability. Unsuccessful implementation reveals the weak spots which can be improved by putting micro process in existing process to handle it.
1. Micro process is the sub process within the main process to handle a problem faced during the execution of main process. This ensures that the end result is achieved even after facing a road block. It is like exception handling in computer programming. If error is not handled program fails to achieve the desired result and terminates. But if you handle the potential problem then end result is achieved.
• Root Cause Analysis (RCA) = Problem seen is usually only a symptom rather than the main problem. Root Cause Analysis highlights the main problem. Treating the symptom is only a temporary fix while treating the root cause is a permanent fix. Hence it is Key.

They are the foundation. The key objective is keep the wheel rolling.

Process:

How To Create Solution For a Problem?

Principle:

Solution development can be explained as writing algorithm i.e. sequence of steps which when followed one can achieve what is desired. So, start with the simplest and the easiest way to move towards the destination i.e. what is desired. Then find how close have you reached and what is preventing from reaching the destination. Once the hurdle is identified modify the earlier path then move closer to destination. Repeat the process of identifying and editing the path till destination is finally reached. Once first cut of steps are available review them to reduce or simplify steps.

Procedure:

How To Take Quick Decisions?

Principle:

In our everyday life we need to decide on lot of actions to be taken. Some of them are so regular that we tend to stop thinking before taking the actions; we just do it. This could be dangerous as it’s like letting people cross across India boarder without check. Hence a check mechanism on all actions taken is required to ensure actions taken have the correct purpose and give desired results.

In Quick decision making, actions are already defined e.g. sending email, what should the email contain, speaking out something to a person etc. hence we just need to keep a watch and check each action before executing it. Since our focus is that the action should have a purpose and should be giving desired results hence we will use this as the foundation for quick decision making.

Process:

How To Take Decisions?

Principle:
Decision is making a choice among available options. Correct decision is the choice which gets you what you desire and has minimum negative impact on other units in the system. Hence decision making process relies on this theory.

Process:

How to Solve Problems?

Principle: 

Problem is anything which keeps you away from what you desire.  Hence to reach what you desire you need to remove it or find a bypass.  Usually what you see as a problem is only the symptom.  So getting rid of symptom won’t remove the problem.  To remove it, the ROOT CAUSE need to be found and attacked.  So aim is to investigate and find the root cause.  Once found, choose the way to solve it.

If the source of problem is not getting identified due to steps being not visible use elimination technique to identify them.  Get system to last working state and then start adding the eliminated changes one at a time.  The change which regenerates the problem is the source of problem.

Process: