Mt Moriah (33) – Putting It All Together (Part 1): the ChildFund Australia International Program Team

May, 2018

I began a new journey two years ago (May, 2016), tracing two long arcs in my life:

  • Climbing all 48 mountains in New Hampshire that are at least 4000 feet tall (1219m), what is called “peak-bagging” by local climbers.  I’m describing, in words and images, the ascent of each of these peaks – mostly done solo, but sometimes with a friend or two;
  • Working in international development during the MDG era: what was it like in the sector as it boomed, and evolved, from the response to the Ethiopian crisis in the mid-1980’s through to the conclusion of the Millennium Development Goals in 2015.

*

Picking up the story in July of 2009, I flew to Sydney for what would become 6 great years as ChildFund Australia’s first International Program Director; Jean would join me there in a few weeks.  In two previous blog entries of this series, I described how I was thinking about programming, and about putting together a strong set of teams in Sydney and overseas, as I approached this exciting new challenge.

In many ways, as I headed towards Sydney, I was hoping to put it all together: 25 years in international development and social justice, designing and implementing programs and partnerships, building cohesive and high-performing teams – this was my chance to start afresh with all of the lessons learned over those decades.  To really get it right.

In this article, I want to introduce the program team at ChildFund’s head office in Sydney – the “International Program Team” – share a bit about the great people I worked with, along with a description of how the team’s staffing and structure evolved.  I would approach this task very mindful of what I had learned in Plan International, especially how we refocused and restructured the agency; and keeping the lessons about building strong teams in complex situations, that I had learned at UUSC in my mind also.

But first: I climbed Mt Moriah (4049ft, 1234m) on July 22, 2017, with Kelly Royds and Raúl Caceres, friends from Australia who, coincidentally, had worked at ChildFund (but not on the IPT.)  We had hiked up Mt Pierce and Mt Eisenhower a year earlier, in August of 2016…

*

Raúl and Kelly came up from Cambridge the day before, and we left Durham at about 7:45am, and stopped for sandwiches and coffee in Ossipee on the way north.  Traffic was heavy on this summer weekend, so it wasn’t until 10:45am that we reached the trailhead in Gorham, in the northern reaches of the White Mountains.

IMG_1489.jpg

Raúl and Kelly at the Beginning of the Climb

 

Mt Moriah is the northern-most of the six 4000-foot peaks in the Wildcat-Carter range.  I had climbed Wildcat “D” and Wildcat Mountain (on one day), and Middle and South Carter (on the next day), in September of 2016, solo; and I had summited Carter Dome on 9 July, 2017, with our friend Draco.  So Moriah was the last of these six that I would climb.

Moriah is an “easy to moderate” hike, and we had a nice day for the climb: not too hot, partly cloudy and a bit misty.   It’s 4.5 miles up, and we retraced our steps from the top.

Screen Shot 2017-07-24 at 10.44.47 AM.png

 

 

 

The trail climbs moderately from the trailhead just outside of Gorham, reaching a ledge outlook at Mt Surprise.  There, views opened to the west towards the Presidential range:

IMG_1495.jpg

 

This ledge area seemed unusual to me – not so high in altitude, but quite alpine in nature: low pines and large areas of lichens, as if we were at a much greater elevation:

IMG_1524

IMG_1523

 

I guess the conditions here were affected by a combination of elevation and latitude: since we were at the northern end of the White Mountains, perhaps the winter weather would be a bit more severe?

It was a bit misty, with views that were not quite as dramatic as last time I was up on this range, but still very impressive.  There is a short boggy area near the top.

IMG_1497.jpg

Nearing the Top – Raúl, With Kelly in the Background

IMG_1498.jpg

 

We reached the spur path to the summit of Mt Moriah at 2pm.  From here it wasn’t too far to the top.

IMG_1508.jpg

 

The summit itself is a small, rocky clearing, and on this day it was quite crowded, so we ate a late lunch at an outlook a short distance from the top, with great views to the north:

IMG_1503.jpg

The (Crowded) Summit Of Mt Moriah

 

An outcropping was visible to the south, without anybody on it.  It looked like there would be great views from there so, after lunch I thought that I would go ahead to try to get to it.  Maybe the view there would be worth the walk.  When we reached the intersection with the Kenduskeag Trail, Kelly and Raúl decided to wait for me there; I kept going, hoping to reach that outcropping.

IMG_1509.jpg

 

Taking first the right-hand turn (along the Carter-Moriah Trail, coincident with the Appalachian Trail here) and then doubling back to explore briefly along the Kenduskeag Trail, I just couldn’t find that outcrop.  After poking around a bit, I headed back to where I had last seen Raúl and Kelly, but they had gone.  So I began the descent back to the trailhead.

Soon I passed a couple who were climbing up, and I asked them if they had seen my friends.  No!  Whoops!  Clearly we had gotten separated at the top, so I asked the couple to tell Raúl and Kelly that I had begun the descent.  A few minutes later I was able to get reception on my cellphone, and rang Raúl: sure enough, they were waiting for me back at the summit!  In retrospect, I should have thought of that – of course they would want to wait where there was a view! – but I had been too tired to climb back up there, and assumed that they were feeling similarly.

From their perspective, as I was descending, Raúl and Kelly became worried that I was lost and perhaps injured.  Finally they decided that it would be best to walk to the trailhead, and then I called Raúl and we realized what had happened.

I descended as we had ascended, a beautiful day for a hike in the White Mountains:

IMG_1519

IMG_1520

IMG_1521

Presidential Range, Now Backlit In The Afternoon

 

Nearing the trailhead, I came across part of an old car that I hadn’t seen on the way up:

IMG_1528.jpg

 

I arrived back at the trailhead at 5pm, and Kelly and Raúl finished at about 6:30pm.  Despite our inadvertent (and temporary!) separation, all turned out OK and it was a pleasant and enjoyable day.  Mt Moriah, peak number 33, was climbed – 15 more to go!

*

When I arrived in Sydney, one of my first tasks was to finalize the structure of the new International Program Team (“IPT”), and complete its staffing.  Having spent lots of time and energy worrying about structure in previous roles (particularly at the International Headquarters of Plan International – see this blog), I was thinking about this in two ways:

  1. Because structure has a strong influence on behavior, I wanted to keep the IPT’s structure lean, flat and close to the field, and efficient, cost-wise;
  2. Because with the right people, structure wasn’t the most important thing, I wanted to not worry about it too much: just get the right people, make as good a structural decision as I could, and then get on with the work and let things evolve through intentional, restorative, reflective learning.

It turns out that these two aims are fairly consistent.  Yes, structure does have a strong influence on behavior, so it’s important not to get it wrong.  And, within reason, flatter structures are better: fewer levels of bureaucracy between field and senior management keeps things a bit more grounded in the reality of our NGO work.  Flatter structures help keep head-office costs down, also.  But I had also learned an important lesson along the way: hire great people, make roles very clear and connected to the organization’s mission and people’s passions, and then let things evolve, reflecting and learning-by-doing.  Don’t obsess too much about structure.

So that’s what I did.

*

When I arrived in Sydney, the IPT was in flux.  Even though ChildFund Australia had been working in Papua New Guinea for fifteen years, and in Viet Nam for a decade, the main role of Sydney-based program staff at that point was to oversee projects funded through the Australia-NGO Cooperation Program (“ANCP”) of AusAID (the Australian Government’s overseas aid agency), implemented by the US member of the ChildFund Alliance, confusingly-named ChildFund International.  This meant that the IPT had little role with regards to ChildFund Australia’s own programming…

In 2009, ChildFund Australia was preparing for growth: our private income was growing strongly, and because the new Labor government was promising to strongly-increase overseas development assistance in line with international commitments, and we had just become top-tier ANCP “Partners” with AusAID, it looked like that income stream was also going to grow quite rapidly.  Part of that preparation for growth resulted in the creation of my new role as International Program Director, which would assume the management of ChildFund Australia’s three (becoming five) Country Directors.

ChildFund Australia’s organizational structure as I arrived in Sydney looked something like this:

IPD Structure - 1.002

 

  • Five Department Directors worked with Nigel: Bandula Gonsalkorale (Finance and IT); Jan Jackson (HR); Lynne Joseph (Sponsor Relations); Di Mason (Fundraising and Marketing); and me;
  • Initially we had three Country Directors, handling program implementation and reporting to me: Carol Mortenson (Cambodia); Smokey Dawson (PNG); and Peter Walton (Viet Nam).  Peter also handled regional responsibilities for the Mekong, supervising ChildFund’s research into setting up operations in Laos.  I will share more about these Country Directors, and their successors and teams, in upcoming articles in this series…

And in the Sydney Program Department, five positions were in the FY2010 budget (in addition to my own):

  • Veronica Bell had just left ChildFund, taking up a position at the Human Rights Council for New South Wales.  So her International Program Manager position was vacant;
  • Richard Geeves had just joined, only a few days before my arrival, as International Program Coordinator for the Mekong programs (Cambodia and Viet Nam).  Richard had long experience in the education sector in Australia (including in indigenous areas), and was recently returned to Australia after many years working from Cambodia;
  • Rouena (“Ouen”) Getigan had joined ChildFund several years earlier, and therefore was our repository of wisdom and knowledge; the rest of us were new, but Ouen knew how things worked!  She handled relations with our ChildFund partners in Africa and Asia that were funded through the ANCP program, and did an outstanding job of building and maintaining these partnerships.  In addition, to support a large regional HIV and AIDS project in Africa, Ouen supervised a very capable Kampala-based project coordinator, Evas Atwine;
  • Terina Stibbard, like Richard, had just joined ChildFund, only a few days before my arrival, as International Program Coordinator for Papua New Guinea.  Overflowing with passion for the work, and with a tireless commitment, Terina took on what was perhaps our biggest challenge: building a strong program in PNG.  I will write much more about PNG in a future blog post in this series.  Also, among other things, Terina introduced us to the concept of “critical friend,” which perfectly captured the IPC role with our Country Offices: without direct authority, but able to advise and speak truth directly without harming relationships;
  • And Nigel had left one position undefined, for me to consider.

Interviews for the Mekong and PNG roles had begun before I was hired, but before finalizing things with Richard and Terina, Nigel and Jan had consulted me, asking if I wanted them to wait until I got to Sydney before finalizing these hires.  But Richard and Terina looked great to me, on paper, and I saw no reason to delay.

In terms of the program-team’s structure, I didn’t see any reason, at this point, for the extra structural level implied by the “International Program Manager” role.  Over time, I saw things might evolve in three general domains:

IPD Structure - 1.001

 

In the Program Support domain, one group of staff in Sydney would accompany Country Directors and, most directly, the Program Managers in our program countries, helping develop projects and programs with the greatest impact on the causes of child poverty in each location.  In the Program Development area, Sydney staff would provide technical and systems support, establishing standards and helping measure results.  Finally, of course, we had a general function of Program Implementation – our Country Directors.

As we will see, in fact, the IPT structure did in fact evolve in this way.

*

So here is the first iteration of the IPT structure, put in place soon after my arrival:

IPD Structure - 1.003

 

Richard, Ouen, and Terina focused mainly on “Program Support” duties, working directly with our Program Managers in Cambodia, PNG, and Viet Nam, and with ChildFund partner offices in Asia and Africa to help them develop and implement, and learn from, increasingly sophisticated programming.  Two new hires, Jackie Robertson and Cory Steinhauer, joined ChildFund to support program development: Jackie was focused on developing the policies and standards that would govern our work; and Cory would focus on building a development-effectiveness framework through which we would design our programs and measure our results.

Here are some images of that first IP team:

Copy of IMG_1483.jpg

Terina, Richard, Cory, Jackie, Me and Ouen

OLYMPUS DIGITAL CAMERA

Richard, Terina, Me

OLYMPUS DIGITAL CAMERA

Ouen

*

This structure worked very well.  In terms of how I managed the team, from the beginning I tried to put in place a range of “restorative” practices, aimed at keeping the team together, keeping us grounded and motivated:

  • Every Monday morning at 10am, we had a team checkin.  I had learned how to do this from Atema Eclai at UUSC, though I had to adapt it quite a bit: Australians weren’t enthusiastic about the “touchy-feely” aspects of checkins like Atema’s.  So we limited things to a brief general chat followed by a discussion of priorities for the week.  This seemed to work very well, settling us into the week smoothly, and was replicated by the team even when I was away;
  • Every month or two, we had a formal IPT Meeting.  These events had agendas, minutes, pending-action-items lists, etc.  They were business meetings, which I would chair, meant to be efficient fora for decision-making and accountability.  They worked very well.  For example, I had learned how to use “pending-action-items” lists from Max van der Schalk while working at Plan’s international headquarters, and the introduction of this tool was very important at ChildFund: decisions that required action went onto the list, organized in order by date, and stayed on the list until they were completed or the IPT agreed to remove them.  This provided a strong element of accountability and was a helpful irritant that kept us from neglecting decisions and becoming less accountable.  Once the ChildFund Australia “Development Effectiveness Framework” (“DEF”) was completed, we introduced a short reflection from a field case study at the beginning of each IPT Meeting, to help ground us in the reality of our work; much more detail about the DEF will come in a future blog in this series;
  • My intention was to complement the formal IPT meetings with periodic reflection meetings about a topic related to our work.  These sessions wouldn’t have agendas or minutes, much less structured and more relaxed than the IPT Meetings, and would be chaired by different members of the IPT who had expressed an interest in a particular topic – micro-finance, human rights, direct giving, etc.  These sessions were always interesting and useful, and energizing, so I regret not organizing more of them.  Somehow they seemed to drop off the agenda with the fast pace of work, over time, and I don’t think that I fully realized the potential of this concept;
  • I tried to have an open door policy, available for IPT members at any time.  I made sure to close my door only when necessary, and to invite any team member to come in and sit down whenever they dropped by.  I think this was helpful in creating and sustaining a culture of caring and support, clearly communicating to everybody that helping the team was my main job.  Of course, there were times when my office door needed to be closed – for the discussion of sensitive matters, particularly on the phone with our Country Directors – but I had learned at UUSC to be quite mindful of asking permission to close my door, to enhance transparency and make sure people were comfortable.  As with the team checkins, it seemed that our mostly-Australian staff viewed this habit of mine – asking permission to close my door – as a bit silly.  But I think it was helpful;
  • Of course, I carried out an annual performance review of each member of the team, and spent lots of time preparing these documents.  I tried to be balanced, but to always include areas for improvement – loyal readers of this blog will remember my experience with Pham Thu Ba, back in Plan Viet Nam: when I finished her first performance review, which was stellar, she told me I wasn’t doing my job if I couldn’t help her improve!  This made a big impression on me, and even though western culture these days seems to only value praise, I wanted to honor Thu Ba’s example in my work in Australia.  This worked well, most of the time!;
  • In addition to the yearly performance review process, I tried to have some less-formal, one-on-one time with each IPT member every year.  I’d invite them for coffee or lunch, and have an open, unstructured chat about how things were going. I wasn’t able to make this happen as often as I wanted, but it was a very useful mechanism, helping surface concerns and opportunities that I might not have appreciated otherwise;
  • Finally, also dating from my time in Viet Nam, I adapted and used a “Team Effectiveness Assessment” for use with the IPT, and was able to use this tool to formally assess how we were progressing.   The framework I used came from a great workbook that I had discovered at Asia Books in the Bangkok Airport, back when I worked in Hanoi in the late 1990’s: “The Team-Building Workshop,” by Vivette Payne.  The approach included in the book outlined eight elements of team effectiveness, and a survey was included that could be used to measure the status of a particular team.  Starting with how I had used the survey in Hanoi, I now adapted the survey and used it four times with the IPT, tracking results and identifying areas that we could focus on to improve (in yellow):

Screen Shot 2018-05-10 at 1.26.17 PM

You can see that our overall score, a measure of team effectiveness, improved from 197.1 in March, 2011 to 230.6 in December of 2011, and then moved back down to 204.1 in January of 2014.  I think that the decrease in score reflects the arrival of several new IPT members, and the corresponding need to settle the team down into new roles and relationships.

Each time we used this tool, we identified areas for focus, which are initiated in yellow: for example, in October of 2012 we looked to focus on “Roles” and “Team Relationships” and “Skills & Learning.”  I found the tool to be practical and very useful, though not to be taken too literally; discussion of results and team reflection on next steps was more important than the numerical scoring… and the fact that I was using this tool periodically gave the team a message that I was taking our effectiveness seriously, and investing my time, and all of our time, on improving the team environment.

*

In one of my blogs about UUSC, I described how I had created the “UUSC Handbook,” to enhance clarity of how things would be done in that agency.  From my perspective, as Executive Director there, the UUSC Handbook was a big success, notwithstanding its large size.  Given the tensions that existed in that agency, having an agreed, approved set of standards and procedures was helpful, and since it mainly simply codified and clarified existing practices, it didn’t create too much bureaucracy.

I replicated this approach at ChildFund Australia, creating the ChildFund “Program Handbook.”  Like its UUSC predecessor, the Program Handbook was quite complex and bulky to produce and update, which happened periodically … they were both meant to be living documents.   And it contained much content that was already existing, just needing to be codified.

But, unlike the UUSC Handbook, ChildFund’s document contained much that was new: our Theory of Change and our Development Effectiveness Framework, and a range of program policies – these were new, developed by the new IPT, and represented the ongoing maturing of ChildFund’s programming.

A copy of a version of the ChildFund Australia Program Handbook is here (Program Handbook – 3.3 DRAFT ); even though this is marked as “Draft,” I think it was the final update that we issued before I left Sydney in 2015.

*

Two years later, in 2011, ChildFund Australia was growing strongly, and we had commenced operations in Laos.  The IPT structure in Sydney evolved consistently with this growth:

IPD Structure - 1.004

 

Carol Mortensen continued as CD in Cambodia, but changes had been made in PNG and Viet Nam, and we had started operations in Lao PDR:

  • Andrew Ikupu, a very-experienced Papua New Guinean, had replaced Smokey Dawson as CD in PNG.  Andrew had long experience working in development in his country, and had a PhD from the University of South Australia in Adelaide;
  • Deb Leaver had taken over from Peter Walton in Viet Nam.  I had first met Deb in late 2009, when I visited ActionAid Australia, where Deb was Program Director, and she had been probably the most welcoming of my peers in Sydney.  We were lucky to hire Deb to follow Peter;
  • Chris Mastaglio, with his able colleague Keoamphone Souvannaphoum, had helped ChildFund with the initial research into why, how, and where we should work in Laos.  Once we made the decision to start working there, we were fortunate that both Chris and Keo were available to join ChildFund: Chris as CD, and Keo as Program Manager (and, later, as CD when Chris transitioned to head up a regional sport-for-development program).

We were very lucky to have Andrew, Chris, Deb and Keo join ChildFund Australia.

In Sydney, things had also evolved.  Cory Steinhauer had departed, and Richard Geeves had moved over from Program Support (where he had served as IPC for the Mekong) to work on Development Effectiveness.  He was quite good at this role: while I was the primary architect of ChildFund’s Development Effectiveness Framework, which I will describe in detail in a future blog post in this series, Richard was an able foil, working to keep things simple and practical, and he had a good touch with the field, keeping the implementation of what was a new, challenging system on track, with good humor.

John Fenech joined the Program Development team, helping our Country Offices prepare grant proposals.  Relative to our size, ChildFund Australia had a lower proportion of income from technical grants (bilateral, multi-lateral, foundation) than our peer organizations, and John’s role was to build our portfolio.  Although John was one of the younger members of the IPT, he brought a vivid countercultural sense, sometimes seeming to date more from the 1970’s than from the 2010’s.  In a good way…

Terina remained engaged with PNG, and she was doing a fantastic job working with Andrew Ikupu and his Program Manager Manish Joshi (later becoming CD there).  As a result, our programs in PNG were really taking off – growing in size, impact, and sophistication, and diversifying in income source.  And Ouen continued to work with our ChildFund International partners across Africa and Asia as they implemented an increasing number of ANCP-funded projects.

As our programs were expanding, two new IPCs had joined, working with our programs in the Mekong: Caroline Pinney took over support from Cambodia and Laos, and Maria Attard worked with our team in Viet Nam, while also coordinating research and initial engagement in Myanmar.  Caroline brought long experience in Asia, with AVI (the Australian volunteer-sending agency), and a very strong level of dedication and passion for our work.  Maria’s work had been in Cambodia (working with women and children that had suffered from domestic violence) and the Pacific (in the disability sector), before returning to Australia (continuing in the disability sector).  Maria brought a welcome sense of activism to the team, building on her advocacy work in the disability sector.  Both Caroline and Maria showed remarkable dedication to the heavy workload and complicated realities of the programs that they supported.

Finally, in this second iteration of the IPT structure, we decided that the scale of operations was large enough to merit a program officer to provide a range of support services to the team.  Initially we wanted to hire an indigenous Australian, accessing subsidy programs offered by the government.  This was Terina’s idea, and was a very good one, but we were never able to make it work due to complicated and dysfunctional bureaucracy on the government side.

So we shifted concepts, and decided instead to look towards recent graduates in international development.  Given how many people were finishing degrees in the field, and how few jobs there were, we thought it would be good to make the position time-limited – giving new graduates some real work experience, and some income, while taking some administrative load off of the rest of the IPT.  And then booting them out into the real world.

We recruited externally, and were able to hire a very smart, extremely hard-working new graduate, Mai Nguyen.  From then on, Mai handled a range of administrative and program-support duties with great efficiency and good humor.

Here are images of that iteration of the IPT:

Cropped Team Photo

IPT in February, 2012.  From Left To Right: John Fenech, Ouen Getigan, Me, Maria Attard, Terina Stibbard, Mai Nguyen, Caroline Pinney, and Richard Geeves.  Missing: Jackie Robertson

IPT in March 2012.jpg

IPT in March, 2012.  From Left To Right: Ouen Getigan, Maria Attard, Terina Stibbard (seated), Caroline Pinney, Jackie Robertson, Me (seated), John Fenech, Mai Nguyen, and Richard Geeves

 

*

In 2014 we introduced IPT’s third structural evolution, the last version of my time as International Program Director.  At this point, our scale had grown further, with the addition of Myanmar and, with 11 direct reports, I was having trouble providing proper individual attention to everybody.  So we introduced a new level, partly to break my “span of control”: so Ouen and Richard became “Managers”:

 

IPD Structure - 1.001

 

Ouen would be handling Program Development and the support of our Development Effectiveness Framework, and Richard moved to manage Program Support while also serving as IPC for PNG (after Terina Stibbard departed.)  This allowed me to give priority attention to the five Country Directors now reporting to me, and to Ouen and Richard.

Here is an image of that final iteration of the Sydney-based team:

IMG_3483

IPT in November, 2014: John Fenech, Sanwar Ali, Caroline Pinney, Richard Geeves, Maria Attard, Me, Manasi Kogekar, Mai Nguyen, Sarah Hunt, and Ouen Getigan.  Missing: Jackie Robertson.

 

We had upped our technical support capacity, by recruiting Sanwar Ali from Oxfam Australia; he would head support for our increasing Disaster Risk Reduction and Emergency Response efforts.  John Fenech had moved to serve as IPC for Cambodia, allowing Caroline Pinney to focus on Cambodia, and Mai Nguyen had moved to serve as IPC for Myanmar, allowing Maria Attard to focus on Viet Nam.  To replace John in the grant-development role, we (re)hired Sarah Hunt, who was quickly very successful in bringing in additional resources to the program; Sarah had served on the IPT before my arrival, and we were lucky to bring her back, thanks to Ouen’s strong recommendation.  Sarah made grant development look easy, which it certainly isn’t!

This team worked very well, and seemed harmonious and effective.  Ouen and Richard were good, supportive managers of their teams, and I was able to spend much more time with our Country Directors.

*

In my last article in this series, I shared a framework that I developed over time, for thinking about effective teams in NGO settings:

Clarity Trust Inspiration - 1.001

 

In that article, I said that “… our INGO teams will perform strongly if:

  • their task is clear, accountability is clear, what we are supposed to do, and why, is clear, and if how to carry out our tasks is clear;
  • we operate in a context of high trust;
  • the inspiration that we bring to our work is refreshed periodically.  And:
  • the normal wear-and-tear on our human relationships, the harm done over time, is restored intentionally.”

How did we do in ChildFund Australia’s IPT?

  • Clarity: We did fairly well here.  I was careful to engage with the IPT to make sure that their roles and jobs were clear, and the work we did to develop a programmatic Theory of Change and Development Effectiveness Framework also greatly enhanced clarity.  The preparation and frequent updating of the Program Handbook also provided clarity, though perhaps was viewed as a bit bureaucratic by some.  But, overall, I’d say things were clear;
  • Trust: this is a bit harder to judge, for me, because it was my job to create and maintain an environment of trust.  Trust comes from a combination of competence and honesty, and I feel that IPT members viewed me as quite competent and honest.  For example, I decided to share minutes of all Senior Management Team meetings with IPT members at our IPT Meetings – orally, in summary, and omitting any confidential content.  I think that sharing this information helped reinforce a sense of transparency.  But of course many factors were beyond my control, and I was imperfect in my communications skills;
  • Inspiration: I think we did fairly well here, I tried to bring a sense of the realities in the field into all our meetings, and into board and Senior-Management meetings, using (for example) case studies from our Development Effectiveness Framework to reconnect us with the deeper motivations that brought us into the NGO sector.  Again, I was imperfect in this, but I think we did pretty well;
  • Restorative Practices: earlier in this article I described my efforts to build restorative practices into the ongoing context of the IPT, and I think these worked very well.

Overall, perhaps a solid B+.

*

That’s some of the story of ChildFund Australia’s International Program Team, from 2009 through 2015.  ChildFund’s work expanded enormously during that time, and the IPT  managed to support that expansion smoothly, with increasing attention to the quality and sophistication of our programming.

It did come at a financial cost: program support increased from around 4% of funds remitted to international programming in 2010, to 6.7% in 2015.  My sense is that the gains in effectiveness and impact were well worth this investment – I will explore this in more depth in an upcoming post in this series.

I enjoyed working with the IPT, and learned a lot from them.  Morale was good, consistently, and though I can’t take sole credit for that success, I think that the approach we took helped.

With gratitude and warm appreciation to:

  • Sanwar Ali
  • Maria Attard
  • John Fenech
  • Richard Geeves
  • Rouena Getigan
  • Sarah Hunt
  • Manasi Kogekar
  • Mai Nguyen
  • Caroline Pinney
  • Jackie Robertson
  • Cory Steinhauer
  • Terina Stibbard

*

Stay tuned for more blog posts about ChildFund Australia: our Theory of Change and Development Effectiveness Framework, our work and great teams in Cambodia, Laos, Myanmar, Papua New Guinea, and Viet Nam, and much  more…

*

Here are links to blogs in this series.  Eventually there will be 48 articles, each one about climbing one of New Hampshire’s 4000-footers, and also reflecting on a career in international development:

  1. Mt Tom (1) – A New Journey;
  2. Mt Field (2) – Potable Water in Ecuador;
  3. Mt Moosilauke (3) – A Water System for San Rafael (part 1);
  4. Mt Flume (4) – A Windmill for San Rafael (part 2);
  5. Mt Liberty (5) – Onward to Colombia, Plan International in Tuluá;
  6. Mt Osceola (6) – Three Years in Tuluá;
  7. East Osceola (7) – Potable Water for Cienegueta;
  8. Mt Passaconaway (8) – The South America Regional Office;
  9. Mt Whiteface (9) – Empowerment!;
  10. North Tripyramid (10) – Total Quality Management for Plan International;
  11. Middle Tripyramid (11) – To International Headquarters!;
  12. North Kinsman (12) – Fighting Fragmentation and Building Unity: New Program Goals and Principles for Plan International;
  13. South Kinsman (13) – A Growth Plan for Plan International;
  14. Mt Carrigain (14) – Restructuring Plan International;
  15. Mt Eisenhower (15) – A Guest Blog: Max van der Schalk Reflects on 5 Years at Plan’s International Headquarters;
  16. Mt Pierce (16) – Four Years At Plan’s International Headquarters;
  17. Mt Hancock (17) – Hanoi, 1998;
  18. South Hancock (18) – Plan’s Team in Viet Nam (1998-2002);
  19. Wildcat “D” Peak (19) – Plan’s Work in Viet Nam;
  20. Wildcat Mountain (20) – The Large Grants Implementation Unit in Viet Nam;
  21. Middle Carter (21) – Things Had Changed;
  22. South Carter (22) – CCF’s Organizational Capacity Assessment and Child Poverty Study;
  23. Mt Tecumseh (23) – Researching CCF’s New Program Approach;
  24. Mt Jackson (24) – The Bright Futures Program Approach;
  25. Mt Isolation (25) – Pilot Testing Bright Futures;
  26. Mt Lincoln (26) – Change, Strategy and Culture: Bright Futures 101;
  27. Mt Lafayette (27) – Collective Action for Human Rights;
  28. Mt Willey (28) – Navigating Principle and Pragmatism, Working With UUSC’s Bargaining Unit;
  29. Cannon Mountain (29) – UUSC Just Democracy;
  30. Carter Dome (30) – A (Failed) Merger In the INGO Sector (1997);
  31. Galehead Mountain (31) – What We Think About When We Think About A Great INGO Program;
  32. Mt Garfield (32) – Building Strong INGO Teams: Clarity, Trust, Inspiration.

Mt Garfield (32) – Building Strong INGO Teams: Clarity, Trust, Inspiration

April, 2018

I began a new journey nearly two years ago (May, 2016), tracing two long arcs in my life:

  • Climbing all 48 mountains in New Hampshire that are at least 4000 feet tall (1219m), what is called “peak-bagging” by local climbers.  I’m describing, in words and images, the ascent of each of these peaks – mostly done solo, but sometimes with a friend or two;
  • Working in international development during the MDG era: what was it like in the sector as it boomed, and evolved, from the response to the Ethiopian crisis in the mid-1980’s through to the conclusion of the Millennium Development Goals in 2015.

*

Picking up the story as I arrived in Sydney in July, 2009, to take up the newly-created position of “International Program Director” for ChildFund Australia, I was thinking a lot about how to build great programs for children and youth.  I wrote about that last time.

And I was also thinking about the other big part of my new job: building strong teams.  Next time I will introduce some of the people I worked with in those teams – in Sydney, Port Moresby, Hanoi, Phnom Penh, Vientiane, and Yangon.

This time I want to share thoughts about how to build teams, in particular in the context of international non-governmental organizations.  Through my career in the INGO sector, I was fortunate to work in, and lead, teams across the world, and learning a lot about how to build strong, high-performing teams.  Learning-by-doing, from watching others, and from my own mistakes.

I was determined to bring this learning to ChildFund Australia.  But before diving into that topic…

*

I climbed both Galehead Mountain and Mount Garfield on 19 July, 2017.  My plan that day was to walk up Gale River Trail to join the Garfield Ridge Trail, and then take the Frost Trail to reach the top of Galehead Mountain, which would be number 31 of the 48 4000-footers.  Then I would loop around Garfield Ridge to go up Mt Garfield, and return to meet up with Jean at the bottom of Garfield Trail.

Jean had driven up from Durham with me, and left me at the trailhead of the Gale River Trail.  She would spend the day with an old friend from high school, planning to pick me up at the end of the day.

I reached the top of Galehead Mountain at a little after noon.  When I had arrived at the Garfield Ridge Trail, going up, it seemed that I was making great time.  But by the time I dropped down from Galehead, and left Galehead Hut to head towards Mt Garfield, I was much less optimistic: to reach the trailhead by 5-6pm, as arranged with Jean, I thought I needed to leave Mt Garfield by 3pm, at the very latest.  I had less than three hours to get to the next peak.

So I headed down from Galehead and tried to keep up a good pace.

Screen Shot 2017-07-20 at 12.10.22 PM.png

 

I got back to the junction with Twinway and Garfield Ridge at about 1pm, and continued towards Garfield.  The walking was, at first, quite pleasant as I retraced my steps down to where I had come up Gale River:

IMG_1420.jpg

 

From there, it was pleasant walking along Garfield Ridge.  Continuing along the ridge in a westerly direction, I reached the junction with the Franconia Brook Trail (at the saddle of Garfield Ridge Trail, between Galehead and Garfield) at about 2:15pm.

IMG_1427

View Looking Down Franconia Brook

IMG_1426

Looking Back, Galehead Hut Is Just Visible In The Saddle, With South Twin Above It To The Left, And Galehead Mountain Above It To The Right

 

I was getting nervous: I had calculated that I needed to start descending from the summit of Mt Garfield by 3pm, in order to reach the trailhead, where Jean would be waiting, by 5-6pm.  But from the saddle, well below the summit, at 2:15pm, Mt Garfield towered over me, and the next section of the hike looked to be very steep.  VERY steep.

In all of these climbs, all 32 of them thus far, I don’t think I have ever been as tired as I was now.  The climb up from the saddle between Galehead Mountain and Mt Garfield felt unrelenting, up up up.  It was very hot, very humid, and I was down to one liter of water, of the 2.5 liters I had started with.  Luckily, I passed by Garfield Ridge campsite, and there is a wonderful spring there, so I drank a full liter of cool, clean mountain water – a great relief!  Fantastic!

But, even so, the climb was unrelenting.  It was very challenging, a really tough climb up 0.7 miles from the saddle to the top.

I reached the junction with the Garfield Trail at just after 3pm, and decided to drop my backpack there, and finish the climb to the summit with just a bottle of water and my walking stick:

IMG_1435.jpg

 

At least I had water.

Luckily, though the last section was very steep, I got there at about 3:15pm.  Though I was exhausted, the views from the top of Mt Garfield were stunning, with just enough clouds to produce a nice contrast as I looked around.  I could see Owl’s Head in front of me, and the peaks of Flume, Liberty, Lincoln and Lafayette to the west.

IMG_1436

Summit of Mt Garfield – Foundation of the Former Fire Lookout Tower

IMG_1438

From The Summit Of Mt Garfield: Galehead Mountain Is In The Foreground, South Twin In The Background

IMG_1441

Franconia Ridge, On The Right, and Owl’s Head Below, To The Left

IMG_1444

Looking Back Towards Galehead, and The Twins

 

Sadly, my camera seriously fogged up at the top of Mt Garfield, so the photos I took towards Franconia Ridge were spoiled.  This video panorama of the view is also fogged up, but perhaps the beauty of the day can be inferred here?

 

I couldn’t stay too long at the top, though it was beautiful, because I was worried about reaching the parking lot too late.  So I headed back down to the junction with Garfield Trail, picked up my backpack, and started down from there at 3:30pm, a half hour later than I had hoped.  Here I’m looking back up at the junction as I began the descent down Garfield Trail:

IMG_1470.jpg

 

Luckily, because I was so exhausted, the 4.8 miles down Garfield Trail were not challenging, just long long long.  By about 4pm, I hadn’t seen anybody at all, which was quite a change from the steady stream of hikers, and through-hikers, up on the ridge.  But, at a very awkward moment, a young hiker passed by me, walking quickly, just saying hello.  If she had been just a few moments earlier, it would have been quite embarrassing (probably for us both!)

 

The walking was fairly easy, gently downward, on a beautiful White-Mountains day:

IMG_1473.jpg

 

My feet were sore and I was very ready to finish the hike by the time I arrived at the end of Garfield Trail, at 5:30pm – nicely within the range I had predicted.  It had been two hours, and Jean was waiting there!  Happily, she had only been waiting a few minutes!

IMG_1474

IMG_1476

5:33pm At The Trailhead!  I Look Fresher Than I Felt!

 

What a great day – two 4000-footers on a beautiful day.  But far more challenging that I had expected!

*

As I flew towards Sydney in mid-July, 2009 (Jean would join me there two months later), I was thinking a lot about two aspects of my new role.  On the one hand, my role was “International Program Director,” which meant that I was expected to lead the thinking and strategy related to ChildFund Australia’s development and humanitarian work.  In my last blog entry I outlined some of what I was thinking about when I was thinking about great INGO programming…

At the same time, I would lead several teams and be a member of others.  In Sydney, I would lead the “International Program Team” (“IPT” – I will write more about this team next time), and I would be a member of the two “Senior Management” teams that Nigel Spence, ChildFund Australia’s CEO, had recently established: first, there was the Sydney-based “Business Support Leadership Team” (“BSLT,” chaired by Nigel), which was comprised of Nigel and the five Department Directors based in Sydney.  The BSLT was focused on leading the functions that made our programs possible: fundraising, finance, IT, human resources, sponsor relations, governance support, etc.  The role of the BSLT was described in the team’s charter:

The Business Support Leadership Team is responsible and accountable for developing and implementing systems, policies, procedures, guidelines and controls that enable the organisation to meet strategic and business objectives. The Business Support Team is also responsible and accountable for securing resources and determining resource allocation. 

And then there was my relationship with ChildFund Australia’s overseas teams in Hanoi, Port Moresby, and Phnom Penh.  As Nigel and I had discussed my new role, we looked at two possibilities:

  • Nigel could continue to directly manage ChildFund’s three Country Directors (located in Cambodia, Papua New Guinea and Viet Nam), as he had been doing.  This option would put me in a “staff” role in relation to overseas operations, “line” managing only IPT members in Sydney.  This would be similar in some ways to my role at Plan’s headquarters;
  • I could take over Nigel’s “line” management of the overseas CDs in addition to managing IPT members in Sydney.

Loyal readers of this blog will recall an earlier discussion of the tradeoffs involved here: as I moved from being Plan’s Regional Director for South America to the post of Program Director for the global organization, Max van der Schalk (Plan’s CEO at the time) and I had looked at two similar options.

In that case, we decided that I would not manage Plan’s Regional Directors, leaving him as their “line” manager; this left me in a “staff” role.  This would keep the organization’s structure a little bit flatter, but would burden Max with a broader span of control.  But that’s the way we went, and we made my new title reflect the difference: instead of following Marjorie Smit as “Program Director,” we decided my title would be “Director of Planning and Program Support.”  A rose by any other name…

So I was free to focus on strategy and structure, without being distracted by the daily dramas involved in line management – spending pressures, audit responses, personnel issues, etc.  It felt right at the time, and I certainly had more than enough power to get my job done; but later I did feel that the additional clout that line management would have given my role might have been helpful in making the transformational changes (in Plan’s goals, structure, and resource allocation) we achieved.  But I was happy with the choice we made, and we did make those changes.

I described the tradeoffs as I saw them to Nigel, and left the decision to him; I felt that I could go either way.  But I was delighted when he decided that I would become the line manager of ChildFund Australia’s three Country Directors … though, I quickly discovered that the CDs felt quite differently about what they felt was a loss of status.

So I would also lead and manage those three people, which became five as we expanded into Laos and Myanmar in the next few years.  The second “Senior Management” team that Nigel had recently formed was the “Program Operations Team,” (“POT”), which was comprised of him, me, and the three Country Directors; I would chair that team.  The role of the POT was described in its charter:

The Program Operations Team is responsible and accountable for operations: individually in their countries and head office; and collectively for the wider organization.  The Program Operations Team is focused on program strategy, managing the daily operations of the organization and furthering the achievement of ChildFund Australia’s programmatic goals.

This meant that I was going to be in three teams in my new role, leading two and joining the third as a member.  (I’d also co-chair the ChildFund Alliance Program Committee, but that’s a different story…)

*

Over the previous 25 years, I had learned a lot about working in, and leading, teams.  I had learned that people working in INGOs, generally speaking, are intrinsically motivated.  We join our agencies because we felt driven to help improve the world, with a passion for making a difference – not everybody was like that in my experience, but most were.  I saw this across all the organizations I had worked in, and all the locations where I had worked – we could almost take motivation for granted.  This was a luxury, something that many private-sector organizations work very hard to produce.

And that intrinsic motivation is a gift that could be spoiled if not handled correctly.  For example, my sense was that if a team leader managed as if motivation were a problem, and put in place mechanisms of control based (in part) on distrust, that kind of management culture would clash with the nature of our people, and would demotivate staff.  This accounted for some of the trouble that Alberto Neri got himself into in Plan

As I have discussed in an earlier blog post in this series, I had also learned that leading teams of INGO people did not mean that everything was going to be positive and nice.  Our organizations have plenty of internal complexities and might even have more-pervasive politics and ego than some for-profit environments.  There were dishonest people in our agencies.

In that earlier article I noted that:

… there is no inherent, inevitable contradiction between being clear and firm about roles, being fair but strict about adherence to procedures and performance, and the ideals of a nonprofit organization dedicated to social justice.  

And, for me, the way to successfully navigate the terrain between principle and pragmatism is to learn how to manage conflict while developing a deep sense of humility and self-awareness, mindfulness and equanimity, and engaged non-attachment.

*

Looking back, it seems to me that it boils down to four key domains that I would try to focus on during those years in Australia:

  • Teams, and team members, needed to be completely clear (1) about their task, their role, and the way that they were meant to carry out their duties;
  • They needed to work in an environment of trust (2), where they felt motivated, and
  • Inspired (3) to achieve their best in an important endeavor.  And, finally,
  • The whole effort needed to be founded on maintaining and restoring (4) relationships.  The most fundamental aspect of INGO management, in this model, is building and preserving authentic relationships in a context of clear accountability.

The rest of this blog post will describe how I tried to draw from what I had learned to make things clear, build trust, inspire, and restore relationships in the teams I worked with at ChildFund Australia.  It worked much (but certainly not all) of the time…

*

One aspect of team leadership that seemed to be essential when dealing with INGO people was establishing a clear aim, clear strategy, clear logic, and a clear way of measuring progress.

So the first element I thought about was clarity.  Clarity, in practical terms, meant building a shared understanding of what our teams were going to do, why we were going to do that, how we were going to do it, and how we would track what we accomplished to be accountable for our use of time and resources, and to learn from it.

Clarity Trust Inspiration - 1.002.jpeg

Building Strong INGO Teams: An Emerging Venn Diagram (1)

 

Building clarity was probably my biggest focus during my first year or two in Sydney.   I was lucky that I was able to build on the solid, existing statements of vision and mission for the overall organization:

ChildFund Australia’s vision is of a global community, free from poverty, where children are protected and have the opportunity to reach their full potential.

ChildFund Australia works in partnership with children and their communities to create lasting and meaningful change by supporting long-term community development and promoting children’s rights. 

 

These statements were great foundations, but they weren’t detailed enough to provide the clear, measurable foundation for our program work that I was looking for, the clarity that would be needed to foster high-performing program teams.

So we moved quickly, in the first few months of my tenure at ChildFund Australia, to develop a Theory of Change, outcome indicators, and a measurement framework.  In future blog posts in this series I will describe each of these elements of our program design in much more detail, because I think that they were state-of-the-art at the time; I mention them in passing here, because they created a clear and shared understanding of our program work.  The resulting “Theory of Change” (that I will unpack in a later blog entry in this series) was:

Theory of Change.001.jpeg

 

This Theory of Change draws in particular from two sources: the CCF Child Poverty Study, and from my own learning from the development of the UUSC Strategic Plan.

The overall program framework (which, again, I will describe in detail later) looked like this:

Slide1.jpg

ChildFund Australia Development Effectiveness Framework (DEF)

 

 

Once programmatic clarity began to emerge, in those first months, I started to assemble another key element of clarity and accountability: the ChildFund Australia “Program Handbook.”  Here I built on the “UUSC Handbook” that I had created several years earlier.  The Program Handbook ended up being a very long, complex document, but to me it seemed vital – an unambiguous reference that I could point to whenever I felt that things were starting to diverge in an unnecessary way.

These, and other, elements of clarity were put in place fairly quickly, and we spent a lot of time over the next five years using that framework as a basis for planning, learning, and accountability.

*

Along with clarity, I was thinking a lot about trust.  Knowing the character of our INGO people, and the culture of our organizations, it seemed to me that once we had a strong sense of clarity, the next essential ingredient in making a high-performance team was trust.  If people were motivated (which, as I said above, was something we could count on, at least until we harmed it!), clear about their purpose, learning from their work, and accountable for their behavior, then I had learned that they would get on with the job and fly.

But trust was essential, because without trust then the old management tools of management-by-objective, tight job descriptions, payment for performance, etc., would be necessary, and culture would surely shift in the wrong direction.  Motivation would drop because those old management tools were developed, and are suitable only (in my view) in contexts where people fit in to simpler, more-linear processes such as manufacturing or bookkeeping.

Clarity Trust Inspiration - 1.003.jpeg

Building Strong INGO Teams: An Emerging Venn Diagram (2)

 

That’s a major lesson I had learned from watching Alberto Neri’s work in Plan long before: what he wanted to do was right and good, but the way that he put his initiatives in place destroyed motivation and led him to failure as Plan’s CEO.

How to build trust in a team?  It’s a truism that trust takes years to develop, but only an instant to destroy.  I had learned how to build trust, and how I had damaged trust, along the way:

  • Trust has two elements:
    • You know that the person you trust knows what they are talking about.  They are competent;
    • You know that the person you trust is honest with you, has your best interests at heart, and works to maintain an authentic, human relationship with you.

If either of those two elements are not in place, then trust will be very elusive.  If both are in place, over time, trust can build.

As I thought about my new position at ChildFund Australia, it seemed to me that my own competence was probably unquestioned.  I had worked in the field for over 20 years, in similar, larger, organizations, across the world, and I had done a very similar job (in Plan) before.  I had served as Executive Director of an INGO.  I was very familiar with working in globally-federated organizations (as ChildFund Australia was), and had even been very involved in creating the program approach used by a key member of the ChildFund Alliance.  So even though I would be new to ChildFund Australia, I felt confident that my own competence would be recognized.

So, to build trust, I had to build on that sense of competence by being honest and straight with people on my teams, in a way that demonstrated that I had their best interests at heart, while trying to build and maintain an authentic relationship with them.  This didn’t mean that I would always agree with them, or that I would never discipline people, but that I would strive to be clear and honest and authentic in my management actions.

*

I had a feeling, as I flew towards Sydney, that if I could build clarity and trust, anything would be possible.  But there was one element missing: inspiration.  Given the motivation that is intrinsic in our INGO people, even if they were clear about the test and worked in a culture with high levels of trust, as time went by I felt that they would still need to be inspired to do their very best.

Clarity Trust Inspiration - 1.004.jpeg

Building Strong INGO Teams: An Emerging Venn Diagram (3)

 

Inspiration would be necessary because much of our work in INGOs isn’t particularly exciting.  Yes, it’s an honor to visit the field and work alongside people fighting for justice, for better futures.  Real inspiration comes from those visits.  But we also have to compete for funding, deal with reports and other paperwork, participate in performance reviews, deal with difficult people, (often) cut budgets, change plans, etc.  And we spend most of our time on those mundane tasks, which can create a sense of alienation from the source of our motivation.

That means that we need refreshing of our motivation periodically.  When I worked with ChildFund Australia I tried to make that happen in various ways.  In the Sydney office I organized occasional, open reflection meetings at which we would consider a range of topics that related to our program work, in a freewheeling way.  For example, one time we discussed the notion of direct cash transfers, something that challenged our program approach.

Another way of keeping us connected with the source of our motivation involved using the “case studies” that were produced frequently as part of our Development Effectiveness Framework – see element 3 in the diagram included above.  At our regular, formal IPT meetings, and even (when possible) at board committee meetings, I started our work with a quick reflection on one of those “case studies” to ground our work in the real, lived experience of  people who faced poverty and injustice.  I will describe the DEF, and the “case studies” in much more detail in a future blog, but for now I think that these, and other elements of my approach helped to keep up our teams’ levels of motivation and inspiration.

*

Finally, even with clarity, trust, and inspiration, over time, harm is done.  That’s because the normal, natural interaction in any team produces friction, and that friction takes a toll on the human beings within the team.  Luckily there is a range of principles and practices that are designed to restore harm.

Clarity Trust Inspiration - 1.001.jpeg

Building Strong INGO Teams: An Emerging Venn Diagram (4)

 

Late in my time at ChildFund Australia, as I worked through my Masters in Dispute Resolution at the University of New South Wales, I would study restorative justice in detail, which would help gel this topic for me.  But at this point my intention was to model some of the practices that I had seen Atema Eclai use at UUSC: frequent checkins with the team, and with each member; considering not just how people on the team were doing in their work lives, but as human beings; working in circles instead of around square tables; rotating the chairing of meetings around the teams.  Atema had clearly achieved very high levels of morale and loyalty, motivation and trust, which in part seemed to come from having spent lots of time building real, caring relationships with her team.

(At UUSC this seemed to veer into a sense of disunity, of aloofness and separation of Atema’s team from the rest of the organization, which was not a positive result.  But, overall, her team was very high-performing and, in part, this was due to Atema’s management approach.)

So I tried to put some of those mechanisms in place, and they worked pretty well.  Some of them ended up clashing with the very straightforward culture that is common in Australia, and which I came to appreciated.  But I tried to adapt things.

*

That’s what I was thinking about as I began to plan for my new post.  It makes sense to me, and reflects lots of learning over the years: our INGO teams will perform strongly if:

  • their task is clear, accountability is clear, what we are supposed to do, and why, is clear, and if how to carry out our tasks is clear;
  • we operate in a context of high trust;
  • the inspiration that we bring to our work is refreshed periodically.  And:
  • the normal wear-and-tear on our human relationships, the harm done over time, is restored intentionally.

Yes, we needed formality and controls.  And firm management.  I had learned that too much control, too many private-sector management tools, would harm team performance in INGOs.  But if I could create a management culture of clarity, trust, inspiration, and authentic human relationships, we might achieve a lot.

I’m sure there’s more to it, but that’s what I was thinking about as I flew towards Sydney!

*

Here are some random images of teams I’ve worked with:

This slideshow requires JavaScript.

 

Next time I will introduce the teams I worked with during my six years in Australia:

  • The Sydney-based International Program Team;
  • The Country Directors I worked with, in Papua New Guinea, Viet Nam, Cambodia, Laos, and Myanmar;
  • The senior managers in Sydney, at ChildFund Australia’s head office.

Imperfectly, doing the best I could, I tried to live up to an ambition to make sure that these teams were clear, trusted, and inspired.  Stay tuned!

*

Here are links to other blogs in this series.  Eventually there will be 48 articles, each one about climbing one of New Hampshire’s 4000-footers, and also reflecting on a career in international development:

  1. Mt Tom (1) – A New Journey;
  2. Mt Field (2) – Potable Water in Ecuador;
  3. Mt Moosilauke (3) – A Water System for San Rafael (part 1);
  4. Mt Flume (4) – A Windmill for San Rafael (part 2);
  5. Mt Liberty (5) – Onward to Colombia, Plan International in Tuluá;
  6. Mt Osceola (6) – Three Years in Tuluá;
  7. East Osceola (7) – Potable Water for Cienegueta;
  8. Mt Passaconaway (8) – The South America Regional Office;
  9. Mt Whiteface (9) – Empowerment!;
  10. North Tripyramid (10) – Total Quality Management for Plan International;
  11. Middle Tripyramid (11) – To International Headquarters!;
  12. North Kinsman (12) – Fighting Fragmentation and Building Unity: New Program Goals and Principles for Plan International;
  13. South Kinsman (13) – A Growth Plan for Plan International;
  14. Mt Carrigain (14) – Restructuring Plan International;
  15. Mt Eisenhower (15) – A Guest Blog: Max van der Schalk Reflects on 5 Years at Plan’s International Headquarters;
  16. Mt Pierce (16) – Four Years At Plan’s International Headquarters;
  17. Mt Hancock (17) – Hanoi, 1998;
  18. South Hancock (18) – Plan’s Team in Viet Nam (1998-2002);
  19. Wildcat “D” Peak (19) – Plan’s Work in Viet Nam;
  20. Wildcat Mountain (20) – The Large Grants Implementation Unit in Viet Nam;
  21. Middle Carter (21) – Things Had Changed;
  22. South Carter (22) – CCF’s Organizational Capacity Assessment and Child Poverty Study;
  23. Mt Tecumseh (23) – Researching CCF’s New Program Approach;
  24. Mt Jackson (24) – The Bright Futures Program Approach;
  25. Mt Isolation (25) – Pilot Testing Bright Futures;
  26. Mt Lincoln (26) – Change, Strategy and Culture: Bright Futures 101;
  27. Mt Lafayette (27) – Collective Action for Human Rights;
  28. Mt Willey (28) – Navigating Principle and Pragmatism, Working With UUSC’s Bargaining Unit;
  29. Cannon Mountain (29) – UUSC Just Democracy;
  30. Carter Dome (30) – A (Failed) Merger In the INGO Sector (1997);
  31. Galehead Mountain (31) – What We Think About When We Think About A Great INGO Program;
  32. Mt Garfield (32) – Building Strong INGO Teams: Clarity, Trust, Inspiration.