Friday, August 25, 2017

On Professional Maturation


by Nick Charney RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharney

Apologies in advance for another long meander through my psyche. I've been struggling with these ideas for some time now and have yet to come to ground with precisely how to frame them. What follows is more personal philosophy and storytelling than lessons public service.

First, life's good.

I love my job. I've never felt more supported, appreciated, important, challenged, trusted, respected, and fulfilled in my public service career than I do now. It's equal parts roles and responsibilities, colleagues, and the ability to play to my strengths while leaving ample room to grow. I'm not sure I've ever been able to say that as earnestly as I can right now, and that's pretty awesome. I'm working with two cracker jack teams on two hot files and my days are full to the brim and just as rewarding.

The flip side of loving one's job of course is that one loses the sense of outrage at all of the parts of the bureaucracy that one would normally find offensive. As someone who primarily identifies with archetypal characters who buck the system (i.e. tricksters) this feels a lot like 'losing your edge' or -- as I've put it previously -- gentrifying (See: The Gentrification of #w2p). For a long time the idea of gentrifying to me felt like betrayal. As a self-stylized perpetual underdog, it's been a slow and difficult progression away from that mindset, but despite popular belief, maturing is never easy.

Relatedly, one of the most interesting pieces of advice I've ever received was from an executive who said "the one gift I really wish I could give you but can't is the gift of experience". The irony of course being that that advice would become increasingly salient over time and with experience. It means more to me now that it did then, and I appreciate it more now in hindsight. In all honestly, at the time I took it as validation of what I had already learned (i.e. I'm ready for more responsibility, bring it on!) rather than a confirmation of how much more I had to learn and how much better I could be at what I do.

What I think I'm learning about what I will call professional maturation is that -- for me at least -- it is about being less reflexive and more reflective. While one may think this understanding comes naturally, one's reflexes are their strengths honed over time through repetitious positive reinforcement. Reflexes are always at play and feature more prominently in stressful situations. If you're like me and on balance you feel as though your reflexes have served you well and are prone to throwing yourself into high stress files, its even harder to step away from them.

That said, if being reflexive and being reflective were on opposite sides of a continuum than what I've been doing is trying to increase the distance between them. This requires one to understand the nuance that reflexes are there to fall back on but that one should lead with reflection.

In practice this means digging in more, reading more closely, asking more poignant questions, being more methodical, writing notes and lists, verifying that everything has been covered off that you wanted to cover. Some people do this more naturally than others, others (like me) have to work at it more.

Second, my interests are shifting.

I'm still interested in the confluence of people, public policy, and technology but I'm investing my time differently than I used to. I used to spend a lot of my free time trying to learn about what new (shiny!) thing was coming around the corner and how it would eventually impact the business of the public service. This has generated a lot of interesting lines of thought that I've shared over the years on this blog. That said, I'm growing increasingly tired of the meta-narratives around engagement, openness, and innovation that underpin them, so I'm less inclined to feed them with greater reflection. It's not to say that meta-narratives don't have value, only that they no longer pique my intellectual curiosity in the way that they once did. Another aspect of professional maturation seems to be shifting away from simply holding strong views to a model of strong views weakly held.

There's a number of reasons why my interests have shifted, but one of the most predominant is that while these narratives all share the same roots, they've all branched out into their own unique paths. There are now simply too many players and viewpoints to put one's arms around in any meaningful way (See: The Many Challenges of Convening the Policy Innovation and Experimentation Ecosystem). When there were fewer networks, nodes, and information flows it meant that certain voices were amplified and one could reasonably expect to know who most of the key players were. Moreover, information networks have grown in number and been flooded with users, making keeping up simply impossible. Another likely reason is that my work has taken me to the coalface of the innovation discourse/implementation disconnect enough times to temper my enthusiasm for meta-narratives (See: The Innovation Discourse Disconnect). A couple of recent lessons here include the importance of not being a tax on the productivity of others and the perils and intellectual laziness of invoking specters of the powers that be, but I'll save those for another time.

Third, I'm (re)investing my time accordingly.

I'm pursuing a healthier lifestyle (exercising more, eating healthier, drinking less), investing more in interpersonal relationships (being more social IRL, putting my phone away when with others, retreating from social media), and reading more books (paper books, non-fiction books about things I'm interested that aren't work related). All of which takes time and energy away from engaging with and writing about the civil service.

I'm at fewer meetups, I'm writing less, but I'm still coming to work everyday and killing it for Queen and country.

 I'm just doing it a little differently.

Friday, July 21, 2017

On the Canadian Digital Service


by Nick Charney RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharney

Budget 2017 announced the creation of a new Canadian Digital Service (CDS):

Informed by similar initiatives in the U.S. (the U.S. Digital Service/18F) and the United Kingdom (the Government Digital Service), the Government will adopt new ways of serving Canadians. Better use of digital technologies could improve the ways in which businesses can access government services, speed up immigration processing times through better-integrated information, or make it easier for Canadians to access benefits or tax information online.

Earlier this week, their website and social media feeds went live. I checked out their site and (unsurprisingly) there are a lot of friendly and familiar faces on the team. These are good people looking to do good things and I'm looking forward to working with them on my core work (having had a kickoff meeting thereon a few weeks ago).

Now, all that being said the reaction to the CDS is unlikely to all be positive, one only needs to speak to folks working in any of the agencies listed above (e.g. 18F) to know that a couple basic rules of the internet are probably going to apply, haters gonna hate and come at me bro, spring to mind.

Haters are going to hate the CDS

Why? Because it's different, plays by different rules, and gets the fast lane. Or at least those are likely the charges that will be laid against them. I can hear it now, 'of course they could do x, they aren't restrained by y'. That CDS may have all of its T's crossed and I's dotted by the highest echelons of power is unlikely to influence people's perception of the service.

Look at 18F, good people looking to improve the way government delivers its services but the organization has also dealt with watchdogs coming down on their poor financial management in 2016 and their disregard for IT security policies in 2017. It also was flying close enough to the sun to publicly debate whether or not the agency's talent should continue to serve after the change in administration, but on this I'll reserve any further comment.

CDS will likely have to adopt a come at me bro attitude

Why? Because it can't come out swinging (that wouldn't be very collaborative!) but it will need to defend itself when others start taking aim. The reflex here is likely to be "delivery is the strategy" (or in old fashioned terms "putting its money where its mouth is") but that reflex may be insufficient when the criticism isn't aimed at the end but rather the means (i.e. the aforementioned CDS fast lane).

Final thought on CDS

One of the more interesting things to watch with CDS will be how they reconcile their personal social media with their official organizational online presence. As of right now their contacts page lists employee's Government of Canada email address, their personal Twitter account, their personal LinkedIn account, and/or their personal GitHub account (as applicable). To my mind it's the first such conflation of personal and professional online media on a Government of Canada website.

Friday, July 7, 2017

10 tips for building supportive government fellowship programs (and convincing participants to stay)


by Nisa Malli RSS / cpsrenewalFacebook / cpsrenewaltwitter / nisamalli

In the name of innovation and openness, many public sector organizations have committed to porousness and career flexibility, grafting more agile HR mechanisms onto existing systems through short term fellowships, internships, and exchanges. It’s a model used to bring in temporary technical and subject matter expertise, attract mid-career professionals, and to recruit graduates from fields outside of public policy and political science. But as these initiatives expand, we need to think carefully about how to design these programs in order to support participants and create the conditions for success for their projects. As I wrap up a year in municipal government with the Toronto Urban Fellowship, I’ve been thinking about what makes an effective government fellowship and how we can use these kinds of programs to fill gaps in our recruitment strategies by convincing participants to stay.


  1. Think carefully about the purpose of your program when designing it: What gap in existing HR mechanisms and recruitment are you trying to solve? What is the ideal role of participants and program alumni in your organization? If you want people to stay on after their placements, what combination of experiences will best prepare them for future careers in your organization?
  2. Consider expanding your eligibility requirements beyond your organization's usual constraints. Do you really need participants with graduate degrees or would other training and professional experience suffice? Can you open this program up to other academic fields? Could participants work remotely so that they don’t need to relocate?
  3. Create cohorts so that participants will have peer community no matter where they are placed. If you are air-dropping a brand-new government recruit into a branch or division, they will need connections to other parts of the organization and peers to commiserate and problem-solve with.
  4. Ensure that the placements and projects you offer match the skillsets, experience, and interests of your recruits and your program objectives. Even early career professionals have developed expertise and experience in specific fields. Boring, frustrating, or assigning your participants to known bad managers increases the likelihood of mid-program dropouts.
  5. Build an onboarding and training program. What do recruits need to know about your organization before starting their placement? What training can you provide them in advance and during the program that will make their immersion in government easier? Remember that if your participants come from diverse backgrounds they may not all need the same training modules; an urban planner doesn’t need City Council 101; a policy analyst doesn’t need to learn how to write a briefing note.
  6. Give them the tools they need to excel at their jobs. For some roles, this might look like specific software or technology, for others it might just be remote access to email. For everyone, quick access to health and dental insurance, vacation days, and sick days can go a long way towards preventing burnout and recruiting the best from other sectors. New employees, especially ones in short rotations, will face challenges getting support from corporate functions like HR and IT. Clear some of the red tape cobwebs away for them in advance if you can to make sure they don’t waste the first week or two just trying to get an ID badge and a computer login.
  7. Pay them at a level appropriate to their experience and the level of work expected from them (this might mean jumping some internal HR hoops to give participants higher seniority or pay than other new recruits). Student debt and increasing rental prices are making it harder to accept pay cuts, even to work on worthwhile causes.
  8. If your program has rotational placements, ensure they match the length of the projects. Four months isn’t usually enough time to start and finish anything; consider 6-month, 9-month or 12-month placements.
  9. Develop an exit strategy. Your organization is investing a lot of money in program participants; if you want them to stay, create bridging mechanisms to make it easier for their placement hosts to keep them or give them preferential hiring in open competitions. Maintain their access to internal job postings if they aren’t hired on right away and make sure gaps between postings don’t impact their benefits in their next position.
  10. Document success and failure! Track and report on what past participants worked on and learned and their recommendations for future iterations of the program. Fresh eyes can provide useful perspectives on how your organization operates and the work you do. This might look like failure/impact reports, exit surveys and interviews, a project database, or bringing alumni in to present to next year’s cohort.