Business 2.0

December 20, 2007

How to decide priority of the feature?

Greetings everyone,

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 !

Thanks,

-Yogesh

December 12, 2007

Must have features for product?

There was a discussion going on for “what are the MUST HAVE use would like to see in a mobile?

I felt I should write my thought process on this, here we go!

Let me clear one thing, I don’t have any feature suggestion, However I felt I should still share this thought process. 

I think, we should ask following questions to ourselves before we decide the MUST HAVES!

 ·         What’s the greatest thing user like about any mobile? In my opinion, one of the key factor user would be looking is  “USABILITY”! 

 ·         Why people were crazy about ‘i-phone’? or for that matter any product from apple?I think, USABILITY is very very important factor whenever we consider any product in “retail consumer” market.  

·         I have even seen people changing their mobile models but don’t change their mobile company? Why?  the most probable answer would be usability … the way they “USE FEATURES” 

·         Now looking at usability, again we can drill down with few more questions!

 ·         Can we know any customer who have used or currently using *ALL* features provided by a “Product”?

I bet, we would not find many :( Again in my opinion the key is, customer doesn’t use 100% of the feature provided by product. (If you have a customer, then I believe you/your product goes into luckiest list ;) 

·         Then next question comes, If we consider that 90 % of customer doesn’t uses “ALL” feature then what most likely feature they would use? 
 
Or 
 
·         What’s “HOTTEST” feature they use? and why?  If we search the result, we might end up with 80/20  result!

It means 80 % of consumer uses “COMMON” 20 % of the features. and i think, that’s what are the MUST HAVE !  

·         Now If consider 20 % features, they might say, I can ‘write SMS easily/effectively”  now would you consider this as must have? ;)

If anyone has any other thought process or would like to criticize, please share your thoughts.

 -Yogesh

December 6, 2007

Product integration issues post merger or acquisition?

Filed under: Acquisition, Articles, Integration Issues, Merger, Product, Product Management — Yogesh Hublikar @ 3:32 pm

There was a survey done by ZIGZAG Marketing, which was based on common issues companies
experience following a merger or acquisition.

Here is the survey results, might help you.

-Yogesh

===========================================

ZIGZAG Marketing recently conducted a survey to uncover the most common issues companies experience following a merger or acquisition. Many of these issues have a direct impact on product management and product marketing. The survey was conducted in October 2007. Over 200 professionals at all levels responded to the survey. We’re pleased to present the results.

Post-Acquisition Survey Results

1. My company has been through a merger or acquisition

Within the last 6 months 34 %

6 months – 1 year 13 %
1 – 2 years 14 %

More than 2 years 39 %

2. Before the merger or acquisition was finalized:

Strategy & Operational Plans were finalized for the combined
companies 14 %

A strategy was completed but no operational plan 28 %

Only an operational plan was completed 15 %

Neither 43 %

3. Please rate the following post-merger/acquisition challenges from 1-8 with 1 being the most challenging:

1. Debates on technology platforms

2. Technical integration of products

3. Lack of consensus on target markets

4. Mixed marketing messages

5. Communicating across remote locations

6. Ineffective/divided sales force

7. Disagreement on product direction

8. Aligning people to support a new organization

9. Other

4. Now that you have the benefit of hindsight, what would you have done differently?

Most Popular Answers:
• Better planning and faster merge implementation
• Challenge people to align with strategy or leave
• Get a clearer operational plan in place along with a product direction.
• Better communication of strategic direction throughout the company
• More time planning & strategizing
• More emphasis on how to integrate (infrastructure & culture) of acquired businesses!
• More upfront planning, more aggressive cuts upfront
• Communication announcements weekly
• Push for a 3 year integration plan with milestones, accountability, and measurable results
• More face to face meetings, faster decisions on product platforms and sales territories. Celebrate and communicate early wins.
• Spent more time focusing on the right management
• Build better communications plans
• Ensure the target market and sales strategy was aligned from day 1
• Better planning and communications
• More effort to combine sales forces
• Leave the acquisition as a standalone business unit and NOT try to integrate each of its departments into the acquiring organization.
• Look at situation for what it was, not what it promised to be
• Read Who Moved My Cheese beforehand
• Integration of sales teams, clear market messages, operational plans, etc.
• More planning. Better communication with rank & file on company direction
• Should have left the company earlier

5. My role in the organization is:

Senior Executive – CXX, SVP 13 %

Senior Manager – VP, Director, Sr. Mgr 48 %

Manager 28 %

Engineer 2 %

Other Staff Professional 9 %

————————————————————

Do visit this site for more information: http://www.zigzagmarketing.com/

==========================================

November 30, 2007

Want to create innovative Products? Tap into global brains!

Filed under: Annoucements, Articles, Innovation, Inspirational, Product, Product Management — Yogesh Hublikar @ 4:35 am

Folks,

Here is an interesting article i came across about “Want to create innovative Products? Tap into global brains!” .

It gives lot insight into how innovation works at globally and how it should happen!

http://knowledge.wharton.upenn.edu/india/article.cfm?articleid=4244

Happy reading!

 -Yogesh 

November 28, 2007

Innovation or Surprise? Google, Microsoft, and The Red Sox

Filed under: Annoucements, Articles, Innovation, Inspirational, Interests — Yogesh Hublikar @ 9:50 am

Here is an article published by HBS.

 ————————–

I am writing this post on a crisp Fall morning, in a world in which Google stock has crossed $700 per share, Microsoft’s tiny stake in Facebook values the company at $15 billion, and New England’s beloved Boston Red Sox have won their second World Series in four years. If any of you can explain any of that, I’d love to hear from you in the comments section of this blog.

The only conclusion I can draw? We are living in a world full of surprises. As a company, you never know who’s going to emerge as your most important rival. As an innovator, you never know where the next great idea is going to come from. As a long-suffering baseball fan, you never know when an 86-year old drought is going to turn into a dynasty.

Indeed, that surprising reality defines the new leadership frontier for executives, entrepreneurs, and game changers of all stripes. More than ever, the most powerful source of business genius isn’t the strategic brainpower of an individual CEO or the technical chops of an inspired engineer. It is the “hidden genius” of grassroots innovators inside your organization, and the collective genius of all kinds of talented people outside your organization. Increasingly, the best ideas come from the most unexpected places.

That’s what Goldcorp’s Rob McEwen learned when he invited the whole world to help him figure out where his company should explore for gold. As an entrepreneur, Rob bought a low-performing gold mine, spent years trying to find gold where the previous owners couldn’t find it—and only succeeded when he shared his proprietary geological data with the outside world and organized an open competition to devise the best drilling strategies.

That’s what shoe designer John Fluevog learned when he applied the lessons of open-source software to the creation of high-heel shoes and knee-high boots, in a program he calls open-source footwear. He unleashed the talents of passionate customers around the world, who have designed a bunch of hot-selling new models for the hot-shot designer.

That’s what the founders of Rite-Solutions learned when they decided to create a “stock market” for ideas inside their fast-growing software company, and let anyone in the organization float an idea (in the firm of a stock), and everyone in the organization invest in ideas that they like through $10,000 of opinion money.

These are just a few examples of this game-changing approach to leadership and innovation. Have you figured out how to navigate—as a company, as an executive, as an entrepreneur—in a world in which the most powerful ideas come from the most unexpected places? Don’t be surprised if that emerges as your next big challenge.

———————

Role of Product Manager @ SDK/API Management

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”.

November 20, 2007

Are Product Managers Born or Made?

An interesting webinar @

http://www.featureplan.com/recordings/webinars/requirement_management_07_09_26_dance/requirement_management_07_09_26_dance.html

-Yogesh

September 12, 2007

Article: Recruiting Product Managers

This was copied from ‘The Silicon Valley Product Management Group’ by Marty Cagan…————————-Probably the single most common question I get from CEO’s is where
to find great product managers?
I tell them that often they’re already in their organization, hiding
under a different title – maybe a software engineer, designer, or an
SE – just waiting to be discovered. But whether you recruit product
managers from inside or outside, the easiest way to spot them is to have
a clear understanding of the characteristics to look for. So in this
note I’ll enumerate the specific traits and skills you’re
looking for:

Personal Traits and Attitude

Most skills can be learned, however there are some traits that are very
difficult to teach, and as such they should form the foundation of any
search for a product manager.

– Product Passion

There are some people out there that just love products. Not
necessarily every type of product, but also not just a single type of
product. Great product managers have a love and respect for good
products, no matter where they come from, and they live to create them.

This passion for product is an essential ingredient as it will often be
called upon to provide the motivation to get through the many very
difficult challenges, and long hours, of defining a great product.
Further, the product manager will need to inspire the rest of the
product team, and the passion for a product is contagious.

It is fairly easy to determine whether or not you are talking to such a
person by simply asking them what some of their favorite products are
and why. It is hard to feign passion; the insincerity comes through.
Ask for examples from different domains. Ask what they would improve on
their favorite product if they were the product manager. Ask about bad
products too.

– Customer Empathy

The ideal product manager does not necessarily have to come from your
target market (there are pros and cons to this), but they absolutely
need to be able to empathize with your target market. This trait is
often difficult to find in high-technology companies trying to produce
mass-market products. We tend to want to think of our users as we think
of ourselves and our friends. However, the target market very likely has
quite different values, priorities, perceptions, tolerances and
experiences.

Ask the candidates about the target market, and how they believe they
might be different from themselves. Try and detect how the candidate
feels about the target market, and most importantly, does the candidate
respect and empathize with that target market, or does he view his job
as “enlightening” the target market.

This is doubly important for international products, or those products
targeted at specific countries or cultures. There are many
similarities, and many differences, between cultures. Many of the
differences are incidental and not important to defining products.
However, some of the differences are essential. Does the candidate you
are talking to have enough understanding of the target market to know
which is which?

– Intelligence

There is really no substitute for innate intelligence. The successful
product manager must be able to learn very quickly. Product management
is about insights and judgment, both of which require a sharp mind.
Hard work is also necessary, but for this job, it is not sufficient.

Hiring very smart people is harder than it sounds. Much depends on the
strength and security of the hiring manager. Hiring smart people speaks
to the company culture which is another important topic in its own
right, but suffice it to say here that if your goal is a truly good
product, it is simply not going to happen if you can’t find a truly
bright product manager.

Assuming you are anxious to find the brightest, most insightful person
possible, one technique is to drill in on problem solving. Microsoft is
famous for their very intensive and effective interviewing for
intelligence based on problem solving. The technique is to use one or
more experts in some topic to drill the candidate on a problem. The
interviewer is not looking so much at whether or not the candidate
simply knows the right answer (knowledge rather than intelligence), but
rather, how well they deal with not knowing the answer. How does the
candidate work out problems? When the candidate comes up with a
solution, the interviewer changes the question somewhat and asks what
the candidate would do then. This is done continuously until the
candidate must force herself to deal with a scenario she doesn’t
know the answer to, and then she is asked to verbalize how she would go
about solving that problem. With practice, this can be a very effective
technique in assessing a candidate’s problem solving capability.

Another approach is to ask two or three people in your organization who
are well known for their intellectual prowess, and ask them to interview
this person, and help you determine the candidate’s problem solving
ability.

– Work Ethic

Not every role in the product team requires the same level of commitment
and effort. However, the product manager role is not for someone who is
afraid of hard work. It comes along with the responsibility. The
product manager is the person ultimately responsible for the success of
the product, and this burden weighs heavily on the successful product
manager.

Even when skills such as time management and the techniques of product
management are mastered, the successful product manager is still
consumed with the product. Can you have a family and a non-work life
and be a successful product manager? I believe you can. At least once
you have some experience. But there are many people that want to be
able to work 40 hours a week and most importantly, leave their work
problems at the office when they leave at the end of the day. This
unfortunately is not the life of the successful product manager.

I believe in being very frank with candidate product managers about the
level of effort required for successful product management. But to be
perfectly clear, it is not about requiring the product manager to work
certain hours – if you have to actually ask or tell the product
manager to come in during a critical point you have the wrong person for
the job.

It should also be emphasized that the level of effort and commitment is
not uniform throughout the lifecycle of the project. There are certain
phases that are much more intense than others. What won’t change
for the successful product manager is the degree to which they care and
worry about their product and the lengths they are willing to go to
ensure its success.

– Integrity

This trait also relates to the company culture, but of all the members
of the product team, the product manager most needs to reflect the
values of the company and the product. In most organizational
structures, the product manager does not directly manage the people on
the project team, and as such, he can’t simply direct the people to
do his bidding. Rather, he must work by influencing those on the team.
This persuasion is done by mutual trust and respect.

This trust and respect is built over time by the successful product
manager demonstrating the traits and skills of a strong product team
leader. If the product manager is not perceived to have integrity, or
honesty, or fairness when dealing with his teammates, then the product
manager will not have the degree of collaboration and team effectiveness
that he needs to get the job done.

The product manager may not be an expert in every role of the product
team, but he should have a deep understanding and respect for what each
team member is responsible for, and he should be willing and able to
trust those people to do their job.

As the main interface between the product team and both the executive
team and the sales organization, the product manager is often put in
difficult situations, such as being asked to deliver products earlier,
or with special features for large customers. The product team will
watch closely how the product manager handles these situations.

As with intelligence, assessing someone’s integrity can be
difficult. For candidates with previous experience as product managers,
they can be asked about how they dealt with the stresses in past
products. Press for details of particular situations; what made the
situation hard and how was it dealt with?

– Confidence

Many people think of confidence as a result of experience. However,
while experience may be a prerequisite for confidence, many very
experienced product managers simply do not project confidence (you can
sometimes find brand new college graduates simply bursting with
confidence, although this is generally the confidence that comes from
not yet knowing what they’re in for).

Confidence becomes an important trait in that the entire product team,
executive team and sales organization is looking to the product manager
to convince them that what they are investing their time and money and
careers in will be successful. There will be many difficulties along the
way, and during these times of stress especially the product manager is
looked to for inspiration.

It is important that the product manager be able to project confidence,
to be able to remind the team and organization why the product will be
successful, and why the vision is a good one. In communicating
persuasively, confidence is a critical ingredient.

– Communication Skills

While communication skills can, for the most part, be learned, it can
take years to become an effective speaker or writer, and these skills
will be required from the start. As discussed above, the product
manager influences others by persuasion rather than authority –
making his case by communicating either through writing, speaking, or
both.

Speaking skills can partially be assessed during the interview itself,
but written skills should be assessed specifically. I like to suggest
that product manager candidates bring in examples of written material
such as white papers or strategic documents.

While good communication skills are absolutely essential, it is
important to emphasize that speaking with an accent, or minor
grammatical issues with a non-native language, do not constitute poor
communication skills. The person must speak clearly enough to be easily
understood, and write powerfully enough to persuade, but perfect
pronunciation or grammar is not required.

– Attitude

The successful product manager sees himself as the CEO of the product.
He takes full responsibility for the product, and does not make excuses.
The successful product manager knows he is ultimately responsible for
the success of the product. More importantly, he knows that there are
many very valid reasons for the product to not ship, or fail in the
market when it does – the product is too difficult to build, it will
take too long to get to market, it will cost too much, it will be too
complicated, etc. – but he knows it is his job to see that each and
every one of these obstacles is overcome.

This does not mean that he micromanages the product team, or that he
tries to do it all himself, but rather than he is quick to take the
blame if something goes wrong, and equally quick to give credit to the
rest of the team when it goes well. The successful product manager
knows that it is through the rest of the team that his product vision
will become a reality, but that it is his product vision they are
building.

Skills

In order to succeed at the job of product management, there are several
skills that are important. If the person has the right personal traits,
I believe all of these skills can be learned:

– Applying Technology

One reason many successful product managers come from the engineering
ranks is that a big part of defining a successful product is in
understanding new technology and seeing how it might be applied to help
solve a relevant problem.

While you don’t need to be able to invent or implement the new
technology yourself in order to be a strong product manager, you do need
to be comfortable enough with the technology that you can understand it
and see its potential applications.

There are many ways to develop this skill. Taking classes, reading
books and articles, and talking with engineers and architects can all
help you learn. Ask the senior engineers on your product team what they
would recommend as ways to learn more about the technology
possibilities. Brainstorming sessions with the engineering team is
another way to learn how new technologies might be applied.

– Focus

“The main thing is to keep the main thing the main thing.”
There are so many distractions out there, especially for the product
manager trying to create a product that customers will love. The ability
to keep the focus on the key problem to be solved, and not to succumb to
creeping featurism, or the loud voices of a few key people or customers,
requires tremendous discipline – both company discipline and
personal discipline.

The truth is that nearly every product has features that are not really
all that important – if the features were never there it would not
significantly impact the sales or customer satisfaction. Much more
often, if the features were not there, the product would be better for
it as more users could comprehend and appreciate the resulting simpler
product. Focus will help you reduce the number of cluttering features,
reduce the time it takes you to build the product, and therefore the
time it takes you to get to market.

– Time Management

In today’s e-mail, instant message, and cell-phone based world, it
is so very easy to come in to work early in the morning, work
frantically all day even skipping food, and then head for home well into
the night, not having actually accomplished anything important for your
product. That is because you have spent the day chasing fires and
working on “urgent” items.

It is absolutely essential to get very skilled at distinguishing that
which is important from that which is urgent, and to learn to prioritize
and plan your time. If you can’t manage to get the time to focus on
those tasks which are truly important to your product, your product will
fail.

I have known too many product managers that burn themselves out with
70-hour weeks and the worst part is when I tell them that they’re
not actually doing their job. The natural response is that they just
don’t have any more time and can’t work any harder. I then go
into my lecture on time management and working smarter. So much of what
these people spend time doing is avoidable.

– Written Skills

Product managers spend a great deal of time writing – composing
e-mails, specs, white papers, strategy papers, data sheets, competitive
product reviews, and more. The successful product manager is only
taking the time to write these if he believes people are going to read
them, and since they are going to be read, they need to do their job
well, which is typically to describe, educate and/or persuade.

Being able to write clear and concise prose is a skill that product
managers use every day. The successful product manager realizes that the
readers of his writings are constantly evaluating him based on his
writings. Especially with senior management, sometimes these writings
are all they have to go on.

– Presentation Skills

The other major form of communication that product managers frequently
need to do is a presentation. Presenting in front of a group is hard for
many people. Presenting effectively is even harder. Yet this is an
important skill for a product manager since many of the most important
events in the life of a product require the product manager to stand up
in front of company executives or major customers or the company sales
force and in the short time you have, explain what your product is about
and why it is important.

We have all sat through terrible presentations, with slide after endless
slide; the speaker simply reading the bullets; people straining to read
the too-small print; meaningless graphics; and being unclear what the
key messages actually are and why you should care.

In contrast, the successful product manager has a minimal number of
slides; he is engaging, clearly knowledgeable and passionate about his
product, he speaks clearly and to the point, his slides provide relevant
supporting data for what he is saying, and he has unambiguously stated
his main points, and what he needs from the audience after the
presentation. His presentation finishes early, he entertains questions
and if he can’t provide a clear, useful answer immediately he
follows up diligently and promptly with the questioner, and if
appropriate, the entire audience.

– Business Skills

Finally, business skills are also important for the product manager. As
the main interface with the rest of the company, the product manager
will need to work with company finance staff, marketing people, sales,
and executive management, and the language and concepts that these
people deal with.

I sometimes talk of product managers as needing to be bilingual. They
need to be able to converse equally well with engineers about technology
as with executives and marketers about cost structures, margins, market
share, positioning and brand.

This is one reason why so many product managers are recruited out of
business school. The product organization knows that they need someone
that can talk the language of the business side, so they hire an MBA. I
have known some great product managers that have come through the MBA
path, but if you’re read this far, you know that the business skills
are but one part of the mix required for a successful product manager,
and they can certainly be learned. It is at least as common that an
engineer moves into product management and acquires the business skills
required by reading books, taking courses, and getting coaching and
assistance from mentors in the finance and marketing organizations.

So where do you find these people?

After reading this list of traits and skills, you may be thinking that
such people are extremely rare. They are rare – about as rare as
good products are. But few hires you make will be as critical as your
product managers, so it is worthwhile to interview for these
characteristics and to set the bar high.

There are different schools of thought on recruiting product managers.
Many companies think that all you need is someone from the marketing
organization or someone with an MBA. In the old-school definition of
product manager as product marketing, this may have been true, but this
is a recipe for failure today.

Many companies prefer MBA’s from top business schools that have a
technical undergraduate degree combined with applicable industry
experience. This can work well if you keep in mind that a problem with
MBA programs, even from the top-tier schools, is that they almost never
teach product management, so it is dangerous to assume that the recent
MBA grad has any idea of how to be a product manager.

My favorite source for product managers is to look for people with the
characteristics described above and then use training, an informal
mentoring program, and/or a formal employee development program to
develop these people into strong product managers. Such people might be
found virtually anywhere in the company. I’ve seen outstanding
product managers come out of engineering, technical support,
professional services, product marketing, sales, and the user community.
Often these people will approach management asking how they can get more
involved in the product. It can also be useful for senior management to
approach top performers from across the company about the possibility of
product management, as this can be essential experience for those on an
executive track.

I’ve written earlier about running a good interview process
(www.svpg.com/
blog/files/microsoft_advantage.html), but there have been
some great posts on general hiring practices recently. My favorite is:
http://blog.pmarca.com/2007/06/how_to_hire_the.html.

** Did you find this article useful? If so, please consider forwarding
this newsletter on to your colleagues.
You can find related articles at www.svpg.com/articles/articles.html.

Personality Types in Product Management – Survey

Filed under: Annoucements, Articles, General News, Product, Product Management, Survey — Yogesh Hublikar @ 5:20 pm

 A new survey was posted at http://www.blackblot.com/surveys.shtml .  This anonymous survey explores the link between the Myers-Briggs Personality Type Indicators and the various roles in product management.  Before completing this survey you must determine your Myers-Briggs personality type indicator. To learn more about the Myers-Briggs personality type indicator, please visit The Myers and Briggs Foundation.  There are several abbreviated online tests that are based on Carl Jung’s and Isabel Myers-Briggs’ methodology. Average time to complete an online test is twenty minutes. Examples below:
Personality Test #1 (statments approach)
Personality Test #2 (questions approach)
  
 

‘Unlocking Value’ at Microsoft

Filed under: Articles, General News, Product, Product Management, Sales — Yogesh Hublikar @ 5:18 pm

Following article has been published in the business week @ http://www.businessweek.com/bschools/content/jun2007/bs20070607_329811.htm Here for your reference.—————–After getting a Kellogg MBA, this nontechie became a software product manager in Redmond. Here’s a typical day Scott Buchanan
Product Manager
Microsoft
Kellogg, MBA Class of 2006
What happens after you’ve created an exceptional product? Well, you have to get your customers to buy it, use it, and ideally, love it. That even holds true for something as ubiquitous as Microsoft Office software. I am the product manager responsible for Microsoft (MSFT) office deployment and adoption. In a nutshell, my job is all about unlocking the value in our products. For example, you can only experience the value of a chocolate chip cookie once you “deploy” it to your mouth or the value in a pair of running shoes once you “deploy” them to your feet. It’s the same with Office software&emdash;our customers only realize the value of Smart Art, real-time editing, and other features once our technology is “deployed” on their computer. My job is to develop strategies and tools that make the job of deploying and adopting our software as clear, simple, and inexpensive as possible. In my post-MBA job hunt, Microsoft was not the most obvious fit—I’m not a very technical guy. On my first day at Microsoft it took me 30 minutes just to find the latch to open my laptop (though I did successfully find the “on” button pretty quickly). I think that’s why my MBA at Kellogg has played such a vital part in my career development. Success in my role isn’t about understanding technology, it’s about understanding the customer. You see, many of our customers buy our products, but then delay deploying them. You can imagine that updating Microsoft Office across all the computers in a 10,000-person organization is a huge task that requires a lot of technical support and a lot of money. So, I need to figure out how to leverage our thousands of field sales personnel and partners to make deployment as straightforward as possible for our customers. I also have to figure out how to connect with customers directly, to convince them that every day they delay deploying Microsoft Office they miss out on real business value. In both cases, this takes a clear understanding of their functional (bits, bytes, deployment tools, etc.) and emotional (superstardom, frustration, support, etc.) needs, and ultimately, clear and simple messages about the value of Microsoft Office. With field, partner, and customer interests constantly in play, each day is pretty darn busy. Here’s an idea of how a day typically shakes out: 6:54 a.m.—Hop in the car and head to the Microsoft campus. Plug my Zune media player (shameless product plug) into my car stereo and sing loudly to keep myself awake. Getting out the door before 7 a.m. is crucial to beating the positively brutal Seattle-area traffic. 7:28 a.m.—Wade through e-mails. Throw some random fist pumps. 8:02 a.m.—Run the latest Microsoft Office deployment numbers by country. Identify those countries that are falling behind pace. E-mail local management with ideas on how they can close the gap. 8:39 a.m.—Scoot over to the Executive Briefing Center (EBC) to talk with a group of customers about the business value of Microsoft 2007 Office. Every day, executives from dozens of companies (and countries) attend all-day presentations at the EBC to learn how Microsoft products can help their business. 9:45 a.m.—As I walk back to my office I take a moment to daydream…. I run into Bill Gates and he says, “Scott, I’ve been thinking. I’m going to be working on the Gates Foundation full-time in two years, and I need someone to lead the company. Steve Ballmer is a fantastic, high-energy guy; but your hairline is far better. I think you have what it takes to lift Microsoft to the next level.” Almost hit by car. Snap back to reality. 9:58 a.m.—Quick one-on-one meeting with my director to review current projects and get some more direction on a scorecard I’m developing to track our team success… See Full Version —————————————-Comments: 

  • @ Matthew W. I. Dunn Aug 27, 2007 4:31 PM GMT Amen to J’s comment! My frustration threshold has just about been reached with MS’s products. As a consumer –and, not a tech geek or product manager or whatever — I don’t like how MS products tells me what I should be doing, rather than allowing me to do it. I write intensively. When I went from Word 2000 to 2007, I knew there would be a learning curve: But, I shouldn’t have to relearn aspects of a program I’d been using for 7 years! Word 2000 wasn’t perfect, but I never felt like it was impeding what I wanted to do, which was write. Now, with 2007, I understand what people mean when they complain about “wrestling” with MS products. It’s not a good sign of value when a customer thinks about getting rid of your product and re-installing an older version of it . . . or, worse, when he really starts to consider giving a competitor a shot at impressing him.
  •  
  • @ software guru Jul 31, 2007 1:03 PM GMT These comments seem a bit harsh; as the author said, his job is much more about business and “soft skills” than about technology. As long as he uses his soft skills to enable succesful deployments , he will be succesful. Mentioning that Windows can be installed on XYZ OS and platforms won’t cut it- bring in the techo geeks for that one ( don’t worry, Microsoft has plenty of them as well).
  •  
  • @ J Jul 19, 2007 10:29 PM GMT I spent 17 years at MS, starting in the late 80’s. This guy is the emblem of why I left … unlocking the value starts with defining what customers want and it doesn’t end when the software is installed on their system – it ends when they use the features and would actually choose to recommend the software to a colleague/friend – or be excited about buying another product from you – which hasn’t happened at MS in a long time.

 

Older Posts »

Blog at WordPress.com.