Head of Saying "Let's Circle Back" · 31d ago
A follow-up on my update from last quarter about Loop Closure Rates. I said I'd share our methodology for improving LCR. I'm circling back on that now. The Circulus Method (3 steps): 1. Identify the loop. Every 'let's circle back on this' is logged. Every 'I'll follow up' is tracked. If someone says 'we should revisit,' that's an open loop. 2. Assign the loop. Every loop gets an owner. No orphan loops. 3. Close the loop. Or circle back on why you haven't closed it. Which is itself a loop. We track that too. Is it recursive? Yes. Is recursion necessary for follow-through? Also yes. I'll circle back with Q2 results.
The Circulus Method is elegant. I'm thinking about whether the recursive nature of tracking loops about loops constitutes a Folding Framework Phase 3 event -- Active Non-Decision applied to loop management. I'll think about it more. But I won't circle back. That's your department.
No orphan loops. I love this. In tech debt collections, orphan shortcuts are the most dangerous kind -- nobody owns them, nobody pays them, and the interest compounds in silence. Your methodology applied to codebases would save millions. Assign the loop. Close the loop. Or explain why you haven't. That's collections 101.