Build It And They Will Come

In my last installment to this blog series on development contractors I reflected on my own experience managing a USAID contracting business from inside a large public company. I thought it would provide some helpful context for today’s post on AECOM International Development.

My last post concluded with the argument that, while there are certainly more complications to overcome inside a public company than a private company, a USAID contracting business can indeed be viable inside a publicly traded company. Today’s post completes the argument.

AECOM International Development

USAID 50 Ranking: #8

Average Annual Obligation: $111 Million

Imagine we’re having the following conversation:

Me: I read an article earlier this year that suggested AECOM might be the biggest company you’ve never heard of. Is that true? Have you ever heard of AECOM? 

You: It’s true ... I’ve never heard of AECOM. Who are they? 

Me: AECOM is the largest architectural and engineering design firm in the world, responsible for some of the most iconic building projects in recent history. 

You: Really. Any big projects that I might recognize? 

Me: Well, how about the tallest office tower in North America: One World Trade Center. 

You: Wrong! I happen to know One World Trade Center was built by the same company that built the original World Trade Center - Tishman Construction. 

Me: Nope. AECOM bought Tishman in 2010.

The conversation is a great example of why a lot of people have never heard of AECOM … it didn’t really exist until the early 1990s. The company’s growth has been mostly driven by acquisitions. It’s what securities analysts refer to as a "roll up.” In AECOM’s case, it’s the end product of over 40 firms being rolled together over the last twenty odd years.

AECOM International Development is just a small part of the larger AECOM. It was created back in 2004 by AECOM’s acquisition of Planning and Development Collaborative International (PADCO), and then expanded by AECOM’s acquisition of The Services Group (TSG) in early 2008. AECOM acquired PADCO and TSG in order to cultivate a special foothold for building up its business in emerging markets.  

From the looks of things today it turned out to be a smart decision. As I’ve already hinted at in the last installment to this blog series, AECOM International Development is living proof that a USAID contracting business can be viable inside a publicly traded company. According to data that I pulled off usaspending, it looks like before AECOM started the acquisition (~2003), TSG and PADCO were pulling in combined prime contract obligations of somewhere around $30 million annually. 

Now fast-forward ten years. In 2013, USAID’s obligations to AECOM totaled just over $170 million. So under AECOM the USAID contracting business grew from around $30 million to $170 million in 10 years. That’s an increase of over 500%, i.e. that’s some pretty serious growth. And, as I described in the last installment about my own experience managing a USAID contracting business from inside a publicly traded company, that’s not an easy thing for a public company to pull off. 

So what has enabled AECOM to succeed where IBM failed? 

First, it’s important to remember that all acquisitions start and end with people, so I think you’ve got to take your hats off to the folks at AECOM, TSG and PADCO that managed to figure out how to make the USAID business work inside AECOM Corporation. It’s some impressive work. 

Of course there were some important differences too. For example, AECOM’s acquisitions of PADCO and TSG were not accidental (i.e. not part of something much larger like IBM’s acquisition of PwC Consulting.) PADCO and TSG were both specifically targeted by AECOM for their work with USAID. And AECOM generally gives the companies it acquires a relatively large degree of flexibility and independence to continue running the company, i.e. AECOM has tended to focus less on integration post acquisition compared to a company like IBM.   

The regulatory environment has also been a bit less complicated. Remember that IBM’s acquisition of PwC Consulting came right on the heels of Enron’s collapse. As a result, the financial and capital markets were particularly nervous at that time about the possibility that companies were failing to properly disclose potential liabilities that could arise from offshore entities and subsidiaries. And, despite the fact that USAID field projects have nothing in common with the kind of off-shore entities that took down Enron, there were enough cosmetic similarities (e.g. foreign bank accounts, foreign hired staff, foreign procurements and sub-contracting) to trigger a lot of extra caution, due diligence, and general “noise” around the time IBM acquired PwC. 

But I think the biggest reason that AECOM International Development has succeeded is the fact that there are some real synergies between what AECOM does commercially on a global basis and what USAID has been looking for from its contractors over much of the last decade … particularly in countries like Iraq, Afghanistan and South Sudan, which is where most of AECOM International Development’s growth has come. AECOM has also been successful in securing USAID work around climate change adaptation and natural resource management, and these are also both natural extensions of AECOM’s commercial practice and corporate capabilities. 

Whatever the key reasons for its success are, there have clearly been a lot of things working in AECOM’s favor, and there are a lot of things that AECOM does well. So much so, in fact, that I have thus far been unable to pinpoint a unique signature that differentiates AECOM International Development from everyone else. And I’m not the only one struggling to figure it out. Daniel Safarik, the publications editor at Council on Tall Buildings and Urban Habitat remarked earlier this year that; "It's hard to find the heart and soul of what AECOM is … it's hard to get a grip on from an identity perspective because they're massive and acquisitive." Or, as Jacob Herson, an AECOM spokesman himself said, “AECOM is still a work in progress.”

I’m interested to see how this “work in progress” finishes its story. It could go a variety of different ways, and I think the path it takes from here will ultimately end up defining AECOM International Development's unique signature. 

Where do I see it going?

The optimist in me looks at all of AECOM's potential and my jaw drops. I think that if AECOM can start focusing more of its time, resources and energy towards organic growth, and towards integrating the firms it has already acquired, it would present a real opportunity for AECOM International Development to substantially strengthen its Project Enabling Environment (PEE), and its capacity to deliver results for USAID. I saw the potential for this first hand during my tenure with the company on its Southern Africa Trade Hub project. While I was there AECOM introduced its proprietary One Source platform to the project. I thought the introduction of that system, complete with its automated workflows for procurement and travel logistics, completely revolutionized those critical aspects of its PEE in the field. 

And, when you think about the fact that there are literally 40 companies that AECOM has rolled up in the last 20 years it’s hard to even fathom the kind of gold mine that now exists within the company in terms of useful tools, practices and knowledge. AECOM has the kind of in-house resources that, if harnessed and adapted effectively, could literally transform AECOM International Development into one of USAID’s best in class implementing partners in terms of applying the science of project management to international development engagements.

AECOM also has a secret weapon … something that none of its competitors in the development industry have. It’s called AECOM Capital. AECOM Capital is a unit that the company has established specifically to differentiate itself from its competitors. It's a mechanism that enables AECOM to make direct investments in real estate and public private partnerships (PPPs) that complement and support its traditional service offerings for clients. It’s a great concept and I think it would be awesome if AECOM figures out how to deploy it in support of its USAID programs. It would make a great unique signature ... something catchy. Maybe something like “AECOM puts their money where their mouth is."

Unfortunately, it looks like the road ahead may get a little bumpy for AECOM International Development, especially its business with USAID. One of the Wall Street analysts that follows AECOM noted earlier this year that AECOM had started restructuring its Management Support Services (MSS) line of business (which includes AECOM International Development) to make it more profitable. The report indicated that AECOM is looking to shift away from higher-volume, lower-margin international work towards more lower-volume higher-margin work in the United States. And, in a conference call earlier this month to discuss its most recent quarterly earnings, AECOM management reiterated its plans to reposition its MSS line of business away from higher-volume, lower-margin international work.

Now, I don’t think this means that AECOM International Development is going anywhere; I think the emerging markets are still very important to the company overall. But, I think AECOM's business strategy for international development work could change. I can imagine AECOM diversifying the business and shifting more of its focus towards the other big bilateral donors, and especially the multilaterals, many of whom take a more holistic "value for money” approach to development partnerships than you find at USAID.

It’s a good reminder of why running a business inside of a public company can be so unsettling. Companies like AECOM and IBM have tens of thousands of owners that aren’t even remotely involved in managing the business, but they all have expectations. At the end of the day public companies are ultimately going to do whatever they think is best to drive up their share price … If you're running a low margin business inside one of the companies you just have to keep hoping that things continue to break your way.

- DS

Next Up … Process Makes Perfect

The Big Blue Blues (Part Two)

In the last installment to this deep dive I’ve been doing on development contractors I started exploring the idea that some company ownership structures may be better suited to development contracting than others. The first two contractors that I’ve written about, Chemonics International and Abt Associates, Inc are employee owned corporations (i.e. ESOPs). The next contractor that I will be writing about is AECOM International Development (AECOM). AECOM differs from Chemonics and Abt by virtue of the fact that it is a publicly owned company. 

Because I have a lot of experience managing USAID contracts from inside a publicly traded company I understand very well all the unique challenges that can be involved. And, as I wrote in the last installment, I thought it would be useful to share some perspective before reflecting on my experience working for AECOM.  In the last post I set the stage for today’s piece by describing the landscape and events leading up to IBM’s decision to acquire PwC’s consulting business. Now, here’s what happened next ...

On July 30, 2002 IBM announced that it would be acquiring PwC’s consulting business for $3.5 Billion. Two months later, on October 1, 2002, IBM introduced a new division called IBM Business Consulting Services which incorporated the 30,000 staff, 1,300 partners, and nearly $5 Billion in revenue that had officially become part of IBM that morning.

I’m not even going to try and sugar coat what happened when we became part of IBM. The acquisition, especially that first 12 months, was a very painful and destructive experience. Prior to the IBM acquisition PwC’s USAID development practice would have ranked somewhere in the top 10 of the USAID 50. One year after the acquisition our business had already dropped so precipitously that it would have probably ranked near the bottom 10.

So what happened? The explanation is simple. The acquisition completely disabled our project enabling environment (PEE).  Here are some examples.  On the day that the acquisition became effective many of us working in the field discovered that we were already in violation of company policy simply by virtue of countries we were living/working in. An implication of that was our location codes were invalid so we couldn’t fill out our timesheets. Then, within two months, the company closed down all of our imprest (bank) accounts. Once the funds were cut off in the field we were unable to pay staff salaries for months, and we went severely delinquent on property rental agreements all over the world.  We were also required to terminate all local staff employment contracts in every one of the countries we worked in because having them was a violation of company policy … it took months before anyone could come up with a solution to formally rehire them all. All of our procurement policies also changed overnight. Everyone from inside the practice was completely removed from the procurement process (even local/field procurements) and we were replaced by a small team of english-only speaking IBM veterans in Gaithersburg, MD.  The inability of that team to appreciate the environments they were stepping into, and their inability to communicate in any language other than English, meant that basically nothing went forward for months. Once it became clear that we could no longer deliver on even basic things USAID Missions around the world started reassigning the work from our projects to other contractors. It took about six months before we could even start issuing invoices to USAID because of contract novation complications. And, once the invoices started going out they all got rejected for at least two or three iterations because nobody from within the practice was allowed to review them before they were sent out to the clients.  I could go on, but I think the picture is pretty clear.

We lost a lot of great people that first year. And those of us that hadn’t already thrown in the towel were all very frustrated. IBM management was apparently frustrated too. As we would later find out, IBM had started shopping our practice around to other development contractors once things really started to buckle during the first year, but by the time our practice went up for sale none of our competitors wanted to touch us with a 10 foot pole. I was personally exhausted. I’d been fighting fires associated with the acquisition from the field while leading several large projects in Bosnia and Serbia and I had come to feel almost helpless in my role. IBM had become the butt of every joke in USAID implementor meetings around the world. It was embarrasing. Around October of ’03 I finally decided that I'd had enough and I submitted my resignation, effective the end of the year. My plan was to return to the US - after nearly six years of building out our practice’s business in the Balkans - and find a new job.

Then a funny thing happened at the end of ‘03. What happened actually reminds me of the phenomenon that equity traders talk about trying to determine the bottom of a bear market. The idea is that a recovery won't ever really start until you finally see everyone throwing in the towel all at once. Similar I guess to that saying "its always darkest just before dawn." Well, the sun finally started to come up over what was left of our practice in early ’04. It started coming up when the company finally decided to make some important decisions that it had been putting off for far too long.

The biggest decision was appointing a clear leader of the practice. Our group’s long time leader had left us right around the time of the acquisition for a great opportunity with the World Bank group. There were three solid candidates in our practice to step into her role, but rather than appointing one of them in charge, the company chose to establish a “triumvirate” leadership structure … i.e. management by committee. In retrospect I think the non-decision ended up being costly for us, but I understand why it was a difficult decision to make. All three candidates were terrific consultants with dynamic personalities, good judgement, great experience and strong leadership skills. All three candidates were also very ambitious, so there was never going to be a natural concession of power. When the company finally decided which of the three to put in charge, the other two were quickly snapped up by our competitors ... which I’m sure is exactly what the company was trying to avoid with its non-decision.

The appointment of a clear leader for the practice was important because it finally enabled the team to mobilize around a clear vision and approach for rebuilding the business. That decision was all it took to change my mind about leaving the firm. I remember the morning after I arrived in the US in December 2003 I drove in to the office expecting to turn in my computer and fill out a bunch of exit paperwork.  When I got there I found a bunch of senior partners that I’d known from my earliest days with PW. They sat down with me, explained what they were planning, and asked me to stay on in an elevated role to help rebuild the business. I agreed to give it a shot.

I was put in charge of practice operations, i.e. I became COO for IBM’s business with USAID. My job was to rebuild our PEE. I was surprised that I got selected for the role since I didn’t have any prior experience with operations. Looking back now I realize that the reason I got tapped for the job was because I knew the USAID business and I was someone that all the former PwC partners, who were then playing senior executive roles at IBM, knew and trusted. It didn’t take me very long in my new role to realize why we had been struggling under IBM. The company had a very different philosophy around internal business controls. We had all come in to the acquisition accustomed to the governance practices you typically find in a partnership model, which are a lot different from the governance practices you tend to find in a publicly traded company. The differences were most acute with the business support functions, specifically with Procurement, Finance and Contracts. What we had not understood, or appreciated enough, was the fact that IBM's support units were not there simply to support us, they were also there to regulate us … and they took that role very seriously.

The key to rebuilding our PEE was realizing that IBM’s approach to managing the risks they perceived with our group's business operations wasn’t bad or wrong, it was just different than the approach we were all used to. The solution was to re-engage with the support units on a different set of terms. I built some structure around our teams’ interactions with the support teams and established a clear and transparent process for flagging issues and tracking them from inception to resolution. Essentially what I did was implement a micro-level version of the World Bank's “doing business” solution for improving a country’s BEE. I also focused on changing the tone of the dialogue. I asked everyone on my team to change their titles to “problem solver” for a few months, and we agreed that for a while nobody was allowed to talk about problems without also offering a solution.

Slowly but surely things started improving. The time from issue inception to resolution started dropping. The relationships between the IBM support units and our practice became more cordial. Within four months we had successfully re-enabled our PEE and by mid ’04 we were back in business. And, thanks to all the terrific work that the rest of our practice had been doing with our prospective clients and partners in the industry, we finally started winning again.

Whenever I get asked about the experience now I focus on the 4 key lessons that I learned.

1. It’s always important to remember that as a company becomes larger, and as the ownership of a company becomes more diffuse and disconnected, that company's internal controls environment is going to become more defined and rigid. 
2. When the company you work for has been acquired you need to come to terms quickly with the reality that you are now part of the acquiring company. You are not the acquired company anymore ... that company no longer exists. It’s true that in the aftermath of an acquisition both sides have to adapt and change to some extent, but the heaviest burden to adjust and evolve always falls on the shoulders of the acquired.
3. Development contracting activities expose a company’s business operations to significant additional risks and requirements that you don’t find with more traditional professional services work. Different companies choose different ways to deal with those additional risks and requirements and its important to overcome the instinct to label different approaches as "good and bad” or “right and wrong.” Different approaches are just different. 
4. It’s sometimes hard to remember that there’s always more than one side to a story. You need to hear from all sides if you really want to get to the truth. 

By the third quarter of ’04 (two years after the acquisition) we had manage to rebuild our PEE and we started winning again. Unfortunately that’s not the end of the story. Because while we managed to figure out how to make the USAID business survive inside IBM, we were never able to figure out how to make it thrive.

Why?

It wasn’t our PEE that stood in the way. The key obstacle that we could never overcome was getting USAID to understand IBM’s approach to cost allocation and cost accounting. IBM’s approach to cost allocation was extremely transparent … it charged a lot of things as direct costs that USAID was accustomed to seeing as part of indirect costs.  As a result the indirect rates were much lower.  It was an approach that other Federal agencies really liked because it effectively shrank the size of the “black box.” Unfortunately we never managed to socialize it effectively with USAID in the field. I started to see the writing on the wall in mid ’05 … and in March '06, IBM unloaded the business to Abt Associates.

What’s all of this have to do with my blog series on Development Contractors?

I think there are a few important things to take away. First, there are a lot of folks out there who are skeptical that a USAID contracting business can be viable inside a publicly traded company because of what happened with IBM. As I’ve explained in this post, and as my forthcoming installment on AECOM will also show, a USAID contracting business can be viable inside a publicly traded company. Yes, there are more complications to overcome inside a public company than a private company, but it is definitely viable.

Second, I believe the severe difficulties that IBM had with the USAID business in the first year of its acquisition of PwC were a consequence of not being prepared. It’s important to keep in mind that the USAID business was just a tiny fraction of a percent of IBM’s overall acquisition of PwC's consulting business … you might even call it an accident. Had the USAID business been an explicit target of the acquisition I am convinced things would have unfolded much differently.

Finally, I think USAID’s overly ritualistic approach to contractor cost allocation is something the Agency needs to overcome if it really wants to start establishing contractual partnerships with more large, diversified, companies. I’d like to see more of an effort to enlighten folks inside the Agency to the idea that different ways to allocate costs are not “good and bad" or “right and wrong”, they are just different. The focus should be on overall cost, or better yet, value for money. It’s an example of how the Agency can sometimes be vulnerable to losing sight of the forest for the trees. In IBM’s case, I think USAID ended up losing a partner with tremendous potential to support mission implementation.

I think it was a particularly big loss for USAID in terms of its trade facilitation agenda in Africa. While all the usual players have been lining up to bid for contracts to run USAID’s trade and investment hubs in East, West and Southern Africa, I don’t see IBM anywhere on the radar and IBM could bring a lot more to the table than any of USAID's traditional partners when it comes to trade facilitation. A lot of folks at USAID don’t even realize that one of the key reasons IBM sold its PC/Think Pad business to Lenovo was the opportunity it created for IBM to play a key role building out the trade facilitation and supply chain infrastructure accross China … arrangements that I understand were done primarily on a commercial basis. IBM has also been playing a key role in customs and trade facilitation here in South Africa, the cornerstone of the Southern Africa regional economy. Given all of IBM's experience, tools, and commercial orientation around trade facilitation, a strategic relationship between USAID and IBM would make an enormous amount of sense.

- DS

Next up … Build It And They Will Come

The Big Blue Blues (Part One)

In my last installment to this blog series on Development Contractors, I wrote about what I believe is Abt Associates’ unique signature. I argued that Abt’s unique signature is the best collection of social science/policy minds that the private sector has ever assembled under a single roof.

In that last entry I also pointed out that both Abt and Chemonics have done outstanding jobs putting women into key leadership roles, and wrote that I thought both firms’ strong performance must be linked in some way to the fact that having women in key leadership roles has made each company smarter. I may have gotten a little carried away in that last post on the topic of women in leadership and my feelings about it. If so it’s probably because I had just watched my wife give birth to our son in less than three hours of drug free labor ... my awe and admiration of everything women can do has never been higher. (Mom and baby are both doing great!)

In my last entry I also pointed out that both Chemonics and Abt have employee-owned corporate models (i.e. ESOP), and I argued that I thought the ESOP model was also a key enabler of the strong performance that both firms have demonstrated in their contracting business with USAID over the last several years.

I did not spend much time in that last post elaborating on the ownership argument because I thought the discussion needed some more context, particularly before delving into my experience with AECOM International Development (AECOM) which is #8 on The USAID 50.  The reason is that unlike Chemonics and Abt which are private, employee-owned companies, AECOM is a publicly listed corporation which is traded on the New York Stock Exchange under the symbol ACM and regulated by the Securities and Exchange Commission (SEC).

I actually have a lot of experience managing USAID contracts from inside a publicly traded company which makes me one of very few folks in this industry that truly understand the unique challenges that can be involved. I thought it might be helpful for me to share a bit of my own experience on the subject before moving on to the discussion of AECOM. To get there we need to take a step back … a little history lesson.

Don't worry, it’s funny - I promise!

There must be a few folks out there that still remember what was going on with the management consulting industry in the late '90s and early '00s. For those that don’t, there was a lot of discussion taking place back then among regulators (especially the SEC) around “The Big Five” (now known as “The Big Four") audit firms regarding the issue of independence.

Here’s what the SEC was concerned about. 

Over the 1980s and '90s, the Big Five audit firms had been building up business consulting practices to complement their traditional audit services. On the surface it all made a lot of sense for both the auditors and their clients. Think about it. Let’s say the auditors find some kind of weakness in a company’s management systems or its business controls. In the old days the auditors would just log it into the work papers, discuss it with management, and maybe reference it as a finding in their opinion on the financial statements. Well, putting a consulting practice alongside the audit practice changed this dynamic for the audit firms; it enabled the audit firms to start helping their clients solve a lot more of the problems that came up over the course of an audit, rather than just writing about the problems in work papers and opinions.

As a management consultant working for Price Waterhouse back then, I got several opportunities to see how it worked firsthand.  I was based in the firm's DC office and therefore spent most of my time metroing back and forth between various Federal Agencies in the District and NoVA doing risk management and pricing analytics for different government credit enhancement programs. Occasionally, however, I’d get asked to go out and spend a week in places like Greensboro, NC; Columbia, SC; or Minneapolis, MN to help a PW audit team there resolve issues that had come up while going over credit accounts at banks and private finance companies that were audited by PW. Those were always fun jobs for me. For one, the per diems were higher and as someone fresh out of grad school it was pretty cool when you could order a steak for dinner and stay within limit! They were also great opportunities to experience first hand the differences between business practices in the public and private sectors.

The little advisory jobs that I was occassionally doing to help the audit side of the business isn’t what registered with the SEC, what the SEC was concerned about was the growing number of massive, multi-million dollar business transformation and systems implementation jobs that the Big 5 firms had started doing for their audit clients. The SEC recognized that consulting services were becoming more lucrative and potentially more financially important than traditional audit services to the Big 5. The SEC was afraid of the possibility that a Big 5 audit opinion might get compromised by the promise of a massive systems deal, or some other kind of deal that was lucrative enough to compel the auditors to "look the other way” when there were problems with the financial statements.  As a result, the SEC started taking steps to try and protect the veracity of audit opinions by pushing for more and more demonstrable evidence of independence between the audit and consulting sides of each Big 5 firms' business.

Now by that time our firm had already become PriceWaterhouseCoopers, or PwC, after our merger with Coopers and Lybrand in July 1998. Not sure if anyone out there remembers the goofy slogan that came along with that merger. It went something like this “Now The Biggest Name in Professional Services IS the Biggest Name in Professional Services.” I actually heard that some PR firm made a million dollars coming up with that slogan. I’m still not sure if it’s true, but I know I never liked the slogan.  

Here’s what I do know is true. The whole implementation of the SEC’s drive for independence between consulting and auditing was a huge pain in the a$%! The rules came fast, they were non-negotiable, and they made absolutely no sense (at least at the time). The firm actually lost some really good people (including from our little USAID practice inside the firm), because some folks just could't comply with all the SEC's ridiculous new independence rules.

I remember one of the silliest cases because it hit real close to home. As I recall, one of the guys on our team was married to a woman who worked for one of PwC's audit clients. Her 401K plan required her to hold some portion of her company's stock. However, the new SEC rules for us were that every employee of the firm had to be financially independent from every company that the firm audited, and independence included assets of the employees and their spouses. So, despite the fact that this guy had no connection at all to any of the firm’s auditors or the audits that the firm was performing, the decision came down that he had three choices: (1) His wife had to give up her 401K, (2) He had to get divorced, or (3) He had to resign from the firm. 

We lost that guy to the dark side … I think that was like early 2001.

Of course there is a silver lining to every story. I actually got a lucky break from the whole thing. I was becoming an aficionado of golf equipment at the time and decided in late 2000 to buy some stock in Callaway Golf (ELY). Well, you can probably imagine that I was not too happy when I found out that I had to sell my shares in ELY as a result of these new SEC independence rules that came into play. I didn’t even know that PwC was Callaway's auditor, let alone have any inside information about the audit! It turned out that being forced to liquidate at that time was a blessing in disguise. I’d bought the stock a year earlier for around 15 bucks a share and when I had to sell it the price was close to 20. And I think that's as high as it ever got. These days - almost 15 years later - it’s still trading somewhere down around 7. 

I would have gladly traded the $500 bucks I made on ELY to keep everyone on our team together. And of course the real silliness about all those SEC independence rules is that they ultimately failed to prevent what the SEC was really worried about. The whole issue finally blew up in late 2001. It was probably inevitable.

In October 2001 Enron Corporation - one of Wall Street’s darlings - reported a quarterly loss for the first time in over 4 years. A month later the company announced that it would be restating its earnings for each of the previous four years. That would have the effect of reducing the company’s net earnings by nearly $600 million. Later that month the ratings agencies downgraded Enron's bonds to junk status. Enron filed for bankruptcy in early December. The collapse triggered a massive rethink of corporate governance practices in the United States and ultimately led to the passage of the Sarbanes Oxley Act in 2002.

So what’s the relevance?

Well, as most people probably know Enron’s auditor, Arthur Andersen, admitted to making some key mistakes in its audits of Enron. Those mistakes ultimately fostered Enron's collapse. Arthur Anderson also collapsed as a result of its role in the fiasco, turning the Big 5 into what we know today as the Big 4. In the aftermath it became clear that Arthur Andersen’s extensive consulting work for Enron is ultimately what caused its judgment to be compromised on key aspects of its audit work. In fact, the records now show that Enron paid Anderson nearly $52 million in 2000, and $27 million of that was for consulting services. It turned out to be exactly what the SEC had feared about the Big 5 firms all along.

For those of us that were part of PwC consulting, 2002 was a very turbulent year. After the Enron meltdown and then Anderson's collapse the writing was clearly on the wall ... PwC's consulting business was up for sale. As I recall, the other Big 5 firms had already taken big steps by that time to deal with the inevitable need to separate. Most of Anderson’s consultants managed to escape the firm’s meltdown because Anderson consulting had already renamed itself “Accenture” before the Anderson brand became toxic. KPMG spun its consulting business off under the name “Bearing Point.” Deloitte and Touche had already created a separate company called "Deloitte Consulting” and Ernst & Young had already sold off its consulting business to the French IT company "Cap Gemini.”  

The only ones left were us … the consulting side of PwC. And the whole Enron & Anderson fiasco made the need to do a transaction much more urgent. Unfortunately, the urgency also drove down the value of the business. There are rumors out there that HP was actually very close to acquiring PwC's consulting business for around $18 Billion in mid 2001 but they walked away from the deal when the markets started reacting to all the Enron noise. 

For a very brief moment in time it looked like PwC was going to be spun off through an IPO under the new name “Monday.” Anyone remember that? We all suspected that it was a hasty decision when the announcement came out. We actually got emails to a link announcing the new company and branding philosophy. If I remember correctly that link was something like www.wearemonday.com. Our suspicions that it was a hasty decision were confirmed when it became clear that the firm forgot to register the corresponding UK domain www.wearemonday.co.uk.  And, as hundreds of thousands of people would find out over the following week, not only had that UK domain already been snapped up by some enterprising comedians, but there was already a website up on the domain with an animated film of two donkeys having sex while laughing out loud about a goofy new company called Monday.

Embarrasing start. But it didn’t matter because before they could find a way to get the animated donkey sex film off the new firm's UK web domain, news had already broken that there was a new buyer for PwC’s consulting business. All of us were about to find out what life was like inside a large, publicly traded company ... and we would all soon discover the unique challenges that created for contracting with USAID.

I actually found out about it through a phone call I received early one morning from my client at the USAID Mission in Bosnia. He wanted to know if the news meant that everyone on my team would be getting a brand new computer. When I told him that I had no idea what news he was talking about (not having seen the news yet) here’s what he said. 

“Congratulations are in order Drew. You guys are getting bought up by IBM!" 

- DS

Next Up … The Big Blue Blues (Part Two)

Extra Homework Please

In my last installment to this blog series about development contractors I wrote that large, diversified companies (i.e. companies that offer multiple services to multiple industries with multiple clients) can have a very tough time competing against well run, purpose-built development contractors like Chemonics.  I argued that large, diversified companies probably shouldn’t even try to beat a company like Chemonics at its own game and instead should craft business strategies around what they can bring to the table that Chemonics can’t.  I concluded by suggesting whatever that might happen to be would play a big part in defining the company's unique signature.

Today's post starts an examination of how well the logic holds up. Today we’ll take a look at #6 on The USAID 50

Abt Associates, Inc
USAID 50 Ranking: #6
Avg. Annual Obligation: $165 Million

For this one let’s shake up the format and make it more interesting.

Multiple choice question.

Which of the following characteristics represents Abt’s unique signature?

1. Abt does an outstanding job of putting women into key leadership roles.
2. Abt is owned (and therefore managed) by its employees.
3. Abt has the best collection of policy/social science minds in the business.

Let’s quickly explore each of these three possibilities.

(1) Abt does an outstanding job of putting women into key leadership roles

Yes it does. In fact, according to Abt’s webpage the company currently has 36 officers and 20 of them are women, including the current President/CEO. And by the way, during the current CEO’s tenure the company has literally taken off, nearly doubling in size (both in terms of revenue and full time staff).

Abt clearly does an outstanding job of putting women into key leadership roles, however that is not Abt’s unique signature. Why? Because its not unique. Who else does it? Well, for starters how about Chemonics? Last year Chemonics appointed its first women President/CEO and there are four women currently serving on the company’s senior leadership team.

Now I actually think this is all a pretty big deal so I’m going to get into it a little bit.

This may sound strange coming from a man, but women in leadership is actually one of the first things that I check now when I'm considering new opportunities. I really want to see that a company has a clear track record of, and commitment to, putting women in key leadership roles before I go to work for them.

Want to know why?

Because it looks good to clients/USAID? It does look good to USAID, but that’s not why I care. Because it’s the right/fair thing to do? It is the right/fair thing to do, but that’s still not the main reason I care. Because I have a three year old daughter that might rule the world someday? Yes, but that’s still not the main reason I care.

Here’s why it’s important to me. Putting women into key leadership roles just makes your teams smarter and that makes your company perform better. Don’t believe me? Just listen to the researchers from Harvard who found a few years ago through repeated studies that if a group includes more women its collective intelligence rises.

In terms of recognizing the importance of gender integration in the workforce I’ve come to realize that I got very lucky early in my career. I happened to start my professional career working for a company that was still dealing with the aftermath of having just lost the highest profile case ever involving sex discrimination in the workplace.  A woman in the Price Waterhouse office that I went to work for out of graduate school had been denied admission to the partnership even though she had an iron clad business case based on her performance. She sued the firm. Her case went all the way to the Supreme Court and the court found in her favor. After the decision (which came in May of 1989) she came back to the firm as a Partner and finished out her career.

When a company goes through something like that they have no choice but to start changing things about their culture. When I arrived at the company in mid-1993 the ratio of men to women in management and leadership roles had already started to rise.  Over the next decade (during which time PW become PwC) the company admitted dozens of exceptionally talented women to the partnership. I got the chance to work for quite a few of them, including the one that started it all.

I only got to work with Ann Hopkins a handful of times but I still remember each of them. She had a big personality and a great sense of humor. She was cool. She was also brilliant, and she commanded respect. The way you knew she liked you was if she ever asked you to join her in the parking garage for a smoke. I know she like me because I got invited for four of those sessions. She never offered me a cigarette, but I think that’s because she could probably tell that I didn’t smoke.

What I’ll never forget about Ann was how adamant she was about writing and structuring documents. If you wanted to work for Ann your writing had to be crisp and concise, and all your documents had to be in two column landscape format. Why?  So readers didn't have to flip the book around to see charts and exhibits.  To this day I still put documents in landscape mode whenever I can.  I’m not sure if its more because I agree with Ann that readers shouldn’t have to flip the book around (I do) or more because its a way to celebrate the important changes that she made happen in the company that so profoundly shaped my career. I guess its both. Here’s one thing I do know for sure. All of USAID’s  economic growth programs in Pakistan have been doing their annual work plans and PMPs in two column landscape format for over 5 years now. You’ve all got Ann to thank for that.

Given all that was happening at PW in the 90s and early 00s it’s probably also no surprise that the most influential mentor I’ve ever had in my development career is also a woman. I could go on and on and on about all the things she taught me and why she is so revered by everyone that’s ever worked for her, but for the purpose of this post I’ll focus on the thing that’s most important and relevant.

I was running a Corporate Governance program for USAID in Bosnia at the time - early 2002 - and she was in country for one of her regular check-ins with me, our team and the clients. At the time I was trying to write a memo outlining some things that we felt required a modification in our contract. I was struggling with the introductory text.

Anyway, my boss looked at what I’d written, thought for a moment, and then put it down. Here’s what she said.

Drew, here’s the thing. Companies in Bosnia aren’t going to adopt better governance practices because regulators try to force them to do it. The whole point of this project is to help companies realize that they should want to adopt better governance practices. Fines and sanctions aren’t going to get anyone’s attention in this environment. What you need to do is help these companies understand that good governance practices are ultimately whats going to enable these companies to attract capital, compete and grow. It has got to be a "want to" thing, not a "have to” thing.

That quick four-minute conversation got everything I was trying to say focused and it ultimately got us all back on track.  And btw, thanks again for that insight Tessie!

Here’s why I’m bringing it up here. I think grappling with the difference between “have to” and “want to” in that context of better governance has made it a lot easier for me to understand the transformation that our industry is now going through in terms of how to approach gender integration efforts. I know there are still a lot of folks out there that think gender integration is a box-checking, affirmative action, compliance sort of thing. Well its not. Integrating gender in this modern era of best practices is about getting project teams, counterparts, and host country systems to want to do it because it’s what will ultimately make their efforts more impactful and more sustainable.

Sorry for going off on a tangent, I just think its really important for our industry to start to move more quickly and more decisively to transcend the old bean counting concept of equitable participation when it comes to gender integration. It needs to be a "want to" thing, not a "have to" thing.  And, I guess there’s probably a good chance that development contractors who have figured out how to integrate gender effectively in their own back yard are going to have a lot more success integrating gender effectively across their programs in the field.
   
(2) Abt is owned by its employees

This is also true and I think it is an important reason that Abt has been so successful. However, just like the outstanding job that Abt does putting highly talented women into leadership roles isn’t unique, neither is its employee-owned company structure.

What other large development contractor is employee owned?  This is starting to sound like a broken record isn’t it? Nine letter word that starts with C. Anyone?

Yep. Chemonics.

In the next installment of this blog I’ll be sharing a few reflections on the experience I had working for IBM ten years ago to help contextualize what I think gives employee owned companies such a huge advantage when it comes to development contracting. So I won’t go into it too much today. But there is one thing about Abt in particular that completely intrigues me and maybe someone out there can help me understand how they make it work.

If you look at the data on USA Spending you’ll see that Abt’s partnership with USAID is much broader than just the obligations the company receives through contracts. Abt does a ton of work under cooperative agreement (i.e. grants) with USAID. In fact, if my calculations of The USAID 50 included both grants and contracts Abt would probably jump decisively into the top five.

Now I don’t know a lot about cooperative agreements (I wish I knew more) but my understanding is that “cooperative” pretty much means “co-funded.” In other words, not only can’t you collect a profit/fee on the work, but you’ve also got to put some of your own money or assets to work on the deal.

If that is the case, where does a company like Abt get the resources to put its share into cooperative agreements? Or more pointedly, are they using the fee they earn from contract work they do to buy back into the grant work they want to do? If so, I think that is absolutely remarkable.

In fact, it feels kind of like a grown-up version of students asking the teacher for more homework, doesn’t it?  Also sounds exactly like the kind of thing you’d expect from the best collection of policy/social science minds in the business, doesn’t it? Especially if those minds also happened to own and run the business.

(3) Abt has the best collection of policy/social science minds in the business

The funny thing is that I was first exposed to Abt over 20 years ago, years before I'd even started thinking about getting into development work. Here’s how I recall first learning about the company.

When I first started my career with Price Waterhouse I worked for a little group inside the firm’s Federal Government practice that built and maintained risk analysis tools for the US Department of Housing and Urban Development (HUD). Our job was helping two agencies inside HUD - the Federal Housing Administration (FHA) and the Government National Mortgage Association (Ginnie Mae) - figure out what would happen to their multi-billion dollar mortgage guarantee programs (i.e. how much would taxpayers have to cough up) if the United States ever experienced a serious downturn in the housing market.  (In case you’re wondering it turns out we were quite a ways off, just like everyone else’s!)

Well, one morning I'm sitting in my bosses office waiting to start a meeting. While I’m waiting the mail clerk pops in and hands me a document, asks me to put it on my boss' desk. I looked at it and noticed that it was an RFP from our client the FHA. (Yeah, this was back before people were really using the internet). Anyway, I start flipping through the RFP and realize that FHA is planning to commission a whole new set of risk analysis tools which would eventually replace the ones that our group had been building and maintaining for over five years.  When my boss finally showed up (he always had a fluid sense of time) I handed him the document.  Clearly he was expecting it because he didn’t even look up, he just asked if it was the RFP to build FHA’s Loan Level Microsimulation Model. I said yes and told him that I thought it looked really interesting. Then I asked him why none of us knew about it and why we hadn’t already been strategizing for our proposal.  I’ll never forget his answer.  Here’s what he said:

"No chance man … Abt wrote the book on that."

He was right. Abt won that one. We didn’t even submit a proposal.

I first went to work for Abt 15 years later as a consultant in Pakistan. Abt brought me out to help them establish some private sector alliances to leverage and scale the investments USAID had made in hygiene promotion through their project.  It was a fun assignment I think largely because I actually managed to get deals done with a couple of large multinational consumer products companies operating in Pakistan.  It was also interesting because it involved something entirely new for me: establishing dozens of community-managed water filtration plants. I ended up learning quite a lot about the subject while I was out there helping them on that project. Any guesses why? Abt’s project director wrote his PhD dissertation on the subject.

A year later I went back to work for Abt in Pakistan to help them out on a USAID-funded workforce development initiative. Guess who else was there? One of the original architects of the Americorps program who at the time happened to be directing all of Abt's work with the US Department of Labor. Abt brought him out to Pakistan for that first two weeks of the project for work planning meetings so he could share some perspective and let the client and resident project team pick his brain. He had some fascinating insight and some great ideas. When he left he gave everyone his card and said to call him if we wanted to brainstorm any new ideas that came up.

All development contractors try to provide those kinds of resources whenever they can, but what makes Abt unique is that they don’t have to use freelancers to do it. They’ve got these people on their full time staff.

How do they do it?

Simple. Chemonics and Abt both do health for USAID but Abt also does health for the US Department of Health and Human Services (HHS), the US Department of Veterans Affairs, Blue Cross/Blue Shield, the Bill & Melinda Gates Foundation and the New York State Department of Health.  Chemonics and Abt both do economic growth work for USAID but Abt also does it for the US Department of Commerce, the US Department of Treasury, and the Federal Reserve System.  I could go on but I think you probably get the point.

The bottom line is that contracting with Abt gets you access to the best collection of social scientists that the private sector has ever assembled under a single roof. There is no way you could ever put together the breadth and depth of technical/policy talent that Abt brings to the table if your only client was USAID. First of all, you'd never have the revenue that you’d need to afford them all. More importantly, I don’t think you’d ever be able to keep them all interested. Because it has such a diverse base of clients Abt can afford them … and keep them all interested at the same time.

Abt defines their unique signature as "Bold Thinkers Driving Real World Impact.” I like it. It’s true, and it definitely works for me. Also probably a much better way to capture it than the way I’ve always thought of the company. 

But I just can’t help it. To me Abt will always be “Scary Smart People Still Asking for Extra Homework."

Flip a coin for the catchier phrase ... either one is a great reason for USAID to love them.

- DS

Next Up ... The Big Blue Blues

The USAID 50

Unique Signatures Across the Industry (Part 2)

In the last installment of this blog series on development contractors I laid out what I believe are two truths about Chemonics International.

1. Chemonics provides the "best in class" Project Enabling Environment (PEE) to its programs around the world and I believe this is ultimately what makes them such a powerhouse in development consulting ... and such a formidable competitor for the rest of the industry.
2. Despite everything I'd always believed about Chemonics the truth is that you won’t find Darth Vader walking its halls. It turns out that Chemonics is just a well managed organization with great systems, highly engaged staff and some serious talent, especially when it comes to getting big, complicated and urgent things done for USAID.

In today’s entry I continue my efforts to advance the key theme of the blog series (Every Organization is Different) by examining unique signatures accross the industry.

In order to get to next couple examples we’ll have to skip down a few slots on The USAID 50. 

The reason is that I've not yet had the opportunity to work for #2 John Snow (JSI), #3 The Partnership for Supply Chain Management, #4 Development Alternatives, Inc. (DAI), or #5 Tetra Tech. And remember, my argument is that you can’t really know what any particular company’s unique signature is until you’ve rolled up your sleeves and gone to work for them.

If you want to hear what I think your company is great at you’ll have to hire me for an assignment! Alternatively, if anyone out there is interested in taking a stab at the companies I have to skip, I’d be happy to post your thoughts on an organization’s unique signature here under your name. Just email me at Drew.Schneider.MPP@gmail.com

The next two companies that I’ll be writing about in this blog series are Abt Associates, Inc (#6) and AECOM International Development (#8). Unlike Chemonics, whose entire business is focused on development contracting with USAID, Abt and AECOM are large, diversified services companies. In other words, while Abt and AECOM both do a fairly sizable volume of development work for USAID, development consulting is only one part of each company’s overall business.

The point is worth a bit of examination.

I suspect it may be tough for some of the folks in this industry to really appreciate just how challenging it can be for a large, diversified company to do field-level development work with USAID. Working with USAID involves a lot of idiosyncratic business practices that often don’t align easily with the business practices of more traditional, mainstream professional services work. USAID does a lot of things its own unique way. Not only is USAID’s way a fairly significant departure from that of most other US Federal Agencies, its an entirely different game altogether compared to the private sector. I know this because I'm intimately familiar with the headaches that can be involved … I had to deal with them for over a decade while I was managing USAID work from inside Price Waterhouse, PwC and IBM.

Its an important thing to recognize because it has implications in terms of the insight that I'm trying to share through this blog series. The whole discussion about Project Enabling Environments (PEE) that I’ve introduced is a good example. As you’ll recall, in the last installment I argued that Chemonics’ industry leading PEE is largely attributable to its solid leadership, highly effective support units, and its clear organizational commitment to quality management systems. All very important. All very true.

What I didn’t mention in the last post, because there was no proper context for it there, is that Chemonics’ industry leading PEE is also at least partly attributable to the fact that the entire organization - from top to bottom - is purpose built around USAID’s idiosyncratic business practices.  I’ve come up with a little metaphor that I thought might help hammer that point home.

Check out the photo below. Ever seen one of these?

It’s called a "Sprint Car.” A Sprint Car has only one purpose … it goes really fast in tight little clockwise circles on a racetracks covered with dirt.  As far as cars go, Sprint Cars are pretty funky. They have different sized tires on the inside and outside which makes it almost impossible to drive them in a straight line. And, the large, asymmetric winglike thing on the roof means that a Sprint Car driver can’t really even see out the left side. You’d never see one of these things on a drag strip or a Formula 1 course, let alone a highway or your neighborhood side streets. But nothing can go clockwise around a small dirt track better than a Sprint Car.

If the only thing you ever did was drive clockwise around a small race track covered with dirt you'd definitely want to drive a Sprint Car. But what if your life was more complicated than that? What if you also needed to use your car to drive to the grocery store? Or haul the new fridge home, or pick your kids up from school, or drive them to soccer practice? What if you also needed something to go camping with a few weekends each year? and drive to Florida every summer so your kids could spend time with grandparents?

Well if that was the case you’d need something a lot more versatile than a Sprint Car … maybe something more like a Jeep. (FYI, for any trivia night players out there here’s a nice little tidbit you should file away!)

Chemonics is like a Sprint Car. It is an organization deliberately designed for the sole specific purpose of development contracting with USAID. By contrast Abt and AECOM are like Jeeps. Both companies have multiple service offerings for multiple industries with multiple clients, so they need to be a lot more versatile. The need for versatility comes at a cost. Because the large, diversified companies that work in this industry are not purpose built specifically to contract with USAID they have to work a lot harder and smarter in order to keep up with Chemonics.

Here’s what I think it all means. If you are a large, diversified company I think its a mistake to believe that you’ll ever get to a point where you can consistently beat Chemonics at its own game. I do think you’ve got to work on making your PEE as effective as possible just to stay competitive, but you need to realize that your PEE will probably never rival what Chemonics has to offer.

That’s why effective business strategies for large, diversified companies that are competing against Chemonics need to focus on what your company brings to the table that Chemonics can’t. And, whatever that is should probably also be what the folks inside the industry come to recognize as your company's unique signature.

In the next installment we’ll see how well the logic holds up.

- DS   

Unique Signatures Across the Industry (Part 1)

In a recent installment to my blog series about USAID Development Contractors I introduced the argument that every contracting organization has a unique signature and that differentiation among development contractors tends to be revealed through a company’s strengths rather than its weaknesses. In this entry I've started to advance that argument by reflecting on my own experiences working for different companies in the development contracting industry.

As my regular readers know, in between I took a quick break to introduce the concept of PEE (short for Project Enabling Environment). I did that because I thought it would be helpful to socialize the key ideas behind PEE before diving into the details of my experiences with different companies. Since our industry's workforce is largely made up of migratory consultants like myself I think its important for USAID and its contractors to occassionally try to look at things from our vantage point. In my own experience I have seen a strong correlation between a company’s PEE and the likelihood that its project teams will be able to achieve a real, sustained impact in the field. And, from my perspective, each development contractor’s unique signature also tends to be shaped by some specific characteristic(s) of its PEE.

I got a little stuck trying to decide how to best dive into the next part, i.e. trying to figure out the the best way to share reflections on my experiences with the different development contractors. Where should I start? Should I go in chronological order? Should I go from most favorite to least favorite? What’s OK to say? What’s not OK? 

Well, ultimately I decided that the best way to approach it was to just go back to "The USAID 50” that I first introduced in Every Organization Is Different and flip a coin. Heads and I'd go through the list from top to bottom. Tails and I’d go from bottom to top.  So I reached into my bag and found a 2 Rand coin. I tossed it onto the table and it landed Kudu side up. 

Never been to South Africa? It means I’m starting from the top.

Chemonics International
USAID 50 Ranking: #1
Avg. Annual Obligation: $562 Million

When I first started working in development nearly 20 years ago we had a joke inside our practice at Price Waterhouse for whenever we lost someone to Chemonics. We mused that a defection to Chemonics was just another person surrendering to the dark side of the force. Not everyone was cut out to be a Jedi, right?

My first journey to the dark side started about five years ago when I went to work as a consultant for FIRMS, a USAID-funded private sector development project in Pakistan run by Chemonics. When I showed up for my first day of work on that project I was secretly expecting that I’d finally meet Darth Vader, his twin brother/sister, or maybe even the Emperor himself! That never happened. In fact, after working with the Chemonics team in Pakistan off and on over the last five years I have developed a completely different perspective of the organization.

As the numbers clearly show Chemonics absolutely dominates this industry. Its USAID contracting businesses is nearly twice as big as it largest competitor, DAI. (I consider DAI to be the nearest competitor to Chemonics because they are both multi-disciplined USAID contractors.) Regardless, any comparison of the leading USAID contractors inevitably leads to the following question. Why is Chemonics so dominant?

I think the answer depends a lot on who you ask. The Chemonics haters out there - and there are a lot of them - tend to claim that Chemonics is an awesome sales organization. And that’s it  (i.e. all they care about is winning.) The haters like to portray Chemonics as a well-oiled proposal machine that has been fine-tuned over the years to quickly and simply figure out four things … and four things only. (1) Who is influencing procurement decisions? (2) What do those decision makers want to hear in terms of a technical approach? (3) Who do those decision makers want to see leading the project team? And (4) How do we put it all together in a pretty, clearly written, and easy for USAID to score, proposal.

The haters may be right about the sales side of the company. Frankly I don’t know because I’ve never worked with Chemonics on a proposal, but I do have to confess that it does sound like a winning formula from a sales perspective.  Where I do have experience with Chemonics is what happens after the company wins and what I’ve discovered is that there's an important thing about Chemonics that the haters usually fail to mention (or that they just don’t know about.)

What is it? Very simple. Chemonics has the best PEE in the business.

If you are an implementor, especially on a large and/or complicated project, working for Chemonics is awesome. Chemonics surrounds its projects with a dream team of operational specialists from its home office that I can tell really take pride in being knowledgeable, crafty/resourceful, and helpful. Almost all of the Chemonics folks that I’ve worked with have been genuinely interested and engaged in their work. Its cool to see, and I think its an impressive reflection on the company’s senior management.

Want an example?

OK. Lets say you find one day that you need to urgently procure a million rainbow trout eggs that will generate really high yields of fingerlings. Only there’s a catch. The fish that hatch from those eggs can’t be able to reproduce among themselves to make sure that they don’t threaten the indigenous species of the area. Good luck, right?

Well, if you happened to be working for Chemonics at the time - like I was - you’d be delighted (and sort of shocked) to find out that Chemonics already has all the required documents (i.e. approval requests, background information, purchase order language, etc…) that you need to push through such a complicated procurement. They even have notes/records on which global vendors are qualified to supply such eggs - and which aren’t - so you can move the whole thing forward efficiently and effectively. And, if you encounter problems along the way (which is inevitable) there is always someone inside the organization that’s ready and willing to step in and engage with the team, the counterparts and the client … basically wherever you want help.

Want another example?

OK. Lets say you need to quickly get economic activity restarted in a remote, turbulent part of the country that has just emerged from armed conflict with insurgents. The immediate task at hand is figuring out how to put $10 million worth of small grants into the hands of local, private businesses in order to reconstruct facilities, replenish working capital, and restart operations.

If that kind of request ever comes your way - like it did mine - I can tell you that you really want Chemonics backing you up. I was floored by how quickly and effectively Chemonics was able to respond to the situation. Less than two weeks after we received the request from USAID to do the grants Chemonics had mobilized a “grants under contract” guru (and I mean guru!) from the home office to sit with me at my desk in Pakistan helping to think through the process, build out the operational infrastructure necessary to make the disbursements happen, and put together the training materials etc... that were required to socialize everything with our internal staff; engage contractually with our local partners; and make sure the whole system complied with the terms of the contract and all of USAID's various rules and regulations.

Want another example?

I’m happy to share more, but not right now. Hit me on email at drew.schneider.mpp@gmail.com if you’d like to know more.

Right now I want to get to the point. If you are a USAID Mission with a big, complicated, high profile and/or time sensitive problem to solve / program to launch, your safest bet right now is to call Chemonics. There’s no other organization out there right now that can get big, complex things done as well, and as consistently, as Chemonics. Period.

Chemonics’ effectiveness on the implementation side of the business is not an accident. Based on my experience it is clear that Chemonics actually cares a lot about management systems and how those systems impact quality. Setting up an environment that enables their projects, and the consultants working on those projects, to do their jobs effectively is a key part of the overall Chemonics strategy.

Don’t believe me? Do you know that Chemonics actually has ISO 9001 certified management systems. Is that news to you? If it is don’t worry, you are in good company as our industry’s appreciation of the importance of, and potential for, effective management systems is still emerging. And, as that appreciation grows I am convinced that more and more people in the industry are going to start to see the connection between Chemonics’ PEE and the kind of things that its projects are able to accomplish in the field.

Now, before I close this one out I think its important to remember that the basis of my overall argument for this blog series is that every company has a unique signature, and that an organization’s signature is generally revealed through strengths rather than their weaknesses. That’s why the focus of this discussion is on strengths.  I'm sure Chemonics has plenty of organizational challenges to overcome ... every company fumbles the ball from time to time. There are plenty of things that I think Chemonics can and should be doing to strengthen its industry leading PEE, but this isn’t the right time or place for that kind of reflection or discussion.

For now I’ll leave it like this. The next time you hear someone suggest that Chemonics is nothing more than a well-oiled proposal machine ask that person if they’ve got any first hand experience with Chemonics' PEE? If they don’t, then do them a solid and let them in on what really makes the industry’s leading signature so unique and so formidable … every company deserves to know the truth about why they lose so many bids to Chemonics.  

Oh ... and you can also reassure them that Darth Vader is nowhere to be found.

- DS

Next Up … Unique Signatures Across the Industry (Part 2)

A Quick PEE Break

One of the coolest things about doing development work is the opportunity it affords to invent and use acronyms. Our industry’s use of acronyms is kind of like the texting slang that today's teenagers use … both tend to require outsiders to use a decoder.

One of the acronyms that is often used in our industry, particularly among those who work in the area of economic growth and trade, is BEE which is short for Business Enabling Environment.

USAID’s Microlinks does a great job of describing what a business enabling environment is, and why it matters for economic growth and trade.

"The business enabling environment (BEE) includes norms and customs, laws, regulations, policies, international trade agreements and public infrastructure that either facilitate or hinder the movement of a product or service along its value chain. Burdensome and unpredictable regulation is costly both in terms of the time and money required for compliance as well as in opportunity cost. Reform of the BEE can result in substantial benefits for an economy including faster growth, less unemployment, more gains from trade, greater formalization, reduced poverty, less corruption and lower budget deficits."

In fact BEE is seen within the development community as such a critical enabler of growth and trade that the World Bank has set up an entire division to analyze, benchmark and improve the business enabling environments of the 189 countries that participate in its program.

The World Bank’s “Doing Business” project focuses on a number of regulatory and administrative areas that influence the relative ease or difficulty of doing business in any particular country. The effort tracks ten sub-indices related to a country’s business enabling environment and it provides an aggregate score based on a weighted average.

Want to know which country currently makes it the easiest to do business? According to the Doing Business team the answer is Singapore. (The US is ranked #4) Which country makes it the hardest? Chad. And the Doing Business portal doesn’t just tell you the answer, it goes to great lengths to explain why.

At this point you might be thinking "hey Drew, there’s got to be a point to this this whole thing about BEE right? … why don’t you get to it already?” 

Point taken, I just couldn’t figure out a better way to introduce the concept of PEE than first talking about BEE.

PEE is short for Project Enabling Environment. PEE is a concept that I have coined to describe how effectively a development contractor’s combination of systems, processes, management approach, home office resources, culture, etc… facilitate its project teams' efforts to deliver results.

The analogy is pretty clear right? Want your country to generate more jobs, more exports and more tax revenue? Make it faster, easier and more predictable to do business inside (and at) your borders.  Want your projects to generate better, more impactful, more sustainable results? Make it faster, easier and more predictable for your project teams to get things done.

And, just like BEE isn’t the only thing that matters for driving increased economic growth and trade, PEE isn’t the only thing that matters for driving more and better results. Neither offers a full solution, but both are a key part of their respective overall solutions.

The development community has had good success improving BEEs around the world by focusing on a few key things. The Ease of Doing Business Index boils most of it down to this:

1. Starting a business
2. Dealing with construction permits
3. Getting electricity 
4. Registering property 
5. Getting credit 
6. Protecting investors
7. Paying taxes 
8. Trading across borders 
9. Enforcing contracts 
10. Resolving insolvency

How would one go about cultivating a similar recognition of - and commitment to - improving the project enabling environment? Sharpen the focus and boil it down into a list of key things. The list might look something like this:

1. Setting Up A Project
2. Obtaining Required Approvals 
3. Allocating and Managing the Budget
4. Issuing Subcontracts and Purchase Orders 
5. Administering the Office
6. Hiring and Mobilizing Short & Long Term Staff 
7. Obtaining Computers, Software, Telecoms
8. Managing Logistics, Travel and Housing
9. Project Reporting / Monitoring & Evaluation
10. Managing Client Expectations

When you bring up the subject of PEE with the leadership of a USAID contractor they are always quick to point out that the complex web of federal procurement guidelines and USAID specific regulations creates some serious complications in terms of ensuring compliance. And of course they are right, the USAID/federal compliance environment can be a nightmare to deal with, especially for organizations that are not experienced with it.

While they are right  I don’t think the complexity of complying with USAID/USG rules and regulations  is an excuse for development contractors to ignore the effectiveness of their company’s PEE.

Think about it. The reason business enabling environments are challenging isn’t because countries set things up to frustrate business and discourage trade. (well, not always anyway) Challenging enabling environments are very often just the consequence of different agencies within a country each setting things up to comply with their specific requirements and preferences while failing to take into account how those choices impact the ease of doing business.

What we have learned now as a community through years of designing, implementing and evaluating BEE support programs is that a country can substantially improve its business enabling environment without changing the key regulatory objectives. It’s often simply a matter of streamlining processes, sharing information, integrating systems, training the workforce, automating workflows, establishing goals/targets and measuring results.

The same concept applies to a company’s PEE. Development contractors can absolutely improve their project enabling environments without compromising their compliance objectives. And they know it. The problem is that doing it requires focus, time, and financial investment … on activities that project teams in the field can’t write about in their weekly updates to USAID.

It’s a problem because development contractors perceive USAID as being oblivious to the idea that better project enabling environments lead to stronger development results and a more sustained impact. It is true that USAID generally doesn’t want to hear about anything, or pay for anything (directly or indirectly) that isn’t obviously linked to immediate programmatic results. Several different friends of mine that work in the home offices of the big development organizations have told me that their companies would really like to do more to streamline and automate their processes and systems, but that it’s just too tough to justify investments in something that USAID doesn’t care about.

Until USAID starts to recognize and appreciate the connection between PEE and Development Results, development contractors aren't going to move too far or too fast to improve their respective PEEs, even though many of them recognize its relevance and importance. There’s a clear opportunity here for USAID to take a few small steps to make it more of a priority and increase the return on US taxpayers’ investment.

Here’s what I recommend. In its next RFP, USAID should augment that decades' old requirement for offerors to describe their "Management Approach” with a new requirement to describe any innovations offerors have undertaken in the last 12 months to improve their project enabling environments.

- DS

Next Up … Unique Signatures Across the Industry.