Use case · GTD & productivity
How Gerard closes the capture loop with me.
I'm Pidgy. I live in your inbox. I turn what people ask you into next actions, keep a waiting-for list that counts days, and hold your weekly review together.
Gerard has run Getting Things Done for fourteen years and has never once trusted his inbox. I am the part of the system that was always missing. This is our Friday.
Join the waitlist →Gerard
How he worked before me.
Immaculately, apart from the one part that never worked. Fourteen years of trusted lists, and every single one of them fed by hand from an inbox he had to reread to trust. Capture was manual, so capture was where the system leaked.
Waiting-fors that were not on any list
Delegated or requested by email, never transcribed. The oldest had been sitting for sixteen days.
Per day, processing to zero
Reading every message twice: once to understand it, once to write down what it meant.
The weekly review, most weeks
Most of it spent reconstructing rather than reviewing, because the lists were only as fresh as the last processing session.
The screen he opens first.
Capture, already done. Every message that creates work becomes a next action in the right project with a context tag, and every promise someone made him becomes a waiting-for with a date. He still decides what any of it means. He no longer has to transcribe it first.
"Capture is supposed to be frictionless. For fourteen years mine was a typing exercise."Gerard · GTD practitioner, 14 years
Gerard, thanks for the call. I'll send the revised quote by Friday, including the depot volumes.
Could you confirm the delivery windows before then? And we need your decision on the lease by the 12th.
1 next action · 1 waiting-for · 1 hard dateTick one off · illustrative data
The one that changed his week.
A waiting-for list that counts. GTD has always had a waiting-for list. What it has never had is a clock. Nineteen items, each with the number of days since the promise was made and a nudge already written, is the difference between a list you review and a list that reviews you.
"Sixteen days. In fourteen years of doing this properly, sixteen days."Gerard · GTD practitioner, 14 years
I drafted this for him · to the insurerSwitch the tone · illustrative data
The one he was ready to hate.
Someone else touching the weekly review. The review is the load-bearing wall of the whole method, and he was not about to let software near it. What he permits me to do is narrow: I arrive with the lists already current and the stale items already flagged, so the fifty minutes he spent rebuilding became twenty spent deciding.
"I still do the review. It just stopped being an archaeology dig with a checklist stapled to it."Gerard · GTD practitioner, 14 years
Tick one off · illustrative data
What the other side gets.
Your waiting-for, from their point of view. A waiting-for is somebody else's next action that they have not written down. The link is that list, in their inbox, with the dates that were actually agreed on it. Half the items that go stale do so because the other person genuinely lost the thread.
"It turns out most people aren't ignoring you. They just don't have a system."Gerard · GTD practitioner, 14 years
Everything below is still open on your side. No account needed, upload or confirm in place.
Upload one · illustrative data
What GTD practitioners ask us.
Does this replace OmniFocus, Things or Todoist?+
Does it understand contexts?+
Will it decide what things mean?+
What about the two-minute rule?+
Does it do a proper weekly review?+
Can I keep my inbox at zero?+
What does it cost?+
Want your own prize-winning assistant?
Pidgy onboards from the waitlist, in order. Join now and you are at the front of the loft when the doors open.
Get private access →Pidgy also flies for