Your systems deserve to be treated like products, and you’re the one who owns them
InsideProduct helps businesses treat their internal software like a product, and gives the people who run it the practical tools to do it well.
Does this sound familiar…
You came up as a business analyst and became a product owner, and now you own a custom system with a backlog and a delivery team. But all the product advice you find assumes paying customers and a P&L that doesn’t apply to a tool your coworkers are required to use.
You didn’t plan to own this, but a CRM, ERP, or workflow platform landed on your desk on top of the job you already had. Now you have to make high-stakes calls about configuration, workflow, and what gets built next, with no backlog, no delivery team, and none of the rituals a product title is supposed to come with.
You started in marketing or on the web team, and now you’re responsible for a product customers use every day, inside a company that makes its money doing something else. You have real users, real reviews, and real drop-off data, but the product still gets funded and staffed like a marketing campaign because it isn’t what the company actually sells.
However you got here, you’re the one who decides what gets worked on and what gets left undone. The requests come from coworkers and stakeholders, which makes them harder to say no to. Organizations expect most people in your position to make that call and don’t provide a useful way to make it.
InsideProduct exists to fill that gap
Kent has a keen attention to where within the product lifecycle things may go wrong. His writing not only delivers the right message at the right time, it’s also practical enough to take action on.
Vanathy L.
What InsideProduct Is
InsideProduct is for the people who own an internal product: software the business runs but doesn’t sell, whether it’s built or bought, used by employees or by customers. I help you treat it like a product instead of a project through better discovery, sharper prioritization, and clearer decisions.
The InsideProduct Newsletter
On a regular basis: get practical techniques and real-life case studies for treating internal products like products, whether you built them or bought them, whether the people using them are coworkers or customers.
I’ve been a fan of Kent’s content for a long time. It was foundational reading for the start of my BA career and continues to be a go-to reference.
Mark Biro Jr.
Practical resources when you need them
Articles, frameworks, and tools covering discovery, prioritization, requirements, and adoption, organized for the people who own internal products and the teams that build or configure them.
If you’re the one funding the fix
Maybe none of this lands on your desk directly, but you’re the owner, COO, or operations exec watching system friction slow your business down. You’re trying to work our whether this is a tooling problem or a decision-ownership problem. That’s a different conversation, and one worth having before you buy another tool.
About Kent
I started InsideProduct because most people teaching product management have never worked inside an organization on software it doesn’t sell, and most who used to have stopped doing the work. I haven’t.
I’ve spent more than 30 years as a business analyst and product manager, including years at Wells Fargo, Principal Financial, and HD Supply, building and fixing internal software across a wide range of industries. I’m the author of Stand Back and Deliver, Beyond Requirements, and How to Be an Agile Business Analyst.
Right now I serve as Director of Delivery at Illuminated, where I help a growing advisory firm productize its core services and steer its AI tooling. I also work directly with the people who run software their organization depends on: advisory engagements that fix how build-or-skip decisions get made, and coaching for business analysts and product owners learning to decide, not just document.