How to use MLO to delegate / @Waiting for

[pakiya]

Hello,

I'm a small business owner and have to see different aspects of my business ranging from accounts to documentation to sales to production. My to lists mainly consist of follow up which i need to do , things I need to veify , reminders to my team etc. 

So an actualy part of to do list is (in bracker I mention the frequency) . 

- Review the production tracker from samuel (bi weekly)

- Follow up with bank when I get my password (one time) 

- Check with Suresh about big forms for workers (one time) 

- Implement wtih Suresh fire training needed (every 3 months) 

- Ask Rani where will the files go (one time) 

- Consult Rani where will the weighing scale go (one time) 

- Verify reports written by QC (weekly)

- Verify recievables from Accounts team (bi weekly)

- Ask Rajeev the status of race course membership (keep reminding till the project is finished) 

So my people list is Samuel , Rani , Rajeev & Suresh in above list . I infact deal with around 20/25 more on a weekly basis. 

What's the best way to keep this list in MLO ? Should I use context since tasks are kept in different list ? Should I create a seperate waiting project and create dependency of some sorts ? Just use saved search with a person name  ? 

[Stéph]

Hello pakiya,

 

Funnily enough - I just posted a relevant answer to a different thread on this community.  Basically, my solution is to use hashtagged names (ie #Samuel, #Rani, #Rajeev, etc) at the top of the notes field.  When I'm talking to Rani, for example, I'll quickly type #Rani into the search function and all of the tasks related to that person immediately appear in a list of results for me.  It works very well for me, especially as the search function can filter results based on the view you're working in, too.

 

Stéphane

[Joel Azaria]

One of the best and worst parts of mlo is that there's almost always more than a few ways to get to a given result..

I'm also a small biz owner and my business deals with distinct projects, often related to construction projects. As such I can have a lot of these types of "people" items.  For me though they also often also correlate to some part of a larger project.  My way is taken from GTD methodology where they are referred to as 'agendas' and I create an agenda context for each person I need to track items for (coincidentally, I also use # to denote my agendas/people contexts.) I also create a single #agenda context for one off ppl items that don't merit a whole context for themselves.  I don't use that single #agenda context often but it sometimes has it's place.

Doing things this way allows me to:

Put the items in my outline under their respective project (I have a folder for each project, which may bequeath contexts of its own)

Add more than one agenda context if needed (teams or owner AND contractor for ex., multiple ppl who's opinion I want, etc. - it ends up being pretty free-form)

Create one super context called *Agendas which includes all my #namedagenda contexts (in desktop you can make a context include others.).  I find this useful as I can see at a glance ALL the ppl I need to talk to which sometimes helps decide what to do/where to go next.

HTH.

--
You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mylifeorganiz...@googlegroups.com.
To post to this group, send email to mylifeo...@googlegroups.com.
Visit this group at http://groups.google.com/group/mylifeorganized.
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/a54bbf5f-78a1-480d-afde-0d36f69199a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.