Kory Stevens

Kory Stevens

Entrepreneur of the Year

About

Kory is from Burbank, CA where he grew up watching his parents navigate the fashion and food services industries. He is the second of four children and spent his high school singing in show choir, playing soccer and tennis, and being voted Most Likely to Succeed. He served a two-year religious mission in Cambodia from 2008-2010 and navigated countless emotional and physical hardships in the process.

Forums

•

2d ago

How to conduct feature prioritization audit without alienating important stakeholders

Refusing to fulfill internal feature requests made by sales and engineering departments results in a lot of compromising meetings and too crowded product roadmaps. Last month during our quarter planning meeting each department tried to convince that theirs pet project should be prioritized.

We solved this problem using a strict customer-impact score matrix based on real ticket tag data and churn feedbacks. Each of the feature requests needed to demonstrate that it lowers churn or fixes at least thirty customer tickets to get a spot on our next sprint.

Cleaning up low-impact roadmap features gave us three weeks of extra engineering time to work on product stability. Important decisions are always appreciated better when they are data-based.

Never approve any new feature request without reaching certain threshold of support tickets.

Google's new agent works on your product until a metric moves. Which one would you hand over?

An agent that chases a number will usually get you that number. I'd like to hear which of your numbers you'd be comfortable handing over, and which you wouldn't.

On 18 November Google Labs announced Stitch Loop, which it describes as a long-running product agent. I'm going by Google's own blog post, written by Justin Toupin, a director of product management at Google Labs. It's an experiment with a waitlist and I haven't used it. The post gives no pricing, no customer results and no stated limitations, so everything below is what Google says it does, not what anyone has seen it do.

The idea is that you connect your GitHub repo and your product context, meaning logs, user behaviour and feedback, through what Google says are over 180 integrations. Then you set up loops. Three come by default: security, latency and accessibility. You can add your own, and Google's example is improving checkout conversion.

Each loop has four steps. It suggests opportunities based on evidence from your product. It proposes one or more solutions with the tradeoffs. It builds the one you pick in a sandbox and opens a pull request. Then it watches the live data to see whether the number moved, and after the goal is met it keeps watching in case the metric slips.

View more