You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2024-08-01-good-product-strategy.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,9 +38,9 @@ This resonates deeply with me and feels like exactly what I’ve been aiming for
38
38
### What makes a bad strategy?
39
39
Sometimes, it’s easier to start with what a strategy *isn’t*:
40
40
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
44
44
45
45
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.
46
46
@@ -52,10 +52,10 @@ Also, this [Marty Cagan piece on product strategy](https://www.svpg.com/product-
52
52
53
53
So, what makes a good strategy?
54
54
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
0 commit comments