Skip to content

Fices for product thinking #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MrHinsh merged 2 commits into from
Feb 4, 2026
+2 −1
Merged

Fices for product thinking #314

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d6210d1
Fix image path for Logic Model in Product Thinking guide fixes #313
MrHinsh Feb 4, 2026
825755d
Add author Jeff Patton to Product Thinking guide fixes #312
MrHinsh Feb 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion site/content/product-thinking/2026.1/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ keywords:
author:
- Ralph Jocham
- Magdalena Firlit
- Jeff Patton
date: 2026-01-18T09:00:00Z
type: guide
lang: en
Expand Down Expand Up @@ -55,7 +56,7 @@ This reflection revealed a deeper truth: **output is not the same as outcome** [

This shift is not just about **what** is done, but about **why** and **for whom** it is done [^4]. Too often, teams obsess over delivery speed or process optimization while losing sight of the purpose behind their work. The original intent of Agile, when applied with the **why** and **who** in mind, forces us to ask: _How does this activity or output help customers and strengthen the company's future?_ That question grounds day-to-day work in long-term impact.

![Logic Model - Expanded Value Chain](/product-thinking/images/value-chain-feedback-loop.png)
![Logic Model - Expanded Value Chain](/product-thinking/2026.1/images/value-chain-feedback-loop.png)

This document explores that shift. Using the lens of the Scrum Guide Expansion Pack (SGEP) [^14] and frameworks such as Evidence-Based Management (EBM), this analysis explains why product teams should shift from focusing on activities and outputs to intentionally owning outcomes and impacts [^5]

Expand Down