This week’s curation: official releases and app updates, practitioner discussions, long-form from newsletters and podcasts, plus the prompts, templates, and scripts people are actually shipping (and you can use today). I’m always looking for two things: the “why” behind the “what,” and practical things I can implement to turn information into action.

Here’s something I’ve noticed.

The people who’ve stopped tool-hopping, who actually use their notes, who’ve built AI workflows that feel effortless… don’t talk about discipline. They don’t talk about consistency. They don’t even talk about finding the right system.

They talk about clarity. Not the inspirational kind. The mechanical kind: specifying what they want in enough detail that a system (or an agent) can do it without follow-up questions..

Let me show you what that looks like.

1. Saving Gives You Dopamine, Not Value

A confession Reddit post hit 150 upvotes: “I’ve been saving articles and resources for years, but I never actually use them.”

847 articles. Untouched.

I checked my Raindrop while writing this. Thousands of links and the oldest saved in 2021. I felt called out. One commenter put it plainly:

“The act of saving something gives me a little dopamine hit like I accomplished something. But I never actually DO anything with it.”

The comments revealed the mechanism: the reward comes from capturing, not using. The save button delivers a small dopamine hit (”future me will appreciate this”) and that hit is the actual goal. The article itself is irrelevant.

💎 Saving new information feels like learning. It’s not.

This reframes the problem entirely. You’re not failing to use your saved items. You’re succeeding at something else: the collection ritual.

The intervention that works: forced reflection before the click. One commenter requires themselves to write one sentence about why they’re saving something. Not a summary, but a reason. “Because I might need it for...” forces the question of whether you actually will.

Most items don’t survive that question.

The insight isn’t about self-control. It’s about noticing your brain’s incentives and building a tiny constraint that breaks the loop.

Try it:

Quick (30 sec - 5 min): Before your next save, complete: “The action I’ll take is ___.” No answer? Don’t save.

Deeper (15 min - 1 h): Open your read-later app. Audit 20 random saves with the same question. Delete what fails. Notice how many survive.

This week: Save Monday-Thursday only. Block Friday afternoon to process. The constraint that actually beats guilt.

Source: 847 saved articles confession

2. The Model Isn’t the Magic. Your Scaffolding Is.

Twenty-five years ago, the Matrix called the bad guys “agents.” Recently, that joke went viral (14,000 likes, half a million views) because we’re all building agents now.

But here’s what the meme misses: agents aren’t the enemy. The real villain is building them without understanding what you’re building and why.

Daniel Miessler just rewrote his Personal AI Infrastructure guide from scratch. Buried in the 7-component architecture is a line that stopped me:

”The model matters, but scaffolding matters more.”

We’re all obsessing over GPT-5 vs. Claude Opus vs. Gemini Ultra. But Miessler, who’s been building AI systems longer than most, says the model is just one piece. The real intelligence comes from what wraps it:

• the context it has about you

• the skills you’ve encoded

• the tools it can use

• the security boundaries

• how agents coordinate

• how the interface feels day-to-day.

The real question isn’t AI tools vs. AI agents. It’s: who carries the decision burden?

Tools require you to decide what to do, then execute. Agents require you to specify intent, then delegate judgment. This is why the agent shift matters more than any individual capability bump. Agents aren’t smarter. They absorb the micro-decisions that quietly drain you.

An important distinction: Agents solve input (what comes to you). They don’t solve processing (what you do with it). Automating delivery doesn’t fix the 847-article backlog. It might make it worse. Automation and constraints are opposite strategies for different problems. Use both, but don’t confuse them.

Try it:

Quick (30 sec - 5 min): Open your AI tool. Ask: “What do you know about me?” The answer reveals your scaffolding gaps.

Deeper (15 min - 1 h): Audit your intelligence stack. List: (1) context it has about you, (2) skills you’ve encoded, (3) access you’ve granted. Default setup = running a Ferrari on bicycle wheels.

This week: After every AI correction, say: “Remember this fix for next time.” Watch your scaffolding build itself..

Source: Building a Personal AI Infrastructure

3. Your Note-Taking System Isn’t Failing Because You Lack Discipline

Someone posted on r/Zettelkasten: “I’m researching why Zettelkasten fails for a lot of people.”

The responses revealed the same pattern, and it applies to any knowledge management system, not just Zettelkasten:

Read → Excited → Setup → Capture → Guilt → Abandon

The common interpretation: “I’m not consistent enough.” The actual cause: decision overload.

Every note demands micro-judgments: Where does this go? How do I tag it? Should I link it? What’s the atomic idea? Is this worth keeping?

That’s a design problem, not a discipline problem.

Most failure stories boil down to infinite flexibility. The system asks “how do you want to organize?” and you freeze. Most success stories add constraints:

• just markdown files

• processing on Fridays

• “name the action before saving”

• fewer folders, fewer choices, fewer modes

The system requires you to make dozens of judgment calls per session. Each call costs willpower. Eventually you stop.

I’ve lived this cycle three times. Evernote, then Notion, then Obsidian. The third time worked, but only because I stopped trying to organize and connect everything and started adding constraints.

Here’s the thing: the people who make their systems work aren’t more disciplined. They’ve either automated the decisions or have enough domain expertise that the “where does this go?” question answers itself.

For everyone else, the guilt isn’t a signal to try harder. It’s a signal that the architecture doesn’t fit.

This is Miessler’s scaffolding principle in action: if your system demands constant micro-decisions, you’re fighting willpower instead of building infrastructure.

Try it:

Quick (30 sec - 5 min): Count your notes from last week. Capturing vs. processing: what’s the ratio? If it’s 4:1, you’re building debt.

Deeper (15 min - 1 h): List every decision your note-taking system asks you to make. For each: can you automate it, constrain it, or eliminate it?

This week: Cut your capture rate in half. Process what you have before adding more.

Source: Why Zettelkasten fails

4. Your AI Agent Needs a Security Model (Not Just a Password)

OpenClaw is the hot new AI agent everyone’s talking about. 1Password’s Jason Meller tried it. His verdict: “Incredible. Terrifying.”

The problem isn’t capability. OpenClaw can build kanban boards, make reservations, plan its own database migrations. The problem is that all your credentials, API tokens, and everything the agent remembers about you sits in plain text on disk.

One infostealer. That’s all it takes.

An attacker who grabs your memory files and API tokens can impersonate you, phish your contacts, or (in Meller’s words) “blackmail you with your own thoughts.”

But here’s where it gets interesting. Meller doesn’t say “don’t use AI agents.” He proposes treating them like new hires:

• give them their own identity, not your personal credentials

• grant minimum authority at runtime, not everything upfront

• use time-bound, revocable access, not permanent keys

This connects directly to Miessler’s PAI framework. Security isn’t a feature you bolt on. It’s the fifth of seven architectural components. Without it, your “second brain” becomes a liability.

The specification shift applies here too: if you can’t specify what access your agent needs, you’ll either give it too much (risky) or too little (useless).

Try it:

Quick (30 sec - 5 min): List the directories your AI can access. Can you name them all? Most people can’t.

Deeper (15 min - 1 h): Do a “new hire” review. Open your AI’s settings and ask: “Would I give a new employee this much access on day one?” Revoke what fails.

This week: Add one security hook: a notification when your AI accesses sensitive files. One is better than none.

Source: It’s incredible. It’s terrifying. It’s OpenClaw.

5. Full Life Delegation Is Already Happening

Andrew Wilkinson runs a holding company. Here’s what Claude Opus now handles for him: email triage (not just sorting, but deciding what matters), relationship advice (”my AI therapist,” he calls it), personal styling from wardrobe photos, and investment analysis across portfolio companies.

This isn’t a productivity experiment. It’s his actual workflow.

The pattern: Wilkinson doesn’t use AI to do tasks faster. He uses it to avoid making decisions he’d rather not make. The AI carries judgment that used to live in his head.

The honest caveat: he has resources most of us don’t. Time to experiment, tolerance for failure, existing systems to delegate from. But the architecture is replicable. The question is what decisions you would delegate if you could.

If you can’t articulate what those decisions are, you’re not ready for agents. Specification comes first.

Try it:

Quick (30 sec - 5 min): Write down three repeated decisions you resent making. That’s your delegation list.

Deeper (15 min - 1 h): Pick one decision from your list. Spec it out: What info does the AI need? What output format? What constraints? What’s a failure mode?

This week: Track “decision fatigue” for 3 days. Every time you feel that tiny internal groan - log it. That’s the work to delegate..

Source: Opus 4.5 Changed How Andrew Wilkinson Works

6. Skills Are Systems, Not Prompts

Boris Cherny (Claude Code) recently shared how the team uses it, and the meta-pattern matters more than any individual tip:

They don’t treat Claude as a chat interface.
They treat it as a system they continuously program.

His team’s rules:

“If you do something more than once a day, turn it into a skill.” They’ve built skills for syncing 7 days of Slack, Google Drive, Asana, and GitHub into one context dump.

“After every correction, say: ‘Update your CLAUDE.md so you don’t make that mistake again.’” Claude is eerily good at writing rules for itself. Ruthlessly edit your CLAUDE.md over time.

“Start every complex task in plan mode.” One team member has Claude write the plan, then spins up a second Claude to review it as a staff engineer. Don’t push through. Re-plan.

“Pour energy into the plan so Claude can 1-shot the implementation.” The investment is in definition, not execution.

Every hour spent specifying a skill saves ten hours of re-explaining. This is what Miessler means by “scaffolding matters more than the model.”

I’ve started doing the CLAUDE.md correction thing. There’s something satisfying about watching Claude write better rules for itself than I would have thought to write.

Try it:

Quick (30 sec - 5 min): After your next AI correction, say: “Update your rules so you don’t make that mistake again.”.

Deeper (15 min - 1 h): Identify one thing you do more than once a day. Write a “skill spec”: context, constraints, output format. Save it where your AI can access it.

This week: Every time you re-explain something to your AI, ask yourself: “Could this be a skill?” Build one.

Sources: Thread by @bcherny

The Shift

The six sources point in the same direction:

1. Hoarding persists because collecting bypasses actual use

2. Intelligence comes from scaffolding, not just the model

3. Systems fail because they demand too many decisions

4. Security requires upfront specification of access

5. Full delegation is possible when you can specify what you want

6. Skills work when the decisions are made upfront

💎 The bottleneck moved from execution to specification. The winners aren’t “more disciplined.” They’re better at definition: what they want, what matters, what access is necessary, what decisions they refuse to keep paying for.

—Elle

P.S. We can’t practice having more willpower, but here’s what I find hopeful: specification is learnable in a way that daily discipline isn’t. We can get better at naming the action, defining the output, bounding access, and making decisions once - then reusing them as systems. That skill compounds in a way discipline rarely does.

Topics: Personal Knowledge Management, Learning & Memory

In Part 1: Journals for Time-Travelers, we explored journaling as "thinking made visible." But what if introspection isn’t your thing? You just want to stop losing the lessons you paid for with time and effort.

That’s where the TIL stream comes in.

💡The TIL (Today I Learned) Stream

A TIL stream is a rapid-fire feed of short discoveries: snippets, quick wins, small "aha" moments, timestamped and searchable.

Unlike a journal (which is about you), a TIL stream is about what you solved. Each entry captures one thing: a command that worked, a concept that clicked, a trick worth remembering.

No reflection. No narrative arc. Just learnings, logged before they evaporate.

This is journaling stripped to its most useful core: retrieval. Every entry teaches something specific to you, and to anyone else who stumbles across it.

The original TIL practitioner? Thomas Edison. He filled over five million pages with experiment logs, not essays, but problem-solution pairs. Every attempt, every failure, every lesson. When something finally worked, he’d revisit old entries and apply fresh insights to stalled problems.

The format has changed. The practice hasn’t.

Key Traits

• Short-form and atomic. One insight per entry. A paragraph, a code snippet, a link with context. That’s it.

• Chronological but searchable. Date is the default organizer; tags and categories emerge naturally over time.

• Technical or practical focus. Common among developers, but works for any skill-based learning: design, writing, cooking, parenting, whatever.

• The vibe: A workbench with labeled drawers. “Here’s the trick.” “Here’s the command.” “Here’s what broke.” “Here’s the fix.” Less Dear Diary, more Note to Future Me (who will definitely forget this by Friday).

What TIL Streams Are For

Learning by explaining. Writing a TIL forces you to articulate the solution, not just what you encountered. Even if you’re only teaching a wall.

Building a personal search engine. We all have those moments: “I fixed this exact error last year... how?” A TIL stream is a retrieval system that quickly answers that question.

Tracking your learning trajectory. Over months and years, TILs reveal what you were curious about, what you were struggling with, and what you were mastering at each stage. Breadcrumbs through your own growth.

Making progress visible to others. Shared TILs are the lowest-effort way to build trust and reputation without writing “thought leadership essays” you secretly hate.

Examples to Explore

Want to see TIL streams in action? These are some of the best:

• 🔗 Simon Willison’s TIL — The gold standard. Daily technical discoveries across Python, SQLite, AI, and web development. Searchable by topic, updated constantly.

• 🔗 Brandur’s Fragments — Short, sharp engineering reflections from building production systems at Stripe and beyond.

• 🔗 Josh Branchaud’s TIL — Over 1,000 TILs organized by topic in a simple GitHub repo. Proof that the format scales.

Best Practices:

1. One entry, one insight. “Three things I learned about Docker” is three TILs, not one. Atomic entries are more searchable, more shareable, and easier to remember. Good title patterns: “How to ___”, “Fix ___”, “Why ___ happens”, “Recipe: ___”.

Research note: A systematic review defines microlearning as bite‑sized, targeted content for specific objectives. It reports positive impacts on learning outcomes across reviewed studies, providing strong evidence for the "atomic" note structure. From 📄 Microlearning beyond boundaries (Monib et al., 2025).

2. Capture immediately, polish minimally. The value is in the insight and the timestamp, not the prose. If writing takes longer than learning, you're overengineering. A rough note today beats a polished post never.

Research note: We lose ~50% of new information within an hour, up to 70% within 24 hours. Immediate capture is critical; polish can wait or never come at all. From 🔗 The Forgetting Curve (Ebbinghaus, 1885).

3. Add just enough context. Future-You needs to know why this mattered, not just what it was. One sentence of the problem you were solving and/or the project it related to prevents orphaned snippets that make no sense six months later.

Research note: Deeper semantic processing - understanding why something matters creates stronger, more durable memory traces than shallow surface-level encoding. Context is the glue. From 📄 Levels of Processing (Craik & Lockhart, 1972).

4. Include a minimum viable example. One snippet, one command, one screenshot - something you can copy, run, or recognize instantly. Abstract explanations fade. Concrete examples stick.

Research note: Learners who studied worked examples significantly outperformed those who solved problems on their own. A concrete, runnable example reduces cognitive load and accelerates understanding. From 🔗 The Worked Example Effect (Sweller & Cooper, 1985).

5. Make it a ritual. Spend 10–15 minutes at the end of your day writing down one thing you learned. Not when you "have time." Every day. The consistency matters more than the duration.

Research note: Researchers at Harvard Business School found that employees who spent 15 minutes daily reflecting on lessons learned performed 23% better than those who just kept working. Reflection isn't downtime, it's how learning consolidates. From 📄 Learning by Thinking (Di Stefano et al., 2014).

🧪 Try It Now: Write Your First TIL

15 Minutes: The Daily TIL Email

The easiest way to start a TIL practice? Email yourself.

Near the end of your day, ask: What did I learn today?

Maybe it’s a shortcut that saved you time. A mistake you won’t make again. A concept that finally clicked. A tool you discovered. A workaround that actually worked.

Write it down using this format:

TIL: [One-line summary]

[2–3 sentences of context: what problem you were solving, what you tried]

[The insight, command, or solution—something you can copy or recognize later]

[Optional: link to source, screenshot, or related note]

Then choose your mode:

🎮 Single-player: Send the email to yourself (or write it in a note, doc, or journal). One extra question: How can I turn this insight into action?

👥 Multiplayer: Post it somewhere others can see—Slack, social media, a newsletter. Tag at least one person who'd benefit.

More About TIL Streams

Want to go deeper? These essays shaped how people think about learning in public:

• 🔗 Learning in Public — Why sharing your learning as you go turns progress into a feedback loop (and makes it easier to keep going).

• 🔗 Do Not End the Week With Nothing — A gentle kick to ship *something* each week—an artifact, a note, a fix—so your work leaves tracks.

• 🔗 How to Remember What You Learn — A practical case for “learning by teaching”: explaining what you learned is a fast way to make it stick.

• 🔗 Today I Learned Subreddit — The original TIL community. Fun for trivia, but entertainment-first, not “future-me retrieval-first.”

💎 The TIL isn’t about documenting what you know. It’s about making what you learned findable for the version of you who’ll forget by next month.

—Elle

P.S. But what if quick captures aren’t enough? What if you’re drowning in bookmarks, articles, and resources, and need a system to actually organize them?

Next week: The Curators - when collecting isn’t the problem, but finding what you collected is.

Topics: Decision-Making & Well-being, Personal Knowledge Management, Habit Formation & Behavior Design, Learning & Memory

Time isn’t linear. It has ripples and folds like smooth silk. It doubles back on itself... and if you know where to look, you can catch the future shimmering in the present.

But your notes? Your notes can be wonderfully, stubbornly linear. They can be a timeline. A trail. A Captain’s Log.

This is the next part of the 🔗 Knowledge Organization Styles series. Some people think in webs (🔗Networkers). Some think in outputs (🔗 Makers). Today, we meet The Chronologicals - people who organize by when first, and let “what it’s about” emerge later.

The Philosophy: Sediment over Structure

Here’s the thing about time: it’s the only metadata that the universe automatically assigns to your thoughts. You don’t have to tag a moment “2026.” It just is.

Chronological thinkers lean into this. They don’t organize by topic first. They capture by date and let themes emerge from the timeline. The daily entry isn’t overhead; it’s the atomic unit of the system.

Because the hardest question in knowledge management isn’t “What tool should I use?”

It’s: Where does this go?

And a time-based system answers that instantly: It goes on today’s page, so you can focus entirely on “What’s happening now?”

Da Vinci did this. He filled thousands of pages with sketches, grocery lists, and engineering schematics - all mixed together. Thomas Edison amassed five million pages of daily logs. They weren’t building “systems.” They were thinking on paper, one day at a time.

The Vibe: ”Flowing, autobiographical, low-friction. It feels less like a Library and more like a Captain’s Log. Your notes stack up like layers of sediment: small wins, bugs, questions, drafts, and decisions all mixed together. And it can look messy. But a messy system you maintain beats a beautiful one you abandon after two weeks.

Chronological Notes Organization Great For:

- People who ship or debug every day and need a constant feedback loop: engineers, writers, developers, designers, anyone living in iteration mode.

- Capturing personal story arcs: how ideas, roles, projects, or your thinking evolved.

- High-context work where you regularly ask, “Wait... why did we do it this way?” Timestamped logs make decisions retrievable without forcing everything into folder taxonomies

- Reflective practitioners who value journaling, reviews, and retrospectives as core to their knowledge work, not a nice-to-have.

- Practicing self-anthropology: studying your own patterns, beliefs, and behaviors with curiosity rather than judgment

The Risk

If you aren’t careful, this becomes a write-only graveyard. Dumping everything into a daily note without review creates an archive, not a tool. Writing about problems isn’t the same as solving them.

A journal needs a purpose: retrieval, pattern recognition, or synthesis, to earn its keep. Review isn’t a “nice to have.” It’s part of the system.

The Two Flavors of Time-Travel

I’ve noticed two distinct ways people use time as their primary axis. Most Chronologicals lean toward one, though they often blend:

1. Journal-Driven Knowledge Organization (this week) — today’s page holds your life + work.

2. TIL Streams (next week) — today’s page holds what you learned + fixed.

📓 The Journal-Driven Knowledge Organization

The Director’s Commentary of your life.

The premise is simple: today’s date is today’s note. Everything: tasks, thoughts, meeting notes, existential dread lives under a single timestamp. Topics don’t get folders. They get mentioned, linked, and allowed to emerge over time.

Unlike a private diary, a public journal lets others follow your thinking as it unfolds. You’re not performing insight. You’re leaving breadcrumbs for Future You and anyone curious enough to follow.

The payoff: context. Six months later, you won’t just find what you wrote, you’ll find the situation you were in when you wrote it. That’s the difference between remembering information and remembering meaning.

Key Traits:

- Daily notes as the entry point. The calendar is your navigation; folders are optional or absent.

-Emergent topics. Themes build themselves through repetition and backlinks.

- Reflective and informal. This isn’t polished publishing, but thinking on paper.

- Low friction. Capture first, organize later (or never).

Used For:

- Mental defragmentation: Clearing your RAM so you can actually think. Perfect for morning pages or brain dumps.

- Self-anthropology: Studying your own patterns and beliefs with the curiosity of a researcher, not the judgment of a critic.

- High-context work: When you need to know why you made a decision six months ago, not just what the decision was.

- Processing complex transitions: Career changes, health journeys, creative projects. Documenting as you go turns chaos into narrative

Examples to Explore:

- 🔗 Buster Benson’s Piles — A living “book of life” with chronological changelog and annual reviews.

- 🔗 Chinarut’s Brain Map — Autobiographical map of life events in TheBrain’s visual format.

- 🔗 Winnie Lim’s Journal — A masterclass in vulnerable, useful public journal.

Best Practices:

1. Journal with purpose, not obligation. Before you start, answer: What will I do with these entries? Weekly review for patterns? Monthly reflection for decisions? Annual summary for trajectory? If your only answer is “maybe I’ll look back someday,” this might not be your system.

Research note: 📄 Impact of Perceived Reward on Habit Formation (Judah et al., 2018). Pleasure and intrinsic motivation accelerate habit formation beyond mere repetition: habits stick faster when the behavior itself feels rewarding.

2. Decide your review rhythm before you start. Weekly skim. Monthly “what changed?” Annual “what did I become?” Schedule the retrospective before you begin the habit.

Research note: 📄The Science of Effective Learning (Carpenter, Pan, & Butler, 2022). Spacing and retrieval practice dramatically improve long-term retention, but only when review schedules are planned in advance.

3. Plug into existing rhythms. Don’t add journaling to your to-do list. Attach it to something you already do: morning coffee, end-of-day shutdown, weekly planning session. The best habit draws off an existing one.

Research note: 📄 Habits: A Repeat Performance (Neal, Wood, & Quinn, 2006). Habits are context-response associations triggered by cues. Experience-sampling studies show ~45% of daily behaviors are habitual repetitions in stable contexts.

4. Use low-friction structure. Tiny headings you reuse: Wins / Friction / Decisions / Questions. Nothing that turns journaling into form-filling.

Research note: 🔗 The Fogg Behavior Model (BJ Fogg). Behavior happens when Motivation, Ability, and Prompt converge. Increasing simplicity is more reliable than boosting motivation.

5. Use visual anchors. A photo, a color palette, a quick sketch can hold emotional context that paragraphs can’t. “On this day” images become searchable memories.

Research note: 📄 Personal Photographs & Memory (González et al. review) reporting that personal photographs used as memory prompts are associated with benefits like well-being, mood, and cognitive outcomes in studied contexts.

6. Standardize your dates. YYYY-MM-DD for daily notes. YYYY-MM-DD-Context-Topic for meeting notes. Your future self will thank you when searching 50 years later.

Research note: 📄 Data Management for Researchers: The Importance of ISO 8601 (Kristin Briney, 2018). YYYY-MM-DD format enables chronological sorting, extensibility, and mathematical date comparison.

7. Ignore the “right” way. Most people never start because they’re designing the perfect template. There are thousands of ways to journal. Pick the one you’ll actually do today and tomorrow.

Research note: 📄 Maximizing vs. Satisficing: Happiness & Decision Making (Barry Schwartz et al., 2002). “Good enough” beats “best”: Satisficers report higher happiness, less regret, and lower depression than maximizers across multiple samples.

Try It Now: Build Your Own Time-Travel Machine

60 Seconds: The Timestamp Trail

Open a note right now. Write today’s date and one sentence: What I’m doing → Why → What’s next.

14:35 — Debugging API auth. The token expires too fast. Next: extend to 24h.

15:35 — Brain feels loud after the call. Next: walk before I pretend to be productive.

That’s it. Don’t overthink it. This creates a breadcrumb trail you can follow later.

5 Minutes: Tomorrow’s One Thing with AI

Your journal can do more than record the past. It can help you design tomorrow.

Try this: At the end of your day, paste your journal entry into Claude or ChatGPT and run this prompt:

“Based on today’s entry, help me define ONE concrete goal for tomorrow. It should be: specific enough that I’ll know when it’s done, small enough to finish in 2-6 hours, and meaningful enough to move something forward. Ask me clarifying questions if needed. Then give me a single sentence I can write at the top of tomorrow’s page.”

The next evening, revisit with:

“Here’s what happened with yesterday’s goal: [what you did or didn’t do]. What got in the way? What could I try differently tomorrow? Be direct.”

This turns journaling into a feedback loop: not just reflection, but course correction. The journal holds you accountable because it remembers what you said you’d do.

15 Minutes: The Pattern Hunter

If you have existing journal entries or TILs, scan 10-20 of them. Look for:

- Repeated frustrations. What keeps breaking?

- Repeated wins. What’s working that you haven’t acknowledged?

- Open loops. What questions did you ask but never answer?

Chronological notes make patterns visible, but only if you actually look.

💎 A journal isn’t a record of what happened. It’s a record of who you were becoming.

Read more:

• 🔗 The Bullet Journal Method — Rapid logging as a foundation for daily capture.

• 📄 Interstitial Journaling - Combining notes, to-dos, and time tracking into one daily flow.

• 📄The Lies and Falsifications of Oliver Sacks — A reminder that journals don’t just record who we were, they sometimes reveal the gap between memory and reality.

Parting Words

Chronological systems work because they answer the hardest question in knowledge management: “Where does this go?” And the answer is always the same: today’s page.

You don’t need to decide if a thought belongs in “Projects,” “Resources,” or “Archive.” You just write it down, timestamp it, and trust that patterns will emerge, or that you’ll find it later by remembering when you were thinking about it.

One sentence. One timestamp. The system builds itself from there.

💎 Your personal chronology is the only time machine that works. It won’t change the past, but it lets you meet every version of yourself who got you here.

—Elle

P.S. But what if journaling feels too introspective? What if you want to capture what you solved, not who you were?

Next week: TIL Streams—when "what I learned today" matters more than "what happened today."

In the last edition, we explored the Networkers - people who build knowledge like constellations, connecting ideas across domains through Zettelkasten, Wiki, and Hub & Spoke structures.

But not everyone thinks in webs. Some people think in projects. They don’t take notes “just in case.” They take notes because they’re building something right now and need to capture decisions, document iterations, or create reference material for this specific thing.

Welcome to Part 2, dedicated to the Creators & Makers — the people who treat their notes not as a library, but as a factory floor.

The Four Knowledge Organization Styles

New here? Here’s the quick version:

After analyzing 100+ public digital gardens for their structure and navigation patterns, I landed on four dominant styles of personal knowledge organization::

• The Networkers build webs of connected ideas.

• The Makers structure everything around output.

• The Chronologicals let time do the filing.

• The Curators collect and organize external resources.

The four styles aren’t personality types—they’re structural patterns that serve different kinds of knowledge work. Most people lean toward one primary style with a secondary influence. The goal isn’t to pick a perfect label, but to notice which pattern your best work naturally gravitates toward.

Today: The Creators & Makers.

This edition is for the Creators & Makers: people who think in projects, versions, and shipped work. If your main question is “What did I actually make this month?”, your notes should behave more like a lab, a living book, or a public studio than a library or inbox.

If you often feel paralyzed by complex tagging systems, or if you feel guilty that your “graph view” isn’t pretty enough, you might simply be using the wrong tool for your job. You don’t need a map; you need a workbench.

This edition focuses exclusively on The Makers and the Output-Heavy structures designed for those who learn by doing.

Lab notebooks catch the messy middle; Evergreens capture the enduring ideas; Portfolio gardens tell the public story.

🧪 Lab Notebook / Changelog

A “working out loud” space for unfinished experiments and messy thoughts in progress. Unlike a polished portfolio piece, the Lab Notebook focuses on documenting the evolution of work rather than just the final result. It’s a place for comments, code snippets, failure logs, and iterative testing

Key Traits:

• Work-in-progress documentation: unfinished thoughts, rough experiments, decision rationale.

• Process transparency: the “why” behind choices, not just the “what”.

• Failure-friendly mindset: dead ends and pivots are features, not bugs.

• The Vibe: Raw, iterative, “show your work.”

Used For:

• Overcoming perfectionism: lowering the bar for publishing by embracing the “work in progress” state.

• Debugging context: creating a paper trail to help your future self understand why a decision was made or how a result was achieved.

• Showing your work: demonstrating process, competence, and tenacity to potential collaborators or employers—not just a shiny final object.

Examples:

→ Fabien Benetou’s Explorations — VR prototyping with detailed project logs.

→ Jacky Zhao’s Garden — Experiments with networked thoughts and technology.

Best Practices:

• Write the why while it’s still obvious. The decision that feels self-explanatory today will be mysterious in six months. Date everything, link to the artifact (commit, file, draft), and don’t polish—the mess is the point. A changelog entry written in 2 minutes beats a retrospective you’ll never write.​

• Lower your standards. Lab notebooks only work if you actually use them, which means they can’t require effort. Skip the formatting, skip the complete sentences, skip the context-setting. Just answer three questions after each work session: What did I try? What happened? What’s next? Date it, tag it with the project name, and move on. The value isn’t in any single entry—it’s in the searchable trail you’re leaving for yourself.​

• Write as if you’re explaining it to “future you plus a mildly confused collaborator”: short, clear sentences, and a one‑line “next step” whenever possible.

More about Lab Notebooks:

• How I Use CLOGs to Organize My Writing Files by Bob Doto — CLOGs (Chronological Logs) as a lightweight alternative to complex note systems.

💎 The changelog entry you write in 2 minutes is worth more than the retrospective you’ll never start.

🌲 Evergreens/Living Essays

Long-form, polished content designed to evolve over time. Unlike blog posts (which are snapshots), evergreens are updated, refined, and expanded as your understanding deepens. They’re ideas you expect to revisit for years, not weeks.

Key Traits:

• Timelessness: concept-oriented rather than time-oriented (”How Gravity Works” vs. “My thoughts on gravity today”).

• Publication-ready quality, but never “finished”: revision history often visible.

• Subject mastery: deep exploration of specific domains or concepts.

• Designed to compound: each revision makes the piece more useful, not just more current.

• The Vibe: Authoritative, but calm and evolving.

Used For:

• Building long-term intellectual capital on topics central to your work or thinking.

• Creating reference material you’ll link to repeatedly: from other notes, social posts, and conversations.

• Using writing as a tool to develop understanding, not just record it.

• Establishing expertise publicly: Evergreens become the thing people cite when they reference your ideas.

• Thinking through complex topics that can’t be captured in a single writing session.

Examples:

→ Gwern’s Essays — The gold standard for living, evolving and deeply-researched essays on AI, psychology, and statistics. Many pieces span years of revisions.​
→ Maggie Appleton’s Garden — Beautifully illustrated essays; a “living book” on digital tools and anthropology.​
→ Andy Matuschak’s Evergreen Notes — The origin of the concept. Atomic, densely linked notes written to develop ideas across time and projects.​

Best Practices:

• Don’t wait for perfection to publish. Gwern’s essays carry visible revision histories; Maggie Appleton uses “seedling → budding → evergreen” stages. The evolution is the point.​

• Form follows function. An evergreen can be a 10,000-word essay or a tight atomic note; what matters is that it’s written to compound, not to be consumed once and forgotten.​

• Link liberally. Evergreens gain power when they connect to each other. A web of interlinked essays becomes more than the sum of its parts.​

More about Evergreens:

• Evergreen note-writing as a fundamental unit of knowledge work — Why this approach changes how you think.​

• LessWrong Sequences — Essays designed to be read in order; another “living book” format.

💎 Blog posts age. Evergreens compound. The difference is whether you’re writing for this week or this decade

📂 Portfolio Garden & Building in Public

A Portfolio Garden is a hybrid between a digital garden and a creative portfolio. Finished work and live projects take center stage, but they’re surrounded by the background notes, experiments, and reflections that built them. It’s a “show your work” space: part showcase, part workshop. Unlike a traditional portfolio (which displays polished outcomes only), a portfolio garden shows what you’re trying, what’s working, and what you’re learning—in real time.

Key Traits

• Professional presentation with personal texture: Projects, case studies, and artifacts are easy to browse and understand.

• Notes as supporting documentation: Behind-the-scenes notes, diagrams, and process entries are linked from each project, not hidden in a private vault.

• Creative demonstration: Skills and capabilities are shown through real decisions, constraints, and trade-offs—not just glossy screenshots.

• The Vibe: Confident, generous, “here’s what I made and how I made it.”

Used For

• Validating ideas early by sharing work-in-progress publicly.

• Building trust with potential collaborators, clients, or employers who want to see how you think, not just what you’ve shipped.

• Staying top-of-mind in your field—consistent sharing compounds into visibility.

• Getting feedback that improves your work before it’s done.

• Creating serendipity: public work attracts unexpected opportunities and connections.

Examples

→ Michael Karpeles’ Notebook — A blend of finished software projects supported by deep, Wikipedia-style research notes.
→ Robin Spielmann’s Garden — Design work showcased with supporting notes and process documentation.
→ Simon Hoiberg — A perfect example of Building in Public, documenting the journey of bootstrapping SaaS products from zero to revenue.

Best Practices

• Story beats stats. Your process, pivots, and lessons learned are more relatable than polished case studies. Most people won’t buy your product, but everyone connects with a good struggle-to-solution narrative.

• Share from where you are, not where you wish you were. “Expert advice” often fails because experts forget what it’s like to be a beginner. Progress updates from someone two steps ahead are more useful than wisdom from someone twenty steps ahead.

• Connect your projects. A portfolio garden isn’t just a list of case studies - it’s a web. Link between projects, reference past work, and show how ideas evolved across multiple efforts.

• Expect silence and do it anyway. Building in public requires vulnerability, and most people won’t take the risk. That scarcity is exactly why it works—the few who do it consistently stand out.

More about Portfolio Gardens & Building in Public

• 🕮 Show Your Work! by Austin Kleon — The foundational text: everyone has something valuable to share, and sharing it creates opportunities.

• How to Build in Public 2025 — Comprehensive breakdown of the strategy and its benefits.

💎 Building in public is free, effective, and rare—because it requires the one thing most people won’t risk: being seen before they’re ready.

Try It Now

(60s) – Spot your current “system.”
Look at your last three completed projects. Where does the documentation live—chat logs? Commit messages? Nowhere? That’s your current system, whether you designed it or not.

(5 min) – Write one real changelog entry.
Pick one recent project decision you struggled with (pivot, tool choice, scope cut). In 3–5 sentences, answer: What did I decide? Why? What were the alternatives? That’s a lab‑notebook‑quality entry.

(15 min) – Choose your Maker entry point.

• Need memory? → Start a Lab Notebook. After your next work session, answer: What did I try? What happened? What’s next?

• Need to develop your thinking? → Start an Evergreen. Pick one idea you keep returning to. Write a rough first draft and commit to revisiting it monthly.

• Need visibility? → Start a Portfolio Garden. Take one finished project and write the “behind the scenes” story: problem → approach → result.

👉 You’re Probably a Maker If:

• You feel a note is “pointless” unless it connects to something you’re building.

• Your best documentation happens during a project—and evaporates the moment you ship.

• You’d rather have a messy desk and a finished product than a pristine system and a blank page.

• You’ve said “I should really write that up” about a dozen projects—and written up zero.

If three or more hit home, your notes ask to be organized around output.

Parting Words

Makers don’t need more clever tagging. They need lighter scaffolding around the work they’re already doing.

Most productivity advice treats note-taking as an end in itself. Makers know better. Notes are scaffolding, not architecture—they exist to support what you’re building.

You don’t need a perfect system. You need a good enough system you’ll actually use. Pick one style. Start this week. Let the system grow from the work, not the other way around.

💎 The work you’ve already done is an asset. The question is whether anyone can find it - including the future you.

—Elle

P.S. Which Maker style resonated most? Hit reply and tell me: what’s one project you wish you’d documented better?

You’ve rebuilt your note system three times this year. You watched the Zettelkasten tutorials, set up the daily notes, and created the folder hierarchy someone on Reddit swore by. And somehow your notes still feel like a junk drawer you’re afraid to open.

Most people think they have “a note‑taking problem.” In reality, they have a structural mismatch: they’re trying to grow a jungle of ideas inside a filing cabinet… or run a lab as if it were a library.

The fix isn’t more discipline: it’s seeing what actually works for people who think as you do. Public digital gardens give us something rare: a peek at personal knowledge organization systems in the wild.

Maggie Appleton, designer and visual thinker, writes about digital gardens as “a different way of thinking about our online behavior around information.”

Her garden looks nothing like Simon Willison’s rapid-fire technical discoveries,

which looks nothing like Nikita Voloboev’s sprawling personal wiki.

They’re all “digital/knowledge gardens”, but they serve completely different knowledge work styles.

That’s why I’ve decided to gather and analyze the database of public Digital Gardens. One question drove the analysis: Which personal knowledge organization structures actually work and for whom? The answer isn’t one system. It’s four distinct styles.

Why it matters

When you understand your style of knowledge work better and stop fighting your tools, three shifts happen:

• Simplicity: You stop agonizing over metadata. If you’re a Journaler, you just need the date. If you’re a Networker, you just need the connection.

• Findability: Your notes become retrievable because they are organized the way your brain searches, not how a YouTuber’s brain searches.

• Sustainability: You build a foundation that matches your actual output, not an idealized workflow you can’t maintain. You stop copying random setups from YouTube and start coping with your own constraints instead.

Myth: Master Zettelkasten (or whatever’s trending now) to become a great note-taker and knowledge worker.
Better Option: The structure should emerge from how you actually think, not from someone else’s system. Identify your knowledge work style → Select the model that serves it → Adapt tools to that pattern.

Evidence

When your external tools (graphs, lists, timelines) match your internal mental model, your brain stops wasting energy “translating” the tool and focuses on the work. Foundational research on cognitive fit shows that information systems aligned with user mental models significantly improve task performance and reduce cognitive load. Vessey & Galletta, 1991​

Use / Avoid

Use when: You are starting fresh, rebuilding a vault, or feeling high friction with your current system.
Avoid when: You want a rigid prescription. Most successful knowledge workers eventually blend 2-3 of these styles together.

The Four Notes and Knowledge Organization Styles

After analyzing 100+ public digital gardens for their structure and navigation patterns, I’ve selected four dominant types.​

• Networkers build webs of connected ideas.

• Chronologicals let time do the filing.

• Curators collect and organize external resources.

• Makers structure everything around output.

The four styles aren’t personality types; they’re structural patterns that serve different kinds of knowledge work. Most people lean toward one primary style with a secondary influence. The goal isn’t to pick a perfect label, but to notice which pattern your best work naturally gravitates toward. I’ll walk through each style in depth over the next few editions, starting with the one I see most often misunderstood: the Networkers.

🕸️ The Networkers (Connections-Heavy Organization)

The Philosophy: You think in connections… You don’t read linearly. You find yourself jumping across 3–4 tabs to chase an idea, leaving a trail of open windows behind you. Your best insights come from seeing how ideas from different domains relate. You’d rather link than file and trade tidy categories for dense, idea-level connections. You want to turn your notes into a thinking environment, not just a storage unit.​

Great for:

• Deep, multi-year explorations: research, frameworks, complex projects.

• System thinkers, researchers, and creators who want to explore complexity and interconnectedness.

• Zettelkasten Style. A decentralized web of atomic ideas linked by context rather than category.

  • Key traits:

    • Atomic notes (one concept each). Notes are small, personal, and evolving.

    • Heavy interlinking.

    • Folders are minimal and secondary to links: connections emerge from context, not from a preset taxonomy.

    • The Vibe: Organic, emergent, “bottom-up.”

  • Best Examples:
    → Andy Matuschak’s Working Notes — Nearly “classical” modern Zettelkasten-style notes.​
    → Jerry’s Brain — A massive mind map focused on emergent connections.The best visual “Zettelkasten-style” realization I’ve seen.​
    → Gordon Brander’s Patterns — Atomic entries with heavy tagging across systems thinking, futures, and strategy.​

• Wiki / Encyclopedia Style. A comprehensive resource designed for objective fact-finding and definitions.

  • Key traits:

    • Top‑down topic pages.

    • Factual, reference-oriented tone

    • Great for “what is X?” lookups.

    • The Vibe: Structured, objective, “top-down.”

  • Best Examples:
    → Nikita Voloboev’s Wiki — Huge, fast, with topic graph. The classic personal wiki and a perfect rabbit hole.​
    → Matouš Dzivjak’s Wiki — Traditional wiki structure showing how to organize different knowledge areas.​

• Hub & Spoke Style. A guided exploration where central pages act as launchpads.

  • Key traits:

    • Central “Map of Content” pages branch to specific notes.

    • Guided exploration. Unlike Zettelkasten, this offers clear pathways for the reader.

    • Hierarchical branching (Often 1–2 levels deep: Area → sub‑topic → notes.)

    • The Vibe: Curated, guided, “middle-out.”

  • Best Examples:
    → Paul Copplestone’s Knowledge Garden — Great MOC examples showing work in progress.
    → David Gasquez’s Handbook — Engineering notes and personal systems made approachable.

💎 Networkers build knowledge like constellations—the meaning lives in the connections, not the individual stars.

👉 You are probably a Networker if: You often say “That reminds me of...” while reading unrelated topics, and you feel uneasy when you have to force a note into a single folder.

Topics: Knowledge Management
Sources:

• Hypertext Gardens by Mark Bernstein

• Cognitive Fit: An Empirical Study of Information Acquisition

But not everyone thinks in webs. Some people think in projects, and for them, the work itself is the organizing principle.

Next up: The Creators & Makers. Lab notebooks, evergreens, portfolio gardens, and why your projects might be the only filing system you need.

—Elle

There’s a particular kind of frustration that strikes when someone asks you to “just put that in a diagram or a concept map.” You’ve done the thinking. You have a decent document, solid notes, maybe a tidy summary sitting in your knowledge stack. The ideas are there, coherent in your head, ready to be communicated.

Then you open Keynote. Or PowerPoint. Or Figma. Suddenly, you’re dragging rectangles around, hunting for arrow tools, Googling “nice timeline templates,” and wondering why you ever thought visual communication was within your grasp. The thinking was the easy part. The drawing is where everything falls apart.

Why it matters

Turning ideas into diagrams has always carried a hidden tax: you pay in design skills, time, or someone else’s calendar. That tax means most people stick to text and hope their readers will reconstruct the structure in their heads.

Now you can split the work. NotebookLM acts as a structure engine, proposing whether your idea wants to be a flow, a map, or a grid, and naming the key pieces. Nano Banana Pro acts as a rendering engine, turning that structure into a graphic with real labels and a layout that doesn’t scream “default template”.

Once diagrams are cheap, something shifts. They stop being decorations you add at the end and start becoming part of the thinking itself. You can argue with the structure while it’s still rough, redraw it three times in an afternoon, and keep the one that actually matches how your system works. One honest diagram then earns its keep across talks, posts, decks, and client work.

My “four thinkers, one hourglass” experiment

I tried this on a topic that normally hates diagrams: attention & focus. The thing all of us pretend we can manage with a new to‑do list. I took my own literature notes from four writers: Marcus Aurelius on guarding the inner citadel, Herbert Simon on information overload, William James on attention as a spotlight, and Cal Newport on deep work, and dropped them into one NotebookLM notebook.

Then I asked for three things: one sentence per thinker on what attention is, the main threat each one worries about, and a single visual metaphor that could hold all four.

NotebookLM proposed an hourglass labelled “Potential Attention” with four flows around it: notifications and social feeds leaking grains away, noise and mental clutter whipping up a storm, deep work channeling a focused stream into meaningful output, rest and recovery refilling the glass so tomorrow isn’t wrecked. That spec went straight into Nano Banana Pro with a simple art‑direction prompt. Two iterations later, I had an illustrated poster, “The Battle for Your Attention”, that I can now reuse in talks and newsletters, and tweak by editing the prompt instead of redrawing the scene from scratch.

The point isn’t that attention is special. The point is that the idea → structure → diagram loop now feels like a standard move, not a heroic effort. Yes, it saves time. That’s the boring part. The interesting part is what happens to your thinking when diagrams are cheap.

💎 A diagram forces you to pick a spine. Text lets you waffle. You can hedge, qualify, and layer so many clauses on top of each other that nobody can tell what depends on what. Once you try to draw it, you have to decide what sits at the center, what orbits, what flows, and what opposes. An AI that suggests a structure is, in effect, saying: “Here’s what your argument looks like if we take it seriously...”

Use this workflow when…

Use this workflow when you’re turning a dense research note or strategy doc into a one‑page visual. You’re comparing several options or frameworks that currently live as vague vibes in people’s heads. You’re building teaching material you’ll reuse: onboarding flows, core models, “the same explanation I always give clients.”

Skip it or keep it rough when you’re dealing with messy emotional topics that don’t belong in neat boxes, tiny one‑off decisions that fit on a whiteboard, or anything that needs real visual identity and should land on a designer’s desk. I don’t want to pretend the aesthetics are magical. The diagrams you get this way are competent, not iconic. You will sometimes see that slightly generic AI sheen. If you need something that belongs on a book cover, that’s still human work..

Try it now: one idea → one diagram loop

60 seconds — ask for the shape
Pick a real document: a research note, client summary, or draft article. Drop it into NotebookLM and ask:
“Assume this has to be explained with one diagram. What type fits best (timeline, flowchart, concept map, matrix, funnel), and what five to seven labeled elements should it contain?”

5 minutes — argue with the structure
Read the answer and fight with it a little. Rename elements. Merge two that are secretly the same. Split the one that’s doing too much work. Ask again until the structure on screen matches how the idea feels in your head.

15 minutes — hand it to Nano Banana
Ask NotebookLM to turn the final structure into an image spec: diagram type, element names, relationships, and a few suggested icons or metaphors. Paste that into Nano Banana Pro, add simple style constraints (“16:9, high contrast, clear labels, no more than three colors”), and expect to bin the first image and keep the second or third. Save the best version into a “visual library” folder you’ll actually open again.

Next time someone says, “Can you put that in a diagram?”, don’t sigh and reach for the shape tool. Run the loop instead: idea → NotebookLM structure → Nano Banana diagram. The tools will handle the boxes and arrows happily. Your job is the part that still requires a human: deciding what actually belongs at the center, what orbits around it, and whether the arrows you’re drawing reflect how things really flow (or just how you wish they did).

PS: I’m still not sure what we lose when visualization becomes this cheap. Part of the value of hand-drawing diagrams is that you have to really understand the structure to build it yourself, piece by piece. When you outsource that to a model, you might get a plausible-looking diagram that’s structurally wrong, and miss it because you never did the slow construction work. For now, I’m treating these as drafts for thinking, not finished artifacts.

Topics: Productivity, Automation, and AI
Tools:

• Google NotebookLM

• Nano Banana Pro

There’s a particular flavor of modern absurdity in watching knowledge workers - people who’ve automated everything from their coffee brewing to their cat feeding, manually copy-pasting the same 500-word prompt into Claude for the forty-seventh time this week. We’ve become digital sisyphuses, pushing our carefully crafted instructions up the mountain only to watch them roll back down when we open a new chat. This isn’t a tool’s problem. It’s an environment design problem.

Professional kitchens figured this out sometime in 19th-century France.
Mise en place—literally “everything in its place”—isn’t just about organizing your garlic and shallots. It’s about externalizing cognitive load into spatial arrangements.

The parsley goes here, always. The ladles hang there, without exception. Not because chefs are obsessive (though they might be), but because reliable excellence emerges from environmental constraints, not individual effort.

💎We keep trying to be the smart ones when we should be making our environments smarter.

Myth: Save your best prompts for later copy-pasting.
Better Option: Bundle instructions, examples, and files into Claude Skills that activate automatically, no manual setup required.

Why it matters

• Consistency without copy-paste. Your 500-word mega-prompt becomes a three-word trigger phrase.

• Works everywhere. Skills travel across Claude chat, Claude Code, and the API—build once, use anywhere.

• Compounds over time. Each skill you create is a LEGO block for building more complex workflows.

Evidence:
The power of externalized procedures is well-documented. A landmark NEJM study found surgical safety checklists reduced complications from 11% to 7% and deaths from 1.5% to 0.8%—not through better training, but through consistent procedures.

Cognitive scientists call this cognitive offloading: moving instructions from working memory into the environment reduces errors and mental load. Claude Skills apply this same principle to knowledge work.

Use Skills for:

• Recurring workflows (meeting notes, reports, code reviews)

Avoid Skills for:

• One-off experiments where you’re still figuring out what you need.

Try It Now: Build Your First Skill

(for Claude Pro and Enterprise subscribers)

60-Second Setup:
Enable Claude Skills via Settings → Capabilities → Skills → turn on “skill-creator” and code execution.

5-Minute Quick Build:
Create a “Meeting → Actions” Skill:

1. Start a new Claude chat and type: “create a new skill”

2. When prompted, paste this specification:

Build a “Meetings → Tasks & Decisions” Skill
Outputs: bullets grouped by Topic
Format: {Owner — Action Verb — Result — Due Date}
Include checklist: confirm owners, dates, one sentence per decision.
Add 3 trigger phrases for auto-recognition

1. Download the generated .skill file.

15-Minute Implementation:
Upload and test your skill:

• Upload .skill file via Settings → Capabilities → Upload skill

• In a new chat, paste messy meeting notes

• Say: “Use Meetings to Tasks & Decisions on these notes” (or simply: “meeting to tasks”)

• Watch Claude transform chaos into clear action items.

• (Optional) If you want to make improvements, return to the chat where you created the skill, ask it to modify, then re-upload the new .skill file.

30-Minute Power User (Optional):
Level up with Claude Code - set up local skill development:

• Create skills that operate on local files

• Build skill chains for multi-step workflows

• Read the full guide here: Stop Wasting Time on Claude’s Web

💎 Pro tip: Keep skills focused. Your “meeting processor” shouldn’t also be your “email drafter.”

Think of Claude Skills as hiring a sous chef who already knows your recipes.
You’re not eliminating creativity—you’re eliminating the repetitive setup that gets in the way of it. With Skills, you’re building Claude’s muscle memory for your specific workflows.

The gap between amateur and professional isn’t talent—it’s having systems that make excellence repeatable.

—Elle

PS: What’s the one task you find yourself explaining to Claude over and over? That’s your first Skill waiting to be built. Share what you create—I’d love to see how you’re setting up your AI mise en place.

Topics: Productivity, Automation, and AI
Sources:

• Claude Skills Documentation

• NEJM Surgical Safety Study

• Cognitive Offloading Research

• Alex McFarland on Claude Code

There’s a missing step between research pile and first draft that a lot of writers, researchers, and creators skip: the one where you stop hoarding notes and start mapping them.

What should I do between research and writing?

The missing middle is clustering ideas on an infinite canvas until an outline appears before touching a word processor. In about 15 minutes, this concept-mapping step turns “write” into “assemble,” surfaces missing ideas, and gives you a clean set of beats: main question, key concepts, and action items to draft from.

Myth: Research thoroughly, then start writing.
Better Option: Research → Visual Structure → Write.

Information architect Jorge Arango writes entire books this way: not by collecting more material or crafting better sentences, but by arranging ideas spatially before writing. It’s architectural thinking applied to words: you sketch the blueprint before you build.

The visual brain catches patterns your verbal brain stumbles over, turning that intimidating stack of research into something more like LEGOs with instructions: suddenly, you can see where everything fits.

Why visual structuring matters?

• See the whole project before writing a single word.

• Kills blank‑page freeze by turning “write” into “assemble”.

Evidence:
Concept/knowledge maps improve post‑test performance (meta‑analysis of 55 studies) - Learning With Concept and Knowledge Maps: A Meta-Analysis.

Use / Avoid:
Use for books, long articles, and courses; avoid for short-form content.

Subscribe now

How to start visual structuring?

• (60s) Export or create 5–7 notes using Freeform, Miro, Obsidian Canvas, TheBrain, or good old Post-It Notes.

  • 💎 “We think with things” → switch tools to switch your mind. Changing tools/environments unlocks new ideas and prevents mental blocks.

• (5 min) Map your territory: pile your notes by topic/theme and name your piles.

• (15 min) Bridge test: Draw a line between two piles; write one sentence that justifies the connection. If you can’t, the sentence you wish you could write is the missing pile.

  • 💎 Structure reveals what you don’t know—like Mendeleev’s periodic table predicting missing elements.

• (30 min) Beat Bingo: pick one pile and plan your “beats” (main question, key ideas, action items).

• Continue Writing/Creating/Doing!

Topics: Visual Thinking
Sources:

• Jorge Arango at Sketch Your Mind Conference, October 2025

• Learning With Concept and Knowledge Maps: A Meta-Analysis.

Next time you’re drowning in research, resist the urge to write your way out. Grab whatever’s closest - index cards, sticky notes, napkins from lunch, and spend fifteen minutes playing architect. Draw boxes. Connect arrows. Build the skeleton first. Your future drafting self will thank you for the blueprint.

—Elle

PS: Know someone buried under a research avalanche? Send them this blueprint. We’re all just trying to turn our LEGO piles into something with instructions.

Share