https://share.transistor.fm/s/90c660ca
Hey Indie Hackers!
I checked one off my bucket list this week when I got to sit down with Ryan Singer of Basecamp to talk about that new book we've all been reading :)
Link to the ep is up above, and here are my big takeaways as well:
Constraints change the definition of value, of "good" and "bad." Steak and hot dogs are both "good" choices for dinner depending on constraints.
Allow your constraints/appetite to drive design. Instead of allowing the design to define how much time to give it.
Allow your appetite for a project ("Let's give this two weeks") to establish a floor for betting on projects.
The specifics (6-week cycles) are context and scale-dependent. Don't be dogmatic.
"Are we regularly shipping what we bet on?" is the primary question teams & leaders should be asking themselves to assess the health of their process.
That isn't a quantifiable approach & may not work for some.
It requires a high degree of trust.
Trust from leadership that ppl do their best work if given a balance between guidance and latitude.
Trust from the team that leadership is acting in good faith.
People who read the book and think, "Shape Up would never work for us" are probably right.
Anyone else read it? Thoughts?!