Welcome to MSDN Blogs Sign in | Join | Help

Teched Developer Europe 2007

Would you believe it planning has already started for this years TechEd Europe.  As I am running the technical content strategy this year I would like to ask you folks for your opinions.  I would like to devise a category scheme to help you navigate your way around the sessions at TechEd.  So I really need your feedback on these questions.

Now some of you will plan your whole week using the online tool and get a personal printout.  Others (like me) will look through the schedule in the morning or during a session and figure out where to go next.  The schedule is a small cramped piece of paper which anyone in the 40's will need to use reading glasses to read.  I would like your feedback on how you navigate the conference, and what's good and what stinks.

Firstly the DEV track.   I wonder if there is any point in having a DEV track at a developers conference.  I looked at last years numbers and found that out of about 200 sessions 130 were DEVxxx in other words 65%.  So what do you think about scrapping that designation?  Instead DEV would be implied for everything and we would have more track names like this:

BPI
Mobile
Tools and Languages 
Web
Windows  (Frameworks and Base Platform)
Architecture
Dynamics
SQL
Office

 Now of course some sessions cover more than one thing, such as a session on Orcas and WPF. For this I would suggest a primary category and a secondary category.

Traditionally we have used a number scheme based on courses in North American universities, so we have level 200, 300 and 400 sessions that give you various degrees of credit.  We are not North Americans so how about we scrap that too?  We would use another scheme to show depth or breadth of a session.  Perhaps we could use European ski run designations, Blue, Red, Black each with a different shape so you can see it quickly in the black and white printout. 

Therefore the session number becomes just like a primary key in a table, of less interest except when filling in your online eval forms.

It would look like this:

teched tracks

 Another question is about accessibility.  For those of us ageing rockers or those with visual impairments would you like to be able to get a printout of sessions in larger point sizes?

 

Ok please let me have your input.  Don't forget that this is not a discussion about content yet, my team will be working as hard as ever to bring you the Best Developer Conference in the world!
.


.

Published Friday, March 16, 2007 10:20 AM by davewebster

Comments

Friday, March 16, 2007 8:13 AM by DanielMoth

# re: Teched Developer Europe 2007

Very brave thoughts to break away from what has become an international standard at conferences... It could work though :)

I'd suggest a column for % of time spent on slides vs demos.

Also, we need some way (dunno how) to make attendees read abstracts! 80% of us that attend sessions have not read the abstract and instead make the decision based on level/title/track - that strikes me as just plain wrong!

Friday, March 16, 2007 9:28 AM by davewebster

# re: Teched Developer Europe 2007

Yes it might be helpful to see the demo/slide split I just dont want to over engineer this thing.  What I want is to make the decision process easier and more accurate so we don't have people going into the wrong sessions.  

One of the reasons that sessions score badly is that expectations are not set properly and people are dissapointed.  So yes, reading the abstract would help but I can't change behaviour without having an incentive. Perhaps we have a hidden clue in an abstract for a prize...

Friday, March 16, 2007 10:40 AM by Daniel Moth

# Do you read abstracts of sessions?

Do you read abstracts of sessions?

Friday, March 16, 2007 2:10 PM by Dave Sussman

# re: Teched Developer Europe 2007

Accurate abstracts would be really good, but you'll probably find speakers think they are already submitting accurate ones. You're right though, many people just look at the title, which is after all, the hook. Trying to get the title and abstract matching the session more would help.

The skiing thing doesn't work for me - I don't ski, so don't know what the runs are. I get the black think, but partly because it has the "black-belt" association, but the other colours are meaningless. Why not just use Beginner/Intermediate/Advanced?

I like the idea of finer grained track names though.

Friday, March 16, 2007 7:13 PM by Arnaud Weil

# re: Teched Developer Europe 2007

Those are definitely good ideas. A main category, a subcategory and a colored symbol, that's very neat!

Well, in France we also have green which means ski slopes for begineers, but if it isn't used in other countries I won't insist... ;-)

Now, I apologize for getting (relatively) out of the subject, but I'd love to be part of the TechEd speakers. Whom can I contact about that?

Best regards,

Arnaud

Tuesday, March 20, 2007 6:00 AM by davewebster

# re: Teched Developer Europe 2007

Thanks Dave.  I am still not sure of the best way to go here.  I want to make sure that fewer people are dissapointed by the session because they did not know what to expect.  I just think that there has to be a better way to do it.

I have trouble with the Beginner/Intermediate/Advanced labels too. (Even though the skiing analogy was just that).  I mean why is a deep dive into something obscure in SQL server more 'advanced' than something else?  As your career develops why would you get so much more specialized? I would rather describe it as breadth and depth.

Nothing at Teched should be a soft option.

Tuesday, March 20, 2007 6:03 AM by davewebster

# re: Teched Developer Europe 2007

Thanks for your comment Arnaud.  As for the difficulty rating, I would want to preserve the 3 levels. At present no one delivers a 100 level presentation at Teched so a green would not draw much attention.

We will be calling for content pretty soon.  Send me an email if you have something that you particularly care about.

Dave

New Comments to this post are disabled
 
Page view tracker