generated from vanHeemstraSystems/template-default-repository
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
11f1adc
commit ef46279
Showing
1 changed file
with
5 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# 500 - Give every map section an outcome-based goal | ||
|
||
Outcome-based roadmaps put the emphasis on the goal a deliverable is trying to achieve rather than the milestone a team are trying to hit. Spelling out outcomes and goals empowers a development and design team to build a solution, not meet another milestone. | ||
|
||
Story mapping is the design equivalent of that outcome-based roadmap. So when you combine the two, youʼll be onto a sure thing. Youʼll have the business onboard as theyʼll be able to see the exact problem youʼre solving for them whilst also seeing the design youʼve come up with to do it. You can do this by using the outcomes goals as story themes and using the linear progression of your story map to achieve more and more goals for the business. |