Make JTBD's central for Progressive Delivery
Goal
In order for us to effectively improve the product together with the user's needs in mind, we need to convert towards a more organized approach towards strategy which fosters collaboration, alignment, and acts as a focus point.
This approach will act as a foundation for us to expand upon in our own ways but with a shared understanding going forward.
We will become more effective in visualizing the value we bring to both our customers as well as our company.
Excerpt from "The Jobs to Be Done Playbook – Jim Kalbach"
JTBD helps shift a collective mindset, from focusing on the organization and its solution to focusing on customers and their needs. More than a particular method, JTBD offers a way of seeing your markets, your organization, and your strategy. It’s a way of reframing problems and solutions that I refer to as “JTBD thinking” or “jobs thinking” throughout the book.
More importantly, JTBD can help achieve alignment of teams in an organization. The common unit of analysis—the job to be done—provides not only a lingua franca across disciplines, but also fosters a new type of collaboration necessary for today’s fast-paced business world.
But in order for teams to have their work aligned, they need a shared focal point. JTBD is no silver bullet, but it provides a starting point for tying alignment to the customer with alignment across teams and departments. This approach goes a long way toward speeding up decision-making and reducing coordinate costs.
Example of future value
When we have laid the foundation for JTBD's and user stories, plus we have them documented/registered, we will no longer think about features either being done or not. Rather we will think about how user flows are currently performing over time and how we improve upon them. This opens up perspectives on what we can do beyond just our stage group/product and best create customer/business value.
Plan of action
-
Create a JTBD/Epic overview that will act as a template for us to work off from. -
Define JTBD's which are industry standard and apply them within the GL environment. -
Define JTBD's which are GitLab specific through research. -
Make sure the JTBD's are linked per category -
Define epics for each JTBD or edit existing ones. -
Define the individual user stories as new issues or edit existing ones and add them to the epics. -
Start
Artifacts
JTBD/Epic overview |
---|
Link |
Guides/Resources
UX scorecard video from Iain |
---|
Link |