Re: Moving to written proposals for projects over presentations
toggle quoted message Show quoted text
To add a bit of color on the Falco Sandbox proposal and presentation.
I started with the proposal document first because I felt that the problem we were trying to solve may not necessarily be well understood if we only did a presentation. I also wanted to have any of the questions/requirements for a Sandbox project answered ahead of the presentation. That way any TOC members could be confident that we met the requirements and we weren't wasting anyone's time. If questions or confusion came up, I had the proposal document to refer people back to. Lastly, I wanted people to clearly understand where we were fitting in the Cloud Native ecosystem, and the value we were providing. I felt like that would be harder to get across in the presentation. Personally, I felt that these were the barriers that we needed to overcome to get the TOC sponsors required.
From the proposal I built the presentation, which felt like it naturally came out of the proposal. Each section became a slide (or two), and we had a much more clear story to tell on the slides as it was right there in the document as well. The proposal document also gave us a much more clear story to tell when we presented to the TOC.
I'm not sure if most projects present first then write the proposal, but if not, it might be useful to flip it around.
On Tue, Oct 2, 2018 at 12:10 PM Chris Aniszczyk <caniszczyk@...> wrote: