Kellet Atkinson

Every team is a little different, but based on my experience, generally this is how things typically get divided up: Product: Responsibilities: Feature specs / use-ca...

Generally, the most logical approach is to divide up KPIs according to the user journey, and reserve a few top-level KPIs as shared KPIs. For instance, a generic user jou...

This is fundamentally a question about driving technical quality improvements through data-driven decision making. Let me break down the approach...First, let's clarify t...

When thinking about KPIs, it starts with understanding your customers and the value you expect to create with your product:Think, first, in terms of outcomesOutcomes = Wh...

I'm not sure there's a good, one-size-fits-all answer for this question. OKRs (objectives and key results) are meant to drive behavior change and create focus for your ...

This is a challenge all organizations face as they scale. Most of my experience is in startups, and I know first-hand how hard it is to transition from instinct to data-d...

If you want to create metrics to hold a product team accountable, there are a few things to keep in mind up front:If the goal is accountability, the person accountable sh...