Day 7 - The bullet solution (a way to quickly get to the point of each lesson)
A time saver that keeps me from writing stuff I'd have to cut later
Today is Day 7 of building my next course in public. So far we've followed all five steps I described in my popular Twitter thread on Rapid Course Design.
However, there are some additional outlining steps that allow us to rapidly produce a course.
The sixth step, is answering the outlining questions using bullet points.
So for a question such as "What are the elements of iPARA?" I won't just write out a paragraph. I may lose my way if I do that. Instead, I'll write out some bullet points. I'll repeat that for each question in the outline.
Then I'll circle back in a later step and use those bullets to guide more detailed writing.
I made a short video showing how I engaged in writing these bullets. I did my best to think out loud so you could see my thought process as I did the writing.
The video is 12 minutes long.
https://www.loom.com/share/c2c3ea641dbc4030af78d4275726aa40
Until tomorrow,
Rodney
P.S. I've included the outline so far below with the new bullet points bolded.
The outline so far
Part 1: Setup iPARA
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
Adding stuff to the Inbox
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
Producing projects
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
Weekly Review
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
Monthly Review
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
I'd say almost because of my team training problem.
This is making good sense to me and is, I hope, a really good way to quickly organize the projects I am working on. It doesn't have to for writing a course. It can be for any project. However, I love that I am learning to write an Atomic Course.