@dan rathbun said:
One thing you guys lack.. is a "Yearbook" or "Meet the Team" page.
It's true that we haven't got one of those, but I don't know of any other team at Google that does, aside from executive management, for whom such bios are required by the SEC. I do understand people's desire to learn more about the team, however.
@dan rathbun said:
This is the first time I've ever seen anything resembling a list.. before your post we had to guess how many peple are even on the team. 5 , 10, 20?
It's obviously a matter of how one defines "team", but I hope that the comments at 3D Basecamp by John Bacus (SketchUp PM) and John Hanke (a Google VP) about the size of the SketchUp team are taken to heart. We've always been a fairly small team, which didn't change when @Last was purchased by Google (I believe it's one of our strengths). This is of course inconsistent with the expectation of the numerous folks who believe that an army of Google employees is (or should be) brought to bear on the development of SketchUp.
@dan rathbun said:
If users see and know how many there are, and who's who, and who is responsible for what, we won't have silly speculation.
I'm unconvinced! In my mind, there's nothing whatsoever that we can do to put an end to 'silly speculation'. Each bit of news we reveal only removes one drop from an infinite sea of speculation waiting to be splashed around. Of course, having a yearbook would only serve to feed more speculation with the news of every change, which would ultimately defeat the purpose which one would hope for it to achieve.
For those in the SketchUcation community who were able to join us at 3D Basecamp, I hope the experiences shared by members of the SketchUp team served to underscore the very personal and deep commitment each of us has to the product. There's nothing any of us can say that would be more convincing than the way we conveyed our excitement and passion for SketchUp while telling our real life stories over some of our favorite brews.
I hope it was also useful for the attendees to get a glimpse into what an extraordinarily difficult undertaking it is to determine how to balance the many competing factors that arise during release planning (including limited staff and time, infinite wish list items, complexity of certain changes/features, everybody's personal pet peeves, ever-changing market conditions, and consideration of the varied needs of the mind-boggling number of people who use our product every day).
I don't expect this to end any speculation, but hopefully it'll shift the focus.
Andrew