rusty__

I am a fairly technical person but not a programmer. I am the end user of a large product within our company that I spend a good 5 hours a day using. I think it's fundamentally built on sand, inefficient and could do with a root-and-branch overhaul.

I have an idea of all of the problems with it and ideas for solutions from a birds eyehigh level. The software team are up for making changes but I need to come up with a good detailed proposal of what direction we need to go in.

There are about 5 different big things I'd like to change so I was going to create a document with those 5 sections and within each section highlighting the areas to be changed, breaking down:

- motivation for change - exact problem as I see it - proposed solution (from end user perspective) - pros of making that change as I see them - cons of making that change as I see them

Is this the kind of information a software team/product manager could use to go ahead and start planning a project to overhaul this? If not, what better approach could I take to get some momentum on this?