During my sabbatical, I created an environment where insights gathered from navigating the corporate world could be put into practice — turning ideas into useful features, learning from their use, and progressively shaping my Product Management practice beyond theory alone.
Context — iaci.tech is the environment I created to address my own Product practice needs — with myself as its first user — and where I continue to apply and evolve that practice. It provides the foundation from which individual products and features can be developed around their own users, needs and outcomes. This page documents that practice for my own record and for conversations — it isn't a company, a client-facing product, or a pitch.
Share additional context on the Product work I have been developing and applying, and benefit from your perspective on this direction of professional development.
When I left the corporate environment, I risked losing the ability to practise Product Management and the institutional knowledge I had built over 20+ years.
A personal product environment to continue building, learning and preserving knowledge in a tangible way.
Release notes publishing was repetitive, manual, not scalable, and difficult to keep consistent.
Headless or coupled API-driven features to streamline feature delivery and keep the product alive with minimal friction.
Sequential release publishing was not enough. Priorities change, and reprioritisation should not impact roadmap integrity.
Ad-hoc prioritised releases that slot into the roadmap without breaking sequence or traceability.
Knowledge in Product Management, Payments and emerging domains (e.g. Agentic Commerce) was scattered and at risk of being lost over time.
Structured, extensible dictionaries to preserve and expand institutional knowledge beyond any organisation.
Many tools, no single place for a bird's-eye view of the product work leading to a feature release.
End-to-end visibility of lifecycle activities, deliverables and time per Epic — at a glance.