“We’re in charge of developing your new website. You can have it good, fast, or cheap. Pick two.”
How many times have you heard (or said) something like that on a digital experience project? With any digital initiative, one of those desires is usually odd man out. Application development and delivery pros at corporations, digital agencies, and systems integrators know this; they’re often the people talking reality in the face of the wishes of the business asking for all three (and, frequently, a fourth: “Can you make it as good as Apple.com?”).
Web projects always require compromise. The challenge is figuring out what you can live without.
It’s enlightening to apply the good/fast/cheap triangle to the Healthcare.gov snafu that’s been playing out in Washington, DC. If you’re involved in web applications, reviewing the government’s project might be one way to inoculate yourself and your team against an invitation to the hot seat by preventing website crash and burn. No one wants to be like the Secretary of Health and Human Services, Kathleen Sebelius, and her squad, who’ve had to explain the most visible website flop in history.
It makes me ask: how did the Feds deal with the good/fast/cheap question for Healthcare.gov? It’s a hard reality to deal with on any digital project, never mind a project of this scale. Where would you compromise?
Developers And Their Business Counterparts Are Caught In A Trap
They swim in game-changing new technologies that can access more than a billion hyperconnected customers, but they struggle to design and develop applications that delight customers and dazzle shareholders with annuity-like streams of revenue. The challenge isn’t application development; app developers can ingest and use new technologies as fast as they come. The challenge is that developers are stuck in a design paradigm that reduces app design to making functionality and content decisions based on a few defined customer personas or segments.
Personas Are Sorely Insufficient
How could there be anything wrong with this conventional design paradigm? Functionality? Check. Content? Check. Customer personas? Ah — herein lies the problem. These aggregate representations of your customers can prove valuable when designing apps and are supposedly the state of the art when it comes to customer experience and app design, but personas are blind to the needs of the individual user. Personas were fine in 1999 and maybe even in 2009 — but no longer, because we live in a world of 7 billion “me”s. Customers increasingly expect and deserve to a have a personal relationship with the hundreds of brands in their lives. Companies that increasingly ratchet up individual experience will succeed. Those that don’t will increasingly become strangers to their customers.
What a strange summer this has been! From Boston to London to Paris to Turin, the weather has offered weekly and even daily reversals, with continuous change from sun to rain, from hot and damp to cool and crisp. I missed a nice spring season. Even today, from 35º-38º Celsius (95º-100º Fahrenheit), we just went to 22º Celsius (71º Fahrenheit) with a perfect storm! A continuous climate and sudden change is quite unusual in some of these countries. Certainly it is where the Azores Anticyclone usually dominates from mid-late June to mid-late August, offering a stable summer. How many times have you had to change plans because you discover weather is about to change!?
You might be thinking, "What does this have to do with this AD&D blog?" It’s about change! I am wondering if, in our daily lives, getting used to unexpected conditions and having to handle continuous change favors a mindset where change is just something we have to deal with and not fight. A new mindset very much needed given the change we see ahead in how we develop, test, and deploy software!
My focus in this blog is testing, although the first change we need to get used to is that we can’t talk any longer about testing in an isolated fashion! Testing is getting more and more interconnected in a continuous feedback loop with development and deployment. (See my colleague Kurt Bittner's report on continuous delivery; I could not agree more with what Kurt says there!)
In the days when web applications were king, this type of insight was doable with simple web analytics and similar tools. Today, continual experience optimization is much more difficult because of:
Multiple interaction channels. You must collect, correlate, and analyze data in a coherent way across multiple channels of customer interaction. A single customer interaction may cross between channels or even use more than one channel at the same time.
Many back end servers. You must integrate data from multiple back end servers including recommendation engines, commerce, mobile application servers, digital asset management, community, collaboration, messaging, and more.
The need for rapid change. You must quickly change any or all of your digital experiences and back end services based on what you’ve learned.
The need for contextual experiences. You must use each individual customer’s context to dynamically adjust experiences in real-time.
I just finished my new report on the Agile testing tools landscape. I’ll point Forrester readers to it as soon as it publishes. But there are few things that have struck me since I took over the software quality and testing research coverage at Forrester and which I would like to share with you in this preview of my findings of the testing tools landscape doc.
My research focus area was initially on software development life cycles (SDLCs) with a main focus on Agile and Lean. In fact, my main contribution in the past 12 months has been to the Forrester Agile and Lean playbook, where all my testing research has also focused. Among other reasons, I took the testing research area because testing was becoming more and more a discipline for software developers. So it all made sense for me to extend my software development research focus with testing. But I was not sure how deep testing was really going to integrate with development. My concern was that I’d have to spend too much time on the traditional testing standards, processes, and practices and little on new and more advanced development and testing practices. After 12 months, I am happy to say that it was the right bet! My published recent research shows the shift testing is making, and so does the testing tool landscape document, and here is why:
Google sets amazing new standards when it comes to web, mobile, and cloud technologies. That's why we are here at Google I/O 2013 in San Fransciso to find out what new technologies and tools developers can expect on all technology fronts. See this special edition of Forrester TechnoPolitics to experience the energy of Google I/O.
There is a scene in the Broadway hit Spamalot in which a peasant jumps up from a cart of corpses and vigorously complains that he's "not dead yet". It's a humorous side-story to the main theme of the search for the Holy Grail. One might be accused of thinking of COBOL in the same way, as a side-story to the current major themes of mobile and web development, or perhaps as a historical footnote to the current narrative. IBM's recent announcement of major upgrades to its COBOL compiler technology provides a good reason to pause in our headlong pursuit of the latest technology to reflect on the value of COBOL applications in enterprise software portfolios.
While mobile and web technologies often garner everyone’s attention, the reality is that most organizations that have been around for more than 30 years still run their core business processes using systems that were written in COBOL. Anything that makes these apps easier to evolve and extend is a very good thing. The reality is that evolution and extension of these apps is critical to business success. In order for the flashy-new-social-networking-enabled mobile and web Systems of Engagement to succeed, the workhorse Systems of Record and Systems of Operation are going to have to evolve apace. This means that they must take advantage of the latest architectures as well as being refactored and modularized to align with a service delivery model.
Banks have a reputation for being stodgy and conservative. But Credit Agricole (CA) has broken the stereotype. I had a great discussion a few weeks ago with Bernard Larrivière, Director of Innovation, and Emmanuel Methivier, the CA Store Manager, about the CA Store launched last fall. The store houses new services developed by third-party developers using the bank’s secure customer data — one small step for CA, one giant step for the banking industry and the data economy.
The CA Store was not only inspired by the Apple Store model but also by government open data initiatives. The public sector provided the model of exposing APIs to internal data and working with independent developers to encourage application creation. However, in a move that will likely be carefully watched by their public sector brethren, CA recognized the need for a better business model to incent developers to use the data, and to sustain the development and maintenance of the applications.
Business leaders have revenue growth first and foremost on their minds. On average, 70% of these business leaders place a high or critical priority on revenue growth, customer acquisition and retention, and addressing rising customer experience expectations for 2013. Our data suggests business leaders are 50% more likely to identify these as critical initiatives than they do margin improvement or reducing operating costs. Growth and customer experience improvement take business priority.
Rowan Curran, Research Associate and TechnoPolitics producer, hosts this episode to ask me (your regular host) about The Pragmatic Definition Of Big Data. Listen (5 mins) to hear the genesis of this new definition of big data and why it is pragmatic and actionable for both business and IT professionals.
Podcast: The Pragmatic Definition Of Big Data Explained (5 mins)