PRIORITISE ACCORDING TO STAGES OF GROWTH

[drob...@gmail.com]

Case

Online shop &

our product has got problems with stickiness. (Clients are creating accounts but not coming back)

So we prioritize our impact choosing as a priority only impacts that improve stickiness.

Question:

What about frauds issues e.g.

-accounts with many charge-backs

-bugs like "3 items and last items is for free" - not checking if the 3rd item is cheapest so: (pair of socks; pair of socks; coffee machine (is for free))

for me the issues are connected to the goal related to loosing revenue. Revenue goals are not important when we are in the Stickiness stage Yes?

How to approach this?

 

So What about frauds and the STAGES OF GROWTH tool?

Thanks for answer 

[Gojko Adzic]

When I use the stages of growth it's not a tool for ignoring everything else, but for providing focus. I tend to think about it as the selected stage is what we want to improve, without damaging the stuff important for other stages -- so you can improve stickiness by killing your revenue but that's probably not a good idea. likewise, you can later improve revenue short-term by making decisions that kill growth and usability in order to extract more money from a captive audience, but that's probably not a good idea. so use the other stages as a way to draw the box around potential solutions -- decide on the constraints that must be met by the initiative to improve stickiness. 

likewise, sustainability tasks and fixing urgent bugs shouldn't compete with the initiative to improve stickiness -- just budget a percentage of your capacity for sustainability-style tasks and do it during that percentage of each cycle.

gojko

--
You received this message because you are subscribed to the Google Groups "Impact Mapping" group.
To unsubscribe from this group and stop receiving emails from it, send an email to impact-mappin...@googlegroups.com.
To post to this group, send email to impact-...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[drob...@gmail.com]

Thanks a lot 

so one more question

So sustainability tasks and fixing urgent bugs are % budget and we just do it.

Question: 

Is there value in trying to ask for "what impact" is behind?

sustainability tasks and bugs.

Is there value in Impact Maps for those  % budget related to sustainability tasks and bugs?

How do you approach it?

Thanks

[Gojko Adzic]

the idea with the budget is that you don't really need to do a lot of prioritisation and estimation for those tasks, just do the ones on the top of the list until you run out of budget/time. so in theory it may be good to understand the impact in order to prioritise them, but in most cases I've seen the impact is obvious for urgent bugs (otherwise they aren't that urgent) and sustainability tasks all tend to be gradual improvements, so it's not that critical to select any particular order.

[drob...@gmail.com]

Ok so what in this case

1. We prioritize around impacts related to stickiness (clients of the online shop are not coming back)

2. urgent bugs and sustainability tasks in %of teams budget and time (separate backlog)

3. Q? What about feature request from the shop owner (making the shop owner life easier) like: more automated offers template creator. (impact: Shop Owner spends less time adding new offers)

[Ideas from Shop Owner he wants and pays for them. ]

should we:

- process those request parallel to the stickiness goal or

- work with the Shop owner to convince him to pay for the impact related to stickiness tasks

- put Shop Owner requests on hold (lose revenue)

What would you do?

[Gojko Adzic]

is the shop owner a persona/user segment or a key business stakeholder? if they are the stakeholder, offer them to cancel the current business goal work and switch to a different goal. it's their choice. if it's a persona/user group, then have a discussion with the relevant stakeholders is that goal more important than the thing you're working on now.