Share via


Why hire an IEvangelist

More great comments are coming in about this position.

Why do I think we need an Evangelist?  It’s because we need someone whose full time job is to focus on making sure the community understands what IE is about, what it offers, and responds to feedback.  I’m not looking for someone who will don a blindfold and ear plugs and just shout “IE 7! IE 7!" all day long.  I want someone who can look at everything the product team is building, figure out the value (and yes, the drawbacks where there are any) for developers, and then talk about that with the community.  Call it ICommunityOutreach, or ISharerOfInformationForIEDevelopers if the word "evangelist" is what's getting you tied up here.  You can put whatever you want on your business card :)

 

Should a great product speak for itself?  Sure.  But it doesn’t always work that way.  XMLHTTP didn’t speak for itself in 2000 when we first invented it, but now with just a little help from Google it’s spun into this great excitement around AJAX experiences.  Tivo is so stunning that it (or at least some other similar PVR) ought to be in every home in the universe by now, but I'm told their uptake rate is slow because too many still don't actually get what it is.  They need an evangelist!

 

Sometimes it takes one person dedicated to community outreach to help the product teams keep their focus on what’s important:

To be fair, the IE team’s assignment is to build a great product that has the right mix of features for end-users, IT pros, web devs, and e-commerce sites, and ship it with high quality and security.  The IEvangelist’s assignment, on the other hand, is all about taking it to the community.  Do I hope the IE team steps up and blogs more about the topics that you all care about?  Oh yes, and I sent a copy of Jim’s comments to their leadership team just now (and in fact their product unit manager already responded to me ;)  But I can guarantee you that the IEvangelist on my team will be reviewed on how well he or she blogs and responds in a relevant way to community feedback.

 

Do I expect the IEvangelist to somehow force the IE team into implementing every idea that gets a lot of votes from the community?  No.  But I certainly expect this person to be able to explain, in every case, how the feedback was considered by the team and why a decision went a particular way.

 

Dwain totally gets what I’m thinking about for this position, and in fact he says it more articulately that I have, I think.

Let's keep the conversation going, I'm really enjoying it (although at some point, I'm going to have to get back to my other full time job, which is PDC planning, or my other full time job, which is hiring some Longhorn evangelists too)

Comments

  • Anonymous
    April 19, 2005
    The comment has been removed
  • Anonymous
    April 19, 2005
    The comment has been removed
  • Anonymous
    April 19, 2005
    You need an IE Evangelist (IEvangelist looks like an interface definition (-: ). We do too.

    Why?

    Well, we use IE as our prime mechanism for delivering a number of intra-, extra- and internet applications, and, whilst standards support is important, it's not as important to us as the other great pieces of work that have been done with IE - things like great client side interactivity and (browser hosted) Windows Forms controls, as well as a generally rich scripting environment (especially for our intranet environments which tend to be [mostly :-)] homogenous in terms of clients).

    So we want someone who will continue to promote this side of IE, all the cool bits that some people might complain about becuase they are not standard but are awesome because they provide real developer (and hence [maybe :-)] end user) value. Stuff that you add for exactly that reason.

    I don't think you should be afraid to diverge from the standards if you really think there is value in doing so, but I know where people come from when they want support for a base set of standards.

    The best of both worlds would be to promote both sides; standards growth and wow functionality. I sometimes feel that this wow side of IE gets lost (and their are a lot of people out there using this sort of stuff and wanting more that never post to the IE blog for example and so maybe aren't being heard).
  • Anonymous
    April 20, 2005
    It is always best to have direct access to someone who can post first hand info, answer questions for the community, and provide feedback to the developers, sort of a feature liaison between users and developers.

    Job Title suggestions:
    -IE Liaison
    -IEKIA (IE "Know-It-All")
  • Anonymous
    April 20, 2005
    Having read most of the discussions on the IE blog, the combination of being on the IE team and posting on the IE blog sounds like something of a nightmare.

    Think about it, the team doesn't (probably: isn't allowed to) talk about new developments, which is precisely what people read the blog for (can you blame them?). You're bound to get flamed by the Firefox enthusiasts for whatever you post. And you're continually laughed at for any bugs that may be in IE, especially in the area of security.

    An IE evangelist will need to be a very strong personality to be able to withstand such storms.

    People are complaining IE hasn't had a major update in year. It's gonna get worse, because IE7 will never be good enough, especially if the rumours about not supporting CSS2 are true. People will complain the update isn't major enough. Webdesigners, including myself, will resent MS for this lack of functionality (especially now that they've had a taste of it in Firefox) and this anger will focus on the MS employees most visibly associated with it.

    Wouldn't want to be an IE evangelist. Wouldn't want to be someone posting on the IE blog either.
  • Anonymous
    April 20, 2005
    The comment has been removed