On Fri, Nov 4, 2016 at 6:55 AM, Allison Matlack <[email protected]> wrote:
> Thanks for all of the fantastic write-ups! > > I've been thinking a lot about our discussions and about how we begin to > define "open" and what kind of business impact "open" practices have. And > I've decided to start with the case study closest to home: my own team. > > I mentioned to Laura and Chad in passing that I'm not sure we can say all > of Red Hat is operating as an open org as described in Jim's book -- it > seems to depend on the BU, department, and (most importantly) the managers > you're working for. We are just a little group in the grand scheme of > things, buried way down in the hierarchy on paper (CEO --> Products & > Technologies --> Customer Experience & Engagement --> Customer Platform), > ~150 people currently, distributed across the globe. But there's something > that makes us different, even from other groups in Customer Experience & > Engagement. > > So I asked the question yesterday -- "What makes us different? -- and so > far I've gotten three fantastic responses, each mentioning something > different. The best one so far: *We legitimately care about each other.* * > * Which is not to say that other groups in Red Hat don't care about each other, but that genuine care for teammates on a personal level could be one of the knobs on the "open org" dial. -A > > Bryan, I'll probably need some assistance parsing through whatever > responses I get, along with my own thoughts...whenever I can start making > some sense out of them. ;-) > > Looking forward to our next meeting already!! > > Thanks, > -Allison > > > On Fri, Nov 4, 2016 at 5:19 AM, Laura Hilliger <[email protected]> > wrote: > >> Hi! >> >> Thanks for parsing all of that Bryan! And for hosting as well. I just >> published this post >> <http://www.laurahilliger.com/leadership/greenpeace-the-open-organization-and-all-things-open-2016/> >> (which >> includes a brief reflection from the whole week at ATO). I also put the >> photos I took of our postits here: >> >> https://goo.gl/photos/w8Jj6VNXB7RS3vAi9 >> >> We can use the post its to extend the work plan. There’s some nuggets in >> there that may be valuable to hold on to :) >> >> —laura >> >> Laura Hilliger >> Zythepsary <[email protected]> >> >> *(part of the We Are Open Co-op)*@epilepticrabbit >> <http://twitter.com/#!/epilepticrabbit> >> >> On Nov 3, 2016, at 7:10 PM, Bryan Behrenshausen <[email protected]> >> wrote: >> >> On 11/03/2016 11:13 AM, Chad Whitacre wrote: >> >> Thanks for hosting us, and for the comprehensive "small" write-up! I'm >> excited to start focusing on practical case studies in my next column >> <https://github.com/whit537/openorg/issues/7>. >> >> >> This sounds great; thanks, Chad. >> >> By the way: I condensed some of the more "actionable" bits of the report >> (specifically the items we said we'd be interested in tackling together) >> into a kind of "worksheet" we can use to prioritize the tasks. Just a >> start, and everyone should feel free to reorganize and/or reconfigure it >> into something more useful. We'll talk about this at the ambassadors >> meeting next week. >> >> All ambassadors should have access here: >> >> https://docs.google.com/a/redhat.com/document/d/1mtxW6XFO9du >> -cLOtiETrx8L4nG12fV8XEwrTdvVygLY/edit?usp=sharing >> >> _______________________________________________ >> Openorg-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/openorg-list >> >> >> >> _______________________________________________ >> Openorg-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/openorg-list >> >> >
_______________________________________________ Openorg-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/openorg-list
