12 December 2014
Flexibility is a key part of Mingle’s design. Because Mingle uses a generic card concept, “ideas” can be created, arranged, and broken down into smaller pieces pretty much however you want. We use Mingle for new product development and have found other tools and techniques to be useful as well. Here are some examples of how we use Mingle (in combination with other techniques) that might help you understand more about how you can use it to hash out your product ideas.
Mingle card trees allow you to define a hierarchy of parent-child relationships between any card types. For example, you can create “idea” parent cards and “solution” children cards to foster product development. Or make high level features ideas that are then broken into smaller stories.
We often use lean startup methods and our team has used Mingle to capture high-level product ideas, our assumptions, and our experiments.
For example, in the Mingle board below, the rows are assumptions that we want to test, and the cards are the experiments that will test the assumptions. The whole project represented the product idea and we used wiki pages and cards to capture other details about the ideas.
We also often map out our ideas using user activities or goals as a high-level concept and then break them down into smaller pieces with details. You can use this technique at any stage of a product lifecycle to better understand potential users and detail their needs. You can read more about using this technique in Mingle on our blog.
I hope that this helps give you some idea of the different types of activities you can do in Mingle that support new product development. Mingle can be configured to complement pretty much any workflow, so hopefully you will have fun experimenting with it and making it work for you and your team.