Los mapas de Wardley

Que son los mapas de Wardley

Los mapas de Wardley es una técnica que lo ayuda a examinar un entorno dado, identificar los próximos cambios que van a ocurrir y ayuda a elegir adecuadamente las acciones a tomar. Al examinar qué se necesita, qué componentes se utilizarán, cuáles son sus dependencias y características, se puede construir una representación visual de su mundo, jugar a juegos hipotéticos y elegir su dirección y las mejores acciones para apoyarlo.

Hace poco me di cuenta que llevo usando esta técnica desde 2013 y que conozco los planteamientos básicos de su uso, pero que echo en falta dos cosas fundamentales:

  • Ahondar más en los detalles de la técnica.
  • La inexistencia de una comunidad en español que conozca los mapas de Wardley.

Con ello, me he propuesto traducir parte del contenido de los mapas de Wardley al español, para tratar de mejorar los dos puntos mencionados anteriormente.

Principios y partes de la traducción

  1. El libro, que originalmente está en publicado en medium lo trataré de traducir lo más cercana posible al original, solo adaptando situaciones personales y contenido relevante para aprender sobre esta técnica.
  2. Mapas de ejemplo, herramientas, otros recursos: documentaré algunas cosas que existen e iré añadiendo cosas conforme las vaya usando (mi falta de tiempo es un impedimento importante, ….bueno, como a todos).

Actividades (Kanban)

1.- A realizar

  1. Buscar plug-in sobre rutas o completar cursos.
  2. Buscar plugín sobre conversaciones.

2.- En progreso

  1. Crear contenido y traducir el libro (aquí).
  2. Divulgar la página por las redes y contactos.

3.- Completadas

  1. Hablar con Simon acerca de llevar a cabo este proyecto (hecho).
  2. Crear un entorno donde colgar la documentación (aquí).

Tabla de contenido del libro hasta ahora (Simon continúa escribiendo capítulos)

  • Licencia (hecho)
  • Capítulo 1 – Al estar perdido (hecho)
  • Capítulo 2 – Encontrar un camino (hecho)
  • Capítulo 3 – Explorando el mapa (hecho)
  • Capítulo 4 – Doctrina (hecho)
  • Capítulo 5 – La jugaday la decisión de actuar (hecho)
  • Capítulo 6 – Comenzando usted mismo (hecho)
  • Capítulo 7 – Encontrar un nuevo propósito (en progreso)
  • Capítulo 8 – Manteniendo a raya a los lobos (a realizar)
  • Capítulo 9 – Trazando el futuro (a realizar)
  • Capítulo 10 – ¡No esperaba eso! (a realizar)
  • Capítulo 11 – Una mezcla heterogénea de lo poco útil (a realizar)
  • Capítulo 12 – El escenario (a realizar)
  • Capítulo 13 – Algo malo viene por aquí (a realizar)
  • Capítulo 14 – Sé fiel a ti mismo (a realizar)
  • Capítulo 15 – Sobre la práctica de la planificación de escenarios (a realizar)
  • Capítulo 16 – Super Looper (a realizar)
  • Capítulo 17 – Hasta el infinito y más allá (a realizar)
  • Capítulo 18 – Más por menos (a realizar)

 

Recomendaciones?

Si tienes alguna recomendación sobre lo que debería hacer o mejorar, dímelo.

Year 3, Learning about Raspberry PI and Wardley Maps Q3

A change of content

I feel I need to rest of the financial investing journey I’m doing. I have been thinking about an alternative and I found out that I have a Raspberry Pi in a box that I have still not used. So for this quarter I will try to learn about what can I do with it.

A friend that is going to help me with the Raspberry told me that it will not take so much time, so I should look for other things to learn. I’m not sure about it, but let’s start with something and let’s look for another initiative, just in case.

The alternative learning thread will be focused on Wardley maps. I have used for a long time (I started with them in 2013), and I have the feeling that in the Spanish word it does not have more impact because the language is still a high barrier for some people. I have been thinking about it since some while ago: it’s to translate Wardley maps content into Spanish.

Year 3, Quarter 3

As usual these are the goals for this quarter, following the V2MOM model:

For the Raspberry Pi:

  • Vision: start using the Raspberry Pi.
  • Values: have fun, learn a lot, do practices and more practices.
  • Method: set it up, find a couple of use cases and make them work.
  • Obstacles: Time.
  • Measures:
    • Install OS on Raspberry PI.
    • To have a couple of use cases that are implemented at home: pi-hole and another one to be defined.

For the Wardley maps translation:

  • Vision: have a place with Wardley maps content in Spanish.
  • Values: have fun, learn the details of the different chapters published.
  • Method: set up a place,translate and adapt the content when required, publish some of the maps I did.
  • Obstacles: Time.
  • Measures:
    • Build a place to document about Wardley maps.
    • To have at least 5 chapters ready for publishing.
    • Complete the initial content of the website.
    • Add at least 3 maps I have done to Spanish.

Death line = 30/September/2020

Results (October, 2020)

  • Raspberry PI.
    • Install OS on Raspberry PI (not done).
    • Pi-hole up and running (not done).
    • and another one to be defined (not done).
  • Wardley maps (specific updates here (in Spanish) ).
    • Build a place to document about Wardley maps (done).
    • To have at least 5 chapters ready for publishing (done).
    • Complete the initial content of the website (done).
    • Add at least 3 maps I have done to Spanish (done).

Wardley map for Infrastructure environment

I have been working on a value proposition for a major deal where the customer is looking for a technological partner that enables them to unblock a set of challenges they are having on their data centers.

The customer’s main pain points are highlighted in red, the links between assets are drawn in blue, and the green lines shows the expected benefits for a given user.

All the improvements are implemented through a project, and in the business case there are some interim steps before to achieve the expected state.

Serverless

Serverless is a buzzword

It points to the future of software development in a post cloud world.

The idea of “Serverless” is NOT about removing the servers completely (or you couldn’t use the internet at all), but essentially paying for services that mean that someone else manages the servers for you thereby reducing maintenance load.

It’s all about reducing the obscurity of cost.

Spend control is a necesary evil that enable the organizations to understand where they are allocating their resources. The allocation of the limited resources at the best place of the organization will enable itself to be more competitive.

Total cost of Ownership (TCO) enables to understand the end to end amount of resources that an visible element consumes at its whole lifecycle. When calculating the TCO, there are always assumptions required as not all costs are direct costs that clearly you can assign to a single asset.

Here is where serverless shows up.

The reduction in obscurity of cost through serverless will change the way we develop, build, refactor, invest, monitor, operate, organise & commercialise almost everything.

The idea is to move to a scenario where you are performing the billing per function, where you are investing as much as possible on visible value for your organization, reducing the OPEX as much as possible, and having understanding about where your resources are allocated.

Simon Wardley did a map that illustrates the case:

Source: https://serverless.zone/serverless-is-just-a-name-we-could-have-called-it-jeff-1958dd4c63d7

Serverless Framework

It is a free and open-source web framework written using Node.js. Serverless is the first framework that was originally developed for building applications exclusively on AWS Lambda, a serverless computing platform provided by Amazon as a part of the AWS.

From the framework, it birh Serverless, that is a toolkit for deploying and operating serverless architectures. Focus on your application, not your infrastructure.

 

 

 

Etherium ecosystem

Simon Wardley says related to maps: practice, practice, practice… so here there is a practice.

The map

Development environment

  • Solidity: is quite mature and the community of developers is increasing, there are so many places where you can learn how to develop in solidity, and the documentation is quite good. There are other languages but not as popular as solidity: Serpent, Mutan, LLL.
  • Certification programs : for developers and for the applications itself. This is a natural step that will happen sometime.
  • B2C Vs B2B: right now the majority of applications are B2C, but I’m sure that in the future some B2B solutions will show up. B2B solutions are more difficult to identify as they are not always advertized publicly, right now the Pioneer CIOs are the main consumers that should be looking at them (settlers and town planners are still not interested on blockchain).
  • Official DApp store: this is something that will have to happen in the future. Right now there are some places publishing lists of available distributed applications, but there are not quality checks and there are not enough volume of users using them and rating them.
  • The API : the ability to interconnect with different environments is key, specially to promote the partnership between DApps that benefit to the end user, and hence enrich the ecosystem.
  • Waste of energy: this is a constrain provoked by Proof of work (POW) method. At some time this should be reviewed. Ethereum is trying to move towards proof of stake in it’s next release Casper.
  • Hyperledger: competition is a healthy fact, and a way to compare the evolution. We cannot compare apples with apples, but there are common components where you can determine some comparisons.
  • Ability to run private transactions: right now this is not possible, you can set the transactions as visible or private for all users, but not for restricted users or roles.
  • Reward for each block: the fact that there is a reward for each completed block makes the community to increase, this is an accelerator to me.

Etherium Vs Hyperledger

They are a different thing that will meet in some future.The main differences can be read here.

  • Etherium      = B2C, POW,                   , built in cryptocurrency…
  • Hyperledger = B2B, No-op and PBFT , no cryptocurrency required…

Remember the basic nomenclature of the maps Any suggestion to improve the map?

“bi-modal” model constraints

Gartner is advertising “bi-modal”; a “new” way to drive operations and new activities of a corporation. I was reading the idea and the concepts around it and I found it “old” idea, with some propositions that are so nice to have, and that they can be defended on the paper, but that in the reality of the companies (where there are real people and real egos) I find difficult to implement.

Gartner-bimodalReview the basis of organizations behavior before to accept the “bi-modal” proposition. On this topic Simon Wardley defines here three attitudes, cultures and type of people: pioneers, settlers and town planners (the main “modes”), which impacts the way the organization mainly behaves.

  • Pioneersdevelop novel concepts.
  • Settlers → create great products.
  • Town Planners → create highly industrialized commodity and utility services.

3-type-culturesNot all combinations are possible, and that in some cases you have to give up some of the “modes” to do not be in the “middle of everything”:

  • DON’T try and break into Pioneers and Town Planners. These two groups are far apart. You’ll create a them vs us culture. None of the novel concepts will ever be industrialized because the Pioneers won’t develop them enough and the Town Planners will refuse to accept them for being underdeveloped. Both groups feel they are the most important and both ridicules the other.
  • DON’T bury your Settlers into one of these groups . They won’t feel welcome, they will be in conflict with the group becoming second class citizens. Put them in the Pioneer group and they’ll be denigrated to documenting the “glorious” inventions of others and fighting a losing battle over user needs. Stick them with Town Planners and they’ll be seen as ‘lightweights’, the people whose job it is to deal with those annoying Pioneers and document what they’ve done etc.

Then, what is new in bi-modal model?

My notes:

  • IT industry is full of marketing concepts, which need to be evaluated and understood.
  • Ideas are easy to defend on the paper, but it’s different to put in place with people. When talking about organizational transformations and changes, the risk are high.