The influence of pre-populating web forms
2 Jul 2010 - 3:47pm
2 replies
632 reads
I'm currently working on a revision to a checkout process in which we're debating the pros & cons of pre-populating certain fields.
The application allows users to select an item for "purchase" and pledge an amount related to the value of that item. This means they can in fact pledge more than the stated amount for the item, or the exact amount of the item. They obviously cannot pledge lower.
The debate is such:
Do we pre-populate the form field with the amount of the selected item or leave it blank to encourage some percentage of greater pledge.
I'm interested to hear any opinions, direction to supporting research one-way or the other, or experiences anyone here has had with something similar.
Comments
Hi..
For more understanding... when you say "the user can pledge more than the stated amount". Is it for donation or is there any other reason why the user wil pledge above the stated amount?
I've seen this implemented as a non-editable field with the item value, plus a drop-down allowing them to select additional amounts to pledge ($5, $10, $20, $50, etc).
On Fri, Jul 2, 2010 at 4:08 PM, Charles Adler wrote: > I'm currently working on a revision to a checkout process in which we're > debating the pros & cons of pre-populating certain fields. > > The application allows users to select an item for "purchase" and pledge an > amount related to the value of that item. This means they can in fact pledge > more than the stated amount for the item, or the exact amount of the item. > They obviously cannot pledge lower. > > The debate is such: > > Do we pre-populate the form field with the amount of the selected item or > leave it blank to encourage some percentage of greater pledge. > > I'm interested to hear any opinions, direction to supporting research > one-way or the other, or experiences anyone here has had with something > similar. > >