Professional Documents
Culture Documents
Because product management tasks vary widely, as your company grows, you may want to
split your product management team into two parts: one group focused on developing
requirements for future products and another group devoted to supporting marketing and sales
for current products.
5. Field Marketing
Ultimately, as your company grows over time, your product management team might
begin to customize sales and marketing tools according to the regions you serve. Large
companies with regional sales teams divvy their product managers geographically so they can
create specific product materials and programs tailored to their regions needs and goals.
6. Organizational Structure
Now that you know what your product team is responsible for and how they fit within
your sector and organization, its time to hire talent to fill open positions. The following are
the roles most integral to your product teams success.
7. VP of Product
Generally, the VP of Product (or Product Marketing) is an experienced product
management executive who ensures that the companys product strategy aligns with customer
needs and the overall market. Your VP should lay the foundation for building a strong product
team as your company expands. He or she also contributes regularly to management decisions
regarding business partnerships, marketing channels, product pricing and licensing, and user
requirements.
Additionally, the VP of Product makes sure that customer feedback and requests are
communicated effectively to product development and repackaged for customers. The VP is
also responsible for crafting and executing product strategy and building relationships with
accounting, development, engineering and sales teams. For example, the VP may work with
accounting to revise your companys customer contract or to approve talking points for how
marketing and sales teams should communicate product benefits to the market. In technical
companies, they will serve as the primary liaison between the engineers and the marketing side
of the company, making sure that the goals of both teams are aligned.
8. Product Manager
Product Managers are mid-level professionals that report to the VP of Product, VP of
Product Marketing or (for more technical roles) the VP of Product Engineering. Although
Product Managers are not part of the senior management team, theyre typically responsible
for researching technological developments and trends, and competitor strengths and
weaknesses. Product Managers help create product and business plans that identify market
opportunities and collaborate with multiple roles and departments to ensure the companys
various functions are aligned with product strategy.
Because product managers handle such a broad range of responsibilities, you should create
product manager roles that focus on technical versus business issues, inbound
marketing versus outbound marketing activities, or short-term tactics versus long-term
strategy. Breaking down product manager roles into specific areas will allow team members
to dedicate their focus to developing specific products and product lines, as well as defining
metrics that accurately measure their products success.
9. Product Analyst/Coordinator/Associate
These are typically junior roles within a product management team. Product Analysts hold
anywhere from two to five years of work experience, though this could be less for smaller
companies or if the analyst has a masters degree.
The Product Analyst or Coordinator helps create product documentation and sales
collateral for sales and technical presentations. He or she is also responsible for updating
databases, collecting internal and external requests for requirements and creating business-use
cases. The Product Analyst or Coordinator may organize training sessions that educate staff
on product messaging and prepare senior executives for speaking engagements by sending
them sales collateral and product documents. A Product Associate is typically the most junior
role and will take on various jobs and tasks to support the product team
Conclusion
As with any company department, your product team will evolve and grow as your
customers demand more sophisticated and well-rounded products. By recognizing that product
management is essential to both the business and the technical side of your team, you will
ensure the development and delivery of high-quality products to a greater number of
customers. Developing a new product shouldnt feel like youre fighting in the dark. Theres
an easier way. What you need is a structured road-map that gives your business a clear path to
follow.
PRODUCT TESTING
Product testing, also called consumer testing or comparative testing, is a process of measuring
the properties or performance of products.
The theory is that since the advent of mass production manufacturers
produce branded products which they assert and advertise to be identical within some technical
standard.
Product testing seeks to ensure that consumers can understand what products will do for them
and which products are the best value. Product testing is a strategy to increase consumer
protection by checking the claims made during marketing strategies such as advertising, which
by their nature are in the interest of the entity distributing the service and not necessarily in
the interest of the consumer. The advent of product testing was the beginning of the
modern consumer movement.
Product testing might be accomplished by a manufacturer, an independent laboratory, a
government agency, etc. Often an existing formal test method is used as a basis for testing.
PRODUCT VALIDATION AND VERIFICATION:
Verification process describes whether the outputs are according to inputs or not, and
Validation process describes whether the product is accepted by the user or not.
Difference between Verification and Validation:
Verification
1. Verification is a static practice of
verifying documents, design, code and
program.
2. It does not involve executing the code.
3. It is human based checking of documents
and files.
4. Verification uses methods like
inspections, reviews, walkthroughs, and
Desk-checking etc.
5. Verification is to check whether the
software conforms to specifications.
Validation
1. Validation is a dynamic mechanism of
validating and testing the actual product.
2. It always involves executing the code.
3. It is computer based execution of program.
4. Validation uses methods like black box
(functional) testing, gray box testing, and
white box (structural) testing etc.
5. Validation is to check whether software
meets the customer expectations and
requirements.
6. It can catch errors that verification cannot
catch. It is High Level Exercise.
Pughs concept
Invented by Stuart Pugh the decision-matrix method, also Pugh method, Pugh
Concept Selection is a quantitative technique used to rank the multi-dimensional options of
an option set. It is frequently used in engineering for making design decisions but can also be
used to rank investment options, vendor options, product options or any other set of
multidimensional entities.
A basic decision matrix consists of establishing a set of criteria options which are
scored and summed to gain a total score which can then be ranked. Importantly, it is not
weighted to allow a quick selection process.
A weighted decision matrix operates in the same way as the basic decision matrix but
introduces the concept of weighting the criteria in order of importance. The resultant scores
better reflect the importance to the decision maker of the criteria involved. The more
important the criteria the higher the weighting it should be given. Each of the potential
options are scored and also multiplied by the weighting given to each of the criteria in order
to produce a result.
The advantage of the decision making matrix is that subjective opinions about one
alternative versus another can be made more objective. Another advantage of this method is
that sensitivity studies can be performed. An example of this might be to see how much your
opinion would have to change in order for a lower ranked alternative to out rank a competing
alternative.
Morphological analysis is another form of a decision matrix employing a multidimensional configuration space linked by way of logical relationships.
Morphological Analysis
General Morphology was developed by Fritz Zwicky, the Bulgarian-born, Swissnationalastrophysicist based at the California Institute of Technology. Among others, Zwicky
applied Morphological Analysis (MA) to astronomical studies and the development of jet
and rocket propulsion systems.
In order to apply morphological analysis to product design, we simply identify the critical
functions in our function structure diagram and then identify many different solutions for each
function.
The results of this research are compiled and presented in morphological chart. A
morphological chart has the critical sub functions listed across the 1st row and then each
column contains the different solutions for each critical function.
For example, the figure below shows the FSD for a pneumatic nail.
A completed
Morphological matrix for an exercise product to prepare bedridden patients to use a walker is
shown below.
LATERAL THINKING
A way of solving a problem by thinking about it in a different and original way and
not using traditional or expected methods
Idea generation and problem solving technique in which new concepts are created by
looking at things in novel ways. Whereas the logical ('vertical') thinking carries a chosen idea
forward, the sideways ('lateral') thinking provokes fresh ideas or changes the frame of
reference. And, while vertical thinking tries to overcome problems by meeting them head-on,
lateral thinking tries to bypass them through a radically different approach.
The lateral thinking exhibited by the new research team showed their creativity, originality,
and innovation as they solved the problem.
Lateral thinking is solving problems through an indirect and creative approach,
using reasoning that is not immediately obvious and involving ideas that may not be obtainable
by using only traditional step-by-step logic.