Comment on

First I'd like to say that I think this is a great topic.

My approach, the one that works for me and maybe not for everyone one is:

1. Solicit the input of the target user group - have them become part of the design process. Forget what you think files/directories should be named (unless of course it would cause issues) - let them decide on the conventions, let them decide on interface - help them streamline the process to their liking.

2. Since management wants the tools they must step forward and enforce the use - BUT - the user still will not use it unless they are contributors to the tool.

3. It also seems to help me when I "lead" the user to the solution - this makes them feel like they came up with the idea - therefore making it more palitable to use - rather than having a tool "crammed" down their throats by management and their peers.

Is this foolproof - no. But it will put the odds in your favor - or at least it has for me.

In reply to Re: OT: Getting people to use tools by draconis
in thread OT: Getting people to use tools by logan

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.

Comment on

The best material for plates (tableware) is: