Deliverables belonging to multiple Impacts/Impacts belonging to multiple Actors

[Piotr Włodarczyk]

Hi,

Can impacts be shared by multiple actors (1)? Can deliverables be shared by multiple impacts (2)? Or we should avoid such situations?

Regards,

Piotr

  

 

[jprit...@xanadu.ie]

Hard to comment without more context, but your deliverables will be something that will help change the behaviour of your actors in order to achieve the goal.
If you have deliverable(s) that multiple actors will use then I would suggest being more specifc around the actors involved,  try to keep your actors as specific as possible eg. "First time mobile vistors to the site looking to buy a technical book."

If this is tough, use a broader group eg. "First time vistors to the site". 

Just my opinion!

John.

***** Email confidentiality notice *****

Xanadu Consultancy Limited is a limited company registered in Ireland with registered number 500416 and VAT registered number IE 9793319P. Our registered office is at Floor 2, River House, Blackpool Retail & Business Park, Cork, Ireland. We have a branch office registered in England and Wales with company number FC030315, whose address is at Unit 710 Highgate Studios, 53-79 Highgate Road, London, NW5 1TL.

This message is intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. Do not use, copy or disclose the information contained in this message or in any attachment. Xanadu Consultancy Limited cannot accept liability for any statements made which are clearly the sender’s own and not expressly made on behalf of Xanadu Consultancy Limited.

[Gojko Adzic]

sure, but you may not need to completely show all the dependencies. I use maps to prioritise from the centre outwards, so choose one or two key actors you want to impact with the next milestone, and if anyone else gets impacted positively, that's an added bonus. for deliverables, the fact that something achieves two impacts offers a potential slice -- do enough to achieve the first impact, release, then do the remaining functionality to achieve the rest. so instead of technical dependencies, break it down into slices that solve smaller problems.

I wrote about slicing to solve smaller problems instead of slicing to deliver parts of a solution here, it might help: https://gojko.net/2017/01/05/user-stories-too-big.html

--
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.