"Why would I pay for a course if I can find them for free?" This used to puzzle me.
(h/t) to @tferriss DiSSS rapid learning framework(deconstruct-selection-sequencing-stake) I think people underestimate the importance and time investment needed for Selection and Sequencing...👇
1/ Selection - When I first learn something, everything feels like a signal and I don't have the mental scaffold to decide what to keep and what to toss.
Being guided through a structure course helps to focus on the 20% that yields 80% of the result.
2/ Sequence - I don't think learners pay enough attention to this; there are skills/knowledge that serve as foundational blocks where the right sequence enables
maximum output.
And as an amateur learner, I do not have this knowledge.
3/ Learning is expensive, self-learning even more so.
It requires time, attention and mental effort, which happens to be the most valuable currency for many modern-day workers.
I am not even going to bring up the idea of opportunity cost here.
4/ To a person who values time, attention and mental effort, if there were a program that allows me to spend 20% effort/time for 80% of the result that solves my pain points…
If your time is valuable and highly leveraged, that's a deal that's hard to turn down.
5/ what I find interesting as I watch @fortelabs from the sideline is, conscious or not, this is a good strategy for premium courses.
This approach is attracting customers w/ specific pain pts whose time is highly leveraged.
They care about having a solution, not the price tag.
This is a bit of a late-night brain dump as I continue to think about learning, leverage, business and technology.
If you find this interesting, feel free to bookmark or share. If you have ideas, I am all ears.
Ever wonder if GTD had an app, what that'd look like?
Turns out David Allen (@gtdguy) had a clear idea in 1994, tried to build it twice but never got to where he wanted.
I stumbled on this and decided to prototype it out in Roam.
Took me about ~5h. 🧵👇
1/ Prototype progress: 65% done, but 100% functional.
I want to test drive this for ~2 weeks to tinker with the automation and smooth out some wrinkles.
Also still trying to read David’s hand-writing to decipher some of his feature requests lol
But damn. This is exciting.
2/ "What would David Allen’s tool for thoughts (TfT) look like?" I asked; I was so curious.
With the prototype, I deviated ~20% from David's original design (mainly to adapt the GTD principles to fit the digital context I work in) and 15% blocked by Roam's limitations.
Stumbled upon this gem from @tferriss; on fear, self-love & writing.
TL;DR
•Ask - what might this look like if it were easy?
•On writing - write atomically, have a routine, know thyself
•On marketing - good content has marketing built-in, write the book you wish you had
🧵👇
1/⏰26:24
•What might this look like if it were easy?
This is a really deceptively leveraged question.
BC you start to look for elegance and ease instead of the path of complexity that allows you to absorb and tolerate the most pain.
2/⏰40:15
Fear setting - this something Tim still does.
•Define - what are your specific fear?
•Prevent - what are the things you can do to decrease the likelihood?
•Repair - what are the things I can do to repair the damage or get back on my feet?
Thank you @maggied @roamhack for hosting the "Future of Tools for Thoughts" space. We covered -
1. Key elements for TfT (Tools for Thoughts) 2. Specific use case: task and project management 3. Interoperability 4. Trust 5. Future looking
1. What are the key elements for a TfT to be "good"?
- Capture and storage
- Frictionless
- Speed
- Search-ability
Note: there is no ONE right answer, it will be different depending on the problem you are trying to solve.
2. How do we layering time and action to resurface ideas?
- Touched on task management, spaced-repetition
- Discussed a particular usage of TfT being task management and compared tools such as Roam Research, Obsidian and nerded out on a few GTD plug-ins to play with :-)
It's so easy to get sucked into the tech rabbit hole and end up spending hours on researching, instead of producing.
I wanted to share my process on how I usually onboard myself on any new technology.
It's very raw. I am on hour 4.
1/ Disclaimer: my goal is to get to a "sufficient" state so I can focus on producing, instead of tinkering. Avoiding "procrastination by learning".
By no means am I an expert, and I have every intention to continue to learn more.
2/ TLDR; summary -
•Focus on the problem - think "what am I solving?"
•Get feedback ASAP - test drive the tech against your use case, hack it however you can to see if it works for you
•Write down your pain point, solve it