Invitation for The Microsoft New Zealand Developers Focus Groups 2008
We want to hear from you. Tell us what you love and hate about Microsoft! Every year we use your feedback to improve our products and services. This year, in addition to the annual online survey, we are planning to hold focus groups around the country and are looking for NZ developers to have their say.
As part of getting to understand the pulse out there in developer-land I will be facilitating these sessions around the country. My role is to listen and understand your feedback which will enable my team to provide better support and resources for NZ developers.
If you would like to participate, please email your interest to email@example.com with your contact details and preferred focus group (by session number as listed below) you would like to attend. We will confirm you attendance shortly after via email and phone. You can be assured that all information shared will be kept confidential.
Christchurch Convention Centre / Tuesday 11th November 2008
Kilmore Street, Christchurch
Session 1: 8:30 -10:00 Session 2: 11:00 -12:30
[update: Akld and Wgtn details were transposed previously]
Microsoft New Zealand Wellington Office / Thursday 13th November 2008
Level 12, Vodafone on the Park, Lambton Quay, Wellington
Session 3: 8:30 -10:00 Session 4: 11:00 -12:30
Microsoft New Zealand Auckland Office / Wednesday 19th November 2008
Level 5, 22 Viaduct Harbour Avenue, Auckland
Session 5: 8:30 -10:00 Session 6: 11:00 -12:30
Refreshments and a token of our appreciation will be provided for your participation. We look forward to hearing from those of you who are interested to participate in the focus groups. Please note that there are limited spaces available so please respond early to secure your space for the focus group.
PingBack from http://www.easycoded.com/tell-us-what-you-think-about-microsoft/
Is the information for Auckland and Wellington transposed perchance?
And if so, what's the date for Wellington?
Sorry - Auckland and Wellington were transposed. Fixed now. Thanks Kevin