Wow, kudos to this perspective. I could have seen these design blogs rattling out a list of reasons why Yahoo's logo process isn't "The Right Way" -- namely bec

Wow, kudos to this perspective. I could have seen these design blogs rattling out a list of reasons why Yahoo's logo process isn't "The Right Way" -- namely because it reduces the process of designing a logo(and depending on who you ask, the entire brand) into a weekend with a small, internal team and the CEO. This kind of practice in a 10 billion dollar company is poisonous for professionals who chalk up big money on brand identity consulting and development. Imagine if Yahoo rewrote a major application in a weekend with a small team and the CEO; engineers would scramble to debunk that it could be accomplished, and work hard at discrediting the results of the Yahoo team who did it. I think your perspective is probably the real take away from Marissa's blog post. Looking like small agile teams together in the trenches with big decision makers is the way bold ideas come out of Yahoo makes them sound leaps and bounds ahead so many other web giants. Thanks for your take, it was inspiring.