wardley-maps-examples icon indicating copy to clipboard operation
wardley-maps-examples copied to clipboard

Arrow on evolutions going to the left

Open johnhearn opened this issue 1 year ago • 5 comments

The arrow head on evolutions that go left is pointing the wrong way.

image

The arrow should point left.

johnhearn avatar Apr 08 '24 15:04 johnhearn

Example:

component test [0.9, 0.2]
evolve test 0.1

johnhearn avatar Apr 08 '24 15:04 johnhearn

Hi @johnhearn

My understanding is that components don't generally de-evolve so such a thing wouldn't appear on a wardley map. Is that the intent?

Of course @swardley would be the person to confirm.

damonsk avatar Apr 12 '24 16:04 damonsk

That is correct. The only circumstance when something “de-evolves” is when competition is removed either through a monopoly or it has become redundant.

The far more common circumstance is when something is becoming a commodity BUT a vendor wishes it to remain a product or appear as custom built. Hence the two main forms are:-

  1. Something evolves to a more evolved state A -> A’

  2. Vendor pretends something is less evolved B -> B’

Both are covered by the existing format:-

component A [0.49, 0.64]

component B [0.36, 0.61]

evolve A->A' 0.8

evolve B->B' 0.3

From: damonsk @.> Sent: Friday, April 12, 2024 5:33 PM To: damonsk/wardley-maps-examples @.> Cc: swardley @.>; Mention @.> Subject: Re: [damonsk/wardley-maps-examples] Arrow on evolutions going to the left (Issue #2)

Hi @johnhearn https://github.com/johnhearn

My understanding is that components don't generally de-evolve so such a thing wouldn't appear on a wardley map. Is that the intent?

Of course @swardley https://github.com/swardley would be the person to confirm.

— Reply to this email directly, view it on GitHub https://github.com/damonsk/wardley-maps-examples/issues/2#issuecomment-2052091438 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAANE4JIJANN2BQE7UWAVLY5AEDPAVCNFSM6AAAAABF45W3L6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGA4TCNBTHA . You are receiving this because you were mentioned. https://github.com/notifications/beacon/ACAANE3IBLMJ7N4NAWSXUYTY5AEDPA5CNFSM6AAAAABF45W3L6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT2KBXC4.gif Message ID: @.*** @.***> >

swardley avatar Apr 15 '24 09:04 swardley

My situation is that my company wants to beat competition by gradually customising an existing product. How do I represent that?

johnhearn avatar Apr 15 '24 09:04 johnhearn

By way of example

title Our Plan

component The Market [0.67, 0.68] label [-51, -15]
evolve The Market -> Our Solution 0.3

annotation 1 [0.70, 0.51] In a competitive market, our aim is to "de-evolve" an existing product by either altering market dynamics or creation of some specific need such as status
annotations [0.12, 0.04]

Even if you achieve this, the competitive pressure will still ultimately drive the component back towards a product / heading towards a commodity unless you plan to restrict access to a select few i.e. altering market dynamics.

swardley avatar Apr 16 '24 15:04 swardley