- Mistakes: There is a difference between mistake and bug. In a dynamic environment kinks in the execution and operation will happen and they can be worked out, and we accept those. Mistakes in the planning and decision phase are a sign of inexperience. The transition from Jelsoft to IB seemed simulate a Space Shuttle being handed to a group of 5th graders.
- Transparency/ Communication: only became an issue because way too much was broken and no one ever told anyone why or what was going on. If your paycheck comes every pay period and is the amount it is supposed to be, you are happy. It is when it is late or the wrong amount that you want to know who, why, and what is being done to keep it from happening.
- Communication: This falls along the lines of transparency. We are not so concerned with the What, why, who when things are running as expected.
- Give the customers a promise: At this point promises are empty. Make things right first. Fix ALL of the broken things before you add new things.
Suggestion: Someone needs to learn resource management.
VB.com needs to focus 100% of its resources into making vBulletin run correctly, and efficiently. Stop with EXTERNAL add on like FB Connect. In my opinion when VB added FACEBOOk CONNECT they surrendered Forum superiority to FACEBOOK and that is a tool that relies on FACEBOOK.
vb.org needs to be the place for add ons for external content. vb.org has a wealth of excellent add ons provided by users. There needs to be a section for official VB add ons like Facebook Connect…….. Oh, and tell the person that comes up with the idea for charging for any of these add ons to forget that notion…. Someone will suggest it.
Learn one lesson. if you were NASA you could glamorize, glorify, and take liberties with the truth and facts because only a hand full would know the difference. You are not. You are IB/VB and there are WAY too many End Users that have enough skill and knowledge to step into your job today and do an equal to or better job than you do…… They see right through your BS.
Quit lying. You are not good at it. I would rather see a post from a TEAM member saying, we broke this and it is being fixed than…… Some 1/2 azzed explanation about why it is supposed to be that way. when you KNOW it is not.
Lastly and most importantly……… Your team needs to meet with management and decide if VB is going to be about profit or customer satisfaction, yes you can be about both … BUT there needs to be one or the other that is TOP PRIORITY. If you polled End Users right now you would find our opinion is that your top priority is money. And while that is the prime goal for most all commercial products, you are in a somewhat unique situation where you have taken over from a group that was focused on Customer Satisfaction…. Which makes a bumpy road when quality and satisfaction take a back seat to profit.
We are trying and want to be loyal VB customers. You are not giving us much to work with. There is a difference between effort and result. Telling us you are working “so hard” to fix things is canned, and we could care less. We paid for results, not slaving hard work with a broken end product.