The namespace clojure.pprint has some useful function to pretty print different data structures. The function print-table is particularly useful for printing a collection of maps, where each map represents a row in the table, and the keys of the maps represent the column headers. The print-table function accepts the collection as argument and prints the table to the console (or any writer that is bound to the *out* var). We can also pass a vector with the keys we want to include in the table. Only the keys we specify are in the output. The order of the keys in the vector we pass as argument is also preserved in the generated output.

Recently, I stumbled upon a revelation that seems to echo across organisations in various industries: in the final stages of longstanding contracts, a sudden misalignment emerges between the products or services offered and the current market demands.

This discovery wasn’t entirely unexpected, given my Wardley Mapping experiences. But how does this insight translate into action for us, both individually and as a company?

As architects, especially in the area of consulting and secondment, it is important to continually evolve. Clients don’t just seek relevant expertise, but also continually added value from external partners. What do we as consultant-architects do, to keep an eye on our ‘continuity’ over time? How do we ensure that we remain at the forefront of innovation, rather than becoming outdated relics of the past?

This blog post describes my personal journey in which I will delve into my strategic approach to remaining relevant in our industry, using Wardley’s strategy cycle as my guiding compass: