We’re at the dawn of a new industrial revolution. And just as the steam engine and the spinning jenny transformed the world in the first industrial revolution, the new technology of this new industrial revolution will transform our world as we know it.
The seeds of revolution are all around us: More compute power now resides in each of our pockets than in the supercomputers of the eighties; we are rapidly approaching a point where each person on the planet is interconnected through a web of digital channels; billions of devices are capable of instantly uploading data about the device and its environment as an the internet of things; highly automated manufacturing plants will soon intelligently assemble custom products; and instant video communications now take place regularly around the world. All of these changes are already here.
“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?
Over the past nine months I've been interviewing chief digital officers and senior digital leaders across a variety of industries to gain insight into the emerging role of digital leadership. My colleague Martin Gill and I wanted to discover why firms hire chief digital officers and what they are responsible for — more importantly I was looking to discover what CEOs should be doing to set up their businesses for success in a digital world.
One aspect of the research I'd like to highlight here is the need to think of digital as more than simply a bolt-on to your business. To create a digital business able to compete in the age of the customer, we need to think of building out a digital business ecosystem. I know what you're thinking — "not another ecosystem" — and yes, it's a very overused term, especially by consultants and analysts. But I simply can't think of a better term to describe the interconnected and codependent relationships needed in a fully digitized business (see diagram).
Last month, I delivered a webinar about digital CX teams in the post-PC era. I described the importance of having a clear strategy for the digital customer experience and how it should align with the overall customer experience vision in nondigital touchpoints. I shared examples of how companies hire and train essential in-house skills like journey mapping and storytelling to avoid overreliance on partners. And I talked about how companies should take an ecosystem approach to organizing their digital resources. There were some great questions posed during the call, and I wanted to answer them here.
Q. What is the typical team structure of a post-PC CX team?
A. There is no one standard model for digital CX teams — we see a variety of different structures. Some teams, like the one at Target, are quite large and encompass many disciplines and skills. Others, like the team at Express Scripts, are smaller and focus more on the high-level vision and orchestration of projects.
What is consistent across teams is that they build strong connections with key stakeholders throughout the company. Teams actively foster collaboration and skills development both within the team and with key partners inside and outside of their organizations. Many teams provide career paths for individual contributors and mentors for junior team members by promoting strong performers to manage subteams within the larger digital CX team.