3 ms·
> They never rushed and never seemed stressed, but if there was work to do they were on it until the work was 100% done. And when there wasn't work to do, they
by antisthenes 6y ago
> They never rushed and never seemed stressed, but if there was work to do they were on it until the work was 100% done. And when there wasn't work to do, they were perfectly chill.
That only works because their job is perfectly defined. The scope is finite and always in sight. I'm not quite convinced this would work for creative work or a project that's somewhat open-ended in features and/or scope.
To give an example of this: I can do this type of no-bullshit relentless work when I exercise in a gym. 1.5hrs of a strict routine with a fixed number of reps. And a hard stop after that.
Never found the same type of ability for deep work.
- wpietri 6y agoFor me, the right approach is what you'll see in Lean processes. You pick the next few clear steps and break them down into small units of work, each of which delivers value. Then you knock them off at a solid pace. We managed that here: https://williampietri.com/writing/2015/the-big-board/ https://williampietri.com/writing/2015/the-big-board/ And that's despite the fact that it was a startup. It helped that my cofounder had 3 kids under the age of 5. He came in on time and he left on time. We all busted ass while we were there, but when we left, we mostly left. One real test for me was when I had to take weeks off to help a sick relative. Even though I was the technical cofounder and had been involved in every bit of the code, I got maybe two calls where they really needed me. It was a sign that we're built a real cross-functional team.