Professional Documents
Culture Documents
The product platform, is the set of assets shared across a set of products. An effective
platform, can allow a variety of derivative products to be created more rapidly and easily,
with each product providing the features and function desired by market segment
Since platform development projects can take from 2-10 times, as much time and money as
derivative product development projects, firm cant afford to make every project a new
platform
The critical strategic decision at this stage is, whether a project will develop a derivative
product from existing platform, or develop an entirely new platform
PRODUCT PLATFORM PLANNING (CONT’D)
One technique for coordinating tech dev with product planning is the Technology roadmap
It is a way to represent the expected availability and future use of various technologies
relevant to the product being considered
The method is particularly useful for planning products in which the critical functional
elements are well known in advance
To create a roadmap, multiple generations of technologies are labeled and arranged along a
time line
The roadmap can be augmented with the timing of projects and projects that would utilize
these technological developments
Technology roadmap can serve as a planning tool to create a joint strategy between
technology development and product development
EVALUATING FUNDAMENTALLY NEW PRODUCT OPPORTUNITIES
Some criteria for evaluating fundamentally new product opportunities include :
1. Market size (unit/year X average price
2. Market growth rate (percent per year)
3. Competitive intensity (number of competitors and their strength)
4. Depth of firm’s existing knowledge of the market
5. Depth of firm’s existing knowledge of the technology
6. Fit with the firm’s other products
7. Fit with the firm’s capabilities
8. Potential for patents, trade secrets or other barriers to competition
9. Existence of product champion within the firm
While these criteria are particularly useful in evaluating fundamentally new product, they also apply
generally to evaluating any product opportunity
These criteria can be used in a simple screening matrix to evaluate the overall attractiveness and
types of risk for any given opportunity
STEP 3 : ALLOCATE RESOURCES AND PLAN TIMING
It is likely that, the firm cannot afford to invest in every product development opportunity
in its desired balanced portfolio of projects
As timing and resources allocation are determined for the most promising projects, too many
projects will invariably compete for too few resources
As a result, the attempt to assign resources and plan timing, almost always result in a return
to the prior evaluation and prioritization step to prune the set of projects to be pursued
RESOURCE ALLOCATION
Many organizations take on too many projects without regard for the limited availability of
development resources
As a result, skilled engineers and managers are assigned to more and more projects, thus
their productivity drops of dramatically and projects take longer to complete
Furthermore, products become late to the market and profits are lower
Estimating the resources require for each of the projects, in the plan by month, quarter, or
year forces the organization to face the realities of finite resources
In most cases, primary resources to be managed is the effort of the dev staff, usually
expressed in person-hours or person-months
PROJECT TIMING
Determining the timing and sequence of projects, sometimes called the pipeline
management, must consider a number of factors such as :
1. Timing of product introduction : generally, the sooner the product is brought to market,
the better. However, launching a product before it is of adequate quality can damage the
reputation of the firm
2. Technology readiness : the robustness of the underlying technologies, plays a critical role in
the planning process. A proven robust tech, can be integrated into products much more
quickly and reliably
3. Market readiness : releasing improvement too quickly can frustrate customers who want to
keep up, on the other hand, releasing it too slowly risks lagging behind competitors
4. Competition : the anticipated release of competing products may accelerate the timing of
development projects
STEP 4 : COMPLETE PRE PROJECT PLANNING
Once the project has been approved, but before the substantial resources are applied, a
pre-project planning activity takes place. This activity involves a small, cross-functional team
of people, known as core team
At this point, the earlier opportunity statement, may be rewritten as a product vision
statement
The objective defined by a product vision statement, may be very general
It may not say which specific new techs should be used, nor does it necessarily specify the
goals and constraints of functions
In order to provide clear guidance for product dev organization, generally the team
formulate a more detailed definition of target market and of the assumptions under which
the dev will operate
These decision, are capture in a mission statement
MISSION STATEMENTS
The mission statement may include some or all of the following information :
1. Brief (one-sentence) description of the product : The description identifies the basic
function of the product but avoids implying a specific product concept. It may, in fact, be
the product vision statement
2. Benefit proposition : this element of the mission statement articulates the critical few
reasons a cust would buy the product
3. Key business goals : in addition to the project goals, that support the corporate strategy,
these goals generally include goals for time, cost and quality
4. Target market(s) for the product : there may be several target markets for the product.
This part of the mission statement identifies the primary market as well as any secondary
market that should be considered in development effort
5. Assumptions and constraints : assumptions must be made carefully, although they restrict
the range of possible product concept, they help to maintain a manageable project scope
6. Stakeholders
STEP 5 : REFLECT ON THE RESULTS AND PROCESS
In this final step of the planning and strategy process, the team should ask several questions to
assess the quality of both process and results. Some suggested questions are :
1. Is the opportunity funnel collecting an exciting and diverse set of product opportunities?
2. Dose the product plan support the competitive strategy of the firm?
3. Does the product plan address the most important current opportunities facing the firm?
4. Are the total resources allocated to product development sufficient to pursue the firm’s competitive
strategy?
5. Have creative ways of leveraging finite resources been considered, such as the use of product platforms,
joint ventures, and partnerships with suppliers?
6. Dose the core team accept the challenges of the resulting mission statement?
7. Are the elements of the mission statement consistent?
8. Are the assumption listed in the mission statement really necessary or is the project overconstrained?
Will the dev team have the freedom to develop the best possible product?
9. How can the product planning process be improved??
THANK YOU