Task management, time-blocking and productive habits with Josh Duffney (Logseq & Dendron)

Task management and knowledge work land in two different places depending on how a person structures hierarchy: Josh Duffney’s approach in Dendron leans “hierarchy first” (namespaces that behave like software packages), while his Logseq workflow keeps a “journal-first” fluid graph and then layers time-blocking, staging, and retrieval on top. The practical takeaway is that both systems can work—but the mental model behind them determines whether planning stays stable as responsibilities grow.

Duffney draws a sharp contrast between Dendron and Logseq. In Dendron, notes live inside an intentional namespace tree (e.g., area.discipline → folder-like levels), with tab completion and a refactor-style hierarchy that can rename and reorganize without breaking the overall structure. That mirrors how developers browse code: packages contain functions, and knowledge is navigated the same way. He describes this as a systems-driven design shaped by years managing computer systems—he doesn’t just write a note about something; he creates a place for it, then lets the hierarchy evolve as understanding deepens.

Logseq, by comparison, is presented as more flexible and “gardening”-oriented: journal notes act like scratch pads, then links and collections assemble them into usable views. Duffney emphasizes that this fluidity helps him keep momentum and avoid the friction that can come from rigid upfront structuring. He also notes a practical tool-lifecycle habit: he tends to trial tools for about six months, then experiments again once the system “explodes” into unmanageable complexity.

On task management, Duffney’s core method is time blocking with time boxing across three daily realms: personal life (husband/father and health), a creative manuscript project, and full-time work (shifting from Microsoft technical writing to a cloud advocacy role). He uses weekly staging (“week ahead”) to place tasks onto future days without planning every detail the night before. Then, each morning, he plans at the start of work—staged tasks become the day’s execution plan, while deadlines and projects anchor the schedule.

For deeper control, he uses Logseq templates and varying resolution: a weekly snapshot for overview, then templates for morning and afternoon grids when interruptions or encroachment require hour-by-hour precision. He also follows a “maker vs manager” split (deep work vs meetings/shallow tasks) and uses session timers to block distractions like Twitter and Outlook during maker blocks. A shutdown ritual—capturing loops and staging tomorrow’s work—functions as a daily off-ramp.

Duffney’s knowledge-management philosophy ties into feedback mechanisms: note systems can become “black holes,” so he relies on reverse-chronological retrieval, tags for reliable re-entry, and a Logseq Random Note plugin to surface neglected pages for cleanup. He also discusses the PARA method (projects, areas, resources, archive) as a way to separate life domains digitally and prevent overwhelm—especially by archiving completed creative work so it doesn’t clutter active decision-making.

Finally, the conversation highlights an integration challenge: automating task handoffs across tools requires workflow orchestration and shared standards (APIs, formats, and clear handover steps), not just early automation. Duffney’s approach keeps the “process” legible first, then considers automation once the handoff logic is clear.