5 differences technical product manager from the business-oriented PM

Many probably encountered different versions and interpretations of the role and functional of the product manager. In large companies and start-ups today you can find strategically important employees of different levels related to product management, which are becoming more and more popular.
The role of the product manager in the company depends on the internal hierarchy and scope of activity. Somewhere one manager is enough, and in some large corporations a whole department can operate, in which there is Product VP, product director, product owner, product manager, junior PM or other positions. In the technologically-oriented companies and the field of software development, the position of technical product manager is increasingly encountered. How is it different from other product roles?
5 differences technical product manager from the business-oriented PM
how to develop a product strategy .
When you request a technical product manager on the social network LinkedIn, you can see that most of the managers found have a technical education or profile courses.

By the way, the number of proposed technical managers also indicates the great popularity of this position in companies.


How does the technical PM differ from the business-oriented product manager?

Before describing the differences, let's pay attention to the common points that the product manager and technical product manager unite: Both managers are responsible for the following:
Develop a global strategy and determine the vision of the product. Both managers need to take care of how to avoid mistakes in determining the strategy at the earliest planning stage.
Collection of ideas. Both PMs are responsible for generating and promoting the most useful and relevant ideas and initiatives.
Management of the development plan or roadmap. This is planning and prioritizing what, how and when the product team will implement. Technical product managers work with technological roadmaps, which have some unique functions, which are described below.
Definition of functions. Both managers work with the user and requirements of the product for planning the functionality in the future.
Release issues. Product managers and technical PMs work closely with multifunctional teams to ensure complete customer satisfaction and successful release.
Now let's define the key differences.

5 differences between technical PM and business-oriented

Product manager "general profile" is customer-oriented and participates in the definition of the overall product strategy. The technical manager, to a greater extent, focuses on the possibilities and modes of operation of the product or service that he /she engages in.
Product managers usually work closely with different departments and technical and non-technical team members. They work with marketers, sales managers, support staff, financiers, project managers, and also collaborate with external partners. Technical PM is more often in communication with internal technical teams, including developers, engineers and testers.
Carrying out professional research, the product manager studies the range of competitors from the point of view of strategic business and the product /service on the market, and the technical product manager thinks more about new development trends and technologies, assesses competitors in terms of their technical capabilities.
More often than not, the formation of a product manager is related to business disciplines, while the technical manager of a product is more logical to have a degree in engineering, computer science and other technical disciplines. His skills are useful for optimizing priorities and planning. If there is a clear idea of ​​how the product is developed, then managers can evaluate the risks of certain functions. Close contact with the developers helps to understand the consequences of certain decisions on the product and reach compromises.
Technical PM is well versed in the application of Agile or other methodology that they use. Many technical PMs come to product management from development and naturally know what is the difference between Scrum or Kanban , however, it is not worthwhile to go into complexity and spend time not on your key responsibilities as a manager.
Like any manager today, a technical PM needs certain online services and tools that help in the work.

Tools and services for technical PM

One of the main tools in the "clip" of the product manager is a roadmap or product roadmap. This is a strategic document in which they can plan product goals, fix ideas, short-term and long-term initiatives.
One of the first large companies that began to use the roadmap development plan was Motorola in the 1970s. Since then, more companies have begun to refer to this handy visualization tool.

What are the features of the technological roadmap and what is it for?

Technological roadmap (sometimes - technical) or technology roadmap is sometimes called the IT roadmap. This roadmap provides key information that helps IT professionals make better decisions about product technologies. A feature of the technical roadmap is that it is designed for developers.
You can even conduct a simple road map using MS Excel. However, complex IT projects and strategies require careful approach and application of special services with convenient functionality such as Hygger, Aha, Asana, Trello, etc. The development team and product manager helps to determine which technologies and when to apply, and Also visualizes the schedule for the introduction of new functions.
The use of technology roadmap is, among other things, a way to organize the work of a team. In software development companies, the key goal of road maps is to harmonize all engineering, IT, marketing and other issues by developing a common action plan using new solutions.
Technological roadmaps can differ in goals, strategies and team members:
developers roadmaps, internal IT roadmaps, architecture roadmap, software roadmap, hardware procurement roadmap, and others.

The two main advantages of technology roadmaps are

allows technical managers to effectively organize and prioritize all ideas, goals and requirements in the strategic product plan.
helps to present the strategic plan and its details to all participants with whom you will need to cooperate throughout the development process.

Components of the technology roadmap

Most often, the technology roadmap includes:
Product objectives Are the planned achievements that companies want to achieve. They can be short-term and long-term. The objectives of the product are based on its business opportunities.
New product features , which will be achieved and implemented through the application of technology.
The release plan is with support for new features and capabilities. Usually managers plan releases in a few months.
The main stages are or milestones are key reference points that must be achieved in the development process. Stakeholders track milestones, and this allows them to see progress in achieving long-term goals.
Resources Identify participants for the implementation and maintenance of systems.
Risk factors There are external and internal barriers that can impede the achievement of goals and milestones in accordance with the technological plan.
Status report helps to inform all team members.
For any road map, it is very important to share it. This opportunity is offered by platform for managing products Hygger.io .


Today you can meet companies in which the business-oriented product manager and technical product manager are actively working. But most companies still require one product manager.
Another important point is that the names do not always accurately reflect what people do. Perhaps, it is you who have all the prerequisites for becoming a technical product manager. In any case, regardless of names and roles, product managers must have all the professional skills necessary to perform all stages of product management and be able to use the technological road map competently.
+ 0 -

Add comment