Practical writing on product strategy, continuous discovery, delivery and AI tools for teams that want less disconnected work.
A practical way to measure Jira sprint carry-over, separate rolled work from scope change and run a retrospective without turning velocity into a people score. Includes a CSV calculator.
I made a list of everything the product does today and it came out longer than I expected. Instead of a bare feature list, each entry says why it exists and when you should actually turn it on - because half of what is listed here is not what your team needs on day one.
For years, most of my time went into preparing to think rather than thinking. That part is now automated, and three things are left: ask the right question, challenge the answer, make the call. A five-step loop, and why without the challenge step it produces bad answers faster, not good ones.
A practical plan for controlled Jira cutover: what to move, how to verify mappings and when to declare a new source of truth.
What does Jira Product Discovery really cost after Jira seats, creators and cross-product administration are included? Current JPD pricing, scenarios and when the Atlassian stack beats one connected Product OS.
What changes before Jira Data Center reaches end of life in 2029, when Jira Cloud Migration Assistant fits, and when a CSV move to another product system is more appropriate.
A checklist for teams moving from Jira to WorkThroughLine: migration ownership and scope, preflight without writes, mapping, a representative pilot, reconciliation and an explicit source-of-truth cutover. Includes a downloadable CSV.
A precise Jira data matrix: automatic migration, mapping and limitations.
Jira excels at execution. The problem starts when goals, discovery evidence and delivery live in separate systems.