I currently work at a sales & marketing consulting company that happens to sell desktop software as one of its offerings to clients. The software was tacked onto the company as a response to needs we identified at our clients. Unfortunately, due to the company's consulting DNA, what has eventually resulted is a pretty ugly mishmash of feature explosion, completely inconsistent builds across clients, and a complete lack of product roadmapping. All product management is done by the head developer and one of the company's managing directors, who clearly isn't built to manage a software organization. What's more, the innards of the software are so broken that the developers spend the majority of their time putting out fires rather than pushing the product forward.<p>Though I am not a developer, I work with this team every day and from what I've seen, there is little in the way of development methodologies, source control is shoddy, and I am completely unaware of any user that is actually happy with the software. As somebody who plays a client facing role, it's pretty discouraging having to deal with unhappy users who are only using the software because their organizations require it.<p>How does one fix this? There is a push to start building a new version of the software from the ground up to do away with the tangled mess of the current version, but since resources are usually tied up with putting out fires, it's difficult to do. Worse yet, I'm afraid the problem of feature explosion and client builds that bear little resemblance to each other will persist simply because management wants to allow clients to customize as much as they want in order to keep them happy.<p>Things are very broken and I'm trying to figure out what I can do to start turning things around. Any advice from HN would be greatly appreciated!
Leave. You can't turn it around. Not to sound negative or anything :) This kind of situation can only be turned around from above, not grass roots style. There has to be VP level buy off on the importance of the product, the user interface, and engineering. Unless you are in a start up, then one implementer can make a large difference.
> unhappy users who are only using the software because their organizations require it<p>Software is rarely any better than it absolutely has to be for people to put up with it, and these people <i>must</i> put up with it. You need to find a business case--either customers are defecting to other vendors, or fewer leads are converting to customers, or time to market for new features is hurting you, or good staff are resigning in disgust. If none of these things are true, then sadly the business is actually making the right call, because terrible software is cheaper and the market is all too willing to take it.
From your post it seems you're not quite ready to leave. So trying to share your insights and raise awareness may be worth a shot. That is, if you can comfortably speak with upper management without being singled out.<p>If the company is profitable and the users are pleased with the product then from an upper management perspective there may not be anything wrong. Until the bottom line is impacted there may not be leverage for change. The key is to alert management to the state of the product and the course it's on.<p>Parallel development may be an option as the next release of the product would address the underlying issues. This is costly and upper management would have to understand why that's necessary.