You are here
This blog post is on purpose, Open Source, profit and pie. This week I had an opportunity to meet Professor Klaus Schwab, Founder and Executive Chairman of the World Economic Forum. I was inspired by the following comment he made (not his exact words):
"Because companies strive to have a positive balance sheet, they take more in, than they give out. However, as individuals, we define success as giving more than you take. Given that many of us are leaders as individuals *and* also leaders in our businesses, we often wrestle with these opposing forces. Therein lies the leadership challenge."
I’ve seen many Open Source developers struggle with this as they are inherently wired to give back more than they take. Open Source developers often distrust businesses, sometimes including their own employer, because they take more than they give back. They believe businesses just act out of greed and self-interest.
This kind of corporate distrust comes from the “fixed-pie concept"; that there is only so much work or resources to go around, and as pieces of the pie are taken by some, there is less left for everyone else. The reality is that businesses are often focused on expanding the pie. As the pie grows, there is more for everyone. It is those who believe in the "expanding-pie concept" who can balance the opposing forces. It is those who believe in the "fixed-pie concept" who worry about their own self-interests and distrust businesses.
Imagine a business that is born out of a desire to improve the world, that delivers real value to everyone it touches. A business that makes employees proud and where team members are passionate and committed. A business that aspires to do more than just turn a profit. A business that wants to help fuel a force of good. That is Acquia for me. That should be your employer for you (whoever your employer is).
The myth that profit maximization is the sole purpose of business is outdated, yet so many people seem to hold on to it. I started Acquia because I believed in the potential and transformative nature of Drupal and Open Source. The purpose of business is to improve our lives and create value for all stakeholders.
Acquia's growth and capital position has given me power and responsibility. Power and responsibility that has enabled me to give back more and grow the pie. I have seen the power that businesses have to improve the world by accelerating the power of good, even if they have to take more than they give. It's a story worth telling because business is not a zero-sum game with one winner. I believe Open Source companies are in a prime position to balance the opposing forces. We can do well and do good.
I'm proud to share that Acquia announced its certification program today. You can now get "Acquia certified in Drupal", something I'm pretty excited about.
This is something I've been hoping to see in the community. While there have been other experiments around certification, we as a community have lacked a way to ensure professional standards across Drupal. Over the years, I've heard the demand coming from partners and clients who need a way to evaluate the skills of people on their teams. More and more, that demand has drowned out any perceived criticisms of a certification for Drupal.
A good certification is not just a rubber stamp, but a way for people to evaluate their own abilities, and make plans for improving their knowledge. In some countries, certification is really important to create a career path (something I learned when visiting India). For these reasons, I feel Drupal's growth and development has been hindered without a formal certification in place.
The certification we've built is based on the combined years of experience among Acquia staff who oversee and manage thousands of Drupal sites. We've observed patterns in errors and mistakes; we know what works and what doesn't.
People have debated the pros and cons of software certifications for years (including myself), especially where it involves evaluating candidates for hire. Certainly no certification can be used in isolation; it cannot be used to evaluate a candidate's ability to perform a job well, to work in teams or to learn quickly. Certification can, however, provide a valuable data point for recruiters, and a way for developers to demonstrate their knowledge and stand out. It is undeniably valuable for people who are early in their Drupal career; being certified increases their chance to find a great Drupal job opportunity.
One of the biggest challenges for Drupal adoption has been the struggle to find qualified staff to join projects. Certification will be helpful to recruiters who require that job candidates have a good understanding of Drupal. There are many other aspects to recruitment for which certification does not provide a substitute; it is only one piece of the puzzle. However, It will provide organizations added confidence when hiring Drupal talent. This will encourage the adoption of Drupal, which in turn will grow the Drupal project.
The community has been talking about this need for a long time. One approach, Certified to Rock, evaluated an individual's participation and contribution in the Drupal community. Acquia's certification is different because we're assessing Drupal problem-solving skills. But the community needs more assessments and qualifications. I hope to see other providers come into this space.
Today, the web is not just about publishing content anymore. As the web evolves from content management to digital experience management, it's about understanding visitors' interests and preferences, and figuring out how to deliver them an optimal personalized experience. Many organizations are exploring ways to more effectively create and deliver valuable content to site visitors to increase traffic, conversions and revenue. Great content is still gold, but delivering the right content to the right user at the right moment in the right format is platinum.
Today's personalization tools aren't great and put marketers at a disadvantage. This is why I'm excited to announce that we're rolling out Acquia Lift, a solution that equips the site owners with powerful website testing and content targeting tools to optimize content for each visitor. Acquia Lift learns about a visitor's interests and, based on these insights, uses machine learning algorithms to automate the delivery of personalized content. Marketers and site builders can test content, for example using A/B or multivariate testing, and even add rules about the types of user profiles that get specific content. There is implicit learning that takes place as well that continuously helps Acquia Lift provide increasingly more appropriate content to individuals. Attributes of the user, such as location, and even what the current weather is, can be taken into account in providing the right content. Check out this short Acquia Lift video if you want to learn more or see Acquia Lift in action:
As I talked and wrote about earlier, I believe personalization and contextualization will be a critical building block of the future of the web, and I'm excited to help make that a reality.
As is now a tradition, here is my annual Acquia retrospective. Time to look back at 2013. In your life, you only get an opportunity to do so many things, so you have to focus on doing things that matter. I'm fortunate that Drupal and Acquia are remarkable stories. I take time to write these retrospectives for you and for me. I write them for you, because you might benefit from my experiences or from analyzing the information provided. But I also write them for myself so I don't forget this incredible journey. If you want, you can read previous retrospectives: 2009, 2010, 2011 and 2012.
For Acquia, 2013 was another excellent year. It was our fifth full year in business (i.e. revenue-generating year), and we finished the year with 19 consecutive quarters of revenue growth. In short, 2013 was a year of continued momentum, record bookings and great customer success. With five-year sales growth of more than 84,100 percent, Acquia was identified as the second fastest-growing company on Deloitte's Technology Fast 500 in North America. Acquia was also listed among North America's fastest growing software companies in 2013's Inc. 500. We're all very proud of that.
We hired 208 people this year and ended the year with 412 employees, up from 280 employees at the end of last year. 337 employees are based in the US, with 197 in Burlington, 27 in Portland, and 113 remote employees. We employ 75 people outside of the US, 53 of which are based in our office in Reading, UK. In 2013, we almost doubled our headcount in the Reading and Portland offices. Additionally, we hired 31 interns in 2013.
Acquia grew its customer base to more than 4,000 organizations. Some of the brands we've added as customers include Intel Corporation, Polycom, News Corp Australia, Timex, the National Association of Realtors, the X PRIZE Foundation, Columbia University, McGraw Hill Financial, Bart.gov and the Red Cross.
In 2013, Acquia continued to be focused on providing Drupal support to our customers. We reached the milestone of 100,000 support requests received and resolved during our company lifespan. In 2013 alone, we resolved almost 32,000 customer service requests, up 30 percent from 2012. We invested a lot in scaling our support team and on improving overall customer satisfaction and responsiveness. For example, we created a dedicated customer onboarding team. The result is that we spent more time with our customers to better understand their needs and help solve their Drupal questions. In 2014, we'll continue to keep customer success front and center. It's something we are very passionate about.
With regards to Acquia's software products, it was certainly our busiest year. Not only did we continue to invest heavily in Acquia Cloud and Acquia Network, we also launched some new products. Acquia Commerce Cloud was unveiled last quarter, providing a platform for creating content-rich, socially enabled shopping experiences. Acquia Cloud Site Factory was also released, providing a platform for launching and managing hundreds of websites. We unveiled Drupal Commons 3.0, our Drupal-based community platform, that was identified a Social Platform leader by Forrester Research. And we delivered the general availability release of the Mollom Content Moderation Platform, a content moderation platform built for the enterprise.
The cloud continues to prove to be a great way for organizations to save money, manage websites more efficiently and bring them to market faster. And Drupal is no exception to this trend -- in 2013, many organizations decided to standardize on Drupal in a big way, moving away from the variety of different systems -- exactly the vision we laid out in 2010.
And the proof is in the numbers: Acquia Cloud grew from 4,300 AWS instances at the end of 2012 to 7,300 AWS instances at the end of 2013. In aggregate, we're now serving more than 22 billion hits a month or 319 TB of bandwidth. I believe that makes Acquia the largest Drupal infrastructure provider in the world. Some of the Acquia Cloud achievements I'm most proud of include hosting the Grammy Awards (462 million visits) and hosting Red Nose Day during their largest fundraising event ever (£75 million/$113 million raised in one night).
Drupal community and Acquia
In 2013, we continued our long track record of giving back to the larger Drupal community.
- We sponsored 77 Drupal events in 2013, helping thousands of Drupal developers connect and collaborate together.
- Our product teams sponsored work on numerous important community modules, such as Media, Organic Groups, and more …
- The authoring experience work for Drupal 8 that we started last year landed in core this year, including WYSIWYG and in-place editing. We also sponsored work on redesigned content creation page and an improved blocks UI for Drupal 8.
- Also on Drupal 8, we sponsored work on the Web Services and Migrate in Core initiatives, donating the Migrate module authors' time.
- We helped set up numerous process improvements to help streamline Drupal 8 core development, including various "hard problems" discussions at DrupalCons to work through complex issues, releasing monthly alpha releases for user and developer feedback, and laying out the criteria for beta 1. We've also helped establish communication channels to help promote what is happening in Drupal 8: the This Week In Core series, and the Drupal 8.0 landing page.
- We helped the Drupal Association to establish Drupal.org Working Groups to provide better leadership and transparency to the Drupal website. Some of our team also helped assist on Drupal.org upgrade and security issues.
I'm particularly proud of Acquia's contributions to Drupal. It's part of our philosophy to give back, and we work hard to do our part by contributing to the Drupal community -- the reason why we exist. I'm proud of this because it is not trivial to give back as much as we do.
What I'm most proud of is that we have accomplished all of this "the open source way". Since Acquia's interests are so aligned with Drupal's, we try to raise the tide for the Drupal community at large.
At the end of the day, we're not selling Drupal or cloud hosting. We're selling what can be done with Drupal. The belief in the limitless. No matter what you dream, you can do it, and Drupal will get you there -- and Acquia is here to help you succeed. Thank you for 2013, and we're looking forward to working with more customers that are changing the world.
People wonder what we do at Acquia's Office of the CTO (OCTO). In order to provide some more transparency, I wanted to share how we plan to give back between today and the end of the year.
Drupal 8 beta 1
Now that we're forgoing an upgrade path for a migration path, we need to redefine the release criteria for 'beta 1'. We also need to track the issues that block beta in order to help escalate the most critical of the critical issues. We will work with the Drupal 8 core maintainers to define and communicate these criteria, and help with timely patch reviews and issue management for beta-blocking issues.
Migrate module in core
As a co-author of the Migrate module, Moshe will be assisting the core development team on the goal to get Migrate module functionality into core and support a Drupal 6 to Drupal 8, as well as the Drupal 7 to Drupal 8 migration path.
Improve the Drupal 8 developer experience
We want developers to be productive and enjoy writing Drupal 8 modules, so we will be fleshing out the D8DX battleplan based on discussions at DrupalCon Prague, and working with others in the Drupal community to ensure that we fix the most important developer experience problems in preparation of Drupal 8's release.
Develop learning resources
We will be working on a central resource on Drupal.org for developers to find the information they need in order to port their modules to Drupal 8, including documentation, tools, and other resources.
Evaluate semantic versioning
There was a lot of talk at DrupalCon Prague about lessons learned in Drupal 7 and 8 and how to do better in the future. One such area of improvement is a release strategy that allows for iterative innovation in Drupal core every few months. We plan to work with other community leaders and the Drupal security team in order to come up with a strategy around this. A component of this strategy may be to adopt semantic versioning.
Improve Drupal 8 performance
We will also dedicate the OCTO team's time to help the Drupal core community identify and fix some major performance issues in Drupal core.
Authoring experience improvements
Major development efforts on the UX features the Spark team helped get into Drupal 8 core—WYSIWYG, in-place editing, mobile-friendly toolbar —are winding down. We still have work to do on fixing up some loose ends, and are committed to see this through. We will also backport the major Spark modules to Drupal 7.
Communicate Drupal 8 progress
We aim to continue the weekly D8 progress reports that you can find at This Week In Core, and are actively seeking other core developers to help get these important posts out.
A drop in an ocean
We're a handful of contributors in the OCTO and can only do so much. We will continue doing these things within a community of hundreds of other contributors and supporting their work in other ways. We're looking forward to much Drupal 8 progress in the next 3 months!