Discussion Locked

I'm doing research for a biz proposal

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hey all,
I'm new to the forums, but thought this would be a good place to get some feedback.
My company is approaching a MS about fixing their IT Pro and Dev support and communication vehicle. I've been given the job of designing something for them that actually works. No mean feat.

What they've found is that most IT problems with their products are researched first through search engines, forums and blogs.
Also that their update system of email missives is largely ignored.

My role is to find out what people find broken in dealing with the MS entity, then what would make it better.

I'm trying to take the corporate greed/ROI/value spin out of the equation right now and just trying to approach this in an ideal world setting (yes I know I'm dreaming here, but their typography division is just that, so there may be a chance we could design something worthwhile.)

So my questions to you are:
When you have a problem with an MS product, how do you find your answers?

Do you ever deal with their support structure?
If not, why?

What would get you to go to an MS entity first?

Is there a company out there you deal with that "does it right?"

Why?

Thanks in advance.

1 reply

by w2ktechman

along with Web searches and knowledge of how a product works.
Calling MS can be a pain, and expensive, so should only be done if a mass problem appears, or if it is on a mission-critical device.
rebuild if necessary.

This discussion is closed to new replies.