Design doubts
My most recent book is IT service by design, written with Catherine Zuim Florentino . It’s a lovely book. One of my best. So far. Feel free to buy it.
Unsurprisingly, one of the key concepts is design. Design is such a deceptively innocent word. However, it?gave me quite an exquisite headache trying to grasp what it actually is. “Actually” in italics because it turned out to be one of those ineffable and amorphous things that, just when you think you’ve got hold of it, takes on another form. This article explores my doubts.
After much iteration – iteration being true to the nature of design – I came up the following definition. I say “I” not “we” because I had the headache. Being a designer, Catherine knows better than to go down this rabbit hole. As for me, I must have been a ferret in one of my previous lives.
Definition
Anyway, I was reluctantly happy with a (not “the”) definition as “an intentional, emergent, adaptive and generative act of harnessing potential and envisioning reality, which precipitates the transformation of ideas into reality”. This typically terse assertion needs a voiceover, as follows:
It’s a useful definition. It addresses significant aspects.
Doubts
And yet. And yet. That final sentence. “This transformation is not part of design, but what follows design.” It seems so innocent. First you design something, then you build it. Or do you?
One of the sources for my doubts was Dan Nessler ’s “Revamped Double Diamond Design Process Framework”, that builds on the classic Double Diamond[2] (2004).
Dan’s variation first emerged in 2016[3] (see header figure) and was updated in 2018[4], better visualizing the iterative nature of the deliver phase.
It initially concerned me that the framework included “build”. If it’s a framework for design, then it’s ‘obviously’ not about build. So, what was behind this thinking?
Is design involved the transformation of a design into an artefact? Surely. But does this imply that design is part of build and, if so, how can you model this entanglement?
Dan, by the way, is far from dogmatic. He positions his framework as a mix of a practical how-to guide as well as an abstraction of the real world. A world that is too complex to be captured in a two-dimensional figure. It’s a source of inspiration to be contextualized to the specific situation’s needs. And very useful too.
Solution?
Maybe the solution is to distinguish between phases of progress and types of activities performed in these phases – design activities in the build phase. Oh well, maybe in the next book.
For the time-being, problem solved by looking at it from another angle and making the phase-activity distinction. The power of perspective. Instant paracetamol. Until it wears off…
Resignation
For the record, this is how we framed design in our book, with a clear distinction between design, realization(build), and operations.
I still like it, but look at it differently than a few months ago.
I can live with doubt[5].
I have to.
[1] Inspired by Rudolf T. A. Greger – Businessdesign-Coach in one of our reflective discussions
Inventor of 'Planguage', Consultant, Methods Inventor, Textbook Writer, Keynote Speaker and Teacher to many international organizations
4 天前Your diagram is one I like. Compare with my EVO cycle https://www.researchgate.net/publication/383749778_EVO_2024 (free frozen copy) Keep on struggling!
Strategic Technology Leader | Pioneer of XLA ITIL & Inducted to ITSM Hall of Fame | Top 25 HDI Thought Leader and Digital Experience Expert
1 周Mark Smalley Back before the modern era, in 1991, as part of our Learning Organization semester at Nyenrode Business University, I was taught Viable Systems Theory by Luc Hoebeke (based on the work by Beer and Checkland) and tried to create an ITSM system reflecting it. I wrote a (long-lost) paper on effective ITSM metrics "in the system, on the system, and between the systems." Imagine, this was pre-ITIL. I recently had a great conversation with John Worthington about it. I reflect that my thinking in the XLA Experience Management System has not strayed far from the thinking over 30 years ago.
I always enjoy the continual confusions between design of a service in terms of the required outcomes to deliver for the business consumers and ITSM service design..
Digital Transformation, Business and Policy Development around it are my daily meal. AI, mindfulness, sustainable humanity, relentless leadership development - tea conversations. Mostly a happy person. :-)
2 周Great one, Mark Smalley! Little rough on the edges in terms of visuals, but the message is clear. Thank you so much for sharing! ???? ?? ????