Just an observation after working at two different companies. It's important for everyone to know what the potential and limitations are for products.
One example of a good business practice is for sales to interact with the developers before a sales presentation. The idea is to gauge how much work it each for each component they want to sell. At this meeting, the developers can say how long it will take to complete something, and/or if it is feasible for the time period and price point proposed. This will avoid problems like over-selling and under-delivering, project timelines being delayed, and general frustration headaches.
It's fine to segregate responsibility to specific people so that they can focus on that area, but if one group needs to speak for another, e.g. sales speaking for developers, the two groups must discuss and agree on what is presented.
Also, make sure to TEST new ideas and processes before implementation. Often when implementing something for the first time in a new environment, adjustments are required. Throwing a new idea or process into an environment without prior testing slows down everything, often causing damage.
Subscribe to:
Post Comments (Atom)
2 comments:
you have nailed a classic problem. sales pitches versus the guy who comes to install the gadget. the first will tell you anything and the second will tell you whats real.
sales weasels ought to be forced to go on the installation trip for every sale they make. they ought to be there to answer customers when their promises turn out to be smoke
Post a Comment