Giulianno Vollmer

Automation demos end at the click. Real operations begin when the click partially succeeds.

If an agent creates a record, sends a request, updates permissions, or starts a job and then loses context, who owns the next step? A human needs an exact action log, current external state, safe retry behavior, and a clear answer to whether repeating the action will duplicate anything.

Agent failed is not a handoff.

What information would you need before taking over a failed automated task?

Retention dashboards usually tell us who came back. They rarely tell us whether the product helped someone return after falling behind.

For learning, fitness, finance, and any habit-shaped product, recovery deserves its own measurement: time from interruption to meaningful return, the smallest successful comeback action, and whether the product reduces guilt or adds to it.

A system that only works for perfect streaks is optimized for the users who need it least.

What does a good recovery path look like in your product?

Launch retrospectives often become traffic summaries: rank, views, signups, comments. Useful, but none of those says what the team learned.

I think every postmortem should name one belief the launch disproved. Maybe the audience misunderstood the promise, setup friction mattered more than price, or the users who converted were not the segment you expected.

If nothing could have changed your mind, the launch was distribution, not an experiment.

What belief did your last launch force you to update?