







A crash introduction on the DO System — the system we use to get stuff done at Doist.We have been iterating on it for many years, and it helps us plan and execute work better. We would love to fully open this at some point, as it's a critical element lacking in many teams and… pic.twitter.com/iIO2WGOOxR— Amir Salihefendić (@amix3k) January 4, 2024
Hundreds of Ways to Get S#!+ Done—and We Still Don’t
You want to be productive. Software wants to help. But even with a glut of tools claiming to make us all into taskmasters, we almost never master our tasks.

Declaring Systems Bankruptcy
For years and years, I’ve helped teams evaluate their systems, fix their systems, tweak their systems, and evolve their systems. And sometimes it’s even been necessary to help teams declare bankruptcy on their systems, blow them up, and start anew. And now it’s my turn. It started as a slow re

How finishing what you start makes teams more productive and predictable
Hot takes and cold truths on software, startups, and the lies we tell ourselves.
Solving a Million-Step LLM Task with Zero Errors
LLMs have achieved remarkable breakthroughs in reasoning, insights, and tool use, but chaining these abilities into extended processes at the scale of those routinely executed by humans,...

Agents Done Right: A Framework Vision for 2026
Agents choke on context, loop on failures, and dump walls of code for review. It's time to rethink the architecture.

henrythe9th/AI-Crash-Course
AI Crash Course to help busy builders catch up to the public frontier of AI research in 2 weeks
Breaking Ground
Hello, everyone! It's been a while since our last update, so we wanted to catch you up on some of the early work we've been doing behind the scenes to set up the organization and what's coming up soon. Building the Organization Turns out, setting up a

Beginner’s Guide to GTD (Getting Things Done)
Ship working code while you sleep with the Ralph Wiggum technique
Raising An Agent Episode - Episode 10
A Local-First Task Planner On ATProto - tyler's blog
Just-In-Time PM #12: Just-In-Case to Just-In-Time - Forte Labs
In Part 11, I introduced the concept of a “critical path” of tasks in a project, and the rationale for pushing tasks as late as possible on the timeline. The late starts approach inspires a tremendous amount of resistance, especially from creative knowledge workers. It sounds an awful lot like taking control from individual employees, centralizing it in a central decision maker, and forcing people to finish everything at breakneck speed at the last minute.

Bobby Grayson - Deciduous
Redundancy Protects Human Collaborations from Failure
In the name of efficiency, organizations and governments around the world are increasingly trimming redundancy---personnel or overlapping capabilities beyond what routine operations require. Drawing on distributed computing and cognitive science, we challenge this view. Using queueing simulations and a preregistered multiplayer experiment (N = 832 in 187 teams of 3–6), we show that redundancy improves performance through two distinct routes. Adding collaborators to a team improves resilience, with larger teams completing more tasks when members became temporarily unable to contribute. Giving team members overlapping capabilities also improved efficiency, with teams in which collaborators could perform multiple roles completing substantially more work. These findings suggest that efforts to improve short-term efficiency by reducing redundancy may come at a cost, quietly eroding a team’s capacity to withstand unexpected failures.
Stop Begging Billionaires To Fix Software — Build Your Own
This is part one of a two-part series on using AI tools as one piece to fight back against tech company control of our lives. Part two shares the details of how I built my own task management tool …
