I was sorry not to be able to attend as I'm pretty excited about this. @Jen very happy to test your tool and try to break it.
I mentioned to Jen in prep for our meeting with Jim that an graphic/visual representation of the model would be worth exploring. Perhaps as a a kind of "quick and dirty is always fun in FOSS" stopgap. Could be a cool addition to any sort of a workbook (love that idea). I'm imagining something simple like this http://moon.greenpeace.org/workshopinabox/exercises/images/graph-3buckets.png but can imagine summarizing pieces and parts of the maturity model so it's not overwhelming. On another note, I thought it might be interesting to have a discussion about how this pairs with the ODF. Maybe a topic for the future, but I was just thinking about how the resources we contribute to integrate more seamlessly. Did I already say I <3 the workbook/manual idea? --from laura on a mobile device, likely typed in haste. On Jul 20, 2017 18:45, "Sam Knuth" <sfolk...@redhat.com> wrote: Thanks for the notes. I'm happy to see this out in the world and look forward to Jen's work and adoption stories -Sam On Thu, Jul 20, 2017 at 10:41 AM, Bryan Behrenshausen <bbehr...@redhat.com> wrote: > Hi all, > > This morning, a few of the ambassadors met online to celebrate the > release of the maturity model and discuss next steps. Several points > emerged, and I wanted to make sure the rest of the community received > some insight into them. Without further ado: > > * Jen Kelchner and the experts at LDR21 are already hard at work > building an assessment tool that people/groups can use to plot their > positions on the model and generate plans for becoming more open. Jen > says that (if all goes well) the model will be available in a few weeks, > and she's asked for ambassadors' help with initial testing. She'll > follow up with additional details as they become available. > > * Ron stressed the need to begin using the model in very small, focused > settings to evaluate particular projects and initiatives—perhaps by > developing a small "score card" that teams can use during project > debrief to initiate a discussion about the way openness did (or did not) > factor into the project's outcome. > > * We discussed the need to begin developing a bank of case studies, > articles about organizations who exemplify various aspects of the > maturity model (and, by extension, embody the characteristics of the > Open Organization Definition). I (Bryan) mentioned that these would be > very useful for another proposed volume in the Open Organization book > series: a "workbook" or "how-to" manual that lays out the maturity model > and then presents readers with specific activities/case studies they can > explore to actually achieve the benefits of becoming more open. > > Anyone at the meeting should chime in with details that I've missed! > > Congratulations again, everyone, on a great release. As with any open > project, it's open to continual revision and modification—so let's not > be shy about asking others for feedback as we embark on v1.1, 1.2, 1.3, > and beyond... > > Bryan > > _______________________________________________ > Openorg-list mailing list > Openorg-list@redhat.com > https://www.redhat.com/mailman/listinfo/openorg-list > -- Sam Knuth Director, Customer Content Services Red Hat, Inc Mobile: +1 612-840-1785 <+1%20612-840-1785> _______________________________________________ Openorg-list mailing list Openorg-list@redhat.com https://www.redhat.com/mailman/listinfo/openorg-list
_______________________________________________ Openorg-list mailing list Openorg-list@redhat.com https://www.redhat.com/mailman/listinfo/openorg-list
