how to make a method notes:
---
##
**Method Development Life Cycle – Summary**
**By James Straughan**
###
Introduction
Method development in cubing is the process of creating a solving method that fits human limitations. Since humans can’t memorize and instantly apply a solution to all 43 quintillion cube states, we must develop practical strategies that balance:
* **Move count**
* **Recognition**
* **Ergonomics**
* **Algorithm load**
Creating a new, competitive method takes experience and deep understanding—not just fast solving. This guide walks you through all stages of method development.
---
###
1. Ideation
Every method starts with an idea. It might be:
* A new **method shape**
* A way to solve an existing **problem**
* A combination of steps from known methods (though this rarely succeeds on its own)
To make something truly new:
* **Don’t just change the order of solving pieces.**
* Try solving core problems or inventing **new concepts** (e.g. *Method 42* uses conjugation to reduce algorithm count).
Before continuing, **research** if your idea already exists:
* **SpeedSolving.com** (Wiki + forums)
* **Cubing History**
* **Discord servers** for method discussion
Watch out for commonly reinvented methods like:
* **Belt**
* **RouxFOP**
* **ZBRoux**
* **Non-EO Petrus**
---
###
2. Design
Now define the **step-by-step plan** of your method. Test many options:
* Can you borrow useful steps from other methods?
* Try multiple variants of solving edges, corners, etc.
* Ensure steps logically flow from your base idea or problem you're solving.
Design isn’t just building from scratch—it’s exploring *every possible path*, even abstract or unusual ones.
---
###
3. Analysis
This phase tests the potential of your method:
* **Measure efficiency**: average move count, lookahead, ergonomics.
* **Compare** with current top methods.
* **Identify weaknesses**, like difficult recognition or poor transitions between steps.
Try hand-solving with your method and gather initial impressions. Early testing helps refine your step choices and prepares for deeper development.
---
###
4. Development
Build out your method:
* Create and refine **algorithms** for each step.
* Develop **multiple options** for different cases (e.g. alternate algs for one-handed use).
* Test **intensively**: time solves, collect feedback, analyze move counts.
If a step feels awkward or inefficient, return to design or even ideation. Be flexible—methods evolve as you work on them.
---
###
5. Publication
When your method is solid:
* **Document it** clearly: write a tutorial, create example solves.
* Share it via forums, Discord, videos, or cubing websites.
* Choose a name (avoid duplicates), and make your method easy to learn.
Good documentation helps others try it and give feedback—which could improve it even more.
---
###
6. Maintenance
Once published, maintain the method:
* **Update algs** if better ones are found.
* Answer questions and improve tutorials.
* Track community feedback and adjust accordingly.
Some methods fade away due to lack of support. Others become popular because their creators engage and keep refining.
---
###
7. The Future of Methods
There’s still room for innovation. New hardware, solving styles (like OH or feet), or even twisty puzzle types can inspire new methods. Focus on **problem-solving and creativity**, not just move-count optimization.
>
“Any method distinguishable from magic is insufficiently advanced.” — Joseph Briggs
-
i asked chatgpt to summarize it so that i can focus on making a method and not writing down notes lol
