Showing posts with label reflections. Show all posts
Showing posts with label reflections. Show all posts

2013-08-29

Co-production: Learning from Lucie Stephens (part 2)

As a follow-up to my last blog post, I wanted to share some more things I learned about co-production by meeting Lucie in person, and having the opportunity to chat with her. (For an intro on co-production, see my previous blog post.)

Lucie, Geraldine Cahill (from SiG at MaRS), Karen (our manager at CIWC), and I meet a few weeks ago after Lucie's session at MaRS. She had a number of great examples on how her organization, nef (new economics foundation), has successfully facilitated programs and co-produced solutions alongside the people who traditional services impacted. It was pretty thrilling to hear about those examples, because it indicates to me that we might be able to play with co-production in Ontario to solve some of our complex problems - like health care, poverty/homelessness, and climate change.

I asked Lucie a few questions, and thought I'd share some of her thoughts on them.

On risk

Q: How do you prepare ministers/people accountable for government programs for the potential bad press if something goes wrong?

A: Put risk in its place. Lucie said that when nef goes in and helps facilitate a co-produced solution to something, they don't ignore that there's always a risk that things might go wrong. Rather, she turns the question of risk on its head by inviting officials to see firsthand the positive impact that co-produced solutions have on the people effected. I guess what she's saying is they effectively give officials stories to tell in case a bad news story emerges.

For example, in one place where people with dementia and mental illnesses were involved in co-producing a new kind of environment for their care, a press story came out saying that the government was making people with mental illness make their own tea, casting a negative light on what was traditionally a service that service providers delivered. In fact, the people at the residence - professionals providing services and the residents, too - found it was empowering and even good for the health of residents to set their own routine and do things like make their own tea. People with dementia, for example, were shown to benefit.

The more stories that officials can witness firsthand, the better they'll get at taking on the perceived risk of co-produced solutions.

On creating the conditions for co-production

Q: Is it fair to say that support for co-production depends on who's in power or who's elected at the time?

A: It helps, but isn't necessary. Lucie said it's definitely easier to develop co-produced solutions when there's top-down leadership and support from officials/commissioners in charge of certain public service files. But where there's a need for it, and passionate practitioners on the ground, co-production will happen.

Lucie says co-production calls for policy-makers to do less in order to create the environment where co-production can thrive at the grassroots. Government should admit to itself that with a lot of these complex problems, it doesn't have all the answers; policy makers need to write public policy as a "discovery tool" - something that can be nimble and change/iterate, as needed.

On government as catalysts of co-production

Q: Do you have any examples where governments or government agencies are using co-production as a new method of service (co-)delivery? Should governments lead the way?

A: No, and not necessarily! This one surprised me... Lucie said that it's not always a great idea for governments to lead these kinds of innovative approaches, reason being because, typically, officials in the government aren't close enough to the ground-level to really sense the passion and ability of the grassroots to affect change.

As well, co-production is very much a method/approach that depends on understanding and being in the local context. Lucie gave many examples where co-production worked in small environments. During her presentation at MaRS, she touched upon this point - she said that one of the challenges co-production faces is seeing how it might work on a bigger scale. There aren't really examples of co-production being used for big public programs, or services that effect masses of people, which governments typically deliver.

Thoughts? Ideas?

Our conversation left my head spinning with ideas... what if government re-defined what it means by service delivery? What if governments scaled down its idea of what its role and impact on people should be? How can government foster an environment, through public policy/law, that encourages co-produced solutions to complex problems?

So many more questions than that... what do you think?

2013-08-22

Co-Production: learning from Lucie Stephens (part 1 of a series of posts)

A few weeks ago, I was invited to MaRS for a talk by Lucie Stephens about co-production. I'd never heard about co-production before, and I'd never heard of nef (new economics foundation) either. So I didn't know what to expect.

I was so inspired by Lucie's talk at MaRS, and I had the opportunity to meet up with her a few days afterwards to ask her some questions. I shared what I learned on our internal blog, and wanted to share them here, too. But first, I wanted to give a bit of an overview of co-production, and then get into what I've learned about it over the past few weeks.

Co-production: a working definition


Our team at CIWC has been exploring design thinking and other methods/processes for solving complex problems. Co-production is a way to design and deliver services for communities, with communities. Here's a bit of background on Lucie's/nef's definition of co-production.

Co-production is about empowering people who have a need for a service/program to co-design it alongside professionals (e.g., from the government), and co-deliver it as well. It's about sharing power, in the truest sense; rather than consulting at people and delivering a program to them, co-production seeks to build solutions alongside the people who need them, and build programs with them.

Six elements of co-production

There are lots of things that might look like co-production, but nef has determined that when co-production is happening, these six elements are always present.

  1. People as assets. nef believes there are three parts to consider in our economy: the environment, the financial markets, and (what's most abundant), people. The traditional sense of economics was based in scarcity; gold is scarce and therefore highly valued, but traditionally, people/human resources aren't valued as highly because they might not be as scarce. nef believes in focusing on people as what they call the core economy, and one of the principles behind it is that people all have something to contribute, and therefore should play an active role in the community's well being.
  2. Building on assets. Another principle behind co-production is building on our abundant assets (people), and finding the opportunities where they might make the best use of their skills. It's about leaving no one's talents behind.
  3. Mutuality. Co-production happens when there is a true partnership occurring between professionals and the end users of something. It's not a partnership in the traditional sense, where professionals (government) are still just consulting at people; rather, there's a true reciprocity of expertise and wisdom shared, and each person brings equal levels of value to the equation.
  4. Networks. Another element inherent in co-production is the ability to transcend boundaries - to work between networks and diverse populations to make sure that where linkages can be made, they are, so that the best outcome/service can be achieved.
  5. Blurring distinctions. This speaks, again, to mutuality, and goes a step further. Where in traditional service delivery models, the professionals develop and deliver services, in co-production, there might be solutions created where users are delivering services, too. There's a blurring of titles or traditional hierarchy in co-production where power is shared more evenly.
  6. Facilitating. Another important thing that happens in co-produced scenarios is that the participants are truly empowered to make decisions for themselves. In co-production, each user that's part of the system has a stake in the outcome, and if something were to go wrong, it's OK - it's a matter of coming back together and working out a solution.
During the MaRS talk, and at the co-production meetup this past Tuesday, Lucie gave several examples of where co-production has worked in the UK, and then took a few questions from the participants. I'll end this blog post here so you can digest some of the fundamentals of co-production.

As well, you can learn more about co-production on nef's website, and download this publication by nef that gives a more detailed overview of this method: Co-production - A manifesto for growing the core economy.

I will get into some examples of how co-production is being used, and some of Lucie's answers to our questions about co-production, in a follow up blog post.

2013-07-08

Guest post - Cristian Contreras reflects on GovJam 2013

I have attended several hackathons in the past but none have been as focused on the big picture as GovJam. For two and half days, a group of public servants, social entrepreneurs, and government aficionados took to designing better public service systems in the hope of creating a better place to live. Thanks to my previous exposure to design thinking, I was familiar with the constructive chaos that characterizes the creative process between teams of relative strangers working on ideas at an embryonic stage. The creative tug-of-war from this multidisciplinary collaboration was as it always is - an incredibly rewarding experience.

The idea of improving the quality of public services by redesigning them to include citizen input was a recurring theme during GovJam. Our team was no exception. We decided to work on designing a revolutionary approach to citizen engagement that gives people an opportunity to shape their community by letting them vote on projects with real tax dollars.

In addition to creating more opportunities to participate, a relationship between education and engagement was also present in many of the projects. I, for one, echo both of these ideas. In my work with Next Parliament, I have learned that there is a very real need for a more participatory democracy, but I have noted that solutions to this need are being held back by lack of widespread political engagement. Often, lack of confidence in the system is cited as the reason for this growing political apathy, but in my opinion this is simply the go-to excuse. The real problem lies in the fact that the wider public needs to be much better informed about various issues affecting their lives.

Next Parliament is my attempt at fixing this problem. I have created a site dedicated to educating Canadians on every issue related to politics. Next Parliament works as a Wikipedia-style website where every entry can be edited by the community. Every issue and community recommendation has an argument in favour, an argument against, a community discussion thread, and links to more information. Visit NextParliament.ca to learn more.

We are privileged to be witness to a Cambrian explosion of innovative Gov2.0 initiatives taking place all around the globe. It can sometimes be easy to lose sight of these new government breakthroughs in the sea of cloud, crowdsourced, mobile, and other social innovations, but we must never lose sight of the fact that this space represents one of the most fundamental transformations of the digital era to date.

2013-06-26

Post-Jam reflections

Thanks to all who were able to attend our post-Jam reflections meeting in the wee hours this morning (ok, 9am isn't exactly "wee" but seriously, who has a meeting at 9am??). With a last-minute venue change due to our home building being shut down (generator/power failure yesterday), I wasn't sure everyone would still be able to attend. Thanks for being so flexible.

You might have noticed a couple of new links on the sidebar of this blog. I've created a post-Jam links section for lessons learned from GovJam Toronto to share with all of you, as well as anybody who might want to attempt a Jam in the future.

As always, if you have anything else to share, or the links above jog some ideas, reply below or email me/connect with me on Twitter. And keep checking this blog every now and then for news and info on what's next for GovJam Toronto. Hope to re-connect with you all soon.

P.S. - why not sooner than later? Come to our meetup tonight!

2013-06-12

Wrap-up: GovJam Toronto 2013

It's been difficult for me to start putting into words all the things I learned and all the things we experienced while organizing and participating in GovJam Toronto. Since we wrapped up with our after-party last Thursday, I've done a lot of catching up on sleep. And now that my brain is somewhat rested, maybe I can articulate a few highlights from the event.

Design Thinking IRL*

d.school's design thinking method
* In Real Life
I think one of the most valuable things that came out of GovJam was putting design thinking into practice. We didn't have a lot of time to teach all the different components of the design thinking method, but we did try to emphasize empathy (and there was a lot of testing and prototyping and ideating going on, even if people didn't realize it). Good service design starts with understanding the user, and teams did a great job designing prototypes around people. Some went out on the street and tested their concepts with potential users; some called people up and brought them to the Jam to provide their feedback/experiences; some used social media like Twitter to ask questions. We organizers also had a roster of Advisors and Judges who were generous with their time and provided feedback to teams as they developed their prototypes. This helped them get a fresh perspective and build even better designs.

Making connections

When we invited people to participate in the Jam, we reached out to both internal and external networks. It was amazing to see all these worlds come together... I founded an inter-governmental network about a year ago, and it was personally gratifying to see some of the people on that network connect with other public servants who they might never have gotten to know otherwise. I'm sure that being stuck in a room with the same people, working on a common, wicked problem over an intense 48 hour period has forged some new professional relationships and opportunities for Jammers!

Event planning, redefined

I've had experience planning events in some way or another ever since I got into corporate communications more than six years ago. But the most different sort of event I'd planned before GovJam was an unconference. The Jam was a whole new thing all together because there's no template or similar process to follow. Planning a Jam requires a little design thinking in itself. Thankfully, I had colleagues who have a design thinking background to help me out. Nisha was instrumental at helping me sort out a lot of the details. Not too long after we decided to plan the Jam, she participated in a Charrette, and both of us participated in Global Service Jam. With this new perspective, we were able to plan an event that brought the best from both worlds.

Fun!!

PlaceBuilder's model prototype
There was a lot of pressure on everybody at GovJam Toronto to not only meet deadlines, but create something amazing. I observed a lot of human emotions at the Jam: frustration and epiphanies, annoyance and happiness, and everything else in between. But I think I can confidently say that everybody who spent time at the Jam had fun. This reinforces, to me, that you can have fun and be incredibly productive at the same time. In fact, I think we need to have more fun in the OPS to really unlock our creative potential.

What's next?

We have a lot of post-Jam feedback-gathering, learning, and reflection to do. And I hear Global Sustainability Jam is coming up in November... In the meantime, I'm sure that people who participated at GovJam will bring design thinking techniques they used at the Jam back into their work. And who knows; maybe we'll see a couple of the prototypes go forward in real life :)

What'd you think?

I hope some of you who joined us at GovJam Toronto have some thoughts to share... anything surprising or unusual about the Jam? Anything interesting or frustrating? Leave a comment below!

Author's note: There will be a more formal feedback mechanism (survey, maybe, and/or meeting) sent out to all participants/facilitators at some point.

2013-06-05

brain... overload...

So... how does everybody feel after two days of the Jam??

A little bit exhausted and a little bit wired? A little bit anxious and a little bit excited? A little bit confused and a little bit inspired?

You're not alone... it's been an intense couple of days, and the #GovJamTO teams are doing great. There have been moments of insecurity and doubt, but I've also see some brilliant ideas come together in prototypes that teams have taken to the streets to gather feedback, test, analyze, and strengthen.

Today, we were fortunate to have a few Advisors in the room to give teams the critical feedback they need to better design their services. I listened in on so many great discussions, and saw each participant play a leadership role to build on others' ideas... lots of talking, but also lots of doing today.

Tomorrow marks the end of GovJam. We've got a panel of Judges scheduled to give some final thoughts and advice to teams after they demonstrate their concepts to the group. But even though we wrap-up the Jam soon, it's not the end of the many connections we've made, and hopefully, it's not the end of the prototypes teams design. I'm hoping some teams continue the conversation on our ideas site and find ways to build their prototypes towards implementation.

Looking forward to see the concepts finalized and demonstrated tomorrow after 3pm... see everybody soon!

P.S. continue updating your concepts on the GovJam.org headquarters site! Check out what the rest of the world is doing, too... so many cool ideas!

2013-03-03

We participated in Global Service Jam this weekend!

Friday, 6pm. We met on the 9th floor of the old Toronto Star building at 1 Yonge street. The weekend began with a chill in the air. But just beyond the elevator doors was the headquarters for Global Service Jam Toronto, which emanated the subdued chatter and warmth of about 20-30 eager designers, students, professionals, and general keeners who want to change the world.

At 6:30, after introductions and getting to know each other, the global headquarters revealed the theme in an entertaining video. This year's theme was simply "grow." Brainstorming around this idea, the team I was on was drawn to the idea of introducing complex or real world problems to children. How can we start growing their minds to start solving the complex problems of tomorrow? And how do you do it in a way that helps them get on the path to their life's passion?

The process

What a rollercoaster ride... at first, our idea was a platform - a shared virtual space for kids and teachers to play with ideas around things they were learning in school. Then we realized we needed a service for Service Design Jam; the platform was great to prototype, but we were thinking too small.

We were inspired by a TED talk by Sugata Mitra, suggested by a girl in the room named Alex. We thought, "Why not introduce self-organized learning environments to the Ontario school boards?" and "What if we delivered it in a pop-up school that shows up randomly around Ontario and disrupts classrooms in the middle of the day to shake up their thinking?"

Evidently, we were now thinking too big. We did a little research by interviewing middle school teachers. I went home Saturday night for dinner with my family - my mom, a veteran, with 43 teaching years, and my brother, a relatively new teacher, currently supplying in a couple of different boards. The response was unanimous: leave teaching to teachers. Stop disrupting our teaching time. It's all been done before. (Just a summary of the barriers - my mom loved the idea, as long as it worked with curriculum objectives and as long as it was voluntary to those special teachers who could help champion and pilot the new way of learning.)

So we regrouped on Sunday, now with less than three hours to work out what, exactly, we were designing. We went back to the beginning, with one twist: our focus was on teachers instead of students. So we centered our service around them - we partner with teachers, develop what's inside the pop-up school with their curriculum objectives and expertise, and introduce design thinking and self-organized learning environments using teachers as facilitators.

Our service: TEaM with Teachers

The latest "T"echnology; safe spaces and inspiring "E"nvironments; support and new "M"ethods for Ontario teachers to help them pass their learning objectives with flying colours.

Why? We believe that by teaming up with teachers to introduce new ways of teaching and learning, we can inspire student’s curiosity re-ignite their sense of discovery, and help students develop a passion for learning and finding their life’s quest.

Tired & Contented

It's been both a very invigorating and exhausting weekend. It's going to take awhile to absorb everything we did, and the unique way we came to our final prototype, and consider whether this idea is something we can move forward in any way in the future.

In any case, I'm looking forward, more than ever, to GovJam Toronto now that I've experienced the process.  If I can do it, with no design background, anybody can. This is gonna be great!