I am a big fan of @ejames_c writings at @commoncog. A subscription to his service leads to many amazing essays. #TfT

I want to highlight this article and why the concept is valuable to use in Tools for Thought. (Article is free to the public)

commoncog.com/no-learning-do…
In this essay, he talks about the amazing work of Edwards Deming, specifically the PDSA model.

PLAN
DO
STUDY
ACT

It's a model for continuous improvement by iterating through multiple workflows to achieve desired results through trial & error (honest examination of results).
The idea of PDSA is that it involves multiple loops of PDSA.

Rarely in life do we reach our intended goals with just one attempt, rather we succeed over multiple iterations, with each iteration getting closer to the desired result.
In this article, Cedric calls our attention to one sad reality. While it is easy to plan and get started (Plan, Do), we often fail to do the Study (analyze their results) and Act (adjust our approach).

He encourages us to "finish the loop" even if it seems like it won't succeed.
Finishing the loop allows us to fully gather the information we need so that we can adjust our workflow and then try another loop.

In other words, what lessons were learned in the current loop to feed into the next loop.
Why is this relevant for TfT? We rarely find the perfect worklfow or approach to some problem we want to solve on our first attempt.

Rather we need to define the goal and then start multiple loops of testing our theories until it finally succeeds.

Let me give you an example.
EXAMPLE: I have to read a lot of material for work. The problem is time.

How do I not only get through all the reading material but extract useful "things" from that material? I mean, what is the point of reading if you don't benefit from it?
I started a series of PDSA loops to experiment with improving "value-based" reading.

For example, how do I select what is relevant and important?

How much time do I spend reading each topic?

How much time a day can I read?

These are not easy answers to these questions.
So I started with a list of priority topics and non-priority topics.

Week one, I had 4 priority topics, and I read 5 minutes on each topic each day (20 minutes reading)

Week two: 4 priority topics, reading 10 minutes per topic (40 minutes reading)

and so on....
I did these loops over multiple months, increasing and decreasing time, the number of things to read, and so on.

Each loop was a week so that I could iterate the process fast.

As I went through each loop, I documented the plan and, during the study phase, "the results".
Then I adapted to what I learned for the next cycle.

It is a painful process, but slowly I started to see how much I needed to read daily to get measurable value from my reading (also to enjoy it and not hate it)

I gathered many interesting insights on myself.
So, the lesson is, PDSA is a useful tool for getting your TfT system optimized, but its a serious investment. My advice:

1) Determine the big problems you need to solve
2) Try PDSA loops on the problem
3) Stick with it until you have resolved the problem.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with TfT Hacker - Exploring Tools for Thought and PKM

TfT Hacker - Exploring Tools for Thought and PKM Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @TfTHacker

Nov 8
1/5 Obsidian Survey on frontmatter (YAML)

Please answer these questions:

Do you use YAML in your notes? (frontmatter or inline fields)
Do you like YAML?
What do you dislike about YAML?

YAML is cumbersome to work with but does add a "database" like layer to our notes. #TfT
2/5 While I don't find YAML hard to work with, it does create a fair amount of "busy" work in Obsidian. This si one of the appeals to me of a tool like Tana, which provides more UI for quickly working with schema and inputting data.
3/5 On the other hand, Markdown is not a database and doesn't have a way of capturing schema like information. This is why some tools like Obsidian have added a "schema" layer.
Read 5 tweets
Nov 5
1/ In the spirit of sharing, here is my folder structure.

I keep things shallow for "active" documents. I only keep active notes and projects on the root. That way, they are super easy to get to. I archive them once done to prevent the structure from becoming overwhelming. #TfT
2/ in 00-Folders, I maintain my "Archive" with some logical structure (not too much, not too little).

Using the move file command makes it super easy to stick a file into an archive folder.

I collect files in the root of the vault during the week, then once a week archive them.
3/ My Archive is not a black hole of FILE DEATH.

I actually frequently review my archived notes via search or through linking and "Strange New Worlds" resurfacing linked ideas.

I also delete notes of no value. Deleting is a healthy part of managing your archive.
Read 8 tweets
Nov 3
1/ Showing appreciation for developers of open-source plugin developers

Gratitude! A powerful tool that helps those who express it and those who receive it.

Let me provide context. #TfT
2/ I have built plugins for many Tools for Thought. Obsidian, Craft, Roam, Readwise & Office (Excel, Word, SharePoint -- if you consider them to be TfT).

This opens doors to meeting many wonderful users and developers of Tools for Thought. I learn so much from each conversation.
3/ Many of us use plugins for our tools and don't think much about the effort that goes into them. We know there is a lot of effort, but we know we don't really know.

Let me give an example.
Read 19 tweets
Oct 29
1/ Is @tana_inc a "shiny object"?

Man, I hate that expression. While this term has its place, somehow, in the #TfT space, it has become a way to throw mud at others. (competitors, jealousy, etc).

Tana is not a shiny object. Their Slack is proof something good is cooking.
2/ I did not record any official numbers, but before their early access announcement, I am sure slack was sitting around 200-300 users. As of today, it is 3000+.

That is a significant and overwhelming increase in just a matter of a few weeks.
3/ In the introduce-yourself channel on their Slack, numerous new people introduce themselves daily.

These are amazing, smart, sincere & exciting people.

They want to be a part of something special. I applaud them for investing time and energy in Tana's early development.
Read 4 tweets
Oct 24
Learning Planning Skills with baby steps

Another nice Cal Newport video on baby steps for those lacking planning skills.

Read on for some additional opinions. #TfT

I have always been a planner. I enjoy planning, and I enjoy seeing plans come to fruition.

However, I am a realist.

20% - 30% of my plans often don't succeed how I envisioned them.

But when there is no plan, this often means worse results.

Failing to plan is planning to fail.
I have seen that some people give up on planning because plans often fail and require a lot of work.

However, what they fail to take into account is how GOOD things went because they had a plan.
Read 5 tweets
Oct 16
1/ Funny you should ask, @n_vanderhoeven just asked me that same question. Let me share my answer here.
2/ Obsidian and Tana are not easy to compare. They are in the same competitive space: Tools for Thought, but they solve different problems. So there is overlap, but they are fairly different.

Obsidian is the best choice for Markdown, TNO, and long-form writing. Single-user work.
3/ Tana will be best for outliner database-like functionality: (everything is a database record). So stronger for more structured content and querying against that. Multi-user collaboration.

Tana solves many problems within the product that other TfT tools need plugins for.
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(