Lenaghan Friction-First Productivity System Builder
Design a personal productivity system that matches the way your brain works, so you spend time doing work instead of endlessly maintaining your system.
// TL;DR
The Lenaghan Friction-First Productivity System Builder is a framework for designing a personal productivity system that matches how your brain actually works, so you stop rebuilding systems and start doing real work. Instead of adopting a new method wholesale, you treat every moment of hesitation—'Where do I file this?' or 'Where did I put that?'—as a diagnostic friction point, then make small, targeted changes that resolve each one. Use it when you're stuck in a loop of switching or rebuilding productivity systems, feel like you're the problem, or want to stop optimizing your system and start working on the things inside it.
// When should you use the friction-first productivity system builder?
Use this skill whenever someone is stuck in a loop of rebuilding or switching productivity systems, feels like they are the problem rather than the system, or wants to stop optimising their system and start actually working on the things that are in it.
// What do you need before you start building your system?
- Current system or app in userequired
Whatever productivity system, folder structure, or task manager the user is currently using (e.g. PARA, GTD, OmniFocus, Notion, Apple Reminders). If they have none, note that. - Known friction points
Specific moments where the user has to stop and think — e.g. 'I never know whether to file this in Projects or Areas' or 'I can't find files I saved last week'. Can be vague at first. - Mental model for organising life
How the user naturally thinks about their responsibilities — by life silo (personal/business/family), by active vs. inactive, by urgency, by context, etc. - Preferred starting approach
Whether the user wants to start from scratch or customise an existing system. If unsure, default to customising an existing system.
// What core principles drive the friction-first approach?
Systems Are Designed for Someone Else
Any published productivity system was designed by its creator for their needs. When it doesn't work for you, that doesn't mean you are the problem — it means the system wasn't designed for the way your brain works.
Working on the Things in Your System vs. Working on Your System
The goal of a productivity system is to spend time on the tasks inside it, not on maintaining, restructuring, or rebuilding the system itself. Rebuilding folders or re-tagging tasks feels productive but is not.
Friction as a Signal
Every time you have to stop and think 'Where should I save this?' or 'Where did I put that?', that is a friction point — a signal that your system is not yet aligned with your thinking. Friction points are diagnostic data, not personal failures.
Gradual Personalisation Over Big-Bang Overhauls
Instead of rebuilding everything based on a new method you read about, make small, targeted changes each time you encounter friction. Over weeks or months, the system converges on one that is specifically yours.
Natural Retrieval as the Success Metric
The system is working when you instinctively go to the right folder or the right project group without having to stop and reason about it. If finding or saving something feels natural, the system fits.
// How do you apply the friction-first system step by step?
- 1
Audit the current system for friction points
Ask the user to recall the last several times they paused while saving a file, searching for a file, adding a task, or deciding which project group something belonged to. List each friction point specifically. If the user has no current system, skip to Step 3 (Start From Scratch path).
- 2
Identify the underlying mental model mismatch
For each friction point, ask: 'Where did you expect that thing to live?' The gap between expectation and reality reveals how the user's brain naturally organises information. Common mismatches: thinking in life silos (personal/business/family) but using a system organised by status (active/inactive); thinking by topic but using a system organised by time. Name the mental model the user actually has.
- 3
Choose a starting path: Scratch or Customise
PATH A — Start From Scratch: Create folders, project groups, and tags only as needed, at the moment a new item doesn't fit anywhere existing. Let structure emerge from real use. Periodically group related folders under a parent folder as patterns appear. PATH B — Customise an Existing System: Take the existing structure and, friction point by friction point, adjust it toward the user's mental model. Recommended for anyone unsure where to start. Do NOT wholesale adopt a new system just because it sounds better in a video.
- 4
Redesign around the user's mental model, one friction point at a time
For each friction point identified in Step 1: state what the current structure expects the user to do, state what the user naturally expects, make the smallest structural change that resolves the mismatch (rename a folder, move a level up or down, split or merge a category). Example pattern from the creator: PARA's top-level 'Projects' mixed personal and business items, which conflicted with thinking in life silos — solution was to elevate the life-silo categories (personal, business, family) to top level and nest projects inside each.
- 5
Build and maintain a visual working model of the system
Create a diagram (mind map, outliner, plain-text outline — tool doesn't matter) that shows the current folder structure, tag taxonomy, and project group hierarchy. Keep this document live and updated whenever a tweak is made. This makes it easier to spot structural problems visually and drag-and-drop test new arrangements before committing to them in the actual system.
- 6
Run the Natural Retrieval test after each change
After implementing a change, the next several times the user needs to save or find something in that area, notice whether they go there instinctively or still have to pause. If still pausing, the change didn't fully resolve the mismatch — go back to Step 4. If retrieval feels natural, the change is validated.
- 7
Establish a no-overhaul rule going forward
When the user encounters a new productivity video, article, or system, instruct them NOT to restructure everything based on it. Instead, extract only the specific elements that address a current friction point. Chip away at what doesn't work; keep what does. The goal is to stop working on the system and start working on the things in the system.
// What does the friction-first method look like in real situations?
A freelance designer uses PARA but constantly hesitates whether client project files belong in 'Projects' or 'Areas', causing them to lose files and waste time searching.
Identify the friction point: the Projects/Areas boundary doesn't match how they think. Determine their mental model: they think in terms of client name first, then whether work is active or archived. Customise: elevate client names to top-level folders, then use subfolders for Active, Archive, and Assets inside each. Test natural retrieval: do they now go straight to the right folder? If yes, friction is resolved without rebuilding anything else.
A small business owner has tried GTD, PARA, and a custom Notion setup over three years, rebuilding from scratch each time and never finishing the migration before switching again.
Name the loop: they are working on their system rather than working on the things in their system. Stop the overhaul cycle. Take whichever system is most recent and do not migrate again. Instead, list three specific friction points in the current setup. Address only those three, using the smallest possible structural change for each. Commit to this system for at least two to three months, resolving friction points incrementally as they appear.
// What mistakes should you avoid when customizing your system?
- Rebuilding or restructuring the entire system every time you discover a new method — this is 'working on your system' instead of 'working on the things in your system' and is the core trap to avoid.
- Assuming you are the problem when a well-known system doesn't click — the system was designed for someone else's brain, not yours.
- Treating friction points as failures rather than diagnostic signals that tell you exactly what to change.
- Making big-bang changes to resolve friction instead of small, targeted adjustments — big changes introduce new friction points before the old ones are validated as fixed.
- Adopting a whole new system because one element of it sounds appealing — extract only the element that addresses a specific friction point instead.
- Never creating a visual working model of your system, making it hard to reason about structure and spot problems before they become embedded.
// What are the key terms in the friction-first framework?
- Friction point
- Any moment where you have to stop and consciously decide where to save something or where to look for something. Friction points signal a mismatch between the system's structure and your natural mental model.
- Working on the things in your system
- The desired state: using your productivity system to execute actual tasks and projects, rather than spending time maintaining, reorganising, or rebuilding the system itself.
- Working on your system
- The trap state: spending time restructuring folders, re-tagging tasks, migrating to new apps, or adopting new methods — activity that feels productive but produces no real output.
- Natural retrieval
- The success condition for any structural change: you instinctively navigate to the correct folder or project group without pausing to reason about it. When retrieval is natural, the system matches your mental model.
- Life silos
- The creator's term for top-level categories that map to distinct domains of life (e.g. personal, business, family). Used as an alternative organisational axis to status-based categories like active/inactive.
- Visual working model
- A diagram (mind map, outline, or similar) that represents the current state of your system's structure — folder hierarchy, tags, project groups — kept live and updated as the system evolves.
- Gradual personalisation
- The practice of making small, targeted adjustments to a system each time a friction point appears, allowing the system to converge on a design that fits your thinking over weeks or months, rather than through periodic full rebuilds.
- PARA
- An existing folder-organisation system with four top-level categories: Projects, Areas, Resources, and Archives. Used in this framework as a common starting point to customise from, not as a prescribed final structure.
// FREQUENTLY ASKED QUESTIONS
What is the friction-first productivity system?
The friction-first productivity system is a method for building a personal system by fixing the specific moments where you hesitate—like deciding where to save a file or search for one—rather than adopting a pre-built method. Each hesitation is a friction point that signals a mismatch between your system's structure and how your brain organizes information, and you resolve them one small change at a time.
What is a friction point in a productivity system?
A friction point is any moment where you have to stop and consciously decide where to save something or where to look for it. Friction points aren't personal failures—they're diagnostic data. Each one reveals exactly where your system's structure doesn't match your natural mental model, telling you precisely what to change.
How do I stop constantly switching productivity systems?
Stop migrating and commit to your most recent system for two to three months. List three specific friction points, then fix only those with the smallest possible structural change—renaming a folder, moving a level up, or merging categories. Rebuilding from scratch feels productive but is the trap; small targeted fixes converge on a system that's actually yours.
How do I customize a productivity system to fit how I think?
Audit the last several times you paused while saving, finding, or filing something. For each pause, ask where you expected that item to live—the gap reveals your true mental model. Then make the smallest change that closes that gap, and test whether you now navigate there instinctively. Repeat, one friction point at a time, over weeks.
How does the friction-first method compare to PARA or GTD?
PARA and GTD are complete systems designed by their creators for their own brains, so they prescribe a fixed structure. The friction-first method treats them as starting points to customize, not final answers. Instead of adopting a whole system because it sounds good, you extract only the elements that resolve a real friction point you're actually experiencing.
When should I use the friction-first system builder?
Use it whenever you're stuck rebuilding or switching productivity systems, feel like you're the problem rather than the system, or want to stop optimizing your setup and start doing the work inside it. It's ideal right after you catch yourself hesitating over where to file something or losing files you saved recently.
What results can I expect from the friction-first approach?
You'll reach a state of natural retrieval—instinctively going to the right folder or project group without pausing to reason about it. Over weeks or months of small fixes, your system converges on one specifically shaped to your thinking. Most importantly, you stop spending time maintaining the system and start spending it on the tasks inside it.
Why does every productivity system I try eventually fail?
Because every published system was designed by its creator for their own needs and their own brain. When it doesn't click for you, that's not a personal failure—it means the system wasn't built for the way you think. The fix isn't finding a better system; it's customizing one to your own mental model.
What's the difference between working on your system and working in it?
Working on your system means restructuring folders, re-tagging tasks, migrating apps, or adopting new methods—activity that feels productive but produces no real output. Working on the things in your system means using it to execute actual tasks and projects. The entire goal of the friction-first method is to shift you from the former to the latter.
How do I know when my productivity system is actually working?
Your system works when retrieval feels natural—you instinctively navigate to the correct folder or project group without stopping to reason about it. If saving or finding something still makes you pause, the mismatch isn't fully resolved and you need one more small change in that area. Natural retrieval is the single success metric.