Skip to content

2025

The Product Manager's View on Composability

Composable Definition and MACH

Composability, also known as Composable solutions or Composable commerce, is a design principle in which individual components or services are modular, independent, and interoperable. It allows them to be easily combined, reused, or replaced to build complex systems.

We have a custom-built core product for software businesses, whether a monolith or a set of microservices. In addition, you (when I mention you, I mean a product, area, or organization) have several external integrations with different levels of complexity.

For non-software businesses, several vendors of different scales have some in-house solutions. Those businesses are the primary beneficiaries, as Composable is a way to eliminate vendor lock-in and gain more control while also being flexible enough to adapt to market changes.

Composable addresses the latter case by using "best-of-breed" components available, whether market or house-built and adapting them according to business requirements.

To build such a miraculous system, you need middleware that connects several headless subsystems via API and provides governance and data consistency.

Stakeholder Alignment: The Underrated Skill Every Product Manager Needs

There is much buzz about whether AI could replace human product managers. I am not very concerned. Much of my work involves dealing with stakeholders at different levels and pursuing various objectives. AI will find it challenging to substitute that side of people interaction. I mean politics in a sense of power dynamics among multiple groups of stakeholders.

We don't like politics in the workplace, but it is inevitable when there are more than a dozen people.

Dealing with internal or external stakeholders always involves politics and personal-professional relationships. The larger the organization, the more complex the political landscape and the bigger the stakes.

The power dynamics impact everyone in the organization, including individual contributors. When an individual contributor (IC) transitions to a manager role, they become a part of the game without any choice.

New Chapter of Requirements & API - Workflows

A new chapter in the Requirements & API series is available.

The final chapter of my Requirements & API series is here! This article dives into designing and documenting hashtag#workflows, showcasing how to manage several API interactions effectively.

šŸ” Key Highlights:

šŸ–Šļø Using UML Sequence Diagrams to illustrate interaction flows across multiple actors.

šŸ–Šļø Exploring the new hashtag#Arazzo specification from the OpenAPI Initiative, which enables referencing existing OpenAPI operations to outline workflows step by step.

šŸ–Šļø Taking a look into ServerlessWorkflow, a powerful DSL for designing and executing workflows that support various protocols.

This was one of the most challenging articles to write, given the variety of notations and languages involved. But Iā€™m thrilled to share it with you!

Previous chapters:

Buy Me A Coffee