Since Peter Drucker first introduced the concept of "innovative organization”, it has become a buzzword amongst corporate managers. Particularly in IT, companies strive to create innovative teams. But whilst there has been a lot of theoretical discussion on how to build innovative organizations, there have been few practical experiments and analysis. Innovative organizations are like the moon: beautiful to look at, but seemingly impossible to grasp.
As an Office Principal who started a new ThoughtWorks office in Chengdu, China, I spent a big portion of my effort trying to make the new office an innovative organization. In this article, I will share my experience during the journey.
Innovative Organization: A Case Study
ThoughtWorks Chengdu is the company’s 28th office to open. The Chengdu location broke ground at the end of 2011and officially opened for business in April 2012. Leveraging Chengdu’s excellent educational institutions and industrial infrastructure, this new office has shown sturdy growth in just its first year. ThoughtWorks Chengdu now employs more than 90 IT professionals serving both overseas and domestic clients, of which over 80% were recruited from Chengdu locally. In addition to English and Mandarin, the local Sichuanese dialect can commonly be heard throughout the office.
Benefitting from Chengdu’s talent resource, ThoughtWorks Chengdu emphasized innovation from the beginning.
This highly localized enterprise has within one year not only achieved viability and its business goals, but has also came up with innovations that have influenced the IT industry and the broader scope of society, such as:
- To ease the difficulty of testing system integrations, a ThoughtWorker, Zheng Ye, developed the Moco testing tool. Within a few months, this tool has already been used in multiple commercial software projects around the world. An article on InfoQ’s global site described how to use this tool to improve the efficiency and effectiveness of integration tests. It also has been recommended on Twitter by renowned software guru Martin Fowler.
- A group of employees creatively used cutting-edge IT to help non-profit organizations to plan, develop and operate IT systems. They helped the Liren Rural Library project (a Chinese NGO focused on building non-profit libraries in rural areas) develop a book donation app for iOS, making donation more organized, purposeful and effective. They also helped Social Learn Lab, a Chinese educational NGO, develop New Class, an online experiential teaching platform that has already received universal acclaim from the volunteer sector. On July 1 this year, New Class obtained free rental space and corresponding resources at the Chengdu Civil Organization Service Park, as well as project support, financial support and team-management support, amongst others.
In addition to innovations like these that have already borne results, ThoughtWorks Chengdu is exploring more innovations of which a few, through articles or public speaking, have begun to make an impact. In total, employees of ThoughtWorks Chengdu have published 13 public speeches and six articles.
Such rapid and intensive emergence of innovations is not common in enterprises. This makes ThoughtWorks Chengdu a company worth tracking: how has this young company become such a strongly innovative organization?
The Value of Being Innovative
Before discussing how to build innovative organizations, it is necessary to first ask why innovation is so important. The enterprise, clients and employees of a modern IT company commonly demand innovation and it is that which comprises this company’s core competitive strength.
Increasingly, IT companies keep trying to solve problems in creative ways, and these “creative ways” soon become industry best practices, learned by customers and competitors alike so there’s little reason to differentiate a company that way. For example, 10 years ago, only a handful of IT companies truly grasped agile software development and now this methodology has become an industry standard, its status having moved from high technology to everyday practice. Only through continuously striving to find new and better solutions can they maintain their high-end IT professional status.
Clients of IT service companies do not seek staff simply able to write software, but instead seek IT expertise and innovation experts; they need these experts to help them find creative ways to solve problems, or even use IT innovation to drive business innovation. For these clients, the ability to innovate is an important reason they choose to work with a service firm.
IT employees, meanwhile, want to improve and innovate, to try new ways to solve problems, which not only helps them improve their capability and professional competence, but also makes the work itself more interesting. An encouraging atmosphere of innovation helps IT companies to attract talent.
Innovation makes working more interesting.
In summary, for a decent modern IT company, innovation is equally critical to the company, its clients and its staff. It’s not a surprise that leaders in charge of a ThoughtWorks branch have “to create an innovative organization” as a priority.
Innovation Myths and Facts
The word "innovation" arouses feelings of respect and fear in equal measure, as if it were an extraordinary trait belonging only to those with superhuman abilities. Within the IT industry, some common myths surround the idea of innovation:
- “Only world-changing inventions can be called innovation.” A lot of people believe that only things like the iPhone and Google Glass, items that revolutionized the way people live, can be called innovations, and hence don’t dare themselves begin innovating. In fact, these ambitious, world-changing innovations are just the tip of the iceberg peeking out above the water, supported by a huge number of micro-innovations and micro-advances. These tiny innovations are by and large unknown to the public, but they bring value to businesses and customers.
- "Innovation relies on inspiration." Many believe that innovative ideas come from a spark, one that is both unexplainable and unpredictable. That is to say, innovation is inherently unmanageable. In fact, it is daily work and life that provide the most abundant source of innovative ideas. Something that causes frustration for an individual or team is likely to frustrate many people in other teams. For those that are good at recognizing such pain points, these will always produce a steady stream of ideas. “Analysis of daily work to discover new pain points” is a totally predictable process and can be managed.
- "Innovation can only be carried out in the garage." The root of this view comes from dissatisfaction with enterprise environments. Mature companies do not allow for mistakes, don’t encourage new methods, are slow to respond, cling too tightly to a set of rules…. Mature companies are simply not suited to innovation. On the other hand, mature companies can provide more resources to support risky innovative activities and can provide a larger stage (for example, the opportunity to access quality customers, and media exposure) to promote innovation. As long as thinkers can separate themselves from conservative and slow ways of doing things, mature companies are also a hotbed of innovation.
- "Most innovations end in failure." Perhaps wary of too many stories of failed start-ups, many people believe that innovation is a fool’s game with only a handful of winners able to achieve success while most attempts end in dismal failure. This is one reason why a lot of people do not wish to put their energy into innovation.
But if we adopt appropriate methods to implement and manage innovation, small steps at a time, and continuously deliver, then with each step an innovation initiative can deliver tangible results and also get real feedback. Even if an initiative stops at a certain step, its previous work will not have been wasted, as it will have already generated benefits.
Given that employees in the IT industry generally have a high level of education and access to the latest information, they should naturally be one of the most innovative groups. Many IT companies lack innovation and vitality not because their staff members do not have ideas but because the company’s rigid thinking and work style has stifled them. To create an innovative organization, we must get rid of these myths and encourage and help employees to find ways to innovate within their daily work by way of gradual, controlled micro-innovations. Promotion of micro-innovations enables the potential to develop into the more influential big innovations. To do this, companies need to support innovative methodologies.
Lean Thinking and the Innovative Funnel
In 2012, the book "Lean Startup" suddenly became very popular. Established on the principles of lean thinking, the book advocates a lean approach to starting a business, so that entrepreneurship is a gradual and controllable thing. The essence of “Lean Startup” is a "building => measure => learn" cycle, i.e. take a small step forward and get fast feedback. For innovative businesses, the same principles apply.
As previously mentioned, widely influential "big innovations" are built on a foundation of micro-innovations. In the process of development and promotion, a large number of micro-innovations will stop at a certain stage, creating value within a comparatively smaller scope, and will not evolve to “big”.
The innovation and the development process can be thought of as a funnel, which consists of the following stages: discovery of pain points => problem solving => experience sharing => generalization => promotion.
The innovation funnel.
This funnel metaphor helps us understand some of the key points in creating innovative enterprises. First, ensure an abundance of source material, which will allow employees to explore innovative ideas. Second, ensure smooth flows and eliminate barriers between the various stages. The innovation funnel has five main stages, each with a different focus.
Discovering Pain Points
Every project has its own set of problems and every team has members with complaints – this we take for granted. But from the perspective of innovation, every problem and every complaint can be seen as an opportunity to innovate. Rather than team members becoming downtrodden or bored by existing problems, they instead may see them as exciting possibilities.
Firstly, one must encourage team members to summarize their own existing pain points. Agile retrospectives are a good time to do this. In a typical retrospective meeting, team members recall what they have done well in order to improve the self-confidence of the whole. Then the team covers what they have done less well so that they may find opportunities for improvement. In these frequent “retros”, which are targeted at issues and not persons, members are willing to speak honestly in order to reveal problems and pain points.
Sometimes, team members are so caught up in their project that they fail to detect pain points. At times like these, communications between teams become even more important.
At ThoughtWorks Chengdu, there are more than 10 independent projects. Team leads have a biweekly meeting to share what they have learned and to identify pain points. During one such meeting, a team lead shared his desire to speed up automated build. The leads discovered that this was a common wish across several teams.
However, some deep-seated, large-scale problems are difficult to detect due to limited scope and ability. For example, within ThoughtWorks Chengdu, four teams were working on four different applications for the same brand. Because the teams paid little attention to each other’s products, the UI and UX among these applications were not consistent. Such inconsistency causes users to feel a disconnect when, in order to fulfill different business scenarios, they traverse through an application. To reveal these sorts of pain points, teams need an experienced external observer.
ThoughtWorks Chengdu has a practice called a Technical Deep Dive. For this, members of the China Technical Council (CTC), composed of prominent technologists from ThoughtWorks China, join a team for two weeks. During this period, the CTC members will interview team members, hold exploratory workshops and review current practices (architecture, code, workflow) to try to discover pain points.
Problem Solving
After discovering pain points, team members must solve them in a timely manner to gain a sense of achievement. Otherwise, the acknowledgement of pain points will simply cause low morale amongst employees and will not become a source of innovation.
Time is a limited commodity, so how does a company, and in particular a professional service company like ThoughtWorks that spends eight hours a day serving clients, find time to solve problems? The company, client and employee should trust each other, so that they can collectively create space for continuous improvement.
The first thing a project team will do in addressing pain points is to record technical debt within current system. The team discusses pain points with the client and identifies the root causes of the pain. The team records these causes in the form of technical debts, puts them into the backlog and manages them with stories. In this way, resolving debts become an integral part of the delivery plan. Technical debts reduce the velocity of delivering stories, so the team and client must come to agreement on how to balance the short-term yields (only deliver functions) and the long-term payoff (getting rid of technical debt).
Some pain points are not suited to a resolution within daily work as a regular task, and instead need a dedicated period of time in order to be resolved. An example would be developing a software tool in order to improve support. One approach to solving this problem is to buy beer and pizza and run a code jam on a weekend, developing an open-source piece of software to address this problem. ThoughtWorks Chengdu’s client also holds an Innovation Day every quarter, encouraging employees to use two days’ working time to realize great ideas. Combining pain points with the opportunity to innovate usually brings achievements beyond expectations.
Experience Sharing
No matter how seemingly trivial and rough the solution for a pain point, it is still worth sharing the solution among other teams within the company. This type of sharing has two benefits. First, it is a form of encouragement to the project team, letting them know that discovery of pain points and continuously looking for improvement are admirable traits. Second, other teams may have found the same problem in their projects and can re-use or even improve the solution.
A lot of technologists are introverts unwilling to share their experiences in public. To encourage them, ThoughtWorks Chengdu organizes a Team Showcase every week. One team each week presents their recent achievements. Since delivering on time is a basic responsibility for ThoughtWorkers, it is not considered an achievement. Teams instead focus on new approaches, tools or technologies that they have used to eliminate pain points. With 10 projects in the office, each team presents a showcase every three months. This pushes every team to make continual progress, lest they be caught with nothing to share.
Every week there is a project showcase to demonstrate achievements.
During the team showcase, you often hear, “We encounter the same issue.” Sometimes, the ready-made solution can be re-used. More often what you hear is, “We have a similar problem, but this solution doesn’t completely work for us.” This feedback is a signal, indicating the solution might be a good start but needs closer attention.
Generalization
There’s a saying that “There’s nothing new under the sun.” Nobody is able to create a wholly original question. There may be thousands of people and teams who are suffering from the same problem you have suffered, but just like leaves, none are identical. Dedicated solutions usually do not work everywhere. Abstracted and generalized solutions have more power and can be more widely used.
The evolution of the Moco test tool is a great example of abstraction and generalization. Integration tests greatly frustrated Zheng Ye. They were slow to run, hard to prepare test data for and ran in unstable test environments. To simplify them, he developed a tool that at first could only be used via its API interface.
Through discussion with other project teams, Zheng Ye learned that not only integration tests written in JUnit had this problem. Functional tests written in Cucumber, Concordion and other testing tools were also pain points for other teams. Zheng Ye realized that these problems could be abstracted to “it’s difficult to test integration points”, and that led to a standalone model of Moco.
Beyond expectations, mobile developers began to use Moco to simulate server-side behavior for relieving workload, simplifying their daily development work. This is one example of an advance made possible by abstraction.
Whilst using Moco on another project, I discovered that the main obstacle to integration tests is actually test strategy itself rather than the testing tools, and that test strategy is affected by software design. The key to solving testing difficulties is to design integration points appropriately in order to plan a good test strategy. Through some practical project validation, I was able to summarize a set of integration points’ designs and test strategies, which greatly improved our integration tests. I wrote “A Test Strategy for Enterprise Integration Points” and published it on InfoQ. Since then, Moco has, from humble beginnings as a simple test tool, become an important part of the approach for design and test strategy for integration points.
Even in such a success story, we still cannot generally answer, “How to abstract solutions from pain points?” In my opinion, the ability to generate abstractions still relies on a mysterious spark of insight. Even so, there are still ways to promote occurrences of these sparks. In ThoughtWorks Chengdu, micro-innovation owners and experienced colleagues (especially CTC members) are encouraged to communicate frequently with each other. The key to this communication is to make clear what the pain points are, what the root causes are, how to solve them and to what scenarios the solution can be applied. Mind maps and whiteboards are the best tools to convey this information. Inspiration may occur during this clash of minds.
Promotion
When a micro-innovation has already been abstracted and generalized and is suitable for use by many people and teams, then it is time to promote it in order to gain greater influence. When promoting, it is important to consider channels and content.
In ThoughtWorks Chengdu, there are three methods of distribution: intra-company promotion, client-side promotion and external promotion. Inside ThoughtWorks, an innovation might not be applicable just to a particular project within a particular office, but also to projects in other offices in China and even globally. ThoughtWorkers can easily introduce innovations to global colleagues via their internal forum, mailing list, the CTC, and more. Promotion amongst clients occurs similarly in clients’ internal forums and mailing lists and through recommendations via Client Principals. ThoughtWorks’ clients expect to reap the fruits of creative thinking and so top managers are typically keen to hear of any new developments.
The above two channels are inner ones, where a clear email is enough to achieve the promoter’s goal. When promoting innovations to clients, the organization of content becomes of utmost importance. Common channels for external promotion are Weibo, blogs, public presentations, articles, books and more. There’s no need to describe every channel’s characteristics, and it is actually more valuable to point out their similarities. Organic use of these channels can help the author collect feedback and organize thoughts, resulting in better content.
When a content structure appears in my mind, I will quickly tweet about it. The 140-character limit helps me to pare a thought down to its core elements, allowing me to form a 30-second elevator pitch that I can use to introduce my idea to anyone. I then would use a mind map to sort out my content structure, and write a blog post under 2,000 words to describe its structure. This is the most basic introduction, without any lengthy expansion. A post like this is sufficient to the gain the sympathy of readers with similar pain points, at which point they often provide feedback to the author.
After this, authors can present this blog post to online and print media editors to gauge whether its contents are of interest. If a media outlet is willing to publish the article, the author can tailor his piece according to the characteristics of its format, add statements and examples and making it ready for publication. Using the same skeleton framework, the author can draft a speech, using the words from the article as speaker notes for their presentation slides. When the article is complete (and usually earlier), so is a well-organized speech. Now you can go ahead and deliver your speech at influential industry conferences such as InfoQ and QCon.
In the case of Moco, we did more than the above. After publishing in InfoQ China, two colleagues from ThoughtWorks Chengdu translated the article into English in order to introduce Moco to our clients. We realized the English version could be published as well and contacted editors of the InfoQ global site. The English version was subsequently published on InfoQ global after a few modifications. We entered Moco for the Duke's Choice Award, held by Oracle, and duly won. Moco has, from an unknown internal innovation, become a highly influential open-source project.
Leader Responsibilities
Organizations lack innovation not because their employees lack the capability, but because they have not provided a supportive environment. Creating an environment conducive to innovation and eliminating obstacles is the responsibility of the whole team, but especially of the leader.
Leaders have to make employees aware that innovation is encouraged. Nearly every organization claims to encourage innovation, and no leader will say, “No innovation, please.” We can conclude that the building of an innovative consciousness is done through deeds, not empty words.
Innovation means doing jobs in a different way and possibly making mistakes. If an organization cannot accept mistakes and punishes employees who make them, then no employee will innovate. In my daily work as an office principal, I keep asking every project: Is there anything you’re able to do better? What kind of new approaches do you want to use to deliver the project?
If a team does something wrong, the first question I ask is, “What have you learnt from this?” I want employees to know that making mistakes is allowed but making no attempt at progress is not.
Employees need to know as much as possible to produce innovation. An organization that wants to foster innovation should be a transparent organization whose employees can access all manner of information beyond what they need in their daily work context. ThoughtWorks Chengdu holds a full office update every month with information relevant to business operations announced in the open to everyone. Traditional companies might consider much of this information to be sensitive: sales progress, customer feedback, staffing, financial data and more. A lot of management meetings are open to any employees who wish to attend. We are eager to have staff understand wider contexts in order to engender new thinking.
Even with information, employees may not have enough perspective to innovate. As a more senior employee, a leader needs to help inexperienced colleagues expand their horizons. A leader can help developers understand the impact of software for business, help on-the-floor staff understand the background to corporate operations, help internal staff learn to gain exposure within the industry through writing and public speaking – these are all methods a leader uses to expand an employee’s horizons.
When employees have good ideas, a leader should guarantee that they receive enough resources to implement them. When a micro-innovation has still not been realized, what an employee needs most is time: time to discover project pain points, to create a solution, to share experiences. All of these may take up work time. A leader must give their employee enough support so that the innovation can be pushed forward.
Take care to not provide too many resources too early. Doing so smothers the will to innovate. Just as every company claims to encourage innovation, so too does every individual claim to have innovative ideas. However, many endeavors are half-heartedly undertaken and put aside soon thereafter. A commitment is the standard by which to judge passion, and investment in new ideas should follow the principles of lean startup: when an innovator has created something from scratch and found a clear direction, invest necessary resources only when investing populates corresponding output quickly.
Why are innovators willing to start from scratch and even to spend spare time to implement their new ideas? Aside from the high brought about by the act of creation, another important reason is that their creation may help others. The desire to lend a helping hand is a key factor in the culture of innovative organizations. Employees who are happy to help others empathize with clients, colleagues, fellow IT professionals and even vulnerable groups within society, and will do their best to help. Such employees have a greater probability of finding meaningful new ideas and making them come to life. Leaders should assist these types of employees and these types of innovations. An atmosphere of helping others is what leaders should encourage and cultivate.
ThoughtWorkers doing voluntary work in the Sichuan earthquake area. Helping others is a source of innovations.
Summary
This article has introduced some of the achievements of ThoughtWorks Chengdu that have been made possible by creating an innovative organization. Despite “innovation” being a word every company and individual likes to say and hear, myths surrounding the implementation of creativity make many people feel threatened. This article dispels the most common of those myths, using lean startup principles to build an “innovation funnel” model, and introducing how ThoughtWorks Chengdu has used this model to grow.
Leaders play a key role in the construction of an organization but only its members can determine its culture In the course of creating a culture, leaders simply play enabler and focus on eliminating obstacles, ensuring employees have enough information and freedom. At the same time, new innovations will also be promoted. By adopting these methods, an organization will be much more likely to possess an innovative spirit.
About the Author
Jeff Xiong is an Office Principal of ThoughtWorks Chengdu. He is also an enterprise application developer with over 10 years experience. His biggest interest is to find approaches to help people with software technologies.
