Capture all the required data to build a plan.
Ensure that you are considering your architecture in lock step with the plans for the product. (A lesson Twitter has been learning)
Validate with Market and document requirements.
Plan timelines and resources required to complete
Capture all the required data to build a plan
There are many inputs into what the next shiny thing is for your product or what the next new product should be and it is important to collect data from various different sources so you have perspective and as close to full information as you can get. Any decision related to your product must come with input from customers and prospects. Get the good the bad the ugly. Don’t wait for this info to pour in, go out and get it. User groups, web 2.0 tools, hosted onsite sessions, webex’s, basically any way you can make it easy for the customer to provide their thoughts, suggestions and feedback…..just make sure you get it. In addition to customers talk to your sales people, your technical support group, your call centre, your development group. Get as much data as possible. Lastly make sure you are looking at what your competition is doing and what new entrants to the market that may be on the periphery of your product are doing.
All of this data collection is not event based. This is a continuous process that must be working every day in your organization. Make it part of everyone’s job to collect this info and have a formal central repository where it is easy for people to dump their info as it is collected.
Ensure your underlying architecture will continue to support your plans
This seems to go without saying but it doesn’t. Time and time again I see companies whose product evolves to a point they never imagined it would and it creates significant problems if the platform is not supportive of the type and pace of new product releases you want and need to do. Validating this regularly will allow you to not get too far down the path before having to make a possible switch. No one wants to have to switch something significant midstream but the reality is that with the best forethought and planning things can change in the marketplace so fast that you may eventually have no choice.
Validate with the Market and Document Requirements
Once you have defined a roadmap for the product validate it with the group you collect data from. When building the roadmap and communicating back to your group it is best if you can lay out for them your thoughts (based on what you know today) for the next 2-4 releases and where you see the product going, with the caveat that there may be a fair amount of change given the time horizon you are presenting is long.
Plan the Timeline and Resources
Now the execution. Build the plan to deliver what has been scoped, look at resource gaps and ensure you have a plan to secure the help required and that timelines are built for delivery to customer that are reasonable with a fair amount of buffer in them for….well…you know.
Everyone agrees that customer experience and the continued velocity of product development is critical for early startups and for more established companies with a start up culture. To successfully manage this it is important that you build a process to inform you and allow you to plan your way through to improving the experience. the above contains a brief example of the major requirements and this process will be very different depending on the size and scope of your company and product. the important message is HAVE a process that is part of your company’s daily pulse and you will stay in tune with your customers, the market and success.