Stephen Todd.
I'm Stephen. I build with AI, write about the work, and help small teams get things done without getting buried in process.
I spent a decade leading projects and operations, mostly in environments where things were messy and time mattered.
That experience shapes how I build now. Keep things simple. Focus on what actually moves things forward.
What I’ve learned the hard way
- More tools makes things worse, not better
Every new tool adds an edge. Five tools is ten edges. The team spends more time moving work between tools than doing the work.
- If no one owns the system, it breaks
Workflows do not maintain themselves. Someone has to be responsible for how work moves, or the process quietly goes back to whatever is easiest in the moment.
- Documentation is part of delivery, not an afterthought
A system the team cannot explain is a system that will not survive the next hire, the next reorg, or a week off.
- The team in the work knows more than the deck says
The people doing the work have seen the failure modes. Ask them first. Most plans improve within an hour of talking to whoever handles it now.
How I think about the work
- Keep it simple
If it takes a diagram to explain, it probably needs cutting down.
- Clarity is a deliverable
If the team can’t explain it in a sentence, the doc isn’t finished.
- Ship, then sharpen
Real feedback beats imagined feedback. Every time.
- Operators build the best products
Because they’ve lived with the failure modes.
Say hello
If you're building something interesting, working through a messy operational problem, or want to compare notes on small teams and AI, I'd like to hear about it.