Krista Rose King
I've learned a lot about building products by listening to customers, pestering smart coworkers with questions, and getting close enough to the work to break things myself.
I like complicated problems and the people who help make sense of them. I'm especially fond of finding ways to fix the recurring annoyances that take time away from more interesting work.
A couple quick brags
A few products and projects I've helped bring to life.
As coding agents change how software gets built, our team is rethinking a testing product designed around a visual interface. The challenge is supporting existing customers while making the same capabilities useful through MCP, CLI, APIs, and agent workflows.
Read case study →Mobile testing grew from customer discovery into a new product offering through work across product, design, engineering, and go-to-market teams. It reached roughly $1M in revenue in its first year.
Read case study →As engineering started shipping faster, the small PM team needed better ways to keep up. A set of connected automations helped organize customer issues, bring scattered feedback into backlog discussions, and keep customer-facing teams informed.
Read case study →Little nuggets from the noggin
Occasional thoughts on product management, AI, and working with people.
A product keynote, agents doing most of their work out of sight, and a demo that kept changing right up to showtime.
Read this nugget →Three conversations that changed how I think about product judgment when the technology underneath the work keeps moving.
Read this nugget →The agent vocabulary I’ve picked up over the past year, explained in the plainest language I can manage.
Read this nugget →Agents are much more useful when they can finish a task without stopping every few minutes. The tricky part is deciding which actions a team is comfortable handing over.
Read this nugget →Coding agents can make changes quickly. Teams still need a separate way to check that the change actually worked and did what the developer intended.
Read this nugget →When assumptions keep changing, a roadmap gets stale fast. I’ve been thinking about which parts of a plan should stay steady and which ones should be easy to change.
Read this nugget →More capable software gives people more ways to get confused when something goes wrong. Clear states, sensible defaults, and easy recovery still matter.
Read this nugget →Changing an established product means carrying current customers with you while the new model takes shape. Most of the hard part is in the sequencing.
Read this nugget →About
I started out in civil engineering, spent some time in UX and quality engineering, and eventually found my way into product. It's been a slightly winding path, but I've always liked understanding how things work, asking a lot of questions, and getting close enough to the details to be useful.
These days I'm at mabl, figuring out what software testing looks like when AI agents are writing more of the code. I spend a lot of time with engineers, poking at new ideas, and trying to make complicated things easier for people to use. I'm lucky to work with some very smart people who put up with my questions.