25 February 2013

Break Down


Friends, hope you are using Smart Manager actively. Let's move on towards next concept of Break Down
  • Some times person comes across projects which seem to be of huge size requiring great amount of effort and time. Sometimes people dream of starting a new venture. But even before starting, people start taking stress that how would such big thing be managed. Would they be able to do it or not ? They start doubting their capabilities. Many times people just buckle under the pressure of such thoughts and simply give up the idea
  • In reality they have the capacity to execute but problem lies in attitude.
  • This can be avoided by believing in Break down concept. It means that project / task of any magnitude and however complex it may be can be broken into simple units. You have to analyze the whole thing and break it down into simple units and execute them as per Tasks Management System which brings in systematic way of doing things.

When instead of seeing the whole thing at a time, you see small units your confidence grows and you start believing that yes this is possible

You will be able to handle any task with ease
 
There's lot more in Smart Manager coming up so stay tuned !

Thanks
Aman Preet Singh
GlobalFactor 

Prev  Keep Light

Content © 2013 GlobalFactor All Rights reserved   
Feeback ? Share it on globalfactorapps@gmail.com

17 February 2013

Keep Light

Are you feeling loaded because of ever growing tasks list ? Don't worry solution is on the way !

As more and more tasks are executed, number of tasks under Done, No response categories may increase to large numbers over a period of time. This can
  • Increase document loading time
  • Increase scroll time 
  • Make document look heavy
To keep things light, set a time interval in which all Done, No response (if response is not expected anymore) tasks are moved to Archive. Archive folder should be named as <context> tasks. Document which will hold the transferred tasks should be named as
 
<context> Tasks Done till <date of transfer>

Some important points to consider
 
  • Whenever future tasks come, see if you have already done something similar before. If yes, follow the stages through which task was executed earlier. This would substantially cut execution time as you don’t need to reinvent the wheel
  • Time interval of transfer should be defined on basis of how fast the Task list grows or process can be executed if you feel it’s getting loaded
  • Move Done/No Response tasks to Archive which can be in your computer or external hard disk (assuming you use a mobile device for day to day updates). Remove in the active document to make things light
Sample

Folder:  B Tasks

Here B represents Business context
 
Documents under B Tasks
  • B Tasks completed till 25 Sept’12
  • B Tasks completed till 10 Nov’12
Stay tuned for more !

Thanks
Aman Preet Singh
GlobalFactor     

Next Break Down
Prev Snapshot

Content © 2013 GlobalFactor All Rights reserved

Feeback ? Share it on globalfactorapps@gmail.com

9 February 2013

Snapshot


Friends, hope you have all gone through the last post on Tasks Management. Let's move on to next part of Smart Manager which is Snapshot

Snapshot is a special document which gives an instant view of what you are expecting from others and what all is pending on your end.  

Expecting
As tasks are performed, often external inputs would be needed. You may have asked someone for feedback, given a task to someone  or may have initiated a transaction (eg. bank) whose execution would take finite time. All these come under Expecting category

Pending
This is a snapshot of what things are due from your side. You may have to provide data to someone, work on a task etc.

More categories

Deferred
Expecting/Pending items which are not to be pursued in immediate future can be moved to this category

No response
Expecting items where no response is received after considerable time

Some important points

  • Each Expecting/Pending item should be very brief, only a few words
  • If context of item can be remembered, writing it can be avoided (though, this should not be done at the cost of loosing clarity)
  • As soon as activity is performed, Snapshot list and the related task (if there) should also be updated
  • Mostly Expecting/Pending items are connected with Tasks except in some scenarios where an entry may be directly added
  • Expected date of action should also be added. In case of Expecting items, if response is not received by this date, follow up should be done

Benefits of Snapshot

  • It helps in tremendous saving of time as one does not need to scan all tasks 
  • It helps in having timely follow ups
  • It helps in improving one's reliability

Sample

Expecting

. Feedback Raman websites analysis 20 Aug’12

Here websites analysis is the context. If no other feedback is being expected and you can remember the context, you may not write it, just to make it concise
 
Pending

. Sending email Ajay 25 Aug’12

If response is not received from Raman by due date, follow up should be made

After sending email to Ajay, entry should be cleared from list and update should be added to related task as applicable

Stay tuned for more !

If you like it, don't hesitate to share it further and do a favour to your friends

Thanks
Aman Preet Singh
GlobalFactor 

Next Keep Light
Prev Tasks Management

Content © 2013 GlobalFactor All Rights reserved

Feeback ? Share it on globalfactorapps@gmail.com

1 February 2013

Tasks Management

Friends, let us talk about concept of Tasks Management in Smart Manager
  • An efficient & robust Tasks management system is the need of the day
  • Everyone who wants to work in systematic way with high efficiency must follow it
First step is to define place for your Tasks to reside. If you operate in multiple contexts, create documents with context specific name

For Personal tasks it can be P Tasks, for business tasks B Tasks, office Tasks O Tasks and so on If initial letter is same for more than one context two letters can be used

Hope you are moving along. Going to the next step ..

Add all known Tasks to the appropriate context. This is a recurring process. These documented tasks come under Planned category  

Example Getting son’s book goes to P Tasks whereas Talk to service provider goes to B Tasks

Segregating the tasks according to context helps you balance different roles you play with ease    

  •  Moving on, select tasks which you intend to do in the coming days and move them to Scheduled category. Allot start and completion schedule dates for each of these tasks
  • Add to Pending list also (under Expecting/ Pending list*) 
  • As you start work on a scheduled task, move it to Progress category. Many times,  tasks may not be completed in one go. Whatever activity is performed, add a numbered update (U1, U2 and so on) to describe it. Always add date of starting and completion in each update. If an activity is completed in 1 day, add one date  
  •  Make  U1, U2 bold (if support is present to do this) to easily identify Task stages
  •  It’s good to create an execution plan for Tasks. It brings clarity as to how the complete task would be executed and also to have better schedule estimation
Each activity which is part of plan should be added  as a planned update (U1’ , U2’ and so on) to describe the planned activity. Special symbol should be used to distinguish planned update from executed update. Same symbol used twice can be used to mark updates which are in progress
 
  • Schedule can also be added to planned updates
  • Once the task is completed move it to Done category
  • Separate each task with special character. Don’t use numbers as tasks are moved in different categories or shifted up/down in list, it could consume lot of time to update numbering
  • Always update Expecting/Pending list* as you work on tasks

Have you identified your contexts yet ? Do a little brain storming and add some tasks to appropriate contexts. Start following the above process to get comfortable with the approach.

Let's move on to tasks categories

Tasks categories

Planned Tasks which have been documented but not assigned a schedule yet. If broad priority is known, keep Tasks with higher priority on top and vice versa. This helps in quickly moving top tasks to scheduled instead of thinking every time which tasks to pick in the case where tasks are present in random order

Scheduled Tasks which have been assigned a start & completion schedule 

Progress Tasks having at least one executed/ongoing update    

Done Tasks with all planned activities executed

Deferred Tasks which are not to be done in immediate future due to certain constraints

No response Tasks where you are dependent on an external entity for execution but you have not received necessary response from them yet and expectation for getting response is bleak
 
Need external input Tasks where you have performed actions in your scope and are waiting for someone else’s input before proceeding

Done/Repetitive Tasks which have been executed once but need to be repeated at a certain period of time again in future. Define: Repeat interval, last executed, upcoming execution date, dates on which execution happened

Sample

B Tasks

Progress

Do analysis of existing web sitesU1 Analyzed 5 sites SD 10 Aug’12 ED 12 Aug’12  U2’ Share analysis document for review 13 Aug’12 
SD: Update Start Date  ED: Update End Date U1 Executed U2’ Planned
Stay tuned for more !

If you like it, don't hesitate to share it further and do a favour to your friends

Thanks
Aman Preet Singh
GlobalFactor

NextSnapshot

Content © 2013 GlobalFactor All Rights reserved


Feeback ? Share it on globalfactorapps@gmail.com

 * We would talk about this in future post