Have a chapter about building and leveraging trust through all levels of the org.

[InfoSec812]

In my experience, the most important aspect of adopting openness is trust. "Old School" management and uninitiated people within organizations often have a fear of the unknown. Earning and keeping their trust is the key to adopting openness and expanding it's use throughout the org.

It often starts as a grass-roots movement IMHO. One person and a small group of people start showing how openness can improve efficiency/agility/deliverables, and they build trust with their manager(s). That manager can be helped to evangelize the process and leverage their team's processes and philosophies to other teams and the philosophy spreads. But earning and keeping that trust is key.

Additionally, managers and executives also need to be taught to learn to trust their employees as they earn that trust. Allowing their employees more flexibility as they earn trust gives them the ability to be more efficient and agile once they are trusted.

I'm not sure that I would be able to write the chapter myself, but I would be willing to try.

[semioticrobotic]

I think you're absolutely spot on, @InfoSec812. Were you by chance part of a situation or scenario that demonstrated this? We're looking for illustrative case studies for this book—examples from folks who've tried (and either succeeded or failed).

[InfoSec812]

At my last position we had partial success and ultimate failure. It worked for our team and some adjacent teams but never spread and ultimately failed. Deven

…

On Aug 14, 2017 9:14 AM, "Bryan Behrenshausen" ***@***.***> wrote: I think you're absolutely spot on, @InfoSec812 <https://github.com/infosec812>. Were you by chance part of a situation or scenario that demonstrated this? We're looking for illustrative case studies for this book—examples from folks who've tried (and either succeeded or failed). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGFa7dSgV72viyAeSNEgwn5_dgTKO-nks5sYEgygaJpZM4O2UN4> .

[semioticrobotic]

Stories about failure are welcome, too! The most important facet of the case study is the part that details the lessons you learned about openness at the organizational level.

[InfoSec812]

I'll have a look at some of the other Open Org books and see what I can learn from the format and style of the chapters. Then I will try to gauge the level of effort and my availability. I'll try to let you know one way or another sometime this week. Deven

…

On Mon, Aug 14, 2017 at 9:29 AM, Bryan Behrenshausen < ***@***.***> wrote: Stories about failure are welcome, too! The most important facet of the case study is the part that details the lessons you learned about openness at the organizational level. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGFa4VqHEdrHNdrn23Pr6GKW0KhjzLsks5sYEvOgaJpZM4O2UN4> .

-- Deven Phillips Senior Consulting ENgineer, RED HAT OPEN INNOVATION LABS Red Hat <https://www.redhat.com/> deven.phillips@redhat.com <https://red.ht/sig>

[semioticrobotic]

Sounds great, @InfoSec812. Looking forward to hearing more.

[InfoSec812]

@semioticrobotic What is the timeline to have the chapter submitted as complete?

[semioticrobotic]

Thanks for asking, @InfoSec812. Let me explain the milestones on the project timeline.

• This week we'll observe the "table of contents freeze," which just means that we'll "lock' the list of proposed and incoming submissions to review what we have and identify high-priority gaps that need filling.

• The "content freeze" on October 6 is the date by which completed first drafts must be submitted so editing can begin. Anyone can submit before this deadline (and some will), but this is the final date that rough drafts can be outstanding.

• November 10 is then the "editing freeze," where copy editing ceases and we prepare for book launch and marketing.

[semioticrobotic]

Are you still planning to submit this chapter, @InfoSec812? We're still interested in having it but would need to see a draft very soon so we don't slip too far off the project timeline.

[InfoSec812]

Bryan, I apologize. I should have followed up with you MUCH sooner... Unfortunately, due to current workload I have been unable to even get started on this, though I would have liked to do it. I kept thinking to myself that I would make time soon and put off letting you know. For that, I cannot make any excuses. I wish you the best of luck with the book! Deven

…

On Sat, Oct 21, 2017 at 7:28 AM, Bryan Behrenshausen < ***@***.***> wrote: Are you still planning to submit this chapter, @InfoSec812 <https://github.com/infosec812>? We're still interested in having it but would need to see a draft very soon so we don't slip too far off the project timeline. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGFa1y6rpRE_7UlbYgXbG-o8KtCRme9ks5sudVcgaJpZM4O2UN4> .

-- Deven Phillips Senior Consulting ENgineer, RED HAT OPEN INNOVATION LABS Red Hat <https://www.redhat.com/> deven.phillips@redhat.com <https://red.ht/sig>

[semioticrobotic]

Thanks for letting me know, @InfoSec812. While we're disappointed at not having the chapter, we certainly understand and appreciate your honesty here. Best of luck with your full plate!