InsideProduct is shifting to the systems you work on
You haven’t seen an InsideProduct issue in a while. In that time, the work behind this newsletter shifted, and the newsletter needs to catch up to the work most of you do.
Most of you aren’t building shiny external products. You’re working on CRMs, workflow tools, ticketing systems, ERPs, and internal applications that keep your business running.
You’re the people your organization calls when the system is slow, confusing, or getting in the way.
Going forward, InsideProduct will focus on practical product thinking for the people who own and improve business systems.
That means:
-
Discovery aimed at understanding how people really work around the tools today rather than gathering requirements.
-
Prioritization to decide which system requests are worth doing now when everything feels urgent.
-
Techniques such as example mapping and story-based interviews applied to business systems and business workflows instead of customer-facing products.
If your title is business analyst, product owner, project manager, or “sort of the person responsible for the internal tools,” this is for you.
Over the next few weeks, the InsideProduct will cover:
-
Why most system changes don’t change anything
-
How to decide which system requests are worth doing now
-
What a good systems practice looks like in a growing business
If that matches the work you’re doing now, hit reply and let me know what system(s) you’re wrestling with.
If you signed up mainly for classic product or BA content and the new focus is no longer relevant, no hard feelings if you need to pare down the traffic to your inbox.
Thanks for reading,
Kent
