I build products by working with an AI agent as my primary tool - not by writing every line myself - for the whole loop: scoping, deciding, shipping, and learning from what happens next.
Twenty years in tech, most of it before “AI-native” was a phrase anyone used. Developer, then tech lead, then product owner, then COO - twice - then, this year, senior product manager for GenAI. Each step added a layer without dropping the one before it. I still read code. I still think in systems. I just do it now with an agent doing most of the typing.
That combination - technical depth plus product and operating experience - is why I build instead of spec. A PRD tells someone else what to make. An agent lets me make it myself and find out what's wrong with the idea a day later instead of a quarter later.
Alongside the day job, I've spent the last three years mentoring - 20+ people, from interns to C-level, on leadership, operating cadence, and staying productive without burning out. It's mostly one-on-one, built around whatever the person in front of me is actually stuck on, not a curriculum.
“I'm already envious of the colleagues at whatever company Michał joins next.”- Katarzyna Berbas, Managing Director
A context management system for teams building with AI - so context is captured on purpose, not reconstructed after the fact.
A survey tool that lives inside your AI agent instead of a browser tab. Both creating and answering happen through MCP.
A Matomo plugin with 39K+ downloads, and the open product blueprint behind ez-pollster.
“Product Owner” - field notes, mistakes included, from ~4 years in the role.
Leadership mentoring, in mentees' own words - interns through C-level.
A lightweight Context Management System for teams building with AI.
Most AI projects start from a pile of Jira tickets and Slack scrollback standing in for real context - the decisions, constraints, and reasoning nobody wrote down. The agent doesn't have it, and three weeks in, neither does the team.
CxMS is my attempt at making product context something you actually capture, maintain, and share on purpose - not something you reconstruct after the fact, badly, right when an agent needs it most.
It's in closed beta right now. I'm building it in the open - the calls I'm making, what's working, what isn't - mostly on LinkedIn.
A survey tool that lives inside your AI agent instead of a browser tab.
Both creating and answering surveys happen entirely through MCP - no forms, no browser flow for respondents, no separate app to check. If you and the people you're surveying already work through an agent, the survey should too.
I open-sourced the product thinking behind it, not just the code: a full blueprint with positioning, decisions, features, and build sequence - ezpollster-blueprint. Feed it to your own coding agent and build your version from it, not a copy of mine.
That's the actual pitch: not “here's my repo,” but “here's how I thought about it - go think about yours.”
I publish some of what I build - not everything, but the parts worth other people picking up.
Matomo (Piwik) plugin · GPL-3.0
A URL shortener that lives inside your Matomo instance instead of as a separate tool - create shortcodes for any tracked page, redirect through Matomo, and get usage stats, including external-link attribution, in the same reporting UI you already use.
The open product blueprint behind ez-pollster - positioning, decisions, features, build sequence. Not the code, the thinking.
Co warto wiedzieć o tej roli, a mało się o tym mówi.
I wrote this after nearly four years as Product Owner at Brand24, during the company's move to agile. I went looking for what to expect going in and mostly found tool lists, certifications, and courses - not much about the actual texture of the job. So I wrote the version I wished I'd had, mistakes included. If “Owner” is in the title, the failures should be owned too.
Role or position? Why treating PO as a role - not a title - changes how you show up, and the “missionary vs. mercenary” split in how people lead.
Thinking in systems. Everything in a product is connected; decisions in one corner ripple everywhere else.
Getting your footing in a new org. Reading the org chart, the stakeholder map, and your own gaps before you start making calls.
Responsibility. Why authority has to be earned through owning outcomes - including the bad ones - not claimed on day one.
No sentiment in business. Budget is time, time is the team's hours, and every product decision is quietly a budget decision.
The iron triangle. Scope, cost, and time trade off against each other - “the best solution” almost never exists, only the best one for this situation.
What a PO actually needs to know. A working map across analytics, strategy, UX, marketing, customer success, leadership, sales, and technology - not mastery, just enough to ask the right questions.
Taming the chaos. Automation, delegation, time-blocking, and a task-list system that survives a day full of interruptions.
Plans vs. planning. Why a roadmap is a living, regularly-updated best guess, not a promise carved in stone - learned the hard way after promising three features on fixed dates and delivering one.
Transparency, inspection, adaptation. Scrum's three pillars, applied past Scrum - to 1:1s, to habits, to basically anything you're trying to steer.
63 pages, free to read.
Three years, 20+ people - interns through C-level.
Leadership, operating cadence in small and mid-size companies, Agile/Lean adoption, team building, and staying productive without burning out. It isn't a program with a curriculum - it's mostly one-on-one, built around whatever the person in front of me is actually stuck on. Here's what a few of them said about it.
“Michał guided me through an intensive four-session mentoring process that turned out to be incredibly fruitful and inspiring. With his support, I learned how to set and achieve goals effectively, work with my team more efficiently, and plan the growth of my company in the medical field, spanning physiotherapy, dietetics, and training.”
“I wholeheartedly recommend Michał as a mentor to anyone looking to grow their company and sharpen their management skills. His professionalism, commitment, and passion make working with him an investment that’s sure to pay off.”
“Michał is an exceptional professional who combines deep knowledge and experience in his field with strong business acumen and soft skills. […] During our mentoring sessions, I valued his honesty and communication skills. […] What mattered most to me was that the sessions were tailored to my needs - we worked through the real problems I was actually facing.”
“We worked using Scrum and OKRs, and Michał trained me in these frameworks to the point where I feel comfortable implementing them from scratch on my own. […] He's also a big believer in accountability, transparency, and candour, and brought much needed change to the company by living these values.”
“He helped me grow both as a manager and more generally, as a professional. Above all, he's an empathetic, dependable colleague, and a pleasure to work with!”