Day 9 - How to create examples when you don't have any good ones laying around

Necessity is the mother of course invention

Today I create some examples to use in the Part 1 lesson.

Creating good examples can be time-consuming if they are not already assembled in advance.  And mine were not assembled ahead of time.

I wanted to explain how I sort a series of files from my Desktop into PARA, but my desktop was clear.

So my first step was to drag some random files to my desktop.  Then I started the video and sorted while thinking aloud.

Tomorrow, I'll write up what I did as it is useful to keep a course in one format as much as possible.  However, I'll include the video in the course as well.

Here's a link to the video:

https://www.loom.com/share/9b3b21b96d604440bc1fc9272201a7c4

Thanks for reading today's update.

Rodney

P.S. I've included the outline below with the example I'm working on highlighted in red.

P.P.S. If you have a messy desktop and would like a free coaching session in which I help you sort it out, email me and we'll set it up. I'll record the session to use in the course.

---

The outline so far

• Introduction

• Part 1: Setup iPARA

  • Drama

  • Defining each element

    • What are the elements of iPARA?

      • Inbox - place to put stuff you don't know where to put yet (most be reviewed regularly)

      • Projects - has an outcome and a deadline

      • Areas - consistent performance over time

      • Resources - categories you are interested in

      • Archive - stuff you no longer need but keep just in case

    • Why are the elements organized as they are?

      • The PARA part is organized according to actionability.  Projects are most actionable, Archive is least actionable.

    • How do you sort stuff into each box?

      • First ask, does this item relate to a project I'm working on?

        • If yes, put in the correct project folder.

      • If no, ask does it belong to an Area?

        • If yes, put it in the correct Area folder?

      • If no, ask is it a Resource I want to keep for the future?

        • If yes, put in the right resource folder?

      • If no, ask if it belongs in archive or trash?

        • If archive, archive, if trash, trash it.

    • Examples:

      • show 10 items on a desktop, then explain where each goes and a reason why

      • Video demonstrating the sorting of items from a desktop into PARA folders

    • Mistakes:

      • Overthinking each element (search can find something if you "misplace it")

    • Exercise: Listing 3 projects, 3 areas, 3 resources and 3 archives and put them in a note in your inbox

    • Exercise: Sort 10 items from your hard drive or browser bookmarks into PARA.

• Part 2: Using PARA daily

  • A: Adding stuff to the Inbox

    • Drama

    • Why add stuff to the inbox and not just find the right place for it immediately?

      • If you know where it goes, put it where it goes

      • If not, put it in inbox to avoid disrupting your flow

    • How do you add stuff to your inboxes?

      • Copy paste method

      • Web capture tools

      • etc?

    • When do you add stuff to your inboxes?

    • Examples:

      • Found a web page with some cool info for a project you may do someday,

      • read an article about potty training (parent of a 9-month old),

      • found a great quote in a book you read and you typed it up in a note

      • Saw a gift idea for your Christmas that's month's away

    • Mistakes:

      • Not scheduling regular time to review your inbox

      • Not adding a note to explain why you saved something

    • Exercise:

      • Add 1 web article to your inbox,

      • Add a note about your progress through this course to your inbox

  • B: Producing projects

    • Drama

    • What do I mean by "producing projects?"

      • Taking a project from starting idea, to conclusion

    • Why is it important to produce a project?

      • If you don't have a conscious process for creating a project, you may never get it done.

      • Or if you get it done, you may end up doing it with heavy lifts instead of many small lifts.

    • How do you use project folders to help you produce projects?

      • They become a collection box for all info related to a project.

      • They cause you to notice when there's something you could put in the box

      • They let you be expansive, since you don't have to make a decision now, you can just store it and decide later.

    • Examples:

      • Fully Alive Program,

      • five training courses I do every year,

      • PARA course

    • Mistakes:

      • Not keeping the same name for a project across all your systems

    • Exercise:

      • List all of your projects

      • Create a folder for one project that doesn't have a folder

      • Make a note that lists three thoughts or ideas you have about the project

• Part 3: Maintaining PARA

  • A: Weekly Review

    • Drama

    • What is the weekly review?

      • It is a ritual that allows you to keep your PKM system in shape

    • Why is it essential?

      • It allows you to trust your system.

    • How do you conduct it?

      • [show the checklist]

    • Example: Video demo

    • Mistakes

      • The Either/or error - do a little if you can't do it all

    • Exercise:

      • Schedule your first weekly review - block an hour even

      • Put the date in your digital calendar with a link to your weekly review checklist

      • Follow the weekly review checklist

  • B: Monthly Review

    • Drama

    • What is the monthly review?

      • It is a monthly ritual that allows you to keep your PKM humming

    • Why is it so important?

      • Keeps the folders from getting cluttered

      • Keeps you on track with your goals

    • How do you conduct the monthly review?

      • [show checklist]

    • Example: Video demo

    • Mistakes:

      • Not having this in your calendar

    • Exercise:

      • Schedule your first monthly review

      • Put the date in your digital calendar with a link to your monthly review checklist

      • Follow the monthly review checklist

• Conclusion

• Total checklist