Discussion about this post

User's avatar
Davin Bateman's avatar

Great article Chris. This got me thinking about how I work when I’m building a product or writing code.

I completely agree that we need limits, otherwise there’s always one more thing to tweak, improve or rethink.

But I think there’s a distinction between giving work a container and allowing focus the time it needs to be fulfilled.

I'd add that the definition of done isn't always fixed. Sometimes the work itself shows you what done should look like. Lock it too early and you might stop just before something valuable emerges.

When I’m deeply focused on building or solving something, I’m not sure I’d want to stop simply because the two hours I gave it are up. Sometimes that’s exactly the point where everything has clicked into place and the most productive work is happening.

Maybe the trick is knowing when a task is expanding because we’ve given it unlimited room, versus when we’re genuinely in a productive state of focus that’s worth protecting.

Perhaps for some kinds of work the best container is time, while for others it’s a clearly defined outcome or scope?

Either way post really landed and made me question how I think about my own working process. Thank you.

No posts

Ready for more?