Hey there,
I can't help you sell your specific proposal, but I will tell you what I am
looking for whenever someone is asking me for more resources. I want to know
how... how will it help, how much will it help, how much real gain will we
see.
1) Numbers help. "Reduced processing on the current server" is not as
compelling as "overall process throughput will increase by 20%". Know the
numbers, use the numbers. Be prepared to answer questions about impact on
network traffic, etc.
2) Standard jargon is not going to convince a manager (at least one who
knows his business). If you "need" something you should be able to explain
why. Start by playing devil's advocate with yourself. When you say
"seperate logical layer", ask yourself "How does that help"? "Is it really a
seperate logical layer ... or is it a seperate *physical* layer? Either way,
how does it help? The worst thing that can happen when you pitch these ideas
is to be asked "how will a <insert jargon here> help improve performance?"
and be caught jibbering or flat footed. Asking yourself the hard questions
first lets you a) decide if it is valid proposal and b) prepare a solid
response.
Here is a devil's advocate question to ask yourself: How is spitting web
apps and web services onto two servers more scalable? ..... If you do not
have an answer at the tip of your tongue, then get one ready. Again, numbers
will help. At what point (numbers here) will the processing demands outweigh
the network delay? Is it based on current figures or projected figures? If
projected, over what period? Etc.
3) Redirect to the focus if the manager strays. If the proposal is intended
to increase productivity, maske sure that he understands that. For instance,
if he asks "how will this improve performance", redirect him to the goal.
Just because he is asking about something else does not mean there is no real
benefit in improving productivity, you just need to make sure you are both on
the same page.
4) Reselling a proposal is harder than selling it right the first time. On
the second trip you not only have to overcome the standard issues, but you
are now faced with scepticism resulting from the failed first proposal.
Best of luck on your proposal.
John
"bi" wrote:
Hi
I am trying to convince my manager to buy a seperate server for webservices,
however I am having real trouble convincing him of the business benefits.
My arguments are based on the following
a) seperate logical layer
b) reduce proccessing on the current webserver
c) allows for a more scabale envoirment
Has anyone got any other comments to add to this.
