He knows a lot more about naming than me! I guess the main distinction is that he's talking about brands and my piece is about the products within a brand which maybe don't need that level of process? (It sounds great but expensive!)
Interesting read. Totally relate with the 'test and iterate' bit, with all your stakeholders. Recently I also read another pov on naming, albeit on a brand level. David Placek, who's responsible for the Intel's "Pentium" name, has a "Diamond Framework" that he recommends. Curious to know your thoughts on that.
Then there is the I'm a "one-person marketing team" process, which is suspiciously similar to how a garage band finds its name.
It usually involves a high caffeine induced "what if I just called it..." moment at 11 PM, which everyone agrees is a joke until it accidentally gets put on the website and is now the official name forever.
Love the article - Num 2 is my favorite! I think products should follow the JTBD framework throughout their product dev starting with the name. A clear name that immediately tells the user what this product is all about like linked, lift, and doulingo - no further explanation needed.
He knows a lot more about naming than me! I guess the main distinction is that he's talking about brands and my piece is about the products within a brand which maybe don't need that level of process? (It sounds great but expensive!)
Interesting read. Totally relate with the 'test and iterate' bit, with all your stakeholders. Recently I also read another pov on naming, albeit on a brand level. David Placek, who's responsible for the Intel's "Pentium" name, has a "Diamond Framework" that he recommends. Curious to know your thoughts on that.
This will help me a lot!
Then there is the I'm a "one-person marketing team" process, which is suspiciously similar to how a garage band finds its name.
It usually involves a high caffeine induced "what if I just called it..." moment at 11 PM, which everyone agrees is a joke until it accidentally gets put on the website and is now the official name forever.
Love the guide on how teams should do it!
Love the article - Num 2 is my favorite! I think products should follow the JTBD framework throughout their product dev starting with the name. A clear name that immediately tells the user what this product is all about like linked, lift, and doulingo - no further explanation needed.
Totally!! Glad it resonated, Yael!