Showing posts with label lego. Show all posts
Showing posts with label lego. Show all posts

Wednesday, February 12, 2014

Millenials, Lego, and the Perimeter of Ignorance

by Kent Aitken RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Kent Aitkentwitter / kentdaitkengovloop / KentAitken

Every time I read an article about Gen Y or Millenials I run it through this litmus test: throughout the text, can you replace "Millenial" with "employee" with no loss of meaning?
 “[Employees] want meaningful work, they want to do things that are making an impact and if they’re not in a good environment where they can do that, they’re always going to be looking for something else"
From this piece, which was - sadly - actually about Millenials.

Of course, there are legitimate and meaningful trends and changes occurring, even about Millenials (I'd give more credence to this idea about changing prioritization between work and family life). But it's worth it to be skeptical, to put ideas in broader context, and to look for what's truly meaningful.

Baby boomers are retiring, or about to. Deloitte has suggested that this wave of retirements has been delayed slightly - by "better than expected health" and "worse than expected wealth" for would-be retirees - but here's the demographic profile of the public service up to 2012, Boomers identified by forward slashes:

Figure 7

Over the next decade, we're going to see a demographic shift in key positions throughout the public service. But the question is: does that matter?

And why?


The Perimeter of Ignorance

Here's my frontrunner idea for why it might. I don't think living in the age of information leads directly to collaboration as a first-order condition. Instead, I see collaboration as a second-order condition of a more fundamental result: being constantly reminded of one's ignorance. Collaboration is a symptom, in this view.

Admittedly, this isn't really new. It's not like there was a period of human history in which our knowledge was static. The idea of heliocentrism, for example, would have been world-shattering, dramatically changing the parameters within which people constructed their beliefs. But it seems as though people throughout much of history always considered that the universe ended where their knowledge did, simply expanding the universe slightly when their knowledge grew.


"It's Like Lego."

I simply think that the recognition - deep-seated, not just logically, on principle - that we don't know everything has taken hold, and reached much further into the bulk of populations. The plural of anecdote is not evidence, but this has been on my mind lately:
  • In the last few weeks I've met two people whose lives' work was connecting people, based on the idea that all the building blocks for building a better society are already there, the question is simply one of assembly. "It's like lego."
  • Lately I've had the opportunity to help colleagues with marketing campaigns, internal strategies, and policy presentations, somewhat awed by the idea that I had something to contribute to any of these.
  • Last week Tariq posted about Planning and Idea Generation in Government, in response to Chelsea's point that even deciding that something is a good idea is a muddy and difficult process.
  • Which led to a conversation about decision-making models. Some very (very) smart people were debating their merits. One view would be that they're a useful heuristic, and I'd add that their existence and popularity is based on a recognition that we'll muck things up simply by throwing neurons at problems. But at the same time they have limits, and over-reliance can lead to sub-optimal results.
Or, this, from Joeri van den Steenhoven from the MaRS Solutions Lab:
"We never have all the knowledge in place. So we have to learn... Mostly, it's about organizing a learning process for the stakeholders and users involved, and trying to find out together how we can bring about successful change."

Strategy in a Gigantic Universe

I didn't intend this when I started writing, but this gets back to the last few weeks of posts: Nick on Blending Public Sentiment, Data Analytics, Design Thinking, and Behavioural Economics, or me on Building Distributed Capacity. These posts could be read as buzzword-heavy, or as reasonable management strategies in a world where solutions are elusive, subjective, and fleeting. As ways to, as Josh McManus suggests:


What do you think? Is increased recognition of our limits a genuine shift? Or am I unfairly assigning importance, or missing longer-term context? Is a more collaborative, tentative approach to solution-generation actually a characteristic of those people who'll be replacing retiring Boomers?

And what would that mean for the public service?

I think it's important to look at possibilities and plausibilities for the public service in the long term. To be perfectly honest, my interest in determining whether or not this idea means anything is partially driven by the conversations that came out of George's leave and Nick's interchange from the public service. It seems staying or exploring opportunities elsewhere is on many people's minds.

That's quite alright. We can go "from Public Service to public service," as George put it. But I'm interested in at least complicating these decisions by pointing to opportunities for positive change in the public service. It seems to be the problem I've fallen in love with.

Friday, March 9, 2012

All I really need to know about Public Policy I learned from Lego

I love Star Wars.

When I was a kid I used to queue up the entire trilogy (yes, the trilogy) empty my vast Lego collection out onto the floor and spend the entire day in the Star Wars universe building things I'd seen on the screen before me.  It shouldn't come as a surprise then that I have passed those interests on to my children, both of whom love Star Wars (although they know 6 movies, animated series and countless video game versions) and Lego.

My son Kohl (4) with our new Lego AT-ST
Last weekend we watched Return of the Jedi then retired to the play room to play with the Lego (yes, I still play with Lego).  I somehow got it stuck in my head that I wanted to build an AT-ST walker. But before I did wanted to gauge the kids (stakeholders) interest in the project; they were obviously on board.  So with their blessing, I built the AT-ST pictured above completely from scratch (no instructions, no sets) in about a week's time.  It's far more complicated than anything I ever built as a child and I am incredibly proud of how it turned out.

That said, what I never anticipated was just how much the experience would teach me about public policy.  Here's what I mean.


Public Policy, like Lego, requires vision

You aren't going to get very far if you don't have vision.  In my case it was fairly easy, as a long time fan I have a good sense of what the end product should look like.  I think this speaks to the value that subject matter experts bring to the public policy discourse.  But even then, I repeatedly went online to look at pictures of AT-ST walkers, I needed to check my assumptions against hard facts.  The same applies to policy analysts who need to consciously check their assumptions against the data available to them.  Moreover, not only did I look at photos of AT-ST's but I purposely sought out photos that exposed different sides of the walker to me or that were done in different medium (sketches, paintings, computer generated graphics, other Lego builds, etc).  Policy makers need a well rounded understanding of their medium and that often requires expanding inputs beyond a small handful of expected sources.

But periodically checking in with photographs for direction also gave me the intelligence I needed regarding my resource pool.  Given what I've already completed and that which I have yet to complete, do I have enough resources at my disposal or did I need to go back for more?


Public Policy, like Lego, requires the right resources

I started by building a small chunk of the AT-ST but soon realized that I didn't have easy access to the pieces I needed to work on it project efficiently.  I have a huge (I mean huge) Lego collection.  My kids have not only the benefit of all the Lego they've been purchased over the years, but also everything I was purchased as a kid as well (thanks mom!).  Rummaging through an enormous bin of pieces can be incredibly time consuming.  After all, I had very specific needs for the project in front me.  I didn't need all the resources at my disposal, only a subset.  So I decided to slowly source the parts I needed before continuing to assemble the walker.  My requirements were fairly simple. Anything that was gray was in with the exception of wheels and really large platforms and priority was to be given to any parts that moved or could be used to make joints or connect angles. 

But I also had to be realistic. I knew that I wasn't going to need every piece of Lego I collected, so I didn't need to go through the entire collection routing out all of they gray pieces, I just needed enough resources to complete the job.  The rest could easily be returned for another project.  Having the right resources was incredibly important; but knowing what resources were in my collection but not yet directly accessible to me (buried pieces) was even more important.  The familiarity with the resource pool meant I knew whether or not my approach - an approach that hinged on a particular type of resource or its abundance within the collection - was plausible or not. For example, smaller pieces are generally the hardest to reach resources because they usually wind up at the bottom of the bin and as such require additional effort to secure.  At one point in the process I even had to build a makeshift scaffold from some small buckets to hold back pieces from collapsing back into the large container in order to reach these exact pieces at the bottom of the bin. Additional work pays dividends when you are certain the resources you hope to uncover actually exist. But sometimes those pieces don't exist, you simply can't find them, or you can't access them without huge cost. That's why you need to be able to pivot your approach, why you need to be flexible. You need to be prepared in the event that the end product may not look exactly like your vision.  Vision is, after all, limited to resources.  Remember that a roadblock often means an improvement, not a detraction of the quality of the end product. 


Public Policy, like Lego, has to stand up to scrutiny

The more complex the undertaking the more fragile it is.  This is especially the case during the initial build when you are unfamiliar with how to best handle your creation with care.  Quite frankly while you may have an idea of where the weak points are you aren't quite sure.  Typically we expect breaks at the joints but tragically, the only way to know for sure is to purposely break that which you have just created. 

So don't be afraid to knock it over, apply pressure, or add some weight.  Make note of where it breaks, then rebuild it, re-test it, and see if it breaks in the same spot again. Repeating this process a couple of times not only shows you its strengths and weaknesses but also teaches you about the act of rebuilding itself; which is to say that it breeds a familiarity and expert understanding that is important.  It's important because it will frame your reaction.  It will determine how you reinforce the joints, what pieces you swap out or in or lead to a complete redesign that circumvents a problem that cannot otherwise be fixed.

In the end you want to build something that can support its own weight.  A task that is made more difficult when you have moving parts.  My walker for example has a moving head that moves both horizontally and vertically. Moving parts are complicated, awesome, but complicated.  The more of them you have the more additional support you need, but the support you add should create a sense of robustness without undermining mission.  In my experience the best support mechanism in this regard is transparency. 

For example, the mobility of the head combined with its weight meant that I needed additional pieces to hold it in place. If I used coloured pieces it wouldn't be a walker anymore but something else entirely.  Using transparent bricks maintains the mission while offering critical support to the most complex piece of the undertaking. There is greater willingness to accept additional support when that support mechanism is transparent and minimally invasive; you are also quick to accept it when you compare it directly to less palatable (or more intrusive) alternatives. 


Public Policy, like Lego, should be a creative endeavour

Having fun is an inherent part of crafting.  It's incredibly important, so don't be afraid use your imagination and be creative.  If something doesn't work out right away, don't panic and don't abandon ship, its just bricks, there is nothing that can't be fixed, altered or tweaked, and there is always a work around. You just need to be willing to look for it. 


Public Policy, like Lego, could be exciting to next generation

After I finally completed the project, the look on my kids faces was incredible.  They watched me craft something amazing yet tangible; so much in fact, that it left them wanting more.

Shouldn't our governments strive for the same thing?





Originally published by Nick Charney at cpsrenewal.ca
subscribe/connect
RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharneygovloop / nickcharneyGoogle+ / nickcharney