Product & Engineering direction
When a product, platform or API can evolve in several reasonable directions and the difficult part is understanding the trade-offs, technical constraints, compatibility and consequences.
Product · Software · AI · Organisations
Product decisions in complex software systems.
I work in Product, with a software engineering background. I’m particularly interested in decisions where product direction, technical constraints and the way teams build software affect one another.
This site brings together the ideas I develop, the experience behind them and the problems I occasionally help other software teams work through.
Start here
Selected notes
A short route through product decisions, AI in practice, and the way teams make sense of shared context.
- Waiting is one of the most underrated product decisions Product teams are often rewarded for shipping new things. But building something is not always progress. Sometimes the smartest decision is simply to wait.
- Designing for unattended development Unattended development is not the same as leaving an agent alone. It requires explicit eligibility, isolation, verification, stop conditions, and a separate decision about what may enter the stable codebase.
- Shared context is not shared understanding AI makes context easier to retrieve, but access to the same information does not automatically create shared understanding, alignment, or better decisions.
Questions I’m exploring
Three recurring questions.
Follow a question across notes, experience and selected external readings.
Explore all paths- How do teams make better decisions? Product decisions get difficult when several directions look reasonable. Information, trade-offs and timing often make the difference.
- How do people build shared understanding? Access to the same information does not guarantee alignment. Teams still need to interpret context, surface disagreement and build a shared view of the work.
- What changes when AI becomes part of the work? AI changes what people can delegate, how quickly work moves and what the systems around it need to support. I’m interested in what happens to the work around it.
Where I can help
Problems I occasionally help teams work through.
Alongside my product work, I occasionally collaborate with software companies when an independent Product & Engineering perspective can help clarify a difficult problem.
I focus on specific problems with a clear scope, using product context and technical evidence to clarify what matters, what should change, what can wait and what is already working well enough to preserve.
Software delivery and engineering systems
When architecture, testing, release practices or development workflows are making software harder to change safely and predictably.
AI adoption and AI-assisted development
When a team is trying to move from experimenting with AI to using it reliably in products or development workflows.
Featured series
Product Judgment in Practice
How product decisions get made when information is incomplete and every option has a cost.
Evidence, trade-offs, urgency, timing and disagreement before implementation begins.
7 episodes
Read the series
Experience behind the ideas
A path from software engineering to Product.
My perspective comes from moving between software engineering, product direction and developer-facing platforms, from a startup through global product organisations.
See the experienceAcross the site
Choose where to begin.
Read individual observations, follow a curated question or see the external ideas that shaped my thinking.
Contact
Continue the conversation
If a note here connects with a product, platform or team problem you are working through, I am always interested in comparing perspectives.
I’m also open to selected collaborations where product direction, platform evolution and AI adoption intersect.
The easiest way to reach me is via LinkedIn.
Based in Italy, working with teams globally.
LinkedIn
carlocaprini
(opens in new tab)
Product manager working across software, platforms and AI.