Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Managing your CustomerManaging your Customer's Expectations of DotNetNuke
Previous
 
Next
New Post
8/11/2007 1:06 PM
 

Managing your Customer's Expectations

I received  an e-mail the other day that got me thinking about software development and in particular managing my customer's expectations during the software development cycle.

This e-mail from Mike had a couple of lines in particular that got my attention: 

When I was at a particular company, the whole company was founded around a single formula. That formula was:

Customer Satisfaction = Expectation -Experience 

These few words struck a chord with me and I started to think about how I manage my customer expectations. That same day, I was in a customer meeting giving a demo on some new features we were delivering for a custom portal solution in Dallas Texas. 

My partner said to me after the meeting that I had oversold the features and that he didn’t think that the customer was impressed with our delivery. I told him about my e-mail and we both laughed- after which he turned to me and said that he was going to start calling me “BIG E”.

The point is that managing a project and in particular managing customer expectations is just as important as the technical part of the job. In my case, I tend to oversell and sometimes under deliver, although I always put my best foot forward and my intentions are always packed with passion to deliver the best that I can.

The Dotnetnuke core team has done a good job of setting expectations and most customers are happy with their experience, so customer satisfaction is seemingly high.

In my opinion, the Dotnetnuke projects have done a poor job setting expectations, and I would speculate that many of us has had a bad experience with al least one of the projects- probably more than one, driving customer satisfaction lower than it could have been- had the expectations been managed well.

So as Entrepreneurs, Developers and Power Users we need to take some time to consider managing our customer’s expectations and continue to strive to improve the customer experience.

All levels of the Dotnetnuke stack, from the core team down to the consultant, including 3rd party developers and design companies, need to manage customer expectations and deliver a customer experience to match that expectation, thus driving up overall customer satisfaction in the Dotnetnuke community.

I for one am changing my ways and will be using the above formula as a guiding light for my Dotnetnuke Business.

I think if we all do this, our community will continue to flourish, and we can continue to seek a revenue share from those efforts.

What do you think?

“BIG E”
Dallas Texas
Kendallsoft

 

 
New Post
8/12/2007 5:18 PM
 

"You can't disappoint me 'cause I don't expect nothing of you"

 

Based upon my experience, in almost every regard I have sought 3rd party solutions for most of the DNN projects: blog, forum, feedback, almost everything except text/html...
So now, my expectations are- zero.

And I am fine with that.
As long as I know that the job can still get done, it's all good.

 



 
New Post
8/13/2007 12:51 PM
 

I think you are right that managing customer expectations is a very key item.  I personally am 100% honest with my customers taht I setup on DotNetNuke and let them know that we are at the mercy of the core team and core project teams for work with the core modules.  A majority of my clients accept that risk, however, I have others that have went to other sources for modules due to the uncertanty of the progress on core projects.

Now, don't take the above as a negative point to the project teams as I know how hard it is for the outside developers to contribute and there are many things that go into a release.  I know this being a part of the documents module team.  Have some of the teams messed up in their communication?  Maybe.  But they are still doing a good job in developing and I think that those contributions are often overlooked.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Managing your CustomerManaging your Customer's Expectations of DotNetNuke


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out