It's been a while since I posted an update on Logseq Mastery (or anything really)
All my focus has been on finalising the 2nd part of the course: Workflows & Systems. It feels like I've been dragging my heels on releasing updates, which left me ruminating why.
Thoughts below...
1. I think it's reached the point of diminishing returns.
The current version of the course is already high-quality (in my not-so-humble opinion 😋). My next steps were to re-record the videos, update diagrams and add accompanying text, but re-recording now seems unnecessary.
I'm quite satisfied with my delivery after a full run-through of all the lessons (+5.5 hours 😅)
There are some issues to iron out with content flow, but I'm sure most users wouldn't even notice them and it's just my perfectionist eye.
I'll address these with minor iterations.
2. My system had already evolved sufficiently when I released the beta version, and the content remains 100% relevant.
I will address minor developments in specific video updates, and will add more examples to the course from my own database.
Taking a wider lens now...
3. I'm starting to wonder about opportunity costs
It feels like LM has taken time out of other projects: YT videos, long-form writing, consulting work, potentially looking at alternative software courses.
Whilst single-focus is good, I'm feeling a need for some variety #adhd
4. I'm not sure what is really valued in the market: high-speed overviews or slower, in-depth content.
Many have heard of the new PKM tool in the market, @tana_inc. I've seen other creators releasing courses exploring Tana, priced in a similar range to Logseq Mastery.
The turnaround time on those courses has been very quick.
That's not to say they're not good quality. But my gut says that they don't go deep into the fundamentals & systems side of things. They also don't pretend to.
I can't help but wonder if I'm playing the wrong game here.
I've poured a lot of energy into LM over 9 months. Whilst sales have been okay, it's not exactly shooting the lights out.
Maybe I missed the balance point i.t.o. return on effort invested? Maybe I underpriced LM? Maybe I should work on cheaper, lower-effort software courses?
Granted, financial reward is not the only metric of success. Releasing a high-quality info product is something I'm proud of.
But I also need to figure out long-term sustainability, and that might mean lowering my own bar for publishing content.
Lots to explore here in 2023.
Anyways, rambling over.
The price will increase on the 7th of December (2 weeks from now), although only to the $129 amount I laid out earlier this year (also see how I grossly underestimated the effort required
1/ One of the turning points in my PKM practice was coming across a video by @RobertHaisfield where @JoelChan86 breaks down his model for knowledge synthesis in Roam.
I was blown away by the power of networked-thinking & block-based writing workflows.
2/ I've wanted to make a video on applying his process in Logseq for a while but have always found an excuse to delay.
Maybe it's because I've seen how opining on matters in the academic space can be so fraught, and entering that world as a non-academic is opening a can of worms
3/ Well, I finally decided to take the plunge so let's see what comes of it 👉🏽
(I've also learnt that I shouldn't make hints or promises of videos that I'm working towards in the future, because it burns a hole in the back of my brain until it's done 🙈)
1/ A lot has been said about @tana_inc in the last week.
I've been playing around with it for a few days, and the hype is not unfounded.
I scratched together my first impressions & comparisons, along with musings from older tweets on what this means for knowledge work in teams.
2/ First, a word on sticking with your current tool.
There's a lot to be gained from doubling down on one tool, but there's no harm in play 😉 I'm already seeing benefits cross-pollinating into Logseq - the tools complement each other well.
3/ Let's start with problems rather than tools, as software exists to solve user challenges.
PKM users require frictionless input, organisation & retrieval of information to gain mental clarity, generate original output or improve outcomes in their field
1/ There are two broad approaches to deal with 'information overwhelm':
1. Manage the flow (but still consume it all!) - use shortcuts, tools & tricks, and triaged prioritisation 2. Close the tap - stop the information coming in at the source.
I think #2 is more critical.
2/ I've realised the need to improve my filters & make peace with the fact I won't get to it all.
You don't need to listen to every podcast/read every newsletter (esp. if you're trying to appear smart!) Attention is too precious to not enjoy the process of engaging with content.
3/ My goal is to have 2 lists: 'read' & 'don't read'.
There are thousands of non-fiction books out there, and everyone is convinced that the current book on their nightstand is a 'must-read'.
Whilst I take note of these recommendations, there is only so much time in the world.
33 thoughts to commemorate another trip around the sun.
These are some things I've been chewing on over the last while, and I thought it would be a good marker to remember the year by.
The statements are completely unsubstantiated, so take with a pinch (handful) of salt.
As always, I feel the need to caveat.
Any effort to capture broad perspectives in pithy tweets is invariably going to miss some marks. Hopefully there's sufficient ambiguity and minimal preachiness.
Where I fall short, remember your handful of salt 🙏🏽
1. Universal statements on the best way to live your life are best avoided.
Everything is contextual. The current moment is not a snapshot in time, but rather the downstream consequence of innumerable circumstances, and everyone's path to this moment is different.
The lazy answer: all the nouns - people, projects, places. But there's far more to it!
I've been thinking about different components of 'corporate' work & putting together a rough list of links that might help structure workflows.
Many knowledge workers will shift to personal (or collective) knowledge graphs & need frameworks for organising their information.
There are existing frameworks (e.g. the RDF, see wikidata.org/wiki/Wikidata:…) which can be leveraged, but everyone will have their own preferences.
You'll know the feeling of wanting to do something your own way if you've ever opened someone else's Excel model or Notion DB.
It will take time to develop & refine approaches that feel intuitive to the individual, but still conform to protocols that allow for interoperability.