Happy Friday! This week I started a new series around Mapping and Strategy and I’m excited to announce the start of a second series I’m calling #fasterfridays. FASTER is an acronym for a method I developed to help organizations deliver faster (it stands for: Form, Align, Sequence, Test, Execute, Realize). The heart of it is a combination of Lean and Agile techniques, and this series is designed to share short videos around these topics you can use in your teams and organizations.
This week’s video covers how you can approach challenging prioritization or ranking sessions by thinking about the terminology just a little differently. You can watch the video below, and I’ve also included a complete transcript at the bottom. If you’re interested in finding out how to apply this to your organization, don’t hesitate to reach out via Twitter or email hello at coryfoy dot com. Have a great weekend!
Happy Friday! Welcome to a new edition of FASTER Fridays. In todayâ€™s video, I wanted to share a little terminology trick I use to help teams and organizations figure out the order they should do work in. Letâ€™s bring up a little backlog. It looks good! We have post it notes, and things on them. But one problem – what order should we do them in? Does it matter?
Typically weâ€™d call the notion of ordering things â€œprioritizationâ€. Which is good! We should understand from a relative perspective how important work is. But Iâ€™ve been a part of more than one prioritization session where multiple items end up with a priority of â€œ1â€ – or whatever weâ€™re using to indicate the top most thing. For example, preventing fines is a pretty critical initiative, but so is being able to close more sales.
To sidestep this, I separate out the notion of prioritization from sequencing. In other words, we absolutely should know how important the work is, but we also need to know what thing we should tackle first. And that might not always be the top most item.
For example, letâ€™s imagine we have a backlog of features we want to tackle. We prioritize them and even manage to not have duplicates. But then we ask – is this the order we should go after these features? As we discuss them, we realize that a lower ranked feature would actually cause some unblocking of key system debt which would enable higher ranked features to be done more quickly. Or we have a higher ranked feature which has a dependency on some system which has a delay we canâ€™t unblock. Itâ€™s even possible something is higher ranked because of negative connotations (maybe fines or some other bad outcome) but lower ranked features actually generate enough revenue to cover the bad outcomes for a little while.
So next time you are struggling with a prioritization session, let the duplication happen, and then talk about sequencing. You might find it changes the conversation into something much more productive!
If youâ€™ve enjoyed this, feel free to check out all the Faster Friday videos on my blog, or reach out on Twitter at Cory underscore Foy or via email at hello at coryfoy dot com. And be sure to come back on Friday for another Faster Friday!