When I joined ACDSee last September as their community manager I knew that there would be exciting projects! Beta had a meaning for me because I helped with the ACDSee Pro 2 beta last summer. But I wasn’t involved at the level that I have been with this one.
The word ‘beta’ has new meaning for me! I’ve heard my Twitter friends talk about their betas, but now I totally understand. Taking a project from development to launch is an amazing adventure! And incorporating a beta period allows for our customers to join us.
We launched our beta last Monday and after one week the product positioning is beginning to happen. As we developed it, I had a good idea of where I hoped that to be but isn’t it ultimately decided by the customers? Marketing & PR just can’t dictate that.
Someone asked if it will be successful? I translated that into new questions:
- Are we listening to our community?
- Do we know our customer’s wants/needs?
- Will our business expectations be met?
It was interesting to read this today at a forum in our community:
ACDsee is once again flexing their muscles and really coming on strong as a real contender. As I’ve mentioned before, I’ve been giving the Pro 2 software a real consideration and it is very very good. Some real problems still exist and their are some significant holes for the pro photographer (Pro – hence the title of the software). But I’d recommend Pro2/v10.0 and the editor over PSP* now any day… PSP have moved backwards while ACD are bringing their products forward.
That’s a generous trial period and a great marketing idea…*PSP is Paintshop Pro by Corel
That information is quite valuable in a number of ways. It also highlights the opportunities to gather feedback outside of the beta forums.
Beta definitely has a new meaning for me & I’m sure that there will be more to share on the process. What does beta mean to you?
Connie,
As a marketing person, I have been involved with beta testing. Unfortunately, the executives didn’t listen to the community of testers and brought the product to market without implementing any of the suggestions. Their comment: We’ll make the change in V2. Never happened. V1 was a completed disaster and the company went away. Lessons learned: Don’t just listen, respond, react and revise.
Thanks Lewis for those very valid points.
This is my first experience & I’m finding that the time-frame plays a huge factor. There are many things happening behind the scenes with development & QA.