Keynote at ICEEFEST 2018 – Designing Services using DesOps for Industrial Revolution 4.0

 

Design as a practice is undergoing significant change within the product-service continuum. Seismic shits in the era of cognitive commuting that includes Artificial Intelligence, Machine Learning, IoT, IoE and 5G networks, means that we have to deal with increasing complexity as Industrial Revolution 4.0 disrupts every sector transforming all manner of products and services.  The growing and dominant role of Agile Development methodologies and the need to collaborate at speed, has precipitated the emergence of Design Operations (DesOps) as means to integrate service design and user experience design within the lean organisation using Agile Development.

Agile Development is an umbrella term for several iterative and incremental software development methodologies. The most popular agile methodologies include Extreme Programming (XP), Scrum, Crystal, Dynamic Systems Development Method (DSDM), Lean Development, and Feature-Driven Development (FDD) where the emphasis on building and releasing code, features and products. Alongside the emergence of Agile Development has been the adoption of Design Thinking and User Centred Design to design and develop products and services that are both usability and intuitive to use. 

Service Design is set of principles and practices of design that is being adopted by a wide range of sectors as way to deal with complexity when transforming organisations and their offerings. Service design has its origins in banking and financials services and it has now matured into an approach that enables teams to look at complex and interconnected ecosystems consisting of people, places, touchpoints, communications, interactions, processes and systems, and the challenges of transforming and delivering services that result in engaging user experiences to both customers and employees. 

Service design along with other design practices are becoming operationalised so that designers can fully integrated within multi-disciplinary teams using Agile Development methods. The operationalisation of design is referred to as Design Operations or DesignOps or DesOps, and it has emerged as a new paradigm in design practice and project management using a systemised set of design practices and activities to work alongside and dovetail with DevOps (Development Operations) and BizOps (Business Operations).

This paper will explore the principles and practices of DesOps in Service Design, in the design of products and services, and how design activities, processes and toolchains are operationalised to enable designers to integrate and work in a core team (Scrum Team or Tribe) using Agile Development methods. This paper will assert that DesOps requires a systemic change to the way design is used in the development of new products and services in a workflow that is highly collaborative, fast, and lean, to support agile transformation at speed.

Service Design using Design Operations (DesOps) can applied to the design of products and services to create innovative and breakthrough businesses that are capable of generating experience equity and service equity.  This paper explore that principles and practice of Service Design and DesOps and how it changing design practice. This presentation will show how DesOps can be applied to deliver impactful transformation, improve design capability and capacity while working at speed to significantly reduce the time to market of innovative and user-centric products and services.

The world’s businesses, organisations and public services are undergoing seismic changing in the way they operate and deliver value as they transform to become digital first organisations. They are undergoing radial transformation and a period of unprecedented technology change that demands agility, speed and new ways to work together.  As a result there is now a new and emergent field of Design Operations (DesignOps or DesOps) that is part of a new approach to design called Design 4.0. Design 4.0 is a way for organisations to design in Industry 4.0.

Opening Keynote Speaker at BelTech 2018

Digital design as a practice is undergoing change within the product-service continuum in the outcome economy. Seismic shifts in the era of cognitive commuting that includes AI, machine learning, IoT, IoE and born-in-the-cloud apps means that we have to deal with increasing complexity as the Industrial Revolution 4.0 disrupts every sector, transforming all manner of services and the products we use.

The increasingly dominant role of agile methodologies and the need to collaborate as we deliver outcomes at speed has precipitated the emergence of design operations (DesOps). DesOps is a way of systemising design practices and using a new and distinct set of approaches and activities to work alongside and dovetail with DevOps (development operations) and BizOps (business operations).

DesOps, in the design of products and services, is concerned with the operationalisation of service, UX and UI design practices where designers work in a core team (or tribe) to share research, apply data insights and then formulate and test hypothesis-driven design (HDD).

HDD is used to set goals based on a target state and deliver outcomes (rather than outputs) in an iterative and agile approach of ‘design, build, test and measure’. DesOps requires a systemic change to the way design is used in the development of new services in a workflow that is highly collaborative, fast and lean to support transformation at speed and with agility.

This presentation will look at the principles, practices and value of service design using DesOps and how this can applied to the design of products and services. It will explore how service design and DesOps as a philosophy and practice is changing the tools and activities used by designers within core teams using agile approaches.

I will draw upon examples from across a range of sectors and focus on project work undertaken within financial services. This session will show how DesOps can be applied to deliver impactful transformation, improve design capability and capacity while working at speed to significantly reduce the time to market of innovative and user-centric products and services.

About the Speaker

Peter Fossick is a seasoned design director specialising in service design, UX design and disruptive innovation using a range of approaches to deliver disruptive omni-channel and customer-centric experiences within the service-product continuum for the Outcome Economy.

Peter has worked across diverse sectors with top tier global corporations and start-ups in the USA, Europe, the Middle East and North Africa, China and Australia.

His project and client experience includes: AMP, Schroders-Cazenove, GM, Fairfax Media, IBM, Lloyds Banking Group, The Saudi Ministry of Health, Standard Chartered Bank, WilliamHill Online and many more.

With a proven track record in successful boot-strapping and scaling start-ups at speed, Peter is an angel investor in several companies in the USA and UK. He has established Argo Investments to invest in start-ups.

As an academic, Peter has established the IXSD Academy and he developed the first BFA & MFA in service design in the USA, as well as groundbreaking undergraduate and postgraduate curricula in design thinking, HCD, product design, UX design and interaction design as well as in innovation and design management in the UK, USA and SE Asia.

 Peter_Fossick

UXIstanbul

I was thrilled to be invited to UXIstanbul and deliver a keynote on digital transformation using Service Design.

This presentation discussed new approaches in designing and innovating to deliver transformation that supports businesses working at speed as they drive to disruptive innovation in a range of sectors including Banking, Financial Services, Transport Utilities and Defence as we move swiftly into the era of cognitive computing and Industry 4.0

The presentation outlined and explained strategic, tactical and practical approaches to innovating at speed using Service Design and UX in an approach I’ve termed Design 4.0; a holistic design approach that utilizes a range of practices, processes and tool that help us collaborate radically within organisations to deliver digital transformation and disruption in the era of cognitive computing and Industry 4.0.

I discussed service design, agility and the emergent field of design operations (DesOps) and how they are part Design 4.0. in industry 4.0. Design 4.0 marries BizOps, DevOps and the emerging field of Design Operations (or DesOps) to support design in Industry 4.0 and importantly Design 4.0 features semi-autonomous and fully autonomous computer systems (machines) that assist in design. Design 4.0 as a term has been used in different ways to describe design that is focused on social innovation (GK Van Patter, 2009), but my definition extends its definition to align it with tasks and activities relating to design and in Industry 4.0.

Robotics, artificial intelligence and other cutting-edge technologies can deliver huge benefits where  Government and industry co-operate and in Britain may be able to create 175,000 new manufacturing jobs and generate an extra £455bn if the UK takes full advantage of a “fourth industrial revolution” based on robotics, artificial intelligence and other cutting-edge technologies. That’s the conclusion of a new Government-commissioned report by a group representing some of the UK’s top companies, led by Siemens UK and Ireland boss, Professor Juergen Maier.

Service, experience, interaction and visual design as a set of practices offer strategic and tactical approaches to designing products and services that are proving highly effective in a world that is undergoing a digital transformation. Coupled with Design Thinking and Human Centred Design they have utilised contextual and participatory work with users, actors and customers as part of a participatory design process to gather both qualitative and quantitative data undertaken in an iterative and phased process. Essentially they are analogue in nature and are both people and time intensive.

However, increasingly design is informed with data-derived insights using advancing data collection techniques and processed using increasingly ubiquitous machine learning and cognitive computing applications. A traditional phased design model or lean approach is not always fast enough or efficient in an agile world where bespoke services and user experiences can be configured in an instant to match a users preferences, behaviours and location and their unique circumstances.

Design 1.0 was paper and pen, using physical tools like a ruler featuring a human agent. Design 2.0 was computer assisted design (CAD) featuring applications driven by a human agent. Design 3.0 is assisted design using CAD apps where knowledge based systems learn from the human actor. Design 4.0 is fully autonomous or semi autonomous design that may or may not involved a human actor (a designer, developer or product owner).

For companies to compete in the Outcome Economy as a part of Industry 4.0 that features IoT, machine learning, autonomous systems and cognitive computing requires a new model that I have termed Design 4.0. Design 4.0 comprises of semi-autonomous agile approach that will increasingly feature machine intelligence and a data informed driven strategy that features data garnered using people-to-people, people-to-machine and machine-to-machine interactions. More on this in the coming weeks and months!

Traditional design models are failing…

As a Service Designer specialising in UX and Digital Design I have developed a number of frustrations with traditional customer-centric design methods that use a phased approached.

For the past couple of years I have been leading design teams in London, the UAE and recently in Sydney where I was involved in transformational and strategic design projects with a focus on delivering disruptive solutions for large corporations. Often I have found myself working with teams of very smart and talented people that were unable to deliver efficiently or deliver disruptive innovation.

Without a rigorous and sophisticated approach to design that incorporates HCD and DT that is lean and agile, businesses have no means of gaining and sustaining a competitive advantage by creating engaging customer experiences that are timely. Interestingly just 29% of companies surveyed by Forrester in a recent study, follow any formal design process – let alone an agile design process.

Having a customer centred design ethos is not enough. It’s about delivering meaningful experiences and innovative services that are loved by the user that are relevant, affordable, and usable. But importantly these services must be in the market place and ready to scale before incumbents or a start-up have even thought of doing what you have created. 

To achieve this companies need a design model that has the customer continually engaged in ‘conversations’. The organisation has to have the means to focus design based on listening, interpreting and responding in a proactive and anticipatory way. Service and experience design methods must be strategic and practical and based on contextual and participatory work with customers who are part of an established constituency and drawn from new constituencies. Co-design with users has to be undertaken in a continually iterative fast-paced process of discovery, definition, design, development, testing and adaption.

A few years ago I found that traditional double-diamond phased design models are no longer sustainable or efficient in an agile world.

I found that the momentum of design and development had become so complex and fast paced that the traditional skills and labour intensive processes that produced graphic assets were no longer relevant or sustainable. These beautiful but overly complex assets; experience maps, storyboards, wireframes and WOW diagrams, were no longer perceived as having a cache or currency because they were not delivering real value. They have, by enlarge, become irrelevant.

For companies to compete with agile innovation they will increasingly have to adopt a lean UX design model that works with constituencies. This will enable companies to strategically integrate design into their businesses, as well as their culture, behaviours, activities, and values.

A lean UX design process is based around agile methodologies and incorporates insight driven strategic design in an iterative design and innovation solution model that is called WAgile.

WAgile takes the best and most effective features of a phased Waterfall approach (based on a double diamond model) and Agile (based on work-streams and sprints) and features HCD at is core to drive insight based innovation that engages with customer’s and users in a co-design process.

To find out more about Lean UX, its methods and tools please email me. 

More About WAgile…

As mentioned in a previous post, in the past two years I have started to use a leaner design and implementation process as part of an integrated strategic design and innovation methodology that I refer to as WAgile.

In the past there was a focus on phased approaches to design and implemetation called Waterfall where phases like research, insights design and implementation were completed in sequence – this was typified in Product Design using HCD and Design Thinking.

Then Agile came along and the emphasis shifted to implementation through sprints and a series of ‘drops’ as the product scaled from an MVP. This works well for software products or new app development but it sometimes fails to include a research and insights process or understand how the app is a touchpoint in a larger and distributed service ecology.

Both Waterfall and Agile have strengths, weaknesses and their own merits, but used separately they are limited and flawed.

Wagile

HCD & Contextual Research

Understanding users needs and importantly their desires is key.  Increasingly  ‘wants’ rather than ‘needs’ motivate customers.  For example, customers ‘need’ to text messages but they ‘want’ an iPhone. Customers want a great experience and the social cache of owning a premium brand and awesome products. In short cusotmers are seeking self-actualisation and they are willing pay a premium for it.

To understand ‘wants’ and ‘desires’ we need to intimately know and understand our customers; their attitudes and values. To do this we need to undertake sustained research at the beginning and throughout the early phases of a project through ‘conversations’. However, we need to work quickly and with agility, without over committing resource to design directions that might fail in the market place. 

This is where WAgile becomes attractive.  It takes the best features and benefits of Waterfall and Agile to combine them with HCD and Design Thinking. WAgile is an iterative design and innovation model that employs contextual research driven insights, design thinking, business science and uses sprints to work with agility in cross-functional teams to implement quickly.

At the beginning of the WAgile process I use both contextual inquiry techniques and data analytics to discover who is the ‘customer’ and what are their desires, needs and goals. I balance this with the business needs as we seek new opportunities to disrupt.

This means working closely and dialoging continually with current and potential customers. The process starts with Contextual Inquiry (CI) using ethnographic research augmented with data driven strategies where we use data garnered from customer interactions through owned, paid and social media. Each point of contact with the customer is an opportunity to harvest information and data to gain insights.

User Stories – a common currency

An important tool in the WAgile process are User Stories; the common currency of design. We describe customers tasks and goals through user stories that in turn become features and functions to design and build.

Framing the problem, defining the opportunity areas and designing solutions are based on User Stories. Then workstreams and sprints are forumlated based on MoSCoW principles working with users and the core team. This is part of the continual dialogue and conversation model with customers.

Working sometimes only a day or two ahead of the software developers, the designers use ‘Evidencing’ to bring concepts to life. Evidencing involves creating objects or ‘props’ to act out scenarios and create Rapid Experience Prototypes.  The prototypes explore the way a proposed MVP and design concept will feel and perform. 

By ‘Evidencing’ concepts we can animate and interact with concepts to assess their usefulness in an iterative process with users. This results in tangible evidence (as wells as stills and videos) that enables the core team make early informed judgments about the implications of the design concept.

Based on the outcomes and insights of Evidencing, the user stories are refined and translated into detailed features and specs. The information architectures are refined, wireframes are created, GUI assets are created and coding begins.

WAgile is fast, efficient and enables the user to be involved while the team implements what the user wants.