A Five Point
Wellness Plan for High Technology Product Companies
The motivation behind most acquisitions
is strategic in that it opens doors to new markets, expands the breadth of
product solutions, provides an instant customer base, or some combination of
all three.
But after the deal closes, the
wheels of execution often slow to a grinding halt due to differing opinions on
product or technology strategies, lack of market direction for the combined
products and blending of vastly different cultures.
Learn five key initiatives that
will help your organization avoid or overcome post acquisition paralysis.
Click here to download
the white paper.
Product Management:
Five Fundamentals of Market Leadership
You don’t become a market
leader by reacting to the needs of every opportunity. You become a market
leader by systematically pursuing markets that are most conducive to your
strengths and executing in a synchronized fashion to deliver solutions instead of
products.
This one day workshop will help you
understand why the product management function is the lynchpin in all market
leading companies and how your company can adopt five fundamental business
practices to become a market leader. You’ll walk away with a framework that’s
simple to understand and adopt and the tools necessary to execute.Course details
PLEASE RESPOND BY GOING TO http://careers.smarttech.com/
SMART requires a product manager - content for its Calgary, Alberta,
office.
Join one of Canada's fastest-growing companies. SMART Technologies
Inc., a global leader in interactive whiteboards and group
collaboration tools, is looking to hire skilled people to further
its remarkable growth. Explore the careers at one of Canada's 50
best-managed companies, and find a fast-paced environment that
allows your drive and creativity to shine.
You will be responsible for developing a multi-million dollar
accretive revenue stream through the marketing of digital content
offerings. You will focus on working with vertical market
development teams, marketing communications and product development
to oversee the marketing mix for your product or service
offerings.
Responsibilities include the following:
• Managing the entire product life cycle including strategic
planning, licensing of content distribution rights, service/product
offering development, pricing and oversight of product development
• Driving product launches with cross-functional teams
including the product development, marketing, sales and services
organizations
• Developing, implementing and reporting against a go-to-
market plan, and working with all departments to execute
• Forecasting demand and overseeing service level delivery
• Specifying market requirements for current and future
products by conducting market research supported by on-going visits
to customers and prospects
You have a minimum of three years experience in product marketing,
business development or product management. You possess a business
or computer science degree. Experience in high-technology marketing
and developing software as a service (Web 2.0) products is a
definite asset. You have or are able to obtain a passport – this
position requires travel approximately 10 to 15 times per year.
Location Calgary, AB
Please forward this message on to your PM Colleagues.
Brian Lawley of the 280 Group will be holding a Webinar on
Wed Oct 10th on the topic of:
"PM Productivity: How to get twice as much done in
half the time"
Here is an overview:
As a Product Manager, you will always have far more
work than you can possibly accomplish. Between
thinking strategically to executing the day-to-day
tactical work required for product success, there is
always a full list of to-do items and plenty of requests that
go unfulfilled. This webinar will show you strategies and
tactics for being more productive, with the goal of
increasing your output and freeing up your time
for high-level tasks, while at the same time reducing
your overall stress level.
For more information and to sign up go here:
http://community.featureplan.com/community/2007/10/webinar_october_10_pm_product\
ivity.php
PLEASE FORWARD THIS MESSAGE TO YOUR COLLEAGUES, FRIENDS &
RECRUITERS/HR DEPT
There is a new job listings group on Yahoo focused exclusively on
Product Management and Product Marketing called pm_jobs. The Yahoo
pm_jobs group is the BEST place to find and post Product Marketing &
Product Management job listings. JOINING THE GROUP AND POSTING JOBS
IS FREE!
There are already over 60 recent PM positions posted.
To join simply go to http://finance.groups.yahoo.com/group/pm_jobs/join
We are excited to announce the availability of a new book, "Expert
Product Management: Advanced Techniques, Tips and Strategies for
Product Management & Product Marketing"!
Written by Brian Lawley, Founder of the 280 Group and President of the
Silicon Valley Product Management Association, Expert Product
Management teaches the reader how to create compelling product
roadmaps, plan and execute high-impact product launches, run more
effective Beta programs and get great reviews for products.
Expert Product Management is available now at
http://www.happyabout.info/expertproductmanagement-eOffer.php for
$19.95 or through Amazon at http://tinyurl.com/2rb56m. FOR THE NEXT
FEW DAYS WE ARE ALSO ALLOWING PEOPLE TO DOWNLOAD THE FULL EBOOK
VERSION AT NO CHARGE (normally $11.95). If you download the ebook all
we ask is that if you like the book you purchase a printed copy and
tell at least three friends about it. Note: the book also includes a
link to download free templates and a $30 coupon for the 280 Group PM
Office Professional version.
Brian will also be holding a book signing party on November 7th in
Santa Clara, CA prior to the SVPMA (www.svpma.org) monthly event. If
you are in Silicon Valley come and join us for food, beverages and
networking and pick up a signed copy ($5 discount for SVPMA members).
PLEASE FORWARD THIS MESSAGE TO YOUR COLLEAGUES AND ANY OTHER
PM-RELATED LISTS OR GROUPS YOU BELONG TO. THANKS!
The terms product and solution are no longer synonymous and there's a good reason everyone is jumping on the solution bandwagon - the value (read revenue).
Multi-product solutions offer far greater value then niche products because they address larger scale problems of greater impact.
But there is a major disconnect between the market's demand for integrated solutions and the silo approach of many product companies.
Join ZIGZAG Marketing, AIPMM and Accept Software for a three part webinar series that will help companies stalled by product silos quickly transition to a solution mentality.
Friday November 16th - 12:30 ET Product Companies vs. Solution Companies – Five Key Differences
Learn five key differences in how solution companies view the market versus product companies and how that market perspective drives their execution. REGISTER
Friday November 30th - 12:30 ET The Difference Between Managing Products and Managing Solutions
Learn how product teams are structured in a solutions environment versus a product environment and key differences in how they execute the product delivery process. REGISTER
Friday December 14th - 12:30 ET Product Demos vs. Solution Demos
If demos are a necessary part of your sales cycle, how you conduct demos may unintentionally push buyers away. Learn tips for delivering solution demos that drive higher value deals in less time. REGISTER
If you have any questions regarding these events, please contact Brandice Thorn at (404) 601-2866 ext. 1 or via email - bthorn@....
Thought you might be interested in the upcoming Agile Webinar on "How Product Management Must Change to Enable the Agile Enterprise," presented by Catherine Connor, Director of Product Marketing, Rally Software Development.
The topic was the best session I attended at the recent Austin SMP Conference in October. Fortunately, Catherine agreed to repeat this Webinar for the Product Management View (PMV) Webinar Series.
You can get more information, and register to attend at the following link:
Also, Ryma Technology Solutions and Rally Software announced last week the integration of FeaturePlan, the leading Product Management software solution and Rally Software, the leading Agile Requirements Management solution.Here are the links for the Press Release and a 5 minute flash demonstration of the benefits of the combined solution.
Finally, here is a link to the new Ideation module for FeaturePlan.If you want to automate the collection and prioritization of ideas and enhancements, please take a look at the 5-minute Ideation module demo at:
Can anyone highlights key issues involved in the Product Management of any SDK/API Kit Interface?
-
challenges
-
problems
-
benefits
-
Important key stakeholder involved around SDK /API kit usage. (I believe, it must be going to be the developer's/engineering team who uses! Who else?)
-
How your role is different than a 'normal' product manager?One difference I can definitely make out and that is, PM has to be technically very strong to be a product manager of any "SDK/API" interface.
-
-What else are the influencing factors?
Now let's look at challenges while actual managing SDK/API: it would be better if we touch up in the following points,
-
Pros/Cons of Providing SDK / API interfaces between two Enterprise services/product integration?
-
Existing SDK / API Problem / Challenges
-
Where the future trends of SDK / API interface development moving towards?
-
Other value added services/features, useful for the users of SDK/API.
-
SDK / API existence in the upcoming Software As Service (SaS) model
-
What else are the influencing factors?
I would appreciate if anyone can give any pointers addressing above points?
Here are few more inputs, which I've received off the list from few member.
To summarize points,
The main objective behind having SDK for any s/w is
- Have seamless integration with 3rd party software
- Reduce the integration/deployment cycle.
- increase usability and quality of product
- the key audience for SDK are going to be the developers and technical team.
Even to add in, I believe, system integrators/partner also should come into picture! since even some time partner also deploy the integration rather than we as a product company.
Few questions, which pop up to me are
- Their is heavy dependency between the actual product and it's supporting SDK? Do we beleive that whether the product it's self drives it's SDK PRD?
or Customer / Partner / Developers should also drive the requirement?
- How easy or hard to be in the role ? and switching the roles of doing actual "Product Mgmt" and SDK Product Mgmt?
- Sometimes, how boring is it to handle a SDK road map compare to product roadmap?
- If I see, when I would do a product management I can think about new interesting features which would make crazy a customer! however whenever I talk about adding a value to SDK, it just about add/modify/delete the SDK/API? or something else? and more?
- The last question, how do think, we can make a value add in the SDK? and what all are the ways?
-----------------
I can even add the questions which I'd put up to start the thread and here are those.
Can anyone highlights key issues involved in the Product Management of any SDK/API Kit Interface?
-
challenges
-
problems
-
benefits
-
Important key stakeholder involved around SDK /API kit usage. (I believe, it must be going to be the developer's/engineering team who uses! Who else?)
-
How your role is different than a 'normal' product manager?One difference I can definitely make out and that is, PM has to be technically very strong to be a product manager of any "SDK/API" interface.
-
-What else are the influencing factors?
Now let's look at challenges while actual managing SDK/API: it would be better if we touch up in the following points,
-
Pros/Cons of Providing SDK / API interfaces between two Enterprise services/product integration?
-
Existing SDK / API Problem / Challenges
-
Where the future trends of SDK / API interface development moving towards?
-
Other value added services/features, useful for the users of SDK/API.
-
SDK / API existence in the upcoming Software As Service (SaS) model
-
What else are the influencing factors?
I would appreciate if anyone can give any pointers addressing above points?
Can anyone highlights key issues involved in the Product Management of any SDK/API Kit Interface?
-
challenges
-
problems
-
benefits
-
Important key stakeholder involved around SDK /API kit usage. (I believe, it must be going to be the developer's/engineering team who uses! Who else?)
-
How your role is different than a 'normal' product manager?One difference I can definitely make out and that is, PM has to be technically very strong to be a product manager of any "SDK/API" interface.
-
-What else are the influencing factors?
Now let's look at challenges while actual managing SDK/API: it would be better if we touch up in the following points,
-
Pros/Cons of Providing SDK / API interfaces between two Enterprise services/product integration?
-
Existing SDK / API Problem / Challenges
-
Where the future trends of SDK / API interface development moving towards?
-
Other value added services/features, useful for the users of SDK/API.
-
SDK / API existence in the upcoming Software As Service (SaS) model
-
What else are the influencing factors?
I would appreciate if anyone can give any pointers addressing above points?
Here is the summary Role of Product Manager @ SDK/API Management:
Objective behind having SDK for any s/w is:
Seamless integration with 3rd party software
Reduce the integration/deployment cycle.
Increase usability and quality of product
The key audience for SDK is going to be the developers and technical team. Even to add in, I believe, system integrators/partner also should come into picture! Since even some time partner also deploy the integration rather than we as a product company.
PM should consider following points in mind while dealing with SDK/API:
Requirement:
"Base" product will certainly place certain requirements on the SDK, but PM better be listening to the customers who use this SDK – as folks who are doing the development / integration, who would know better what features or services are needed.
Important to specify functional requirements before working on the API signatures and how they're accessed!
PM better be getting pretty involved in the API definition! PM doesn't need to define the exact names of the function calls, parameters, etc – but PM should probably be getting involved in the "spirit" of API, what language its written in, how high or low level is the API (or do you provide multiple types of access routines), etc. all an all, PM have to find the right balance for your product, your customer/market and your engineering/development team! one of the challenges here is knowing where to draw the line!
Strategy:
PM should know where your SDK product need to be headed? Ultimately PM need to get feedback from the various constituents (customers, partners, internal developers) and develop the appropriate strategy.
An SDK can create some very important strategic options for your product/company. A real good example right now is the Apple iPhone and the SDK. Take a look at what has happened with the iPhone platform in the absence of a proper SDK – the community has found a way to get on without it and create some very interesting, compelling and valuable applications. Apple has not yet rolled out an SDK, but has announced plans to do so early next year. Now, as an iPhone user I hope I don't have to pay Apple for each and every application I want on the phone, and I do like the idea of a more "open" environment, but I also see value in the "controls" that we all expect to turn up there…..
Usability:
APIs need to be designed with a long lifespan. Hence, the PM and their engineering counterparts need to give a lot of thought about the current and future direction not only of the product but the APIs they produce.
In API management, PM now not only care about the end features provided, but also how those end features get to the customer… what your customer will be interacting with daily (the API) to get value out of your "whole" product.
Related to the longevity of the API is the usability of the API. This is somewhat subjective, but just as a PM should emphasize usability, a PM working on APIs must spend as much time on ensuring that the APIs are usable and follow standard convention.
Deprecating APIs can be a sensitive issue as it has a significant impact on customers. Changing your APIs from release to release can annoy our customers! Valid reasons for migrate to the new API include: - the old API is insecure, buggy, or highly inefficient - the old API is going away in a future release - the old API encourages very bad coding practices Not all of these reasons are of equal weight, yet deprecation is a reasonable (though not mandatory) choice in all these cases. Therefore, the use of deprecated APIs can never be made a hard error by default. Also, the deprecation comments need to help the user decide when to move to the new API, and so should briefly mention the technical reasons for deprecation. When a feature is deprecated, it is a good idea to notify the engineering organization of this fact, so that other engineers can respond to the change (pro or con) in a timely manner.
Other:
Do not underestimate documentation, sample applications, and if possible provide/support a "developer community".
I also recommend to read a book written by Mr. Luke Hohmann, he has detailed the complexities in handling SDK/API.
Can anyone highlights key issues involved in the Product Management of any SDK/API Kit Interface?
-
challenges
-
problems
-
benefits
-
Important key stakeholder involved around SDK /API kit usage. (I believe, it must be going to be the developer's/engineering team who uses! Who else?)
-
How your role is different than a 'normal' product manager?One difference I can definitely make out and that is, PM has to be technically very strong to be a product manager of any "SDK/API" interface.
-
-What else are the influencing factors?
Now let's look at challenges while actual managing SDK/API: it would be better if we touch up in the following points,
-
Pros/Cons of Providing SDK / API interfaces between two Enterprise services/product integration?
-
Existing SDK / API Problem / Challenges
-
Where the future trends of SDK / API interface development moving towards?
-
Other value added services/features, useful for the users of SDK/API.
-
SDK / API existence in the upcoming Software As Service (SaS) model
-
What else are the influencing factors?
I would appreciate if anyone can give any pointers addressing above points?
In October 2007 ZIGZAG Marketing conducted a survey to uncover common issues following a merger or acquisition, many of which have a direct impact on product management. You can view the results at http://app.e2ma.net/campaign/a0dd7aaa616dee8d3677629998fe34d8
Brandice Thorn Product Marketing Manager ZIGZAG Marketing, Inc. Learn. Execute. Grow. 3475 Lenox Road NE Suite 400 Atlanta, GA30326 Direct: (404) 601-2866 Ext. 1 Toll Free: (866) 797-3647 Web:www.zigzagmarketing.com
******************************************
PM 2.0
The Product Marketing & Product Management Newsletter
12.12.2007
We have three excellent articles for you in this issue.
Hope you have a great holiday season!
Brian Lawley & The 280 Group Team
To read this issue go to:
www.280group.com/insider/12.12.07.htm
CONTENTS:
* ARTICLE: Embracing Agile Development
* ARTICLE: Can you outsource product management?
* ARTICLE: Four critical success factors for your products
From long been, I was thinking about few questions. For some one point of view, it might look very stupid and novice.
However, I thought to share with you all.
Here we go,
1) How product manager should cut the line between setting up the priority of the features? (ex. Line between MUST HAVE or SHOULD HAVE or NICE TO HAVE)? Now the catch is, while we develop MRD/PRD; few features have been recommended by customer, few from services, few are from engineering, few may be very newer and innovative ....how are we going to decide priority for each of these? and would set "X" priority? and If "X" then why only "X" and not "Y"? (I know, its more situational and depends on customer demand and market conditions, but still is their any basics we can follow!)
2) Is their any generic strategy/criteria (Other than ROI), which we could apply while deciding up the priorities?
3) How are we handling/looking at the ROI of any feature we recommend as MUST HAVE?
4) And most importantly, What if feature we perceived as MUST HAVE is not being used by customer after actual release of product?
It indirectly means, our perception about feature was wrong! How to handle these differences?
Anyone would like to put up some thoughts on these !
These days, If we search google or search our own company repository, then we might come up with lot of document as well as links, which talks about these answers.
But I thought, should put on these queries @ group and also should listen to various views of other product managers !
My questions might sounds like as a novice user, anyways here we go.
Whenever we write any MRD/PRD, it doesn't become final at once. And this MRD/PRD has to translate through lot of iterations and then it become a final draft.
My Question is,
1) What a first DRAFT of MRD should contain? with respect to,
- Structure of document ?
- Main areas to be covered in the document.
- My MRD Index page
- *MINIMAL* content
- Total Categorization of features
- Unless HOT favorites features recommended by client and needed desperately, "Priorities" wouldn't be set in the fist draft
- etc...
What else should be added? What all should be part of first draft MRD and at what minimal level it should be part of draft MRD?
2) From any product point of view, what are the broad *GENERIC* categories, we should touch base while writing MRD.
Ex : Functional Features
Non-Functional
Scalability
Performance
Usability
Security
What other categories we should touch our base with?
3) If we apply above two principle to a sample business case. For time being, let's say we are delivering a product, which is dealing with "Data center automation".
On very higher/broad level view, how our first draft should look like?
Bottom line, intention behind asking this question was, i think MRD should be small and precise, rather than a huge story book!
I really think that writing a precise MRD is not less than an art!
But question was, how can we make it precise, small as well as fruitful?
Please don't hesitate to write me in case of any queries in understanding question.
Just a reminder that we will be holding a Webinar on Product
Management Productivity.
Hope you can join us!
Date: Friday, January 25, 2008
Time: 10:00 AM - 11:00 AM PST
Overview:
How to get twice as much done in half the time.
As a Product Manager, you will always have far more work than you can
possibly accomplish. Between thinking strategically to executing the
day-to-day tactical work required for product success, you will have
a full list of to-do items and plenty of requests that go
unfulfilled. This webinar will show you strategies and tactics for
being more productive, with the goal of increasing your output and
freeing up your time for high-level tasks, while at the same time
reducing your overall stress level.
To register go to:
http://www.aipmm.com/html/events/webinar.php
Hope you can join us!
Brian Lawley
President, 280 Group LLC
Author, Expert Product Management
The basic step in implementing total quality management is to judge the
organization's present reality. Organization's history, current
requirements, existing employee quality of working life...
http://www.brsx.co.uk/management/QMgmt/qmi.asp
As the business war on the air is hotting up with so many low-budget
airlines dominating the sky, the passengers can now enjoy the best
deals. The webguide - http://air.myguideforlife.com - helps you find
the cheapest and even free air tickets to make your journey ore
happier and very less expensive.
Visit the website now to find out how to get the cheap and free air
tickets: http://air.myguideforlife.com
As the business war on the air is hotting up with so many low-budget
airlines dominating the sky, the passengers can now enjoy the best
deals. The webguide - http://air.myguideforlife.com - helps you find
the cheapest and even free air tickets to make your journey ore
happier and very less expensive.
Visit the website now to find out how to get the cheap and free air
tickets: http://air.myguideforlife.com
The transition from traditional product planning and development to Agile has thrown many product managers into a tailspin, perhaps unnecessarily. Join ZIGZAG Marketing for a different perspective on the product planning and development process that compartmentalizes key differences between Agile and traditional processes and learn why the impact on product management doesn't need to be so drastic.
Product Development is usually leading the Agile charge and product managers often feel they're being dragged along, kicking and screaming the entire way. Join ZIGZAG Marketing to learn how Product Management can lead and orchestrate the Agile process and maintain control to ensure market and product objectives are being met.
******************************************
PM 2.0
The Product Marketing & Product Management Newsletter February 2008
To read this issue go to:
www.280group.com/insider/2.15.08.htm
CONTENTS:
* ARTICLE:
Where Should PM Report in the Organization?
* TRAINING: PM FAST TRACK TRAINING
Mar 31 to Apr 3rd, San Jose, CA
A four day comprehensive Product Management & Product Marketing
training seminar covering the entire product lifecycle that will make
you dramatically more effective and give you the skills, knowledge,
tools and templates to be more productive.
* WEBINAR: HOW TO ACCELERATE YOUR PM CAREER Wed Feb 20th, 9am PST.
Looking to move your career forward and get a promotion or a great
new job offer? In this webinar you'll learn tried and true methods,
tips and strategies for advancing your Product Management career.
From finding a mentor to working more efficiently to learning how to
manage your boss more effectively, this presentation will give you
the knowledge and insight to get on the fast track.
Details here:
http://community.featureplan.com/community/2008/02/webinar_february_20
_-product_management_career.php
* ANNOUNCEMENT: SOFTWARE INNOVATION AWARDS SoftwareCEO is holding the
2008 Software Innovation Awards. They are looking for software
companies that have shown true innovation with the products,
services, and business processes they've developed.