.. a simple choice. and sometimes that is not enough.
To exemplify,

Q: Would you like Bacon or Eggs ?
A: Yes
~ ~ ~ ~ 
Q: Should A get X0,000 or Y0,000 ?
A: All of it.
[download]

I saw perception mentioned a few times in a couple of meditations this week. If the tool owner (management, users, whoever) perceive that they're making the choices, they can often be more amenable to the dire straits those choices put you in.

I have found that when writing software for in-house use, people can usually describe a tool from one step to another, but have difficulty with the holistic picture. Breaking things down into a choice between this was and that way greatly reduces 'furrowed-brow-syndrome' and lets you get on with the job. It also permits the developer a little bit of fancy footwork like ,

Well here we can use an X.500 directory or an LDAP connected database.
Which do you prefer ?
[download]