|
Concentrate on stuff they care about - response, consistency, durability, future-proof, oh shiny.
speramus in juniperus
|
|
|
|
|
Nagy Vilmos wrote: future-proof
There is no such thing as future-proof in programming.
When the next shiny new framework comes along, this will be re-written. 
|
|
|
|
|
Make an analogy: the web site is a car, and you pretty much "only" changed the engine, which is quite a big change, but not visible at first sight.
Then go into two points:
- the new features
- the benefits in terms of costs (whatever: resources, support costs, dev costs, etc.. as long as it can be converted in money) on mid and long term.
Then you are done.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Do not feed the troll ! - Common proverb
|
|
|
|
|
Rage wrote: the web site is a car, and you pretty much "only" changed the engine,
Automobile companies do better.
They keep the same engine but change the body styling! Every year! 
|
|
|
|
|
AndyInUK wrote: So do I even bother explaining them about the technical side or leave it and just give demo of new features ? What do you guys think??
One aspect that you might want to consider is giving an overview of the security features built into your site.
This could be anything from https to avoiding XSS etc.
This a common concern that is often ignored during initial demos to clients.
|
|
|
|
|
Griff covered what to tell the users pretty well in my opinion.
For the manager class you need to talk even less about technology, only use words from Steve Jobs vocabulary.
Stress that the new site has better maintainability and therefore cost less, it's ok to lie.
Be excellent to each other. And... PARTY ON, DUDES!
Abraham Lincoln
|
|
|
|
|
AndyInUK wrote: I mean all they see is UI. Which at first will look pretty similar to old one until they go and start using it and discovering it.
User Guide
Section 1
Start using it and discovering it.
Section 2
There is no section 2.
If you are producing a text for people who have to use your product (a 'text" does not have to be words on paper; it is anything that communicates information from one person to others), only include information that they want or need.
I don't give a bluddy blue f@rt how MS produced VS, or what technologies are behind it, I only care that it helps me do what I need/want to to, so I only want to know how it provides that help.
Prepare some use cases, show how your thingummy helps to address them, then stop. If people ask questions, find use cases that cover their questions, and document them.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Andy, I kid you not - tell them nothing. Any attempt to explain the technical merits of a new approach to an old problem will be met with stares of absolute befuddlement, bellicose attacks for changing what was working fine, and second guessing your solution by the technically semi-literate, who I admit at least mean well. The rest are merely obstructionists who will only make your life miserable. Deploy it, train the users, and say nothing more. Above all, don't attempt to explain or justify your approach. They won't understand, and life is too short to teach them to understand. They aren't experts; you are, and that's why they hired you.
If your solution is as good as you think it is, users will notice, and word will get out. If you're a buffoon who's implemented a solution no better than what they had before, they'll probably notice that, too, and you've wasted their money. But if you're a true genius, and you have truly delivered a product that the users can't tell has changed, but which will never have to be revisited again in the foreseeable future, you'll never hear about that, either. Sadly, succeeding too well - making, in this case, a transition from last century's programming paradigm to this century's model so seamless and painless as to cause no user protest - is rarely rewarded until long after the job is done, if ever.
Don't waste your time or strain the mental capacity of your users by attempting to explain the technical advances, just demonstrate the new features and cash your check. Congratulations, by the way, on a job well done! You probably won't hear that from your users, but all of us here know what you've done for them, and understand it's import. Good job! 
Will Rogers never met me.
|
|
|
|
|
Thanks for your suggestion. I think it makes sense to just speak features and not go technical during the demo. 
|
|
|
|
|
Thanks everyone for all your suggestions. I have decided not to speak anything technical during the demo. I will just demo few cool features and rest I will leave it on them to play around and find.
Thanks again.
|
|
|
|
|
Got the newsletter and read "Round 1 has ended in the Intel AppInnovation Contest". as "Round 1 has ended in the Intel Inappropriate App Contest". 
|
|
|
|
|
Probably you got it the right way round.
speramus in juniperus
|
|
|
|
|
Looks like somebody let auto-correct write that email 
|
|
|
|
|
If you have seen some of positively brilliant ideas that have crossed the moderation queue... 
This message is manufactured from fully recyclable noughts and ones. To recycle this message, please separate into two tidy piles, and take them to your nearest local recycling centre.
Please note that in some areas noughts are always replaced with zeros by law, and many facilities cannot recycle zeroes - in this case, please bury them in your back garden and water frequently.
|
|
|
|
|
I'm sure the brilliant ideas have been weeded out.
|
|
|
|
|
They were still coming through yesterday. 
This message is manufactured from fully recyclable noughts and ones. To recycle this message, please separate into two tidy piles, and take them to your nearest local recycling centre.
Please note that in some areas noughts are always replaced with zeros by law, and many facilities cannot recycle zeroes - in this case, please bury them in your back garden and water frequently.
|
|
|
|
|
|
Beautiful shot, love the APOD series.
|
|
|
|
|
that viewed, downloaded and commented on my articles. Views just went over 400K and one of my articles surpassed 10.0 in popularity.
Yeah I know I do it every 100K just had to share!
|
|
|
|
|
Mike Hankey wrote: Yeah I know I do it every 100K just had to share!
... and to get a few more clicks 
speramus in juniperus
|
|
|
|
|
No just to say thanks, if I wanted clicks I would have added links!
|
|
|
|
|
Ah, but people can click your name to then get to your articles.
Which is a good thing, cuz I never heard of ya and will take time to review some of your articles.
All this, of course, to be in yer next 100k "Thank you" post! 
The Apostles drove a Honda, for they were all in one Accord.
Moses played tennis, for he served in Pharaoh's Court.
Baseball was the first sport, for it reads "In the Big-inning..."
|
|
|
|
|
BCantor wrote: Ah, but people can click your name to then get to your articles.
Which is a good thing, cuz I never heard of ya and will take time to review some of your articles.
All this, of course, to be in yer next 100k "Thank you" post!
Translation:
"Slap me, please."
I'm good at translations, me.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
Great job Mike! Congrats.
It was broke, so I fixed it.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Beer | [beer]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/beer.gif)