Wednesday, February 26, 2020

Product management playbook 1

My first passion, and my first job before technology strategy is product management. While these two occupations are naturally intertwined, I miss the satisfaction of defining, curating, polishing a strategy, requirement sets, value proposition, positioning and see these finding their market fit.

I have recently helped a few tech companies in establishing or reinforcing product management functions in their organization and I thought I could share some of my playbook.


The roles of the product manager

Traditionally, product management functions are introduced in technology companies as soon as a structured process for receiving, categorizing and prioritizing market inputs to development teams is necessary.
A start up might develop a product or service based on its founder’s vision, but as soon as the value proposition is confronted to potential clients, new requirements emerge, gaps are identified and it becomes necessary to categorize and prioritize all these competing inputs into a coherent framework that facilitate the decision making process.
Product management is the result of scarcity of resources (engineering, hardware, software, time, investments…) and the ever-growing list of potential application of a new product or service (new clients, new geographies, new application, new market segment…).

The more interactions between the company and the market (clients’ meetings, competitive announcements, standards and technology evolution…) the more opportunities are identified for enhancing, evolving, adapting the product or service.
As the product matures, it invariably as well accumulates a technical debt, product of design and architectural concessions or compromises for time to market. This technical debt is a risk to be managed closely. As time goes on, the amount of correction, re architecture, rework that is necessary to correct a faulty initial design becomes extremely punitive.



The product management is responsible for knowing at any time, what the market needs, what the product can do today, what gap exists between these two positions and the level of risk the company is committing to when answering a RFP where gaps with the current offering exist.

How to prioritize requirements?


Every commercial company would like to think itself as market, sales or client oriented. Satisfying the client is the best and fastest way to generate commercial success. Unfortunately, there are many clients that do not know what they need, or that want something that is not what you can provide or that need you to adapt your offering to their proprietary environment to a degree that would make that product version only usable by them.

There are also companies that are differentiating through innovation, essentially creating a new product or market category. In that case, prospects are not necessarily the best guide for developing the product roadmap.

Technical debt is traditionally not a concept that sales or upper management want to concern themselves with. “Losing” time re architecting a product to deliver the same functionalities as today with months of delay can be perceived as a waste of time and commercial opportunity.

Evolution of standards, technology or competitive announcements have variable effect on the urgency to develop a feature vs. another, and the difficulty here is that the information is always imperfect, incomplete and requires a lot of analysis and experience to right-time the investment.
Bugs, errors, failures are always critical to solve when they affect a customer and their revenues, deciding on a workaround, a fix or a redesign is complex and requires a good grip on what the engineering team can produce and what to trade from the roadmap to deliver this.

These four examples are but a few of the decisions that a product management function have to grapple with. As a result, product management is unlikely to satisfy everyone. As the gatekeeper for product decisions, it interfaces with all the key functions in the enterprise and its decisions have an effect on all of them. For this reason, it is key that product management is completely aligned and supported by the management team and the CEO. 

Product management in the company

 The product management function is essentially a decision function. It must evaluate the market, the capacity of the engineering team and find the best market-fit for its product. It must be able to

  • create a value proposition, positioning and message for its product that is aligned with the company positioning and the market
  • translate market requirements into product, architecture and technology requirements,
  • create documentation and collaterals for sales support (brochures, infographics, white papers, business cases, presentations, demos…)
  • negotiate with clients, sales and sales support the roadmap, features, requirements, functional specifications, availability
  • negotiate with engineering the design, features, options, and availability
  • report to management team the product profitability, market position and market share…
  • Because of the range and variety of decisions involved, the product management function must traditionally report to the CEO, to ensure perfect alignment with the company vision, mission and priorities and to guarantee equal footing in negotiations and escalations resulting from its decisions. Because few in the company will know as much about the product, from a technical, strategic and commercial perspective together, product management is a position of trust and responsibility.

For these reasons, it is important that the methodology for receiving and cataloguing market inputs, translating and categorizing requirements, negotiating and recording results of discussions, communicating and reporting internally and externally be transparent, well understood by the management team and underpinned by strong processes.

Sunday, February 23, 2020

Telco growth: my objectives, vision, tactics, doctrine at Telefonica




As mentioned in my previous post, telco transformation through innovation and connectivity control requires a strong framework to guide the decision-making process. Here is a list of objectives, vision, strategies, tactics and doctrines that guided me through my time at Telefonica. I believe they can be adapted to many operators’ situation and organization to generate value through successful launch of new connectivity products.

Objectives:

  • Fast creation of new products and services by systematically leveraging economies of scale, reusing modular technical solutions and automation.
  • Creation of a toolbox of technological tools, operating models, best practices, documentation, blueprints, tests and certified solutions...
  • Deliver complete products, not just technology, but also operating model, suppliers value chain and devops teams...
  • Facilitate the transition from innovation to business
  • Systematically evaluate new technologies, suppliers in the laboratory and in the field
  • Fulfill our ambition to transform the industry


Vision:

Create a sustainable commercial growth factory for the company through the systematic research, implementation of services and products that achieve strategic, tactical, commercial, and technological advantages based on the network such as infrastructure or connectivity as a service.

Strategies:

  • Explore and classify services, market trends, competitive and direct and indirect movements and their technological evolution to identify risks and opportunities to create/destroy value for the company based on the network as infrastructure or connectivity as a service.
  • Creation or integration of network and IT technologies to disaggregate and control the cost structure of the purchase, implementation and deployment of connectivity functions and services.
  • Choice and implementation of disruptive connectivity services, products or businesses by designing the E2E value chain
  • Transfer of technological parts, services, products to commercial teams ready for production
  • Systematic identification of differential competitive advantages for the company and strategies to achieve their implementation
  • Implementation of innovative work and development methodologies, especially aimed at creating a DevOps/continuous development/continuous testing model for network technologies and connectivity services


Tactics:

  • Systematic disaggregation of high-level commercial systems and products of network and IT integration to identify manufacturers, intermediaries, sources of savings and their organizational and process impact
  •  Systematic prioritization of open source for MVPs, to learn the state of the art, limitations and development and integration needs
  • Projects, products, technology parts delivered with operating model, manufacturers / integrators / ecosystem developers
  • Identification and implementation of critical paths to deliver to the customer as fast as possible (MVPs, early prototypes deployed in commercial networks)


Doctrine:

  • Customer first
    • Development of services, projects, products with priority to the voice of the customer and the business over technology
  • One size does NOT fit all
    • Resist the model of trying to implement the same technology, solution, manufacturer for all parts of the network and all situations. Specification, design and development of technological and commercial solutions that are infinitely modular. Nothing monolithic, so that we can adapt the solutions to the realities of each market / segment
  • Always open
    • Technological development based on open models (APIs, standard and published interfaces, ...)
    • Open Source, wherever possible
    • Multi manufacturer and no lock-in by design
  • Modular, serverless when possible > micro services > containers > VMs > VNFs > PNF
  • Availability, generosity, active collaboration with commercial teams, third parties and transparency of communication
  • Systematic use from the design of
    • Data science
    • UX
    • Security
  • Agility, speed and results
  • Planning, development, iteration, continuous deliveries
  • Hypotheses, design, development, testing, ... Repeat
  • Pivot fast
  • Take calculated risks
  • Stop activities that fail to meet objectives
  • Organizational flexibility for team members to have diverse and multi-project responsibilities, and can also change during the life cycle of each project
  • Self-management and organizational structures with minimal hierarchy
  • Simple and cheap
  • Systematic simplification of legacy
  • Good enough, cheap > >  over engineered and expensive
  • DevOps
  • Continuous development



If you would like more details, feel free to reach out, I have developed an innovation / transformation workshop to put in practice some of these strategies.
Also available: