Skip to content

Recent Publications

Pending Backlog Items Have a Price

AI-generated nonsense

For future plans, please don't create one-liner tickets in your backlog.

The only excuse is when you must "proof" some future work. I knew a project manager in an outsourcing project who told business analysts to create 500 Jira issues to showcase to a customer the scope of work for continuing a development team's assignment.

In recent years, I have been dealing with massive backlogs of outdated items written by people no longer around. That has resulted in painful and time-consuming reviews and (re)-negotiations with stakeholders.

If you have such experience at least once, you are likely a fan of focused and precise backlogs like myself.

New Chapter of Requirements & API - Design

A new chapter in the Requirements & API series focuses on structuring each layer to design an API. This time, it is more practice-oriented, with examples of an HTTP API call and its OpenAPI definition.

I am in the hallway through that series. Almost a year ago, I did two webinars on the topic. Those articles help look deeper into the topic, which is better done in writing.

I originally planned to retell my material from offline and online events. However, reality is different, so there are many deviations and extensions.

So, two more chapters will come, and the topic will be closed. I have been writing and talking about APIs since 2022. I continue working as a product manager on the API Platform, and the articles about APIs get more attention from the audience than anything else.

So enjoy reading on Medium (friend link)

Or here: Design

Previous chapters:

  • in Media
  • 1 min read

BArszawa Blog #6 (September'24) is Back!

Here is the next blog edition of our Business Analysis Community in Warsaw: BArszawa Blog #6 (September'24)

What is inside:

  • Community updates from recent events "Offer of the Dream" and "What's in the Box?".
  • A mini-interview with insights about SAP implementations.
  • A bunch of useful materials.

Previous BArszawa editions:

PM Onboarding - Same Organization, New Area

cover

Onboarding is a crucial process of incorporating a new person into a team, product, or domain (for simplicity, let's generalize all that as "area"). The purpose is to align or increase performance as soon as possible after the unavoidable drop due to a structure change. If approached wrongly, it may cause substantial trouble, especially when you dive into a new area as a product manager (PM).

Whether it is a new or same organization, new role, or new area - the approach to onboarding will vary. Here, we talk about horizontal growth within an organization, keeping your role but acquiring a new "area" (for simplicity, let's use this term to generalize one or several products, teams, lines of business, etc). That is the situation I am currently in, so I have something to reflect on. Also, most onboarding guides focus on vertical growth with a new role in another business. So, it is a good topic to uncover.

I follow the patterns of 3 key knowledge types in product management suggested in the "Building Products for Enterprise" book (I wrote about it here): organizational, product, and market knowledge. So, let's construct the onboarding strategy for each.

TRANSFORMED - Some Thoughts After Reading

Book cover

I finished reading "TRANSFORMED: Moving to the Product Operating Model" by Marty Cagan. This is not my usual a few thousand-word review—rather, it is a few aftermath thoughts.

You, as a reader, need to set the right expectations. If you read "INSPIRED" and "EMPOWERED," plus follow the SVPG (Silicon Valley Product Group) blog and watch Marty's interviews (which is my case), then you will find nothing new here.

This book is a logical continuation of Marty Cagan's previous works, focusing on organizational transformation. It streamlines the recent SVPG narrative into a single digestible source, empowering you with comprehensive knowledge.

With all that in mind, I consider "TRANSFORMED" a worthwhile and valuable reading.

If you are not familiar with Caganverse, I can still recommend it. However, you must read the previous books to get the complete picture. It touches on many topics that were explained before but without self-quotation. So this is an excellent point at which to start the journey.

I need to mention a shitty feeling you might have after reading those books:

  • "INSPIRED" trials, whether I am doing product manager work or a masked backlog administrator.
  • "EMPOWERED" makes you question your product leadership and whether you can become such a product leader.
  • "TRANSFORMED" questions the integrity of your organization and its capability to undergo such a transformation

I am convinced that triggering those feelings is intentional. I reflect a lot while reading, so it takes me longer to complete these books.

The "Product Operating Model" is a set of principles, not a framework or guideline, to transform your organization into something more innovative in shiny armor. That book is also for product coaches and others interested in the org-level transformation by:

  • Changing how you build
  • Changing how you solve problems
  • Changing how you decide which problems

These 3 points are enough to characterize the model and the book.

I like the transformation stories, especially ones told by people who participated in them, and the chapter about overcoming objections from different parties. While reading, I was also trying to put myself into an executive shoes who wants to transform a large enterprise. The author says it is a tough endeavor where external help is needed.

Is this book an advertisement for the SVPG consultant services? No, it is not.

It is a tool to popularize the Product Operating Model, a form of evangelism to encourage organizations to change their ways of creating valuable and commercially successful products. No certification is required to start applying those principles.

Only time will tell whether that model will spread around the world and scale, changing the way products are designed, developed, and delivered. Meanwhile, enjoy the book!

Best Book I Read in My Career - "Product Management in Practice" by Matt LeMay

Book cover

It was a sunny day in 2019 when I found myself in the largest bookstore in Dubai, surrounded by a sea of books. I had three hours to choose my next read, a decision that would shape my professional journey. After careful consideration, I picked up "Product Management in Practice" by Matt LeMay, a choice I've never regretted, even though "Building Products for the Enterprise" was a close contender.

Even though I read and appreciated both books in the end, that choice impacted my career without any doubt. At that time, I was a business analyst in an outsourcing software development company who desperately wanted to become a product manager in a product organization.

I can't say that the book made me a product manager. But it definitely impacted me as the professional I am today - for better or worse (I hope for the better). I read it 3 or 4 times while transitioning from a business analyst to acting as a PM. Each time, I was surprised at how much wisdom was placed in that slim book and how differently I looked at some things throughout the years. It is like a peaceful harbor, and you want a return after fighting yourself through multiple storms.

In 2024, I realized that the 2nd edition was published in 2022, so before writing this piece, I enjoyed reading it. There are many changes compared to the previous version, but it is the same brilliant book. Here, I will talk about the 2nd edition.

If it is not the best, then it is one of the best books about product management. Below, I will prove my point.

  • in Media
  • 1 min read

BArszawa Blog #5 (May'24) Edition is out!

Here is the next blog edition of our Business Analysis Community in Warsaw: BArszawa Blog #5 (May'24)

What is inside:

  • Community updates from recent events and further plans.
  • My exclusive article about the so-called "death of UML."
  • Useful materials about dealing with anxiety, AI risks in cybersecurity, producing the best documentation, and more.

FYI: The BArszawa blog is taking a well-deserved summer break. But don't worry. We'll be back with more exciting content! Stay tuned!

Previous BArszawa materials:

Product Manager: Year Three

I almost missed a point of reaching a three-year tier in my product manager career, which nearly matches with ten years in IT. I wrote essays about my previous years (year one, year two, combined article on Medium) as a retrospective of my thoughts and feelings.

I had doubts about whether I wanted to write the continuation. I re-read previous pieces, which made me realize I needed to continue. First, the "Sophomore Year" was quite depressing. Second, I need to finish the series, and having that as a trilogy sounds right.

I don't say it will be optimistic than a previous one. A bit brighter, maybe. And most probably, the last. Writing that in a third time felt more like an obligation.

Anyway, it is time for a retrospective of my 3rd year of being in product management.

Platform engineering and product management

Last year, I had an identity crisis because my job seemed to be far away from what is written on product management. It coincides with general terms, but the devil is always in details.

Then, I realized that platform engineering and product managers who are working on Internal Development Platforms (IDP). There is a community, books, webinars, courses, and tools around that. Many people are doing similar things I am trying to do and have similar problems.

About My Writing Routine

Here is my writing routine: the way how I structure my research on various topics and then write an article.

It is not my usual type of content, but it might be helpful to someone. And yes, I need to fill the vacuum while working on two new writing pieces: a book review and a new topic.

Writing Tools

I use Obsidian as a knowledge base and content management. It is free, keeps your data in your hands, not in a vendor cloud, uses Markdown for formatting, and has a variety of great plugins. 

The latter is handy as my blog is also built with the MkDocs engine based on the Markdown format. So, I keep writing and editing in Markdown, which is very convenient. I don't particularly appreciate it when each tool tries to reinvent the wheel with its custom formatting, which is incompatible with anyone else. With Markdown files stored on my local machine and my cloud storage, I can quickly grab them and migrate them to another tool.

I use the Zettelkasten technique in Obsidian when I research something and need to document some information and my thoughts to reference it later. You can find a lot of information about this approach. I keep my notes connected with tags and internal references where possible. Obsidian provides a nice graph where I can filter out some notes and track references.

Once a year, I clean up by editing, merging, or even deleting some notes. So, I try to keep the number of my Markdown notes from spreading. You can see a part of the notes graph in the attached image below.

Graph view

  • in Media
  • 1 min read

BArszawa Blog - April’24 Edition is out!

A month has almost passed, so here is a new edition of the BArszawa blog, where I serve as a contributor and editor: BArszawa Blog - April’24 Edition

What is inside:

  • Updates about recent offline and online events
  • Announcements of exciting events happening in May (no BArszawa events yet, but that will come soon)
  • Useful materials on a wide range of Business Analysis and related topics
  • Exclusive review of a recent IREB Conference in Warsaw from Olga Rapoport
  • Link to a survey to get feedback on our blog from our dear readers

Previous BArszawa materials:

Take care,

Ilya