Please expand the Scenes

[Tuicemen]

We can request user post their polls with standard answers. That doesn't mean anyone will follow the suggestion.
Also the more options the more confusing it becomes less options are better.
eg:
1: Yes (very important to me)
2: Maybe (I may or may not use it)
3: No (I'd never use it)

[roger1818]

We can request user post their polls with standard answers. That doesn't mean anyone will follow the suggestion.

But no one will follow any standard if we don't suggest it in the "don't post before you read" thread.  Also, as admin, can you not change the questions in a poll?

Also the more options the more confusing it becomes less options are better.
eg:
1: Yes (very important to me)
2: Maybe (I may or may not use it)
3: No (I'd never use it)

I agree that too many options makes it more confusion,  but too few removes the granularity from the features that are urgent from those that would be nice to have but can wait a bit (if everyone answers yes to everything they want, how will the developers know which features are most important?).  Personally I think 5 questions is a good compromise between the two, but will deffer to your decision.

[Tuicemen]

Well the maybe could be worded:
Maybe (I'm not in a rush for it)

[Noam]

Why not use a scale, ex: "How important is 'Feature X' to you?"
1. Very important
2. Somewhat important
3. Neutral
4. Mostly unimportant
5. Not important at all

That way, you could look at what is most important to the largest number of people - and those would be the ones they should focus on first.

[Tuicemen]

That works too. However my experience shows only the Important features would get looked at.
Even if all those were added the somewhat important or maybe features would only get added if the developer was motivated enough.
3,4 and 5 would be the same as far as a suggestion getting consideration.

[roger1818]

Why not use a scale, ex: "How important is 'Feature X' to you?"
1. Very important
2. Somewhat important
3. Neutral
4. Mostly unimportant
5. Not important at all

That way, you could look at what is most important to the largest number of people - and those would be the ones they should focus on first.

Isn't that similar to what I said originally?

[Noam]

Why not use a scale, ex: "How important is 'Feature X' to you?"
1. Very important
2. Somewhat important
3. Neutral
4. Mostly unimportant
5. Not important at all

That way, you could look at what is most important to the largest number of people - and those would be the ones they should focus on first.

Isn't that similar to what I said originally?

Remarkably, yes. Somehow, I had missed your comment when reading through the thread. But we are certainly thinking along the same lines.  :-)

[roger1818]

That works too. However my experience shows only the Important features would get looked at.
Even if all those were added the somewhat important or maybe features would only get added if the developer was motivated enough.
3,4 and 5 would be the same as far as a suggestion getting consideration.

True, but different features will be important for different people.  If most people say a feature not important, it may not be implemented, but that is to be expected.  The alternative is if we say every feature is equally important, we also may not get some of the critical ones if they are difficult to implement. 

This gives us a way of ranking how important each feature is (if standardized, it is easy to calculate which features are the most important) so that they can compare that to how difficult it is to implement.

[Tuicemen]

How a user puts forth their selectable options for a poll is up to the individual.
As well how a user votes is up to the indivdual they need not explain how or why they voted the way they did.
The main thing is that users are contributing.

I don't expect Authinx to push for any one of these suggestions until the Wifi unit has been in the public hands for at least a month (maybe longer).

[HA Dave]

....different features will be important for different people.  If most people say a feature not important, it may not be implemented....

I've never seen a product designer (and I've known a few) that couldn't easily discard any poll or questionnaire about the "customers" desires. After all.... isn't the product designer the expert?

It's important that we give our heartfelt honest, feedback... I am with you on that guys. But our own emotional investment doesn't qualify as meaningful to the "value" of the product. After all.... we don't represent the vast majority of X10 users.   

[Knightrider]

Also, can we use standard, clear questions for the polls?  My suggestion is to use the following:

• Very Important (I want it ASAP)
• Useful (I will want it one day)
• Neutral (I might use it)
• Not very useful (I probably won't use it)
• Unnecessary (I would never use it)

By using the same questions, it will be easier to compare the results.  Also by making the questions clear, the results will be more consistent.  People are also accustomed to ranking priorities.

This is an awesome idea. I have changed my polls to reflect the improvement.

[roger1818]

I've never seen a product designer (and I've known a few) that couldn't easily discard any poll or questionnaire about the "customers" desires.

I have met designers like that, but I have also met many good designers who try to give the customer what they want.

After all.... isn't the product designer the expert?

Usually not.  They are the expert when it comes in terms of how to design things, but to them, requirements come from a document.  If it isn't in the document, it isn't necessary.  Now the requirements can be modified but that  usually costs extra. 

Specifying requirements is expectantly true when dealing with China.  A combination of culture and time zone differences mean that if something isn't clear, they won't ask questions but instead will take a guess (asking questions is an embarrassment) and they probably won't tell you they did so.   As a result  it is important to specify things extremely accurately.

[JeffVolp]

After all.... isn't the product designer the expert?

Usually not.

That's for sure!  Look what they did to Microsoft Word!

I still use Word 2000 because the newer versions think they know better and screw up what I'm trying to do.

Jeff

[Tucson]

May  I suggest a first baby step to improve scenes. Add timers. This would make programming simpler as you could turn on a whole room with one timer. Also would allow repeats.  Two improvements for the price of one.