Scar
#HarveyDent
Hey guys, I started a blog about Lean Melee, I figure since people probably won't be leaving comments on the blog itself, we can use this forum to discuss and refine the ideas that are being put forth.
Pipeline
"Small batch sizes" and the "MVP" (Minimum Viable Product)
The example post showed going through a full feedback loop. The timeline of the entire story was about 10 hours. I thought about what the problem was on the train home, called Tafokints and Darrell and asked them to come over, and started tracking right away. I didn't need to play the best players in the region, I didn't need to make any elaborate plan for how to start focusing, I just needed to start collecting data, and it worked. It's possible that other things would have worked too, but this was real improvement in a few hours. Lean works best when you invest the minimum amount to find out if you're on the right track.
Skill Pyramid and the value of a strong foundation
I believe that skill in competitive gaming is a hierarchy, and results come from building up from a strong foundation. The pyramid as I see it is this:
0: Focus and Tech
1: Strategy and Creativity
2: Adaptation
I'll talk about how I think they work together, and how each level supports the one on top of it. This is going to be subject to a lot of discussion, because it's speculation on my part. I expect that we should discuss the different aspects of "skill" and figure out how they should be set up as a general rule.
Lean as a framework
I think I'd do well to make a post explaining that Lean is a framework built to efficiently diagnose major problems and fix them. Lean is not a way to start winning a few more games quickly, it requires discipline and a good bit of work. This post will be about my idea of how to use lean effectively, and again should be open to discussion as more people start dabbling with the framework.
Q&A
I've received a few questions and comments through PM or through my thread, so I'd like to make posts here and there responding to questions.
Pipeline
"Small batch sizes" and the "MVP" (Minimum Viable Product)
The example post showed going through a full feedback loop. The timeline of the entire story was about 10 hours. I thought about what the problem was on the train home, called Tafokints and Darrell and asked them to come over, and started tracking right away. I didn't need to play the best players in the region, I didn't need to make any elaborate plan for how to start focusing, I just needed to start collecting data, and it worked. It's possible that other things would have worked too, but this was real improvement in a few hours. Lean works best when you invest the minimum amount to find out if you're on the right track.
Skill Pyramid and the value of a strong foundation
I believe that skill in competitive gaming is a hierarchy, and results come from building up from a strong foundation. The pyramid as I see it is this:
0: Focus and Tech
1: Strategy and Creativity
2: Adaptation
I'll talk about how I think they work together, and how each level supports the one on top of it. This is going to be subject to a lot of discussion, because it's speculation on my part. I expect that we should discuss the different aspects of "skill" and figure out how they should be set up as a general rule.
Lean as a framework
I think I'd do well to make a post explaining that Lean is a framework built to efficiently diagnose major problems and fix them. Lean is not a way to start winning a few more games quickly, it requires discipline and a good bit of work. This post will be about my idea of how to use lean effectively, and again should be open to discussion as more people start dabbling with the framework.
Q&A
I've received a few questions and comments through PM or through my thread, so I'd like to make posts here and there responding to questions.