Skip to content

Commit 885e22e

Browse files
committed
Update 2024-08-01-good-product-strategy.md
1 parent 7e388ca commit 885e22e

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

_posts/2024-08-01-good-product-strategy.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,9 @@ This resonates deeply with me and feels like exactly what I’ve been aiming for
3838
### What makes a bad strategy?
3939
Sometimes, it’s easier to start with what a strategy *isn’t*:
4040

41-
- **It isn’t fluffy.** Some people argue that strategies aren’t supposed to be actionable, painting vague pictures that leave you unable to take action. That isn’t ideal. If it isn’t actionable, it isn’t meaningful
42-
- **It isn’t financial metrics.** Simply telling your teams to "increase revenue" isn’t a strategy; it’s a way to measure success. Instead, targeting X segment with Y value to achieve Z revenue—that’s a much better approach
43-
- **It isn’t how your teams collaborate.** Explaining how teams work together isn’t strategy—it’s more about topology. Team topologies define the purpose and relationships of teams. They’re important, but don’t mistake them for strategy
41+
- It isn’t fluffy. Some people argue that strategies aren’t supposed to be actionable, painting vague pictures that leave you unable to take action. That isn’t ideal. If it isn’t actionable, it isn’t meaningful
42+
- It isn’t financial metrics. Simply telling your teams to "increase revenue" isn’t a strategy; it’s a way to measure success. Instead, targeting X segment with Y value to achieve Z revenue—that’s a much better approach
43+
- It isn’t how your teams collaborate. Explaining how teams work together isn’t strategy—it’s more about topology. Team topologies define the purpose and relationships of teams. They’re important, but don’t mistake them for strategy
4444

4545
If you’re into team topologies, check out this excellent post by [Martin Fowler](https://martinfowler.com/bliki/TeamTopologies.html). It’s a fantastic read.
4646

@@ -52,10 +52,10 @@ Also, this [Marty Cagan piece on product strategy](https://www.svpg.com/product-
5252

5353
So, what makes a good strategy?
5454

55-
1. **It identifies a series of problems or opportunities**
56-
2. **It’s written in the order you’ll tackle them**
57-
3. **Each problem/opportunity has a diagnosis**. Breaking things down a little goes a long way
58-
4. **It includes a series of actions for teams to enact**
55+
1. It identifies a series of problems or opportunities
56+
2. It’s written in the order you’ll tackle them
57+
3. Each problem/opportunity has a diagnosis. Breaking things down a little goes a long way
58+
4. It includes a series of actions for teams to enact
5959

6060
Additionally, a good strategy should:
6161
- Be in plain English

0 commit comments

Comments
 (0)